Standard Operating Procedures: Building SOPs That People Actually Use

Most standard operating procedures die in a folder. Someone spends a weekend documenting how everything works, saves it somewhere sensible, and eighteen months later it's out of date and no one's opened it since. The problem is almost never the writing — it's that the SOP was built to exist rather than to be used. Here's how to build procedures your team actually reaches for.

What an SOP is really for

An SOP exists to make an outcome repeatable regardless of who's doing the task. Its job is to let work happen consistently without the owner or the one expert being in the room — which is the difference between a business that can grow and delegate, and one that lives entirely in a few people's heads. If your business stops functioning the moment a key person is on leave, undocumented procedure is a large part of why. That makes SOPs a direct lever on reducing founder dependency, not just a tidiness exercise.

Start with the tasks that actually hurt

Don't try to document everything — you'll burn out and produce a library no one reads. Prioritise ruthlessly. The tasks worth writing first are the ones that are frequent (so the payoff repeats), high-stakes (where an error is costly), or currently trapped in one person's head (your single points of failure). A useful test: what would break, and how badly, if the person who normally does this were unavailable tomorrow? Start there and let the rest wait.

Write for the person doing the task, not for the shelf

The reason most SOPs go unused is that they're written as documents to be admired rather than followed. A procedure someone will actually use has a few consistent traits:

• Numbered, concrete steps. Each step is a single action a real person can do, in order. "Ensure invoices are processed appropriately" is a wish, not a step. "Open the invoice in the accounting software, match it to the purchase order, flag any discrepancy over the agreed threshold to the manager" is a step.
• Written at the level of the person doing it. Don't assume knowledge the reader may not have. If a newcomer could be doing this task, the SOP should let a newcomer do it.
• Show, don't just tell. Screenshots and short screen recordings often beat paragraphs. For anything done on a computer, a two-minute video walkthrough can replace pages of prose and is faster to make.
• State the why and the failure points. A step people understand is a step they follow correctly and adapt sensibly when reality differs. Flag the common mistakes and what to do when something doesn't match the script.

Capture the procedure while the work happens

The most efficient way to write an SOP is to document the task while someone does it for real, rather than trying to recall every step from memory afterwards. Have the person narrate what they're doing as they do it, or record their screen, then turn that into the written steps. This catches the small undocumented decisions and workarounds that live in muscle memory and would otherwise be left out — and those omissions are exactly what trip up the next person.

Make them findable and keep them current

An SOP no one can find might as well not exist. Keep them in one known place your team actually works in, organised so the right procedure is reachable in seconds. Just as important, plan for them to change: assign each SOP an owner responsible for keeping it accurate, and build in a trigger for review — when the process changes, when a tool is replaced, or on a regular date. An out-of-date procedure is worse than none, because it teaches people to distrust the whole library.

Build them into how work is trained and checked

The SOP earns its keep when it becomes the default way things are learned and done, not a reference people forget exists. Use it to onboard new people — hand them the procedure rather than a person's spare afternoon. Point to it when someone asks how to do a task. Use it as the checklist for whether work was done right. When the SOP is genuinely the source of truth for a task, it stays current because people are using it, and it delivers the real prize: work that runs consistently without depending on any one person. That's the foundation of a modern back office that can scale — and the reason the effort is worth it even when no one's forcing you to do it.