Where Should Your SOPs Live? (And Who Keeps Them Current?)

The one-click test

An SOP gets used when it's one click away from the moment the work happens. A checklist attached to the task someone is already working on gets read. A document in a shared drive gets read after something has already gone wrong.

So before you compare tools, ask a simpler question for each process: where is the person physically working when they need the answer? That's where the SOP should live. The tool comparison comes second.

Three places an SOP can live, and what each is good for

How SOPs go stale

• The software changes and the SOP keeps describing the old screen, so people stop trusting the rest of it too
• The person who wrote it leaves, and nobody else knows it exists
• It documents the ideal version of the process instead of what people actually do, so everyone quietly works around it from day one

Who owns each SOP

One named person per SOP — and it should be the person who does the work, not whoever has time to write documents. Give every SOP a review date, and put that review in the same system as the rest of the owner's work, not in a separate reminder that's easy to dismiss. An SOP without an owner is a draft, however polished it looks.

The cheap maintenance rhythm

Once a quarter, each owner checks their SOPs against what actually happens and fixes the gaps. Anything nobody has opened in a year gets archived. A short library that's accurate beats a long one nobody trusts.

And where a process is fully repeatable, it's worth asking whether it should be documented at all — or automated instead, so there's nothing for a person to follow.

A simple SOP template

• Title and owner: what the process is called and who keeps it current
• When to use it: the trigger that starts the process
• Steps: numbered, one action per step, written for someone doing it for the first time
• Exceptions: the common cases where the steps change, and what to do instead
• Done means: how the person knows the process is complete
• Last reviewed: the date it was last checked against reality

Moving existing SOPs without starting over

You do not need to rewrite your library to fix placement. Start with the five processes that break most often when someone is away. For each, move the steps into the place the work happens, such as a checklist in the task template, and link back to the longer document for context. Assign an owner and a review date. Then repeat with the next five. Within a couple of months the SOPs that matter will be where people work, and the rest can be archived.

Related reading