This article walks you through building a form from start to finish: setting it up, choosing who can use it, adding fields and sections, and saving it. Where a topic has more detail, we link to a separate article.
Set up your new form
Click + New Checklist button
Select Checklist settings at the top of the form builder
The settings for your form open in the panel on the right.
Edit your form settings
In the right-hand panel, enter a Checklist name. This is required.
Optional: add a Description so people know what the form is for.
Optional: change the PDF name.
If you leave it as it is, the PDF uses the checklist name.
Select the pencil icon to change it.
Optional: add Tags.
Tags are used to group and filter checklists.
Choose who can fill in the form
Go to Visible to.
New forms start with Everyone.
To limit the form to certain people, remove Everyone by selecting the x.
Search for and add the cohorts who should see the form.
You can add more than one.
To remove one, select the x next to it.
Choosing who can view submissions
Go to Restricted to.
Add the cohorts who can read finished submissions, for example an "HR only" cohort.
The person who filled in the form can always see their own submission.
Build your Form
A form is made up of sections, and each section holds a set of fields. Fields are the questions and content on your form, such as a photo, a signature or a date. Sections group related fields together, for example Key information, Checks and Sign-off.
Add a new section
Drag a field from the Fields panel and drop it below the last section.
A new section is created automatically, with that field in it.
Add more fields to the new section in the same way.
Set up each section
In the Fields panel on the left, choose a field and drag it onto the form builder.
Your first field creates your first section.
Select the section heading. Its settings open in the right-hand panel.
Enter a Label. This is the section title people see, for example "Key Information".
Turn on Not applicable if people should be able to mark the whole section as not relevant to their job.
They can then skip the section without answering its fields.
Turn on Repeatable if people may need to fill in the section more than once.
The whole section repeats, so people can add another copy of it as many times as they need.
For example, put a Signature field in a repeatable section to collect signatures from everyone attending a briefing.
Optional: enter a Passing score if you want the section marked as passed or failed.
This is the number of points the section must reach, based on the scores you give to answers. It is not a percentage.
Leave it empty if the section doesn't need a pass mark.
See "Scoring and pass marks on forms".
Optional: add Rules to show, lock or require the whole section depending on other answers.
See "Use rules to show, enable or require fields".
Set up fields
Select the field. In the settings panel on the right, give it a Label.
This is the question, name or instruction people see, for example "Supervisor signature".
Turn on Required if the field must be answered / mandatory.
Fill in the other settings for that field type, such as the date format or the number of photos allowed.
Optional: add rules to show, lock or require the field depending on other answers.
See "Use rules to show, enable or require fields".
Keep dragging fields into the section until it has everything you need.
To change the order, drag a field by its handle (⋮⋮) or use the up and down arrows on the field.
Check and save your form
Select Preview to see the form as the person filling it in will see it.
Select Close to go back to the builder.
Select Create to save your form.
Your form is now saved and ready to use.
Use Case
Super users and form owners setting up a new form.
💡 Tips
Plan your sections before you start. For example: Key information, Checks, Photos, Sign-off.
Give every field and section a clear label before adding rules. Rules list fields by label, so "Untitled" fields are hard to tell apart.
If you use the same group of fields in lots of forms, save it as a fragment. See "Save and reuse fields with fragments".