do the work
The checks this job needs, without waiting on a developer.
Build the inspections, checklists and sign-off forms each job type requires.
what it does
What Dynamic Form Builder does
Every operation has forms that are specific to it: an isolation procedure, a commissioning check, a customer sign-off with particular wording.
Rather than a fixed set of fields, forms are built to match the job types you actually run, and attached to those job types so the right one appears on the right visit.
What gets captured consistently is what can later be reported on, which is why this module tends to matter more than it first appears.
- Build forms for the job types you run
- Attach the right form to the right work automatically
- Capture photos, readings and signatures on site
- Consistent capture makes later reporting possible
how it works
Four steps, and none of them are magic.
-
build
Your forms, not ours
Inspections, risk assessments, commissioning sheets, permits and sign-offs, built to how you already work rather than bent into a generic template.
-
attach
Rules decide when a form applies
By job type, asset class, site or customer. An isolation certificate appears on the jobs that need one and stays out of the way everywhere else.
-
complete
The technician fills it where the work is
Conditional questions so only relevant fields appear, mandatory fields that block completion, photos and signatures captured in place, offline throughout.
-
keep
A completed form is a record, not a PDF
Answers are data. You can report across them, find every job where a reading was out of range, and produce evidence at audit without opening documents one at a time.
data and integration
What it reads, what it writes, what it sits beside.
Nothing here is a separate database. Dynamic Form Builder works off the same work order, customer and asset records as everything else, which is the whole reason the modules are worth running together.
reads
Job type, asset class, site and customer, to decide which forms apply.
writes
Structured answers onto the work order and the asset; blocking conditions back into job completion.
alongside
License & Certification for who is permitted to sign, and your document store for archived output.
questions we actually get
Before you ask us on the call.
Yes. Conditional logic is the point: it keeps a long compliance form short for the technician actually standing there.
Both, including customer signature on site and photos required before a step can be marked complete.
Yes. Mandatory fields and failed checks can prevent closing, which is how you stop a job being signed off without its safety sign-off.
Yes: exported or queried as structured data. Answers are stored as fields, not baked into a document.
elsewhere in the platform
Other capabilities
further reading