Build a form
A form is the set of questions someone answers after scanning a tag: what's wrong, how urgent it is, a photo. Your team can also use forms for inspections and delivery checks.
Only admins can build forms.
Create a form
-
Open Settings, then Forms, and click New form. Give it a name.
-
On the Build tab, add your questions.
-
Check the Settings tab (more below).
-
Click Publish.
A form needs at least one question before it can be published.
Question types
| Type | Good for |
|---|---|
| Short Text | "What's wrong?" |
| Dropdown, Multiselect, Yes / No | Fixed answers you want to sort or act on |
| Linear Scale | "How urgent is it, 1 to 5?" |
| Photo | A picture of the problem. Staff love this one. |
| Email, Phone Number | So you can reply to whoever reported it |
| Number, Date, Time, Address | What they say |
| File, Signature | Inspections and handovers |
| Statement, New page, Divider | Instructions and layout |
Keep report forms short. Three or four questions get answered. Twelve get abandoned.
Useful settings
| Setting | Does |
|---|---|
| Confirmation message | What staff see after they submit |
| Ticket title | What the ticket is called. It can include the form's answers. |
| Ask which site | Asks which facility before the questions start |
| Require a PIN | Only people with the PIN can fill it in |
| Require sign-in | For forms only your own team should use |
| Save and resume | Long forms can be finished later or on another device |
A form needs a menu
Staff reach a form through a menu. A report only becomes a ticket when the form is opened from a menu option, which is what happens when someone scans a tag.
Changing a published form
Settings, then Versions, keeps every published version. Revert puts an old version back, but it also turns the form back into a draft. A draft form disappears from your menus until you publish it again.
Retiring a form
A form that has been used can't be deleted. Choose Archive from its menu on the Forms page instead. Its old reports stay where they are.