A procedure is the recipe for a specific maintenance job. It tells the technician exactly what to do, in what order, and what evidence to capture. Without procedures, every job depends on the memory and judgment of whoever happens to be doing it; with procedures, the job is consistent regardless of who executes it.
In a paper world, procedures live in binders or laminated cards next to the equipment. In a CMMS, they are digital templates attached to work orders, so the technician sees the steps on a phone or tablet at the moment of work.
Anatomy of a digital procedure
A typical procedure is a list of steps, where each step can include:
- Instructions: free text describing what to do.
- Form fields: a place to record a value (numeric reading, multiple choice, text note).
- Photo capture: the technician must take a photo before continuing.
- Signature: the technician (or an inspector) must sign off.
- Conditional logic: if a reading is out of range, branch to a follow-up step.
Why procedures matter
- Consistency: every PM on the same equipment is performed the same way.
- Training: new technicians can execute jobs they have not done before by following the procedure.
- Audit: regulated industries (food, pharma, healthcare, aviation) need proof that the procedure was followed, not just that the job was done.
- Continuous improvement: if a procedure is wrong, fixing it once updates every future execution.
Procedure templates and reuse
A good CMMS treats procedures as reusable templates. Defining a "Quarterly inspection of conveyor belt" procedure once means it can be attached to every conveyor in the facility, and to every work order generated from a quarterly PM. When the procedure changes, every future work order picks up the new version.