HomeGuides › SOP builder

How to write a procedure people will follow

If only one person knows how to do it, the business has a problem that is invisible until they are unavailable.

An SOP writes down how something is done, so it survives holidays, illness and people leaving — and so it is done the same way each time.

Step-by-step

  1. State what it is for and when it applies.
  2. List the steps in order.
  3. Note who does each where more than one person is involved.
  4. Record the exceptions — the part that carries the real knowledge.

Write for someone who does not know

The commonest failure is writing for yourself. "Process the order" means nothing to someone new; "open the orders queue, check the address against the payment record, then print the picking list" is a procedure.

The test: could a competent new colleague follow this without asking? If not, it is notes rather than an SOP.

Exceptions are where the value is

The happy path is usually obvious. The knowledge worth capturing is what to do when the address does not match, when the item is out of stock, when the customer has already been refunded. That is precisely what lives in one person's head and vanishes with them.

Have someone else test it

The only reliable check. Give it to someone who does not know the process and watch them follow it without helping. Every hesitation marks a gap. This is uncomfortable and it works better than any amount of re-reading.

Keep them current

An out-of-date SOP is worse than none, because it is followed. Put a review date and an owner on each, and update it when the process changes rather than when the review falls due.

Start with the procedures where the cost of getting it wrong is highest, or where only one person knows how. Documenting everything at once fails; documenting the two or three that matter succeeds.

Frequently asked questions

How detailed should an SOP be?

Detailed enough that a competent newcomer can follow it without asking. That is the test, and it is usually more detail than the person who does the task expects.

What should I document first?

The procedures where errors are most costly, and those only one person knows. Attempting to document everything at once reliably produces nothing.

How do I know if it works?

Have someone unfamiliar follow it while you watch without helping. Every point where they hesitate is a gap to fix.

Open the decision tools →