An SOP is useful only if someone who has never done the task can complete it correctly from the page. Many SOPs fail that test because they were written by the expert, for the expert. Here is a structure that works for most operational tasks.
Start with five lines of context
Before any steps, answer these at the top of the document. They take two minutes and prevent most confusion later.
- Purpose: what this task achieves, in one sentence.
- Trigger: what starts it (a form arrives, the first Monday of the month, a client signs).
- Owner: the role responsible for the outcome, not just the person doing it today.
- Inputs: what you need before starting, and where it lives.
- Done means: how you know the task is complete and correct.
Write steps as actions, one per line
Each step should start with a verb and describe one action: "Open the onboarding sheet", "Check the GST number against the invoice", "Move the card to Ready". If a step contains "and", it is probably two steps.
Name the exact system, folder or field. "Update the tracker" is ambiguous when a team has three trackers.
Add a screenshot only where the screen is confusing. Screenshots age quickly; text is easier to keep current.
Make decisions explicit
Most of the real knowledge in a process lives in its decisions. Write them as if/then rules wherever you can: "If the amount is above the approval limit, send to the finance lead before processing."
Where a decision genuinely needs judgement, say so and say who makes it. That is not a weakness in the SOP — it is accurate, and it tells anyone automating the task later where a human checkpoint belongs.
Capture exceptions separately
Keep the main steps for the normal case. Put the unusual cases in a short "Exceptions" section at the end: missing information, duplicates, urgent requests, a system being down. For each, state what to do and who to tell.
Test it with someone new
Ask a teammate who has not done the task to follow the SOP on a real example while the author watches silently. Every question they ask is a gap in the document. Fix those gaps the same day.
Then add a review date. An SOP that has not been checked in six months is probably describing a process that no longer exists.
Key takeaways
- Purpose, trigger, owner, inputs and "done" come before the steps.
- Decisions and exceptions hold most of the knowledge — write them down explicitly.
- The real test is a new person completing the task from the page alone.
