An SOP (standard operating procedure) is a written set of steps for doing a recurring task the same way every time. It says what triggers the task, the steps to follow and what done looks like so the result doesn't depend on who does it.
What an SOP is for
Every business repeats the same tasks: quoting a job, onboarding a client, paying a supplier, opening the shop. When the steps live in someone's head, the result depends on who turns up that day. An SOP writes the steps down once so anyone trained can get the same result.
That gives you three things. Consistency, because the work is done the same way. Delegation, because you can hand a task over without standing over it. And training, because a new hire learns from the SOP instead of from you. More and more, there is a fourth: your AI reads the same SOPs so it answers from how your business actually works.
What goes in a good SOP
- A title that is an action. "Send the welcome pack", not "Welcome pack info".
- The trigger. What starts the task, such as "deposit received".
- An owner. The person accountable for keeping it current. See process owner.
- Numbered steps, action first. One action per step, written so someone new could follow it.
- A definition of done. How the person knows the task is finished and right.
- Supporting material. Templates, a short video or a checklist linked where they are needed.
A quick example
SOP: Send the welcome pack to a new client
Trigger: the client's deposit is paid.
- Create the client's folder from the project template.
- Send the welcome email template with the kickoff booking link.
- Post the welcome pack to the delivery address on the signed proposal.
- Add the kickoff call to the project board.
Done when: the client has the email, the pack is posted and the kickoff is booked.
SOP vs process vs policy
| Term | What it answers | Example |
|---|---|---|
| Policy | What is the rule? | Refunds within 30 days, no questions asked. |
| Process | What happens end to end and who is involved? | Refund request, approval, payment, follow-up. |
| SOP | How do I do this one task? | Process a refund request. |
| Work instruction | Exactly how do I do this one step? | Issue the refund in your payment system. |
More on this in policy vs procedure and what is a work instruction.
Common mistakes
- Too much detail too soon. Match the detail to who does the task. A skilled professional needs guidelines. A new starter on a task-based job needs every step.
- The owner writes them all. It stalls fast. Record the person who does the task and have someone else draft it for them to edit. See knowledgeable worker.
- Starting with everything. Document the 10 to 15 steps your clients pass through first: your Critical Client Flow.
- Filing them where nobody looks. An SOP nobody can find doesn't exist. Keep them in one single source of truth.
Ready to write one? Follow how to write an SOP, browse SOP examples or start from our free SOP templates.
Frequently asked questions
What does SOP stand for?
SOP stands for standard operating procedure: a written set of steps for completing a recurring task the same way every time.
How long should an SOP be?
As short as it can be while still letting a trained person get the right result. Most SOPs are a trigger, five to fifteen numbered steps and a definition of done. If it runs much longer, split it into separate SOPs or move the fine detail into work instructions.
Who should write SOPs?
The person who does the task should provide the know-how but they rarely need to write it. Record them doing the task, have someone else draft the SOP and let the person who does the task edit it. Editing a draft is much faster than starting from a blank page.
Put your systems in one place
systemHUB is SOP software built around the SYSTEMology method. Document how your business runs, train your team and connect your AI to the real thing.
14-day free trial. No credit card required.
