To write an SOP people follow, start from how the work is actually done, not how it should be done: one procedure per job, one action per step, in the words the team uses, with the exceptions included. Every standard operating procedure needs a purpose, scope, trigger, roles, steps, exceptions, systems, records, an owner, a review date and a version. Test it on someone who has never done the job before you publish it.
SOP, procedure or work instruction?
A standard operating procedure (SOP) describes how one team carries out a recurring job, the rules it follows and what to do when something goes wrong. It sits between the process map, which shows the job across teams, and the work instruction, which shows how to click through one screen. If your SOP is turning into screenshots of every field, move those into work instructions and link to them.
Write one when a job is done often, by more than one person, and mistakes are costly or noticed by customers. Do not write one for a task done once a year by the same person; a checklist will do.
What goes in a standard operating procedure
| Section | What it says |
|---|---|
| Purpose | Why the job exists, in one or two sentences |
| Scope | Where it starts and ends, and what it does not cover |
| Trigger | The event that starts it: an email, a date, a status change |
| Roles | Who does each part, who approves, who stands in |
| Steps | Numbered, one action each, in order |
| Exceptions | The known things that go wrong and what to do about each |
| Systems | Where the work happens and where the record lives |
| Records | What evidence is kept, where and for how long |
| Owner | The person responsible for keeping it accurate |
| Review date | When it is next checked against a real case |
| Version | Number, date and what changed |
Most SOP templates stop at the steps. The exceptions, the owner and the review date are what decide whether the document is still true in six months.
How to write an SOP: seven rules
1. Start from the map and the interviews
Do not write from memory or from the system manual. Use the process map and the notes from the people who do the job (see how to map a process). Each step should be traceable to someone who does it. If you cannot say who told you a step happens, check before you write it down.
2. Write the way the team talks
If the warehouse calls it “the pick sheet”, call it the pick sheet, not “the outbound fulfilment document”. Use the field names people see on screen. Short sentences, in the imperative: “Check the PO number against the invoice”, not “The PO number should be verified”.
3. One action per step
“Check the order, enter it in NetSuite and email the warehouse” is three steps. Split it. A step with one verb is easy to follow, easy to tick off and easy to spot when it is skipped. If a step needs a decision, say what the decision is and where each answer leads.
4. Put the exceptions next to the steps
Do not hide exceptions in an appendix. If step 4 is “check stock” and the stock figure is often wrong, the instruction for what to do then belongs at step 4. Lesson 4 covers how to find and document exceptions in more depth.
5. Say who, not “someone”
“The order is approved” leaves the reader asking: by whom? Name the role every time, and say who stands in when that person is away.
6. Test it on someone new
Give the draft to someone who has never done the job, such as a new starter or a colleague from another team, and ask them to follow it on a real case while you watch, without helping. Every time they hesitate or ask a question, the SOP is missing something. Fix it and test again. This is the most useful step and the one most often skipped.
7. Keep it where the work happens
An SOP three folders deep in a shared drive will not be read. Link it from where the work starts: pinned in the team channel, linked from the ticket view in HubSpot, on the wall by the packing bench, in the help text of the form. If people need it, it should be one click away.
SOP template
Copy the template below into Word, Google Docs or your wiki. The sample wording uses a customer order at a wholesaler as the example; replace everything in brackets.
Title: [verb + object, e.g. Enter and confirm a customer order]
SOP number and version: [e.g. OPS-012, v1.0] · Owner: [role] · Approved by: [role]
Effective from: [date] · Next review: [date, e.g. six months on]
1. Purpose
[e.g. Get every customer order into NetSuite correctly on the day it arrives, so the warehouse can pick it and finance can invoice it without rework.]
2. Scope
Starts when: [e.g. an order email arrives in the sales inbox]
Ends when: [e.g. the order confirmation is sent to the customer]
Does not cover: [e.g. quotes, returns, orders placed through the web shop]
3. Trigger
[e.g. A new email in the shared sales inbox with an order attached or written in the body.]
4. Roles
Does the work: [e.g. sales coordinator]
Approves: [e.g. sales manager, for discounts over the usual limit]
Stands in: [e.g. sales manager]
Is informed: [e.g. warehouse lead]
5. Before you start
[Access and information needed, e.g. HubSpot and NetSuite logins, the current price list, the stock spreadsheet.]
6. Steps
- [e.g. Open the order email and tag it “In progress” in Outlook.]
- [e.g. Find the customer in HubSpot. No account? Go to exception A.]
- [e.g. Check each line against the stock spreadsheet. Short? Go to exception B.]
- [e.g. Check prices against the current price list. Different? Go to exception C.]
- [e.g. Enter the sales order in NetSuite, copying the customer’s PO number.]
- [e.g. Send the order confirmation to the customer from NetSuite.]
- [e.g. Move the email to the “Entered” folder.]
7. Exceptions
| If… | Then… | Who decides |
|---|---|---|
| A. The customer has no account | [e.g. Create a draft account and ask finance for a credit check] | [e.g. Finance lead] |
| B. A line is out of stock | [e.g. Phone the customer, offer a substitute or a later date] | [e.g. Customer, with sales manager for substitutes] |
| C. The price differs from the price list | [e.g. Hold the order and ask the sales manager] | [e.g. Sales manager] |
| D. No PO number | [e.g. Email the customer and hold the order] | [e.g. Sales coordinator] |
8. Systems
[e.g. Outlook (inbox), HubSpot (customer record), stock spreadsheet (availability), NetSuite (system of record for orders).]
9. Records
[What is kept, where and for how long, e.g. original order email kept in the “Entered” folder; order and confirmation in NetSuite.]
10. Related documents
[Process map, work instructions, price list, exception log.]
11. Change log
| Version | Date | What changed | Who confirmed it |
|---|---|---|---|
| 1.0 | [date] | First version, tested with a new starter on [case reference] | [role] |
Once the SOP exists, the job is keeping it true. The next lesson covers the exception log that sits alongside it, and the course overview at map your business processes lists every lesson.
If you want to see which of your processes is worth documenting first, the free Bonofici grader reads your company’s public pages and shows where to start.