Procedure field types

A procedure is made of fields — one for each thing the technician records. This page lists the field types you can add. For how to build and publish a procedure, see Create a procedure.

Field types

Field type	Captures	Use it for
Text	A short written answer	Serial numbers, notes, observations
Number	A numeric value	Readings, measurements, quantities
Checkbox	A yes/no answer	“Guard in place?”, “Area clear?”
Single select	One choice from a list	A condition rating, a pass/fail call
Multi select	Several choices from a list	Faults found, parts replaced
Meter reading	A meter value	Hours run, kilometres, consumption
Photo	One or more images	Before/after shots, evidence of a fault
Signature	A signed confirmation	Sign-off that the work was done
Section header	Nothing — it’s a divider	Grouping related fields into sections

Required fields

Mark any field Required and the technician can’t complete the procedure until they’ve answered it. Required photo and signature fields are checked too — the procedure won’t complete without the image or the signature.

Pass/fail rules

Text, number, checkbox, and select fields can carry a pass/fail rule — for example, a number that must fall between a minimum and maximum, or a checkbox that must be ticked. When a technician’s answer breaks the rule, you decide what happens:

• Warn — flag it but let the job continue.
• Fail — mark the whole procedure as failed.
• Block — stop the job from being resolved until it’s sorted.

If any non-warning field fails, the procedure counts as failed. An owner, administrator, or maintenance lead can override a failed result, but they must leave a note explaining why.

Note

Photo, signature, and section-header fields don’t take pass/fail rules — a photo either is or isn’t provided, and a section header only organises the form.