Forms
Forms are configurable checklists and data-capture sheets that technicians or staff complete as part of a job. A form might be a safety inspection, a completion certificate, a service report, or a compliance checklist. This page explains how forms work, how they're built, and how they tie into the job workflow.
What Is a Form?
A Form in ServCraft is a structured document with fields that someone fills in — capturing information specific to a job or service. Unlike fixed job fields (description, job type, status), forms are fully customisable: each business defines what fields appear, in what order, with what validation.
Common uses:
- Safety checklists — technician confirms pre-work safety steps
- Completion certificates — signed confirmation that work was done
- Inspection reports — structured capture of findings during an assessment
- Compliance forms — regulatory requirements (e.g., gas safety, electrical compliance)
- Customer sign-off — captures customer signature on completion
A form is linked either to jobs (completed as part of job work) or to a customer (kept against the customer record, e.g. a site induction or annually renewed certificate). That choice is made when the form is created and cannot be changed afterwards.
Documents in This Section
| Document | What It Covers |
|---|---|
| Building & Managing Forms | Admin-facing: the form builder, publish, versions and revert, single- vs multi-use, expiry, linking to job types |
| Completing Forms on Jobs | Technician/staff-facing: filling in forms, statuses, PDF output, expiry & renewal, the mobile app experience |
How Forms Fit Into the Job Workflow
- A form is defined in Settings (name, fields, structure) and published
- The form is linked to one or more Job Types — so jobs of those types require this form
- On a job of that type, the form is available from the Forms area of the job page
- A technician or staff member fills in the form
- The form is marked Completed
- Completion is enforced by ticking Complete Forms on a job status (Settings → Jobs → Statuses). A job cannot move to that status until every form linked to its job type is completed and not expired
Forms can also be multi-use — meaning the same form can be filled in multiple times on the same job (e.g., if a technician services multiple units per visit), up to 20 times per job by default.
Form Statuses
| Status | What it means |
|---|---|
| None | Form not yet started |
| Draft | Started but not yet submitted |
| Completed | Filled in and submitted |
Field Types
When building a form, you choose from these field types:
| Field Type | What it captures |
|---|---|
| Checkbox | A tick box |
| Text | Single-line text input |
| Text Box | Multi-line text (longer responses, notes) |
| Number | Numeric values |
| Yes or No | Checkbox — binary response |
| Date | Date picker |
| Date and Time | Date + time picker |
| Select | Dropdown — one option from a list |
| Multiselect | Multiple options from a list |
| Table | A grid of values — structured tabular data |
| Image | Photo capture or image upload |
| Signature | Digital signature field |
| Informational Text | Display-only text (headings, instructions, notes) — not filled in |
| Informational Image | Display-only image (diagrams, logos) |
Building a Form
Settings → Templates → Forms → Create Form
Form definition settings
| Setting | What it controls |
|---|---|
| Name | What the form is called |
| Description | Internal description of the form's purpose |
| Link form to | Job or Customer. Required, starts on Job, and permanent once the form is created |
| Job types | For job forms: which job types this form applies to |
| Single use only | Unchecked (the default) means multi-use: up to 20 completions per job. Multi-use is permanent — it cannot be changed back to single-use once saved |
| Form Expires | For customer-linked forms only: whether a completed form goes out of date after a set timespan (defaults to one week when switched on; configurable) |
Building the fields
You:
- Add fields using the Add Field action
- Choose the field type
- Set the field label (every field must have one) and whether it's required
- Group and order fields, optionally into sections
- For Select/Multiselect fields, configure the available options
Publishing and versions
A form definition is Draft until you Publish it — only Published forms can be used. Changing the fields of a published form creates a new version of it: the published version (and everything completed against it) stays intact, and your changes take effect when the new version is published. The forms list shows each definition's status and version number. A Version history tab on the form lists every version, and Revert to published throws away an unpublished draft and keeps the published version in use.
Linking Forms to Job Types
The link can be made from either side:
- On the form definition — the Job types selector lists the job types this form applies to
- On the job type (in Job Settings) — an Add Form action links forms to the type
The job type also has an "Only Allow Linked Forms" option: when ticked, only the linked forms can be added to jobs of that type; when unticked, staff can additionally add any other active published job form to the job.
You can archive a form without deleting it (historical completions are preserved). Restore brings it back.
Forms on the Job Page
When forms are available for a job, Actions → Forms on the job page opens the Allocated Forms dialog. On a customer, customer-linked forms are under Options → Forms. In the mobile app, the job card has a Forms button. Staff or technicians:
- Open (or Add) the form. On the web app, you choose between the original editor and the beta form editor each time (the beta editor is available to every user and is still in beta)
- Fill in each field — saving keeps it as an editable Draft
- Submit the form (status changes to Completed; it becomes read-only unless it is a customer-linked form that never expires)
Completion is enforced on job statuses. A status with Complete Forms ticked cannot be set on a job until every form linked to its job type is completed and not expired, on the web app and the mobile app alike. Ticking it on the status that closes the job stops a job from closing with unfinished forms. A task checklist step of type Complete Forms is a second route: it completes itself once the forms are done, and holds up statuses that have Complete Tasks ticked.
Multiple completions
For Multi-Use forms, each completion is a separate copy with its own status — useful for forms where multiple pieces of equipment are checked on the same job. Up to 20 copies per job are allowed by default (configurable per business). Another copy is started from an existing one with Duplicate in the job's Allocated Forms dialog on the web app, or Re-Use Form in a form's three-dot menu on the mobile app. See Completing Forms on Jobs.
Form PDF Output
Completed forms can be generated as PDF documents. The form PDF:
- Captures all field values as filled in
- Lists the customer, the form's status, the date and the employee. On a completed form the employee is the person who completed it
- Can be attached to emails sent to the customer (e.g., as a completion certificate)
- Can be downloaded from the job page
Form Expiry
If a form (customer-linked) has an expiry timespan set, a completed form becomes out of date once that much time has passed since it was completed — the expiry clock starts at completion. This is useful for:
- Compliance certificates that need renewal on a schedule
- Inductions or safety checks that must be redone after a set period
Expired completions show Expired as their status, and a Renew action inside the open form (Renew Form in the mobile app's form options) starts a fresh copy of the form to fill in — the expired completion stays on record.
Permissions
Completing forms on jobs goes with job access — staff who can work on a job can access its forms. Managing form definitions (Settings → Templates → Forms) requires the Master Office Admin permission.
Form Settings
Settings → Templates → Forms
| Setting | What it does |
|---|---|
| Forms list | View all form definitions with status (Draft, Published or Discarded), reusable flag, and version — plus a "Show disabled items" filter |
| Create form | Build a new form definition |
| Edit form | Modify a draft freely; changing the fields of a published form creates a new version |
| Version history | See every version of a form, preview one, or revert an unpublished draft to the published version |
| Archive/Restore | Take a form out of use without deleting it, and bring it back later. Forms whose structure is locked by an integration cannot be archived while active |
Common Scenarios
"A technician can't close a job — it says a form needs to be completed"
- Open the job's Forms area
- The status they are moving to has Complete Forms ticked, so every form linked to the job type must be completed and not expired
- Fill in and submit the outstanding forms, and renew any expired one. The status can then move
- If the form shouldn't be required for this job type, an admin can remove the form from that job type's linked forms, or untick Complete Forms on the status
"We want a gas safety certificate technicians fill in on every gas service job"
- Settings → Templates → Forms → Create a new form with the certificate fields (text fields for readings, yes/no for compliance checks, signature field for technician sign-off, signature for customer)
- Settings → Jobs → Job Types → open the "Gas Service" job type → Add Form and pick the certificate
- Settings → Jobs → Statuses → open the status that closes the job → tick Complete Forms. Gas service jobs can then not be closed until the certificate is completed. With Advanced workflows, pick the job type's workflow in the Workflow dropdown first
"A customer wants a copy of their completion certificate"
Generate the form PDF from the job page. Attach it to an email and send via the Communications module, or download and email directly.
"We published a form and now need to change its fields"
Edit the published form — your changes become a new draft version, which you publish when ready. Everything completed against the old version is preserved exactly as it was captured. (Some forms managed by an external integration have a fully locked structure and can't be edited at all.)
"We need the same checklist filled in for each unit on a multi-unit service job"
Leave the form multi-use (the default — don't tick "Single use only"). The technician submits the form once per unit — each submission is stored separately, up to 20 per job by default.
Related Topics
- Building & Managing Forms
- Completing Forms on Jobs
- Job Settings
- Creating a Job
- Technician Guide — Mobile App
- Document Settings