The SOP that nobody has opened in a year

Somewhere on a shared drive, most businesses have a folder of SOPs, and a meaningful share of them describe a process the way it worked when the document was written, not the way it actually works now. Nobody updated them, not out of laziness exactly, but because updating an SOP has never been anyone's job the way running the process is someone's job.

Why SOPs drift out of sync with reality

A process evolves constantly, in small ways, as the people running it encounter exceptions, find shortcuts, or adapt to changes nobody thought to formalise. None of those adjustments get reflected in the original document, because updating the document was never part of making the adjustment — the adjustment just happened, in practice, and the SOP stayed exactly where it was written.

Over time, the gap between the document and the actual process widens until the SOP describes something closer to how the process used to work than how it works now. At that point, it stops being documentation and becomes a kind of historical record nobody treats as authoritative, including the people who are supposed to be following it.

Why this is worse than having no SOP at all

A missing SOP is an honest gap — everyone knows there's no documented process, so nobody trusts one that doesn't exist. A stale SOP is a dishonest gap — it looks authoritative, sits in the right folder, has the right formatting, and quietly misleads anyone who trusts it, particularly a new hire who has no way to know it's out of date.

This is precisely the moment where the SOP does active harm rather than simply failing to help. A new team member following a stale document faithfully will make mistakes that an experienced staff member, working from actual current practice, would never make — see why a new hire's first three months are spent asking why.

Why the usual fix doesn't hold

The standard response — schedule an annual SOP review — sounds reasonable and rarely survives contact with a busy calendar. Reviewing documentation competes with every other priority for time, and it's the priority with the least visible cost to skipping, right up until the moment a stale document causes a real problem. Annual reviews get pushed, skipped, or done superficially, and the drift continues.

What actually keeps an SOP current

Update it at the moment the process changes, not on a schedule. If updating the document is treated as part of changing the process — the same way updating a configuration setting is part of changing a configuration — it happens because it's attached to the change itself, not because someone remembered a separate review cycle.

Make the person running the process responsible for its accuracy, not a separate documentation owner. An SOP maintained by someone who doesn't actually run the process tends to describe an idealised version rather than reality, because they're documenting what should happen rather than what does.

Date-stamp and periodically spot-check, rather than trying to review everything on a fixed cycle. Pick a handful of SOPs each quarter and have the person currently running that process confirm, in a few minutes, whether the document still matches reality. This catches drift faster than an exhaustive annual review that never quite happens.

A quick test worth running now

Pick any SOP older than a year and hand it to the person currently doing that job. Ask them to read it and mark anything that's no longer accurate. If the document comes back clean, it's genuinely current — a good sign, and rarer than most businesses expect. If it comes back heavily marked, you've just found exactly the gap this article describes, before a new hire finds it the harder way.

Common questions

Why do SOPs go stale even in businesses that take documentation seriously?

Because processes evolve continuously in small, informal ways as people encounter exceptions and find better approaches, and none of those adjustments naturally trigger an update to the original document. Updating the SOP was never built into the act of changing the process, so the two drift apart gradually and invisibly.

Why is a stale SOP worse than having no SOP at all?

Because a missing SOP is an honest gap that nobody trusts, while a stale one looks authoritative and misleads anyone who relies on it — especially a new hire with no way to know the document no longer reflects actual practice, who then makes mistakes an experienced person following current reality wouldn't make.

Why don't scheduled annual reviews reliably keep SOPs current?

Because reviewing documentation competes with every other business priority and has the least visible cost to skipping, right up until a stale document causes a real problem. In practice, scheduled reviews get pushed, skipped, or done superficially, and the drift between document and reality continues unaddressed.

What's a more reliable way to keep SOPs accurate?

Update the document at the moment the underlying process changes, rather than on a separate review schedule, and make the person who actually runs the process responsible for its accuracy. Spot-checking a handful of SOPs each quarter against current practice also catches drift faster than an exhaustive annual review that rarely happens as planned.

Related: why a new hire's first three months are spent asking why · where to write down why so it survives · why it has always been done this way survives automation