What it is for
A procedure is the step-by-step method your technician follows during a job: a series of items to check off, readings to record, photos to take, or signatures to collect. Instead of know-how that stays in the heads of your veterans, you get a reusable, traced and verifiable checklist. This course shows you how to build a procedure with the right field types, make it reliable with required fields, then run it and find its history.
Key concepts
- A procedure is a reusable template made of fields: you build it once, then attach it to as many work orders as you need.
- Many field types are available: text, number, checkbox, dropdown, date, measurement, photo, file, signature, section… to cover both a checklist and a technical reading.
- The Inspection field provides a scored result (for example pass / fail) and turns a check into usable data.
- A field can be marked required: it becomes blocking, and execution cannot be closed until it is filled in.
- The Signature and Photo fields capture proof straight from mobile: a handwritten on-screen signature, a picture taken on the spot.
- A procedure can be attached to a work order, but also to an asset, a location or a tag, so you find it in the right context.
Step by step
- 01
Create the procedure and lay out its fields
Open the Procedures module and create a new procedure. Give it a clear title, then add fields one by one in the order the technician should fill them in. For each step pick the right type: a checkbox for a simple check, a measurement field for a reading, a photo field for visual proof, a signature for a sign-off.
- 02
Structure with sections and required fields
Group steps into sections to break up a long procedure (preparation, inspection, return to service). Mark critical fields as required: until they are filled in, the job cannot be closed. This setting is what guarantees no essential step gets skipped.
- 03
Add scored checks and proof
For control points, use the Inspection field to get a scored result rather than plain free text. Add Photo fields where visual proof matters, and a Signature field at the end of the procedure to have the job signed off by the technician or a manager.
- 04
Attach the procedure to the job
Attach the procedure to a work order so it opens during execution. You can also link it to an asset, a location or a tag: it will then be suggested in the right context, without having to search for it every time.
- 05
Run it and review the history
In the field, the technician runs the procedure from mobile (or web): checking, measuring, photographing and signing as the job goes. Once the work order is closed, the completed procedure is kept in the history — you can see who did what, with which values and which proof.
Tips & good to know
- Write each step as a short, unambiguous instruction: the procedure must be clear to a stand-in discovering the asset for the first time.
- Only make truly critical fields required: too many required fields slow the field team down and push toward sloppy filling.
- Prefer the scored Inspection field over free text for any control point: a structured result is usable, a free sentence is not.
- A well-designed procedure can serve as the basis for a preventive maintenance plan: you capture the method just once.