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

Every plant has two versions of every procedure

One is written down. The other is how the work actually gets done. Here is why they drift apart, and what keeps them together.

VexumVexum
A clipboard with a written checklist next to a laptop showing the same procedure
In short
  • Every manufacturing procedure exists in two versions: the written SOP or work instruction, and the way the work is actually done on the floor.
  • They drift apart because written procedures are slow to change, the real version is passed on person to person, and the information a step needs lives in other systems.
  • The gap shows up as work done differently across shifts and locations, harder investigations and audits, and knowledge that leaves when experienced people do.
  • Rewriting documents or demanding stricter compliance doesn’t close it for long. A loop does: work from the written version, record what happens, compare, turn differences into approved changes, then publish and retrain.

Walk into any plant and ask for the procedure for handling a customer complaint, changing over a line or servicing a spindle. You’ll get a document. It was written carefully, reviewed by the right people and approved. Then watch the work being done, and you’ll see a second version: the one people actually follow.

The two are rarely the same. That isn’t a discipline problem. It’s what happens to every procedure that lives in a document while the work keeps moving.

What is procedure drift?

Procedure drift is the gap that opens between a written procedure and the way the work is actually done. The written version might be a standard operating procedure (SOP), a work instruction, a standard work sheet or a maintenance plan. The real version is what experienced people do when they run the job.

Safety researchers describe the same gap as the difference between work-as-imagined and work-as-done.

Drift is normal. Equipment changes, suppliers change, people find better ways, and the document stays where it was on the day it was approved. The question isn’t whether your procedures drift. It’s whether you can see the drift and decide what to do about it.

Why do procedures drift away from how the work is done?

The written version is expensive to change. Every edit means a review, approvals and retraining. So the small improvements people make on the job, the better order of steps or the check that catches a problem earlier, almost never make it back into the document.

The real version is passed on person to person. New people learn from whoever trains them, and they learn the workaround along with the procedure. Over time the real version lives with a few experienced people.

The information lives somewhere else. A procedure says to pull the inspection results or check the last work order. Those live in other systems, so people find their own ways to get them, and each way is a little different.

Every location keeps its own copy. A procedure written at one plant gets adapted at the next. Each copy changes on its own schedule, and after a few years it’s hard to say which one is current.

What does the gap cost a manufacturer?

The same procedure gets done differently on different shifts and at different locations. When something goes wrong, nobody can say for sure which version was followed. And when one of the people who carries the real version leaves, it leaves with them.

That last cost is growing. The Manufacturing Institute and Deloitte project that US manufacturers could need as many as 3.8 million new employees between 2024 and 2033, and that 1.9 million of those jobs could go unfilled (The Manufacturing Institute, April 2024). Every one of those new people will learn the work from someone. If the best version of a procedure only lives with a few experienced people, it doesn’t survive the handover.

The gap also shows up in audits. An auditor reads the written procedure, then looks at the records or watches the work. Differences between the two are exactly what an audit is designed to find.

“It’s always a project for next year, until the person who knows everything is about to retire. Then it becomes a project for this year.”
Co-Owner and President · Industrial automation and machining group · 50+ employees

Why don’t documentation projects fix it?

The common answer is a documentation project: rewrite every procedure, retrain everyone, and start over clean. It helps for a while. Then the work keeps moving and the gap opens again, because nothing about how changes get made has changed.

The other answer is to ask people to stop relying on what they know and follow the document exactly. But what experienced people know is often the best version of the procedure. Throwing it away makes the work worse.

A new document management system doesn’t close the gap either. It stores the written version better, with cleaner version control and approvals, but it still can’t see the work. The drift happens on the floor, and the document system finds out last.

How do you keep written procedures in step with the real work?

The fix is to stop treating the written procedure and the real work as two separate things. That takes a few pieces working together:

  1. Work from the written version. People work the procedure step by step, so there is one version everyone starts from.
  2. Record what actually happens. Every step, reading and decision is kept, with a name and a time.
  3. Compare the two. When people consistently do something different from what’s written, that difference is information, not a failure.
  4. Turn differences into changes. Each one becomes a suggested change with the reason attached, and follows the approval route the procedure already has.
  5. Publish everywhere and retrain. The approved version goes live at every location at once, and the people trained on the old version are told.

That’s the loop Vexum runs. The written procedure stays the one your team approved, and it keeps up with how the work is really done. You can read how one change moves through it in How a change gets back into the procedure.

What to look for in procedure management software

If you’re choosing software to keep procedures current, a document library isn’t enough. Look for a system that can do these six things:

  • Structure your existing documents. It turns PDFs, Word files and scans into step-by-step procedures, with every step linked back to the page it came from.
  • Run the procedure with your team. Each step, reading and decision is recorded with a name and a time.
  • Show where the work differs. It compares what people actually did with what’s written, so differences show up as patterns, not anecdotes.
  • Control every change. Changes follow your approval route, every signature is recorded and old versions are kept.
  • Publish and retrain together. A new version goes live everywhere at once, and the people trained on the old one are flagged.
  • Keep your systems. It works with the systems you already run instead of replacing them.

Vexum is built around all six. See how it works for quality, standard work, maintenance and safety and EHS teams, or start with the procedures and change management overviews.

Frequently asked questions

What is the difference between an SOP and how the work is actually done?

An SOP is the approved, written description of how a task should be done. How the work is actually done is what people do on the job, including the shortcuts, fixes and improvements they’ve learned. The difference between the two is procedure drift, sometimes called the gap between work-as-imagined and work-as-done.

Why don’t people follow procedures exactly?

Usually because the procedure no longer matches the job. Equipment, materials and suppliers change, and people find better ways to do the work. Those improvements rarely make it back into the document, because changing it means a review, approvals and retraining.

How do you capture tribal knowledge in manufacturing?

Record the work as it happens instead of interviewing people after the fact. When every step, reading and decision is kept with a name and a time, the way experienced people really do the job becomes visible, and the best of it can be written back into the procedure through your normal approval route.

How often should procedures be reviewed?

Often enough that they reflect how the work is really done. Some rules set a minimum: OSHA’s Process Safety Management standard requires employers to certify every year that the operating procedures for covered processes are current and accurate. A review calendar won’t catch drift between reviews, though. Comparing the written procedure with the recorded work will.

Does a documentation project fix outdated procedures?

For a while. Rewriting every procedure resets the written version, but nothing about how changes get made has changed, so the gap opens again as the work moves on.

What does Vexum do?

Vexum is the intelligent procedure platform for manufacturing. It turns your documents into step-by-step procedures with every step cited, runs them with your team, suggests changes from how the work is really done, routes each change through your approval route and trains people on every new version.

If you run procedures at a manufacturer and want to see this loop on one of your own, request a demo.

Get new posts by email

Product news and notes on procedures, change and training.