Many SOPs are written by the person who does the task every day. They skip the steps that feel obvious to them — which are exactly the steps a new person needs. The result is a document that experts do not need and newcomers cannot use.
The shape of a usable SOP
- Purpose: one sentence on what the procedure achieves and when to use it.
- Before you start: access, tools and information needed.
- Steps: numbered, one action per step, starting with a verb.
- Expected result after key steps: “You should now see the invoice in ‘Pending’.”
- What to do if something goes wrong, and who to ask.
- Owner and last-reviewed date.
Process the refund in the system after checking eligibility and inform the customer accordingly.
1. Open the order in the billing tool (Orders → search by order ID). 2. Check the delivery date is within 14 days; if not, stop and use the ‘Late refund’ SOP. 3. Select Refund → Full refund. You should see status ‘Refund initiated’. 4. Send the ‘Refund confirmation’ email template from the order page.
Test it with someone new
Watch a person who has never done the task follow the SOP, without helping. Note every pause and question. Each one is a missing step, an undefined term or a missing screenshot.
Give it an owner
Systems change; SOPs drift out of date silently. A named owner and a review date make it someone’s job to notice.
Examples in this guide are fictional and written for teaching — not client material or measured results.
