Building & Managing Forms
In one sentence: Admins design forms in Settings → Templates → Forms — choosing whether a form belongs to jobs or to customers, which job types it applies to, its field layout, and whether it can be completed more than once — and then publish it to make it usable.
What Is This?
The admin side of Forms: creating and maintaining the form definitions (templates) that technicians and staff later fill in. This covers the form builder, the publish/version model, expiry, and single- vs multi-use. For the filling-in side, see Completing Forms on Jobs.
Why Does This Matter?
Forms are how businesses capture structured, repeatable information — safety checklists, gas certificates, inspection reports — without developers. A well-built form makes technicians faster and output consistent; a badly planned one is painful to change later, because published forms are versioned to protect data already captured on real jobs.
How It Works
Where forms are managed
Settings → Templates → Forms (visible to Master Office Admin users). The list shows every form definition with its Name, Form Rule, Status (Draft, Published or Discarded), whether it's Reusable, its Version number, and created/modified details. A "Show disabled items" filter reveals archived forms.
Creating a form
When creating a form you set:
| Setting | What it controls |
|---|---|
| Name | What the form is called (required) |
| Description | What the form is for |
| Link form to | Job or Customer — whether this form is completed on jobs or kept against a customer. It is required, and new forms start on Job. This choice is permanent — it cannot be changed after the form is created. An older form that was saved without a link shows Job and is saved as a job form the next time it is saved. |
| Job types | For job forms: which job types this form applies to (multi-select) |
| Single use only | Unchecked (the default) means the form is multi-use: it can be completed up to 20 times per job. Checked means one completion only. |
| Form Expires | For customer-linked forms only: whether a completed form goes stale after a set time (default one week; the timespan is configurable — e.g. in days or months) |
Multi-use is a one-way door. New forms default to multi-use. A single-use form can later be upgraded to multi-use, but a multi-use form can never be changed back to single-use.
Building the fields
In the builder you Add Field rows, each with a description (label), a type, and an optional required flag. Fields can be grouped into sections and reordered. Every field must have a description — the form won't save with blank field labels.
Available field types:
| Field Type | What it captures |
|---|---|
| Checkbox | A tick box |
| Text | Single-line text |
| Text Box | Multi-line text |
| Number | Numeric values |
| Yes or No | A yes/no answer |
| Date | Date picker |
| Date and Time | Date + time picker |
| Select | One option from a configured list |
| Multiselect | Multiple options from a configured list |
| Table | A grid of columns, each with its own type |
| Image | Photo capture / image upload |
| Signature | A drawn signature. Each Signature field picks a Signature Template, which sets whether a customer or an employee signs, the terms they accept, and the QR code, re-sign and hide options. See Signature Templates |
| Informational Text | Display-only text (instructions, headings) — not filled in |
| Informational Image | Display-only image (diagrams, logos) |
Draft → Publish → Versions
A form definition is Draft, Published or Discarded. The form page has a Details tab and a Version history tab, with Save, Publish, a Preview (eye) button and a More actions menu at the top.
- Save keeps the form as a draft — you can keep editing freely. A draft cannot be used on jobs.
- Publish asks "Publish form?" and, once you confirm, makes the form available for jobs and customers. Publishing requires at least one field, and the button is greyed out once the version is already published.
- Changing the fields of a published form creates a new version. The published version stays intact (protecting everything already captured against it), and your changes become the next version number, which you publish when ready. Changes that leave the fields alone, such as the description, save onto the version you are editing. The Version column on the form list shows where each definition stands.
This versioning is why you never need to worry about breaking historical data: completed forms stay attached to the version they were filled in against.
Version history and Revert
The Version history tab lists every version of the form with its version number, when it was last edited, who updated it and its status. The version in use carries a tick in the Current column. The eye button previews any version as a PDF.
If you start changing a published form and decide against it, choose Revert to published from the More actions menu, or the revert button on the newest draft in Version history. After you confirm "Revert to published version?", the unpublished changes are thrown away and the published version stays in use. This cannot be undone. The thrown-away draft stays in Version history with the status Discarded. Revert only works on a draft of a form that has been published at least once, and the menu hides it while the form is archived.
Linking forms to job types
There are two places to make the link, and both work:
- On the form definition — the Job types multi-select
- On the job type (Settings → Jobs → job type editor) — an Add Form action, plus an "Only Allow Linked Forms" checkbox
"Only Allow Linked Forms" controls what happens on the job page: when ticked, only the forms linked to the job's type can be added to a job of that type; when unticked, staff can also add any other active published job form.
Archiving
Forms can be archived rather than deleted. In the More actions menu, Archive asks "Archive this form?" and, once confirmed, stops the form being added to new jobs. Jobs that already have the form keep it. An archived form can be shown with "Show disabled items" and brought back with Restore.
Forms with a locked structure
Some forms are managed by an integration. Their structure is locked, so you cannot rename them, change single use, edit their fields or archive them while they are active. The Name box shows "This form's structure is locked, so its name cannot be changed."
Filling in forms: the original editor and the beta editor
The beta form editor is available to every user and is still in beta. The app asks which editor to use when someone opens or starts a form on a job or customer. Use original opens the editor that has always been there. Use beta editor opens the Beta form editor, a side panel with a section menu whose dots show how far each section is filled in, collapsible sections that open one at a time, checks on each field as you fill it in, and a draft that is saved on your device automatically as you type. If the browser closes before you save, the next time you open the form it asks "Resume where you left off?" and you can Restore or Discard the changes. Closing the panel with unsaved changes asks "Discard changes?". Both editors stay available and the question appears each time a form is opened. See Completing Forms on Jobs.
Key Terms
| Term | What It Means |
|---|---|
| Form definition | The template an admin builds — fields, sections, rules |
| Form Rule / "Link form to" | Whether the form belongs to Jobs or to Customers — fixed at creation |
| Draft | An unpublished definition (or unpublished new version) — editable, not yet usable |
| Published | A live version that can be completed on jobs or customers |
| Discarded | A draft that was thrown away with Revert to published; it stays in Version history |
| Archived | A form taken out of use without deleting it; Restore brings it back |
| Version | Each published edit of a form gets the next version number; history stays on old versions |
| Multi-use | Completable up to 20 times per job (the default); permanent once saved |
| Only Allow Linked Forms | Job type setting restricting jobs of that type to their linked forms only |
Common Scenarios
Scenario: "We published a form and now need to add a field"
What the customer sees: The form builder open on a published form. What happens in the system: Editing it creates a new draft version; publishing that version makes it the one used on new completions. Old completions keep their original version's layout. What staff should know: Nothing captured is ever lost by editing — but the new field only appears on completions started after the new version is published.
Scenario: "We started editing a published form and want to undo it"
What the customer sees: A published form that now shows Draft after a field was changed. What happens in the system: The changes sit in a new draft version. The published version is still the one used on jobs. What staff should know: Choose Revert to published in the More actions menu. The draft is discarded, the published version stays current, and the discarded draft remains visible in Version history.
Scenario: "We picked Customer but this should have been a job form"
What the customer sees: The "Link form to" selector is greyed out when editing. What happens in the system: The job/customer choice is permanent per form definition. What staff should know: Create a new form with the correct link and archive the old one.
Scenario: "Technicians are adding the wrong forms to jobs"
What the customer sees: Random forms appearing on jobs. What happens in the system: With "Only Allow Linked Forms" off, any active published job form can be added to any job. What staff should know: Tick "Only Allow Linked Forms" on the job type to restrict jobs of that type to the forms actually linked to it.
Scenario: "We need a compliance certificate that goes stale after a year"
What the customer sees: A customer-linked certificate form. What happens in the system: Create the form linked to Customer, switch on Form Expires, and set the expiration to 12 months. Once a completion is that old it's flagged as expired and can be renewed. What staff should know: The expiry setting only appears for customer-linked forms.
Important Rules & Gotchas
- Publish is what makes a form usable — a saved draft doesn't appear on jobs. The Publish button is disabled until the form has at least one field, and while the form is archived.
- The job/customer link is permanent per form and is always required; multi-use is also permanent once saved.
- Multi-use forms allow up to 20 completions per job (the default limit; configurable per business).
- Every field needs a label — the save is rejected if any field description is blank.
- Expiry applies to customer-linked forms and defaults to one week when first switched on — set the real timespan before publishing.
- Forms settings require Master Office Admin permission.