An SOP goes out of date for one reason: it has no owner and no trigger. Someone writes it once, it gets filed, and nothing ever tells anyone to change it when the machine, the price, the supplier or the person changes.
Why do SOPs written once go out of date within a month?
A document with no owner has no expiry date, so it is correct forever in the filing cabinet and wrong within a month in the workshop.
- A process causes a problem, so somebody writes it down properly.
- It goes into a folder, on the office computer.
- Three weeks later the supplier changes their terms, or the machine is swapped, or the best person leaves.
- Nothing prompts a change, so the page stays exactly as it was.
- A new starter follows it, it does not work, and the document loses its authority.
That last point is the expensive one. A document staff have learned is unreliable is worse than no document: they stop opening it and go back to phoning whoever answers.
How long should an SOP be?
Short enough to read in five minutes at the workstation: usually one side of a page, or two screens on a phone. Past that you have written a manual, and a manual will be out of date before you finish it. A useful test: more than about seven steps means it is probably two SOPs, and needing a table means it is probably a checklist.
What sections should every SOP have?
Keep the same set every time: it is what lets a new person open an unfamiliar process and know where to look.
| Section | What goes in it |
|---|---|
| Title and job name | The plain name, not a code |
| Owner | One named person, with a phone number |
| Applies to | The roles, machines or sites covered |
| When to use it | The trigger in one line: when this happens, open this page |
| Tools and materials | With quantities, so nobody is short on day one |
| Steps | Numbered, verb-first, one action per line |
| Decision points | The "if this, then that" lines people forget |
| Common mistakes | The three that happen, and how to undo them |
| Safety | What must never be skipped |
| Last revised | The date, and the name of who revised it |
| Related SOPs | Links to the next page they will need |
Print the owner and the revision date in the header. Those two lines make the document alive, and they stop it becoming shelfware.
How do you write steps people will actually follow?
Write what happens, not what ought to happen. The moment a document describes a better process than the real one, staff stop trusting it and start improvising.
- Start each step with a verb: "Open the valve", not "The valve should be opened".
- One action per line. If a line contains "and", it is probably two steps.
- Use the real names: the name on the machine, the name your supplier uses, the name your staff say out loud.
- Put the photograph on the same page as the step it illustrates.
- Write the exception straight after the step it applies to, not in a section at the end.
- Read it aloud to the person who does the job. If they wince, rewrite it.
Who should own each SOP?
One named person, never a department and never "the office". Ownership belonging to a group belongs to nobody.
The owner is not necessarily the author, and should not be the most senior person. The right owner does the job most often, has the authority to change it, and will notice when it no longer matches reality. Give them three things: authority to change the page without permission, ten minutes a month, and their name on it. The name on the page does more for the document's survival than any filing system.
How often should you review an SOP?
Do not rely on a calendar. Calendars get skipped, and they force review of a process that has not changed while ignoring one that changed last Tuesday. Use a trigger, with a calendar sweep as a backstop.
| Trigger | What it must cause |
|---|---|
| A mistake that gets past the process | Review within the week it happened |
| A machine, vehicle or tool is replaced | Review before first use |
| A supplier, price, policy or client changes | Review the same week |
| A key person leaves or changes role | Review within a month |
| A new shortcut appears | Decide whether to write it in or write it out |
| A new starter gets stuck on it | Review immediately; free feedback |
Alongside the triggers, run a quarterly sweep of every page: open it, check the revision date, and ask the owner one question: is this still true? Twenty minutes on a fixed afternoon catches what the triggers miss.
How do you find out an SOP is wrong without reading every one?
Four cheap signals, all upstream of the customer finding out.
- The correction log. Every time someone does a job differently from the page, note it. That log is your review queue, already sorted.
- The "that is not what the page says" message. Make it free to send, and treat it as a gift rather than criticism.
- The unprompted phone call. If staff ring the owner with a question that has a page, the page failed. Count those calls weekly.
- The duplicated page. Two versions in two folders is the most common reason an SOP stops being trusted. Keep one copy, in one place.
How do you stop SOPs becoming shelfware?
Put the document where the work happens, in the format the work happens in.
- One printed copy at the workstation, in a protector, replaced when revised.
- One laminated copy in the vehicle for anything done on site. It will get wet.
- One searchable digital version, for anything looked up on a phone.
- One copy only. A second version in someone's inbox is how drift starts.
- A spoken version: at the start of a shift the owner says the step that changed this week. Fifteen seconds.
- The knowledge base is the same content, not a parallel system. Two copies means one is wrong and nobody knows which.
At Midlands Berry Farm, a 60-person operations team, the processes were written with a named owner and a review trigger rather than filed and forgotten — taking onboarding from four weeks to four hours, 3x faster onboarding, 40% more time saved, and answers available at any hour.
How do you get started this month?
- Pick the process that caused the most recent expensive mistake, not the easiest one to describe.
- Sit with the person who does it daily and record them walking through it.
- Write it to the section list above, on one page, with photographs of your own equipment.
- Name the owner and print their name and the date in the header.
- Put the review triggers in the diary, plus the quarterly sweep as a fixed afternoon.
- Print it for the workstation, delete every other copy, and test it on the next new starter.
If you would rather have someone outside the business look at whether your processes would survive losing their owner, book a free strategy session and we will review it with you.