Create a procedure
A procedure is a reusable checklist or inspection that a technician completes while doing a job. Attach one to a work order and the technician can’t mark the work resolved until the checklist is done — so the safety step, reading, or photo actually gets captured every time.
Follow these steps to build one and publish it for use.
Create the procedure
Section titled “Create the procedure”-
In the sidebar, select Procedures.
-
Select New procedure.
-
In Name, describe what the procedure is for — for example, “Monthly fire extinguisher inspection”.
-
Choose the Kind that fits: a Checklist, an Inspection, a Toolbox talk, a Safety briefing, or a Recovery procedure.
-
Select Create procedure. This creates the procedure and drops you into the builder, where you add its fields and requirements.
Build and publish
Section titled “Build and publish”In the builder, add the fields that make up the procedure, then publish it.
- Add your Fields — one per thing the technician records. Each field has a label and a type, such as a Yes / no, a number, or a photo. See Procedure field types for the full list.
- Mark any field Required so the procedure can’t be completed without it, and use a Section header to group related fields.
- Set the procedure’s pre-work requirements — required PPE, tooling, a Permit kind, and whether a photo or signature is required to complete it — so technicians are prompted before they start.
- Select Publish to make the procedure available to use.
Attach it to work
Section titled “Attach it to work”Once published, a procedure can be attached to a work order or a preventive maintenance schedule. When the technician runs the job, they fill in the fields; required fields, photos, and signatures are checked before they can complete it.
What happens next
Section titled “What happens next”Your workspace also comes with a few starter procedures — like a generic inspection checklist and a pre-work PPE check — that you can use as-is or copy as a starting point for your own.
Was this page helpful?
Thanks — your feedback helps us improve these guides.

