Overview
Form Builder lets authors assemble sections, questions, checklists, and other components, then move a form from DRAFT to PUBLISHED so assigned users can run it. This journey follows Part 1 of the Form Builder guide: reach the builder for a module, lay out the structure, preview, save, and publish.
Who can use this
Role | In this flow |
Content administrators | Own the catalogue of forms for a feature set. |
Form builders | Drag components, configure properties, and publish. |
Module administrators | Align forms with company, location, and job role assignments. |
You need access on Module Settings for Settings → Module Configuration, plus the relevant feature set (for example Verifications or Inspections) and an active tenant. Forms are module-specific; only published forms appear to end users.
Before you begin
From Settings, open Module Configuration, then select the feature set whose forms you maintain.
Confirm you can open Form Builder for an existing form or Create New Form when starting fresh.
Published Checklist Library items are the only checklists you can embed; prepare checklists in the library first if the form needs them.
Walk through the flow
Open Form Builder for the right form
Go to Settings, then Module Configuration.
Select the feature set (for example Verifications).
Open Form Builder for the target form, or start Create New Form and complete the create dialog (Form Title, Form Description where optional, Company Structure, Site/Physical Location, Job Role Category), then confirm Create.
Lay out the canvas
Use the left panel tabs (Sections, Checklists, Proformas, Questions, File Uploads, Info Blocks) to find components.
Drag a component onto the centre canvas and drop it where the guide describes.
Select an element on the canvas to open the right Properties panel and set validation, labels, and display options supported by your form.
Save progress and preview
Click Save Draft (or equivalent) to persist work without publishing.
Use Preview to check desktop and mobile presentations before release.
Adjust sections and ordering with drag and drop until the structure matches your programme.
Publish for end users
When the form is complete and assignments are correct, click Publish.
Confirm the form status moves to PUBLISHED so it can surface to users who match company, location, and job role rules.
Use Cancel only when you intend to discard unsaved navigation per your local policy.
What happens next
End users with the right assignments can start responses against the published form for that module.
Versioning can retain historical copies after publish; duplicates are available when you need a variation.
Status and workflow
DRAFT: Editable; not offered to end users.
PUBLISHED: Live for eligible users.
ARCHIVED: Preserved but not active for new work.
Notes
IMPORTANT: Publishing changes what the field can access. Validate assignments and mandatory questions first.
If Save Draft fails, retry after checking network messages. If a checklist is missing from the library tab, confirm it is published in Checklist Library.
