Most SOP templates you find online are built to look thorough, not to be used. They have a dozen sections, a revision-history table, an approvals matrix, and pages of detail that nobody reads twice. They get written in a burst of enthusiasm, saved in a shared drive, and never opened again. The business is no better off, just guiltier.
A good SOP is different. It is short enough to read in two minutes, specific enough that someone could follow it without asking questions, and simple enough that the person who does the task can keep it current. The format below is the one we use with growing businesses. It is deliberately minimal. Copy it, fill it in, and you have a working SOP.
What an SOP Is For
Before the template, be clear on the job an SOP does, because it shapes how you write it.
An SOP exists so that a task gets done the same way, to the same standard, regardless of who does it. It removes the task from one person's head and makes it repeatable. That is the whole point. If a process only one person can do correctly is a risk to the business, an SOP is how you remove that risk. This is the same problem we describe in why your business needs SOPs: the knowledge that lives in one person's memory walks out the door when they do.
So an SOP is written for the person who will follow it, not for a manager who wants to feel organised. Every section earns its place by helping that person do the task right. Anything that does not is clutter.
The Template
Here is the full format. Six sections, no more.
1. Title. Name the SOP for the task it covers, in plain language. "Onboarding a New Client" or "Processing a Refund", not "Client Engagement Procedure v2". The title should make it obvious what this document is for at a glance.
2. Purpose (one or two sentences). Say what this process achieves and why it matters. "This ensures every new client receives the same onboarding experience and nothing is missed in their first two weeks." This gives the reader context so they understand the point, not just the steps.
3. When to use it (the trigger). State exactly what starts this process. "Use this when a client signs the contract." A clear trigger stops the SOP from being ambiguous about when it applies.
4. Who owns it. Name the role responsible for the process and for keeping the SOP current. Role, not person, so it survives staff changes. "Owner: Operations Lead." If nobody owns it, it goes stale.
5. The steps. This is the heart of it. Number the steps in the order they happen. Each step is one action, written as an instruction starting with a verb. "Send the welcome email from the shared template." "Create the client folder in the drive." Be specific enough that someone new could follow it without guessing, including where to find things and what to use. If a step has a decision in it, state the condition: "If the client is on the premium plan, also schedule a kickoff call."
6. Definition of done. State how the person knows the task is complete and done correctly. "The client has received the welcome email, has access to their folder, and the first invoice is scheduled." This is the quality check, and it is the section most templates leave out. Without it, "done" is a matter of opinion.
That is the entire template. Title, purpose, trigger, owner, steps, definition of done. If you find yourself wanting to add more sections, you are probably writing a manual, not an SOP.
A Filled-In Example
To show how short it should be, here is a complete SOP in the format above.
Title: Sending a Client Invoice
Purpose: Ensures every invoice is accurate, sent on time, and recorded, so cash flow is predictable and nothing slips.
When to use it: At the end of each month for retainer clients, or when a project milestone is reached for project clients.
Owner: Finance Lead.
Steps:
- ·Open the billing tracker and find the client's agreed amount for this period.
- ·Create the invoice in the accounting tool using the client template.
- ·Check the amount, the dates, and the payment terms against the contract.
- ·Send the invoice to the client's billing contact, copying the account owner.
- ·Mark the invoice as sent in the billing tracker with the date.
Definition of done: The invoice is sent to the correct contact, recorded as sent in the tracker, and shows in the accounting tool as outstanding.
That is a usable SOP. Anyone in the business could pick it up and send an invoice correctly. It took five minutes to write and takes thirty seconds to read.
How to Write One That Gets Used
The template is the easy part. Making SOPs that stay alive is the real skill, and it comes down to a few habits.
Write it while doing the task, not from memory. The most accurate SOP is captured by the person doing the work, in the moment, noting each step as they take it. Writing from memory misses the small steps that turn out to matter.
Keep it short. If an SOP runs past a single page, ask what can be cut. Detail that does not change the outcome is noise that makes the document less likely to be read.
Use plain language. Write as you would explain it to a new colleague. No jargon, no formal procedure-speak. The test is whether someone new could follow it without asking you anything.
Store them where the work happens. SOPs buried in a drive nobody opens are dead. Keep them in the tool the team already uses, linked from where the task starts.
How to Keep Them Current
An SOP is only useful if it matches reality. Processes change, and an SOP that describes an old way of working is worse than none, because it actively misleads.
Give every SOP an owner, which the template already does, and make keeping it current part of that role. Review them on a light schedule, a quick pass every quarter, and update them whenever the process genuinely changes. The owner does not need permission to fix an SOP when reality moves. They just keep it true.
The lightest discipline that works is this: when anyone follows an SOP and finds it wrong or unclear, they flag it, and the owner fixes it. That keeps documents accurate through use rather than through a heavy formal review nobody has time for.
How Detailed Should an SOP Be?
The most common question once people start writing is how much detail to include. Too little and the SOP does not actually ensure consistency. Too much and nobody reads it. The right level depends on who follows the process and how often.
A useful rule is to write for the least experienced person who will realistically do the task. If a process is only ever done by an experienced specialist, the SOP can be lighter, a checklist of the key steps and the definition of done, because the person already knows the craft. If a process will be handed to a new hire or someone outside their usual area, it needs more detail: where to find things, what each step looks like when done right, what to do when something is unusual.
Frequency matters too. A task done daily needs less detail, because the person will internalise it quickly and the SOP is mostly a backstop. A task done once a quarter needs more, because nobody remembers the steps between times, and the SOP is doing the real work of reminding them.
When in doubt, write the leaner version first and let it earn detail through use. Every time someone follows it and gets stuck or makes a mistake, the owner adds the line that would have prevented it. This grows the SOP to exactly the level of detail the process actually needs, rather than the level you imagined it might need when you wrote it cold.
Where SOPs Fit in the Bigger Picture
A folder of SOPs is not the goal. The goal is a business that runs on repeatable processes rather than on the founder and a few key people holding everything in their heads. SOPs are one of the tools that get you there, alongside clear ownership and the right systems. They are also what makes delegation actually work, because you can hand over a task with a document instead of a lengthy explanation that has to be repeated for every new hire.
Start with the processes that hurt most when they go wrong or when the person who knows them is away. Document those first, in this format, and expand from there. A handful of good, used SOPs beats a binder full of detailed ones nobody opens.