A standard operating procedure, or SOP, is a short written description of how a task is done in your business, step by step, so that anyone trained to do it gets the same result. The ones that work are short, written with the people who do the job, and kept somewhere the team already looks.
Why most procedures gather dust
When I start working with a business, there is often a folder called Procedures or Staff Handbook. It was written in a burst of effort before an audit or after a mistake, and a year later nobody opens it.
Usually it is too long. Nobody reads twelve pages while a customer is waiting on the phone. Often a manager wrote it, describing how the task ought to go, while the person who does it every day does something slightly different. It tends to live in a shared drive while the work happens in a job system or on a phone, so the two never meet. And nobody owns it, so when the process changes the document stays as it was and people learn to ignore it.
What the evidence says about checklists
The strongest evidence I know for short, written steps comes from surgery. In 2009 a team led by Alex Haynes published a study of a 19 item surgical safety checklist introduced in eight hospitals around the world. After the checklist came in, the rate of death after major operations fell from 1.5% to 0.8%, and inpatient complications fell from 11% to 7% (New England Journal of Medicine, summarised by the Harvard Gazette).
The study compared results before and after, so it shows a strong association, and the checklist was probably not the only thing that changed. Even so, if a short list of checks helps experienced surgical teams avoid mistakes, it can help your office send an accurate quote or your site team lock up properly on a Friday.
Decide what to write first
You do not need a procedure for everything. Start with the tasks that are done often, such as quoting, booking jobs and invoicing. Then the ones that are costly when they go wrong: ordering materials, handling client money, anything a regulator might ask about. Then anything only one person knows how to do. If someone being off sick would stop a task, write that one first.
Most small businesses find that ten to fifteen procedures cover most of what matters.
A format people use
I keep every procedure to the same shape, so people know where to look:
- A title that names the task, such as “Sending a quote”.
- One sentence on when it applies.
- Numbered steps, each starting with a verb: open, check, send, record.
- What done looks like, so people know when they have finished.
- Screenshots or photos where a step is easier to show than describe.
- An owner and a review date at the bottom.
Write it with the person who does the task. Sit with them while they do it and write down what they do, workarounds included. Then hand the draft to someone who has never done the task and watch them follow it. Wherever they hesitate, that step needs rewriting.
Keep them where the work happens
A procedure that takes five clicks to find will not get used. Link each one from the place the task starts: the job board, the quote template, the onboarding checklist. In most workflow platforms you can attach the procedure to the board itself, so the steps sit next to the work.
Keep them up to date
The procedures that last are the ones that change as the work changes. When someone finds a better way, they tell the owner and the document is updated that week. New starters work from the procedures in their first month and point out anything confusing, which is the cheapest test you will ever get. Once a year, the owner checks each procedure against what happens on the ground.
If you want to see where your own processes stand, the free operations health checklist has a section on procedures. This is also a large part of my operations consulting work.
