How to Write a Clear SOP (Standard Operating Procedure)
The one person who knows how to close out the month is on vacation.
Everyone else improvises. The report goes out two days late, with three numbers wrong.
Nobody documented the process, because nobody thought they needed to.
Why “Just Ask Sarah” Isn’t a Process
When a task lives entirely in one person’s head, it isn’t a process. It’s a dependency.
It works fine until that person is out sick, on leave, or gone for good. Then the gap shows up all at once.
What Most SOPs Get Wrong
Most fail in one of two directions.
Too vague to follow: “communicate with the client regularly.” Or too bloated to read: fifty steps documenting a five-minute task.
A usable SOP sits between the two. Specific enough that a new hire could follow it unsupervised. Short enough that anyone actually will.
What a Clear SOP Actually Needs
Four things, no more:
- Purpose: why this process exists
- Trigger: when to use it
- Steps, in order, including the workarounds people actually use
- An owner for each step
Skip the workarounds and the document describes a process that doesn’t match reality. That’s the version that gets ignored.
The SOP Builder Template walks through exactly this structure, one section at a time.
Written Once, Used Every Time
An SOP takes an afternoon to write.
It saves every afternoon after that.
Write it down once, and the process stops depending on who happens to be in the office.
