How to write a one page standard operating procedure
Write an SOP that someone will actually follow: one page, written while doing the task, tested by a colleague and owned by a named person.
Training by sitting next to somebody
In most businesses under fifty people the process lives in one person's hands. A new joiner learns by watching, asking and getting it wrong twice. That works until the experienced person is on leave or resigns or is simply too busy to be interrupted eleven times in a morning.
The usual response is a documentation drive. Somebody produces a long formal document with a cover page and version history, circulates it, and nobody opens it again. The length is the reason. A procedure that takes twenty minutes to read loses to a two minute phone call every single time. One page is not a stylistic preference. It is the only form that gets used.
What an SOP costs and what it cannot capture
An SOP cannot carry judgement. Pricing a complicated job, handling an angry client or deciding whether to extend credit all depend on context that no document holds. Attempting to write those down produces either a list of platitudes or a rule that is wrong in the interesting cases. Document the mechanical parts and name the person who decides the rest.
The cost is the time of your most capable person, because the SOP has to be written by somebody who does the task. Expect an hour per procedure including the test run. Then there is maintenance, which is the cost people forget. A stale procedure is worse than none at all since it sends a new person confidently in the wrong direction.
Which tasks deserve one and which do not
Do not document a process that runs rarely and differs every time. An annual exercise that is substantially redesigned each year will have changed before anyone reads the page. Write a short note of what went wrong last time instead and keep it with the file.
A two person business where both people do everything should also skip this. There is no handover to protect and the writing time is better spent on work. The same applies to genuinely bespoke creative work where the process is the thinking.
The tasks worth one page are frequent, repeatable and currently known to only one person. Raising the monthly invoice run. Onboarding a new client. Closing the premises. Dispatching an order. Running payroll inputs. If the business would stumble when one named person is unreachable then that task is your first page.
How to write it
Write it while doing the task rather than from memory. Open a blank page, perform the work and record each step as you take it. Memory smooths over the fiddly parts and the fiddly parts are exactly where a new person stops.
Five things belong on the page. The trigger that starts the task. The steps in order with the exact system and field names. The decision points and what to do at each. What finished looks like, stated plainly enough to check. And the name of the person to ask when reality differs from the page.
Then test it. Hand it to a colleague who has never done the task and let them follow it exactly while you watch without helping. Every pause is a missing step. This half hour is the whole difference between a page that works and a page that merely exists. Finish by putting a named owner and a review date at the top.
How to judge whether it is working
The count of SOPs written flatters more than any other operations metric. A folder of forty procedures looks like capability and may represent nothing but one busy fortnight.
What matters is whether a new person can complete the task unaided on their first attempt. That is observable and it is the only test that counts. Watch also how often the author still gets interrupted about that task. Interruptions continuing at the same rate mean the page is not trusted or not findable, and both are fixable. A page nobody can locate when they need it has failed as surely as a page that is wrong.
The common mistake
Running a documentation sprint across the whole business. Somebody decides everything will be written up this quarter and assigns the work broadly. The output is a large set of untested pages written at a safe distance from the actual task. This is expensive twice over. You pay for the writing and then you pay again when a new joiner follows an inaccurate page and makes a real error in a client's account.
The related error is having the manager write it. The person who supervises a task usually remembers the shape of it and not the three undocumented workarounds that make it function. Those workarounds are the content.
Keeping the page alive
Give every procedure one owner and one review date, then actually revisit it. The best moment to update a page is the first time somebody follows it and finds a discrepancy, so make correcting it the expected behaviour rather than an escalation. When a process is retired, delete its page rather than leaving it in the folder. An archive of obsolete procedures is how a well intentioned library turns into something nobody trusts.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.