Best Practices when Using Repeatable Groups

Repeatable groups allow users to capture multiple records within a single form submission. Common use cases include :

• Labor entries
• Parts used
• Equipment inspections
• Safety observations
• Customer signatures or contacts

When designed thoughtfully, repeatable groups improve data consistency, streamline reporting and create a more efficient user experience

Keep Groups Focused

Each repeatable group should represent a single type of data. For example, a Labor Entries group might include:

• Technician
• Hours Worked
• Work Performed

Avoid combining unrelated data types, such as labor, parts, and notes into one group. Focused groups are easier to maintain and report on.

Limit the Number of Fields

Keep each repeatable row as simple and efficient as possible. Including too many fields can:

• Reduce performance on mobile devices
• Increase sync times
• Make forms harder to use in the field

Include only the fields users truly need for each entry.

Configure Required Fields Carefully

Require only the fields that are truly essential. Excessive required fields within repeatable groups can create frustration, particularly on mobile devices where users may accidentally add extra rows. A streamlined experience helps users complete forms more quickly and accurately.

Test with Realistic Data Volumes

Always test forms using real-world scenarios, such as:

• 50 labor entries
• 100 inspection items
• Multiple large photo attachments

Testing helps identify performance issues, sync delays, and layout problems before deployment.

 Following these best practices helps improve form performance, simplify reporting, and enhance the overall user experience. Well-designed Repeatable Groups make data collection more efficient while ensuring information remains organized and consistent.