To write an SOP people follow: give it one clear purpose, write numbered actions starting with a verb, keep each step to one decision, put it where the work happens, and test it by having someone new run it without help. Length is not the goal, completion without questions is.
The structure that works
- Title and purpose. One line each. If you cannot state the purpose in a sentence, the procedure covers too much.
- Scope and owner. When it applies, when it does not, and which role maintains it.
- Prerequisites. Access, tools, and information needed before starting.
- Numbered steps. Verb first, one action per line, with links to the exact tool or template.
- Decision points. Written as if-then rules, not paragraphs.
- Definition of done. Something observable, such as a status change or a sent confirmation.
- Review date. At minimum twice a year.
Language rules
- Give instructions, do not describe. "Open the invoice template" beats "the invoice template should be opened".
- One step, one action. If a step contains "and", split it.
- Name roles, not people. Staff change; roles persist.
- Show, do not only tell. A screenshot removes three sentences.
The test that proves it works
Hand the SOP to someone who has never done the task and watch without helping. Every question is a defect. Fix them, then repeat with a second person. Two clean runs and the procedure is done.
Why SOPs get ignored
| Reason | Fix |
|---|---|
| Too long to read mid-task | Split into a checklist plus reference notes |
| Stored away from the work | Link it inside the task or project tool |
| Out of date | Named owner plus scheduled review |
| Written by someone who never did the job | Draft from observing the actual operator |
Where to start
Pick the five processes that run most often and cost the most when they go wrong. Document those before anything else, and follow the mapping method in how to document a process.
Frequently asked questions
How long should an SOP be?
One to three pages for most tasks. If it runs longer, the procedure is probably two procedures, or reference material is mixed in with the steps.
What format works best for SOPs?
A numbered checklist inside the tool where the work happens, with screenshots for anything visual. Documents in a separate drive get read once and forgotten.
How often should SOPs be reviewed?
Every six months at minimum, and immediately after any tool change or process redesign. Put the review date in the document itself and give it a named owner.
Who should write the SOP?
Someone who observes the person currently doing the work. Operators know the real steps but skip the obvious ones; an observer catches what they take for granted.
Want your top procedures written and tested for you? Explore Operations Management or grab a free template. Ready to talk? Book a strategy call.