
The short answer
What to know before you act
An SOP should define its purpose, trigger, owner, required inputs, sequence, quality checks, evidence of completion and escalation conditions. Write for the person performing the work. Validate it through a supervised attempt before treating the document as the operating standard.
- Choose a bounded task: a complete department manual is a poor first draft.
- Record exceptions: predictable uncertainty needs an explicit response.
- Test usability: a document is not installed merely because it has been uploaded.
A process document can be accurate and still unusable. It may explain what an experienced employee remembers to do without stating the inputs, checks or judgement a new operator needs.
Start with one job that repeats and matters. Observe it being done, record the points where decisions occur and test the instructions with someone who was not involved in writing them.
What does the operator need at each point?
| What you see | What to check | Next move |
|---|---|---|
| Before starting | Trigger, authorised owner and complete inputs | Stop or escalate when prerequisites are missing. |
| During the work | Sequence, decision rules and relevant safety controls | Make judgement points explicit rather than hiding them in “check carefully.” |
| Before completion | Quality standard, evidence and next recipient | Confirm that the output is usable downstream. |
| When something changes | Version owner, review trigger and exception record | Update the standard after a controlled review. |
A dispatch SOP that prevents an incomplete handoff
Hypothetical example · not a client case study
Imagine a wholesaler whose dispatch instructions say only “pack and send confirmed orders.” A new employee does not know how to recognise confirmation, check the delivery address or handle a stock discrepancy. The founder keeps correcting shipments after packing.
The revised procedure begins with a released order, a verified address and an availability check. It specifies who can approve substitutions and what record accompanies the parcel. A trained colleague follows the draft under supervision; questions and missed checks become revisions. The test compares errors and handoff completeness, not the number of pages written.
- 01TriggerA complete job enters the process
- 02ExecuteFollow steps and decision rules
- 03VerifyCheck output against the standard
- 04HandoffRecord completion or escalate
Write, test and maintain one usable procedure
1. Observe the real task
Watch a normal execution and ask the operator why each decision is made. Capture the documents, systems and permissions actually used. Distinguish required controls from personal preferences; do not remove safety or compliance requirements to make the procedure shorter.
2. Draft for action
Use short steps with clear inputs and outputs. Define terms that a newcomer may not know. Include a checklist where omissions are costly and a decision rule where conditions vary. State where the operator should stop rather than improvise.
3. Test and appoint an owner
Have another trained person attempt the task with appropriate supervision. Record where they need oral clarification. Assign a version owner and a review trigger, such as changed equipment, repeated errors or an altered customer requirement. Make the current version easy to find.
Put it to work
One-task SOP builder
Work through the four prompts using evidence from your business. These notes stay in this page, are not sent or saved, and disappear when you reload. Copy them before leaving.
Define the boundary
State the purpose, trigger, owner and prerequisites.
Write the sequence
List the actions, decision points and required controls.
Define completion
Specify the output, checks, evidence and next recipient.
Run a supervised test
Record questions, failures and the version owner.
Choose your next step
Keep the SOP close to the work. Its job is to support consistent execution and learning, not to demonstrate that the business owns a large folder of documents.


