Forms & inspections

Build inspection checklists once, attach them to PMs and work orders, and collect structured answers instead of paper.

Forms turn "check the compressor" into a structured record: which checks ran, what the readings were, what failed, and the photo that proves it. Answers are data - filterable and reportable - not a PDF in a drawer.

Form templates

The Forms page lists every template with its status and work category, as a table, as cards, or in split view, which previews the selected form beside the list so you can try its questions without opening the builder. Add Form opens the builder, and Export downloads the templates the list is showing as a CSV file.

In an organization running both Facilities and Infrastructure, each form is filed under Facilities, Infrastructure or Shared with the workspace picker in the builder, and the Forms list has a Facilities / Infrastructure / Shared switch. Forms start Shared, and existing ones stay Shared until you move them. A member assigned to one workspace sees that workspace's forms and the shared ones, and forms they create are filed in their workspace. Attaching a form to a work order or PM schedule offers the forms that fit the work: infrastructure and shared forms for work on a feature, facilities and shared forms for anything else.

A form template is the reusable definition, built in the form builder (Forms). Each template holds ordered items - the questions - chosen by the kind of answer you want:

Item typeUse for
Single selectPass/fail, yes/no, condition ratings - supply the options
Multi select"Which of these apply?" - optionally with minimum/maximum selections
NumberReadings - pressure, temperature, run hours - with min/max, a unit, and integer or decimal precision
CheckboxA simple done/not-done tick
TextNotes and observations (single or multi-line)
PhotoVisual evidence - photos are compressed on upload, served through short-lived links, optionally capped at a maximum count
Team membersWho took part, such as the attendees of a safety meeting - pick people in your organization, or add guests such as contractors by name
SignatureA drawn sign-off, recorded with the signer's name and the time - see Signatures
SectionA heading that groups the checks that follow

Signatures

A signature item shows a pad to sign on with a finger or mouse. When you're signed in, the signature is recorded under your name. An outside contractor on a shared work order link types their name, then signs.

A signature covers the answers on the form at the time it was given. Changing any other answer clears every signature on the form, so a signed form always shows what was signed. Put signature items last, and sign once the other answers are final. A form can carry more than one signature, for example one from the person running the meeting and one from a worker representative.

Conditional follow-ups

Items can be shown conditionally based on an earlier answer - "Describe the issue" appears only when "Belt condition" was answered Fail; a photo prompt appears only when something is wrong. Forms stay short for the happy path and thorough for problems.

Suggested follow-up work

Any choice, checkbox, number or text question can suggest a follow-up work order. In the builder, turn on Suggest a follow-up work order for the question, set when it applies - Belt condition is Fail, Discharge pressure is greater than 150 - and pick the priority. For an inspection checklist, Suggest follow-up work orders on No / Fail answers under the question list does it in one step: every Yes/No and Pass/Fail question without a rule gets one on its No or Fail answer, at medium priority. Save the form to keep them.

When an answer matches, a Create work order button appears under that question - after its own "Describe the issue" question, if it has one. Nothing is created until someone presses it. The new work order is titled after the question and answer, carries the priority you set, and inherits the original work order's site, building, location, assets and systems. Its description is what was written under "Describe the issue", followed by the form and work order it came from. Each question raises at most one work order per form; once created, the question links to it.

Rules you add or change in the template apply to forms already attached to work orders, so an inspection in progress picks them up without being re-attached. They only decide when the button is offered - the questions and what is required stay as they were when the form was attached.

Follow-ups are created by staff in AssetLab. A contractor filling the form through a shared link doesn't see them.

Draft → published

Templates start as drafts and must be published before they reach the field. Publishing validates the template - selects need at least two options, conditions must reference earlier questions - so broken forms can't ship.

A published template that needs changes can be set back to draft, edited in place, and republished. In-flight responses are safe either way: every response takes a snapshot of the template's items at attach time, so later edits never mutate a form someone is mid-way through filling.

Templates can also be duplicated (to branch a variant) and archived - archived templates disappear from the list and can't be attached, but their completed responses remain on the records that hold them.

Getting forms in front of technicians

A form reaches the field by being attached to a work order:

The technician fills it in on their phone as part of completing the job; partial progress saves, photos come from the camera. The same form (photo answers and signatures included) is fillable by an outside contractor through a shared work order link - no account needed, and PM-generated work orders shared with vendors get the same treatment.

Where answers go

Build-fast options