Sop Drift
The SOP said the sample must be logged before it leaves the collection point. On the floor, the sample was logged when it reached the lab, because logging at the collection point took a form and a phone call and the person at the collection point had neither. The SOP had said one thing for two years. The floor had done another thing for two years. Nobody had noticed, because the two had never been put side by side.
This is SOP drift. The process on paper and the process on the floor slowly part ways, and the gap between them is where errors, audits and blame all live.
How the two versions separate
No one writes a wrong SOP on purpose. Drift starts with a small, sensible adjustment. A step is impractical, so someone finds a quicker way. The quicker way works, so it becomes the way. The SOP is not updated, because the change is small and the SOP is not something anyone reads on a busy Tuesday.
Then the process changes again, and again, each time with a small workaround that never makes it back to the document. After a year, the SOP describes a process that no longer exists, and the floor runs a process that no document describes.
- A system is upgraded, and the SOP still shows the old screens.
- A role changes hands, and the SOP still names the person who left.
- A step is dropped because it was never useful, and the SOP keeps it.
- A new approval is added in practice, and never added to the paper.
Each change is minor. The sum of them is a document that no longer matches reality.
Why drift is dangerous, not just untidy
It is tempting to treat the gap as a housekeeping issue. It is not. Drift has real consequences, and they show up at the worst times.
The first is compliance. When a regulator, an auditor or a customer asks to see your process, they read the SOP. If the floor does not follow it, you have a documented process that your own people do not use. That is a finding, and it is a hard one to defend, because the document you wrote is the evidence against you.
The second is safety and quality. The workaround on the floor is usually faster because it skips a check. The check was there for a reason, and the reason does not go away because the check became inconvenient. The error that follows will be traced back to the missing step, and the missing step is in the SOP, so the failure looks like a person ignoring the rule.
The third is blame. When something goes wrong, the investigation asks whether the process was followed. If the floor was following the real process and the real process was not the SOP, the person who did the sensible thing is the one who gets held responsible. Drift turns good employees into rule-breakers on paper.
Why nobody closes the gap
The gap survives because each side assumes the other is the problem. Management assumes the floor is not following the SOP. The floor assumes management knows the SOP is out of date and does not care. Both are wrong, and neither says so, so nothing changes.
There is also a version problem. The SOP lives in a folder, often on a shared drive, often in a version that is three revisions behind. Updating it properly means finding the owner, getting approval, reissuing, and telling everyone, which is a lot of work for a change that feels small. So it does not happen.
And there is the deeper reason. The people who write the SOP and the people who run the process are usually not the same people. The writer describes how the work should go. The runner does the work. The two never sit down together after the process changes, because there is no moment in the calendar that requires it.
How we find drift
The gap is easy to find once you look for it, and it is almost always bigger than the client expects.
- Take the SOP and follow it literally on the floor, step by step. Where you cannot, you have found a drift point.
- Ask the person doing the job to describe the process out loud, then compare it to the document. The differences are the real process.
- Watch for the phrase we have always done it this way. It usually marks a step that drifted years ago.
- Check the version and the date on the SOP. A document that has not changed while the process has is a document that has drifted.
Most clients find that the SOP and the floor agree on the broad shape of the process and disagree on the details. The details are where the risk sits.
Closing the gap and keeping it closed
The fix is not to write a perfect SOP. A perfect SOP would drift too. The fix is to build a habit of comparing the two versions, and to make the comparison normal rather than an audit event.
- Give every SOP a named owner, someone whose job includes keeping it current.
- Review each SOP on a schedule, and whenever the process changes, not only when someone remembers.
- Write SOPs with the people who do the work, so the document starts closer to reality.
- Make it easy to flag a drift. If a step is impractical, people should be able to say so without it looking like a complaint.
- Treat the floor's version as information, not disobedience. Often the floor has solved a problem the SOP did not know about.
When the workaround is genuinely better, adopt it and update the SOP. When the SOP is right, find out why the floor departed from it, because the reason is usually practical and fixable.
The point of the document
An SOP is not a rule for its own sake. It is a way of making sure the work is done the same way by different people on different days. That purpose is defeated the moment the document and the floor stop matching, because then there is no agreed way of working at all, only two versions and a gap between them.
Closing the gap is not about enforcing the paper on the floor. It is about making sure the paper and the floor describe the same thing, so that when the work goes right it is repeatable and when it goes wrong you can find out why.
We do not guess. We investigate. When we audit a process, we do not stop at reading the SOP. We follow it on the floor and note every place the two disagree, because that list is the truest picture of how the company actually works.