NewIntroducing the Vexum advisory boardRead the announcement
All posts · 5 min read

How to see where operators deviate from written procedures

Every plant has a gap between what's written and what actually happens. Here is how to make that gap visible, step by step, and what to do once you can see it.

VexumVexum
A station tablet showing a checklist beside a digital caliper
In short
  • Operators deviate from written procedures in every plant, usually for good reasons, but most plants can't see where or how often.
  • Paper sign-offs and end-of-job checklists record that a step was done, not how it was done, so the gap between what's written and what actually happens stays invisible.
  • To see it, record the work against each step as it happens and compare it with the approved procedure.
  • Capture the reason when the work differs, then treat recurring deviations as a signal: either the work needs correcting or the procedure does.

Ask a quality manager whether operators follow the written procedure and you will usually get an honest answer: mostly. Ask where they don't, and the answer gets vague. Somebody on second shift does the torque check in a different order. One plant skips a step that another plant swears by. The experienced operator has a trick nobody wrote down.

That gap between what's written and what actually happens exists everywhere. The problem is not that it exists. The problem is that you can't see it, so you can't decide what to do about it.

What counts as a procedure deviation?

A procedure deviation is any time a step is done differently from the approved procedure: skipped, done out of order, done with a different tool or value, or done in a way the procedure doesn't describe at all.

Some deviations are mistakes. Many are not. Operators work around a fixture that doesn't fit anymore, use a gauge that reads faster, or add a check that catches a defect earlier. Those are improvements the procedure never learned about.

Why can't most plants see where operators deviate?

The record says the procedure was done, not how. A signature at the bottom of a traveler or a checked box on a form confirms completion. It doesn't say which order the steps were done in, which value was used, or what the operator did when the written step didn't fit.

Audits are snapshots. Someone watches the job once, the operator does it by the book because someone is watching, and the audit passes. The other 364 days aren't in the record.

The reason is gone by the time anyone asks. If a deviation surfaces in an investigation weeks later, nobody remembers why the step was done that way, or whether it was done that way every time.

If the only record is a signature, the gap between what's written and what actually happens is invisible by design.

How do you find where the work differs from what's written?

Run the work through the procedure. Instead of signing off at the end, each step is worked in order, and what happened is recorded against that step: the reading, the photo, the decision, who did it and when, on the version of the procedure that was in force.

Set the evidence each step needs. A torque step asks for the value. A first-article step asks for a photo. A visual check asks for a pass or fail. Evidence set per step is what makes the comparison possible.

Compare what was done with what is written. Once the work is recorded step by step, the differences show up on their own: the value outside the written limit, the step done out of order, the step marked done with no evidence.

Ask why at the moment it happens. The best time to learn why a step was done differently is while the operator is still at the station. In Vexum, the voice agent asks how each step was done. When the answer doesn't match the written step, it asks why, asks for proof, and reads it back before recording it. That is also how what experienced operators know gets captured without anyone scheduling an interview.

What should you do when the work and the procedure disagree?

Decide in advance, per step, what happens. Some steps can be done differently as long as it's logged. Some should prompt for a reason before the operator continues. Some, like a lockout or a hold point, should require a manager's approval. In Vexum those are three settings on each step: allow and log, warn and ask for a reason, or require approval.

Then look at the pattern, not the single event. One deviation can be a mistake. The same deviation on every shift is telling you something. A deviation should trigger investigation, not become the standard. Either the work needs correcting, through coaching or a better tool, or the procedure needs to change.

When it's the procedure, Vexum proposes the change with the runs that show it, and the change goes through your approval route like any other. A person always decides.

What should you look for in software that finds deviations?

  • Step-level records, not only a final sign-off: each reading, photo and decision against its step.
  • A comparison with the approved version, so it can show where the written procedure and the real work differ.
  • Deviations by procedure, step and location, so you can see which procedures are not being followed and where to look first.
  • The reason and the proof, captured when the work differs.
  • Consequences you configure per step, from logging to approval.
  • A path from recurring deviations to an approved change, with retraining when the procedure changes.

Vexum is built around that loop. See how it works on the floor in connected worker and digital work instructions, or start with how procedures drift in the first place.

Frequently asked questions

What is a procedure deviation?

Any time a step is done differently from the approved procedure: skipped, reordered, done with a different tool or value, or done in a way the procedure doesn't describe. Some deviations are errors; others show the procedure no longer matches how the work is really done.

How do you find procedures that are not being followed?

Record the work against each step as it happens and compare it with what's written. End-of-job sign-offs and checklists rarely show this, because they record that a step was done, not how.

Should every deviation change the procedure?

No. A deviation should trigger investigation, not become the standard. When the same deviation keeps happening and the outcome is good, it may be the procedure that needs to change, through your normal approval route.

Can we start from the procedures we already have?

Yes. Vexum turns existing PDFs, Word files, Excel files and scans into step-by-step procedures, with every step cited to the page it came from.

If you run procedures at a manufacturer and want to see where your written procedures and the real work differ, request a demo.

Get new posts by email

Product news and notes on procedures, change and training.