A standard operating procedure (SOP) is only useful if someone opens it at the moment they need it and can follow it without asking for help. Many SOPs fail that test because they are long, vague or out of date. Here is a practical way to write ones that work.
Write it while someone does the task
Do not write from memory. Sit with the person who does the task well, or record their screen, and capture each step as it happens. You will catch the small decisions that experienced people no longer notice they are making.
Start every SOP with three lines
- Purpose: what this task achieves and why it matters.
- When to use it: the trigger, such as "every new client enquiry".
- Owner: who is responsible for doing it and who keeps the SOP up to date.
Use numbered steps with one action each
"Open the client folder and rename the file using the date format" is two actions. Split it. Start each step with a verb. Add a screenshot only where the screen is confusing.
Show what "done" looks like
End with a short checklist or an example of a finished output. This is what lets a new team member check their own work.
Keep them where the work happens
An SOP buried in a shared drive folder nobody visits will not be used. Link it from the tool or checklist where the task begins, and keep all SOPs in one organised library.
Review on a schedule
Give every SOP a review date. When a process changes, update the document before you explain the change to the team, then point them to it.
Good SOPs free owners from answering the same questions and give new hires confidence. They are one of the most valuable assets a small business can build.
