On-site forms
Every job type in concorbit can bind to a form: a set of fields that engineers fill on-site. The form is auto-attached to every job of that type the moment it's created; engineers see it on their mobile app, office staff can review and edit it in the desktop Job page. Fields can be flagged as required for completion, which blocks a job from being marked complete until those fields are filled.
This is the digital record of the work: the meter reading, the insulation-resistance value, the signed-off risk assessment, the serial numbers of parts fitted.
Setting up a form for a job type
Go to Forms > Templates and either clone one of the seeded trade templates (Electrical minor works, Plumbing leak inspection, HVAC service record, Site risk assessment) or build a new form from scratch under Forms.
Open Jobs > Settings and edit the job type you want to bind the form to.
In the On-site form dropdown, pick the form.
From that point forward, every job created under that type gets a draft submission auto-attached. Existing jobs are unaffected: the auto-attachment runs at create time.
Filling the form on-site
Engineers see the form inside the job detail screen on the mobile app. They can fill any combination of fields, tap Save form to persist progress, leave, and come back. Saves are idempotent: each save overwrites the stored data with the current state of the form and stamps the "last saved" timestamp.
Conditional fields (visible only when another field has a specific value, e.g. "Leak details" only appears when "Leak detected" is ticked) are evaluated the same way on mobile and on desktop.
Gating job completion
A field with Required for completion ticked blocks the job's Complete action. Both mobile and desktop surface this clearly:
The Forms card shows a warning strip listing the missing field labels
The complete endpoint refuses the transition with a 422 if any required field is still empty
A partial field (e.g. a checkbox left unchecked, or a text box empty) counts as missing
Conditional fields that are hidden by their rule don't count as missing: a hidden field can't be required.
Reviewing submissions
The desktop Job page has a Forms card showing every submission attached to that job, each rendered as an editable form. Office staff with jobs.forms.edit can update submitted data after the fact; this is useful for typo corrections and dispatcher-side admin. Every edit is audited.
Seeded trade templates
Four starter templates ship with concorbit. Clone them from Forms > Templates > Start from template:
Electrical: minor works: BS 7671 minor-works certificate shape (circuit, protective device, insulation resistance, earth loop, polarity)
Plumbing: leak inspection: leak location, water source, pressure test, parts used, stopcock state
HVAC: service record: refrigerant, pressures, filters, coils, controls, leak detection with conditional detail field
General: site risk assessment: hazards, controls, PPE, optional permit number, safe-to-proceed sign-off
Each template has sensible fields already flagged as required-for-completion. Cloning produces an independent Form you can customise further; changes to the template blueprint don't propagate.
Permissions
jobs.forms.view: read form submissions on a job (office review)jobs.forms.edit: save form submissions (engineers fill their own; supervisors edit any)
Add these to the relevant roles under Settings > Roles. A role with jobs.edit but not jobs.forms.edit can act on the job lifecycle but not modify form data, useful for a dispatcher role that schedules but doesn't do on-site work.