Your business runs on dozens of small procedures — how you quote a job, onboard a client, chase an unpaid invoice. Right now, most of them live in one place: your head. That works until you take a week off, hire someone, or find yourself doing the same task for the hundredth time and still giving it your full attention. A standard operating procedure (SOP) is simply that knowledge, written down so the task can be repeated without you.
The takeaway up front: an SOP is a documented, step-by-step description of how one recurring task gets done to your standard — and writing them is among the highest-leverage admin jobs a small business owner can do, because it's what lets you delegate, hire, stay consistent, and eventually step back. You don't need a binder of them or a compliance department — just a handful of clear, current documents for the tasks that matter most, in a format people actually follow. This guide covers what to document first, how to structure an SOP, a template and worked example to copy, and the mistakes that leave most SOPs unread. The example below is illustrative — adapt it to your business.
What a standard operating procedure actually is
An SOP answers one question: "How exactly do we do this, every time, so it comes out right?" It isn't a policy (which sets a rule) or a mission statement. It's the practical, repeatable recipe for a single task — specific enough that someone competent but new could follow it and get the same result you would.
For a small business, SOPs quietly solve several expensive problems at once:
- Consistency. Customers get the same experience whether you, your newest hire, or a stand-in does the work.
- Delegation without hand-holding. You hand over a document, not a week of shadowing.
- Faster onboarding. New people ramp on written procedures instead of interrupting you all day.
- Fewer mistakes. The steps that are easy to forget sit on the page, not in someone's memory.
- A business that isn't trapped in your head. The more you document, the less the business depends on you personally — which is what makes it easier to sell, or to take a holiday.
If that sounds corporate, reframe it — an SOP is just you explaining a job clearly to someone you trust.
Decide what to document first
The fastest way to abandon SOPs is to document your whole business in a weekend — you won't finish, and the half-empty folder will convince you the idea failed. Write them in priority order instead, scoring each task on three things:
- Frequency — how often it's done. Daily tasks earn their SOP faster than yearly ones.
- Cost of getting it wrong — a botched client handover or payroll run hurts; a mislabelled folder doesn't.
- Bus factor — how much it lives only in one person's head (usually yours).
| Task | How often | Cost if wrong | Only you know it? | Priority |
|---|---|---|---|---|
| Onboarding a new client | Weekly | High | Yes | Write first |
| End-of-day cash & close | Daily | Medium | No | High |
| Responding to an enquiry | Daily | Medium | Partly | High |
| Annual insurance renewal | Yearly | Medium | Yes | Later |
Start with tasks that are frequent, costly to fumble, and locked in your head — they steal the most time and carry the most risk, so they pay back fastest. These documents are the building blocks of the wider systems in the small business operations guide; SOPs are where "get organised" turns concrete.
The anatomy of an SOP people actually follow
A good SOP is short, scannable, and unambiguous. Whatever tool you write it in, include these parts:
- Title & purpose — a plain name ("Onboarding a New Client") and one line on what it achieves.
- Scope & trigger — when it applies and what kicks it off ("when a signed contract arrives").
- Owner & last updated — who keeps it current, and the date it was last checked.
- What you need — the tools, logins, templates, or information required before you start.
- The steps — numbered, in order, one action each, written as instructions.
- Definition of done — how to know the task is finished and correct: the standard, not just the steps.
- Watch out for — the two or three common "what if" situations and what to do.
The real skill is altitude — the level of detail. Too vague ("handle it professionally") and it can't be followed; too granular ("click the blue button top-right") and it breaks the moment a screen changes. Aim for what a competent new hire needs: enough to act without asking you.
How to write an SOP in six steps
- Pick a task you already do well. Document reality, not an aspirational version you don't actually follow.
- Capture it while you do it. Next time the task comes up, narrate each step into a note or screen-record yourself — you'll catch steps you forgot you take.
- Draft the numbered steps. Turn the capture into short, ordered instructions. Start each with a verb; cut anything not needed to get the result.
- Add the standard and the edge cases. Write the definition of done, then the handful of "what ifs" that genuinely come up.
- Test it on someone else. Have a team member or friend follow it without your help. Wherever they get stuck is where the SOP is unclear — fix those spots.
- Store it, assign an owner, set a review date. An SOP nobody owns is a document that quietly goes out of date.
For a straightforward task the loop takes about half an hour — far less than the hours you'll spend re-explaining the job over the next year.
A simple SOP template (with a worked example)
Paste this into whatever you use and fill it in:
Title:
Purpose:
Applies when (trigger):
Owner / Last updated:
You'll need:
Steps:
1.
2.
3.
Done when:
Watch out for:
Here it is filled in for a task nearly every business has:
Title: Responding to a New Customer Enquiry Purpose: Reply fast and consistently so more enquiries turn into booked work. Applies when: A new enquiry arrives by email, web form, or phone. Owner / Last updated: Sam · 12 May You'll need: The shared inbox, the quote template, the enquiry log. Steps: 1. Log the enquiry name, contact, and source in the enquiry log. 2. Reply within one business day using the Enquiry Reply template. 3. Ask the two qualifying questions: rough timeline and budget range. 4. If it's a fit, send the quote template; if not, reply politely and close it out. 5. Set a follow-up reminder for three business days later.
Done when: The enquiry is logged, replied to, and either quoted or closed — with a follow-up set. Watch out for: Phone enquiries. Log them straight away or they get forgotten.
Notice it's a single page, not an essay — an SOP you can read in a minute is one that gets used.
Where to store SOPs so they get used
A perfect SOP saved somewhere nobody looks is worthless. Two rules keep them alive:
- Store them where the work happens. One central, searchable home — a shared-drive folder, a simple wiki, or your project tool — linked from where people already work. If finding the SOP is harder than asking you, they'll ask you.
- Keep them living. Review each on its date and update it whenever the real process changes — a wrong SOP is worse than none, because it teaches the wrong thing confidently.
You don't need special software to start: a clearly named set of documents in a shared folder beats an expensive system nobody opens.
Common SOP mistakes to avoid
- Writing them all at once. Do one a week; a growing set beats an abandoned binder.
- Wrong altitude. Too vague to follow, or so detailed it breaks with every small change.
- No owner, no review date. Unowned SOPs rot — name a keeper and a date to check it.
- Jargon and vague verbs. "Handle," "manage," and "deal with" hide the real steps. Say exactly what to do.
- Never testing them. If you're the only one who can follow it, it isn't finished.
FAQ
What is a standard operating procedure in simple terms?
It's a written, step-by-step description of how to complete one recurring task correctly, every time — a recipe for a job, clear enough that a competent new person could follow it and get the same result you would without asking you.
How do I write an SOP for my small business?
Pick a task you already do well and capture the steps as you do it. Turn that into short, numbered instructions, add a definition of "done" and the common exceptions, then have someone else follow it without your help and fix wherever they get stuck. Store it, give it an owner, and set a review date.
How detailed should an SOP be?
Detailed enough for a competent new hire to act without asking you, and no more. Too vague and it can't be followed; too granular and it breaks the moment a screen changes. Aim for clear numbered steps, the standard to hit, and the two or three exceptions that come up.
What's the difference between an SOP, a process, and a policy?
A policy sets a rule ("reply within one business day"). A process shows how work flows across stages ("enquiry to quote to booked job"). An SOP is the ground-level detail — the exact steps one person follows to complete a task to standard.
Which SOPs should a small business create first?
Start with tasks that are frequent, costly to get wrong, and known mainly by you — both high-risk and a drain on your time, so documenting them delivers the fastest relief. Save rare, low-stakes tasks for later, or skip them.
Next step
Don't try to document your whole business — just start. Pick the one task that's frequent, costly to fumble, and locked in your head, and write a single SOP this week using the template above. Next time that task comes up, follow your own document and fix whatever is unclear. Do that once a week, and many of the jobs that used to need you can gradually run without you — which is the entire point. When you're ready to turn a folder of SOPs into a business that runs on systems, build the rest of your operations playbook at dominerbusiness.com.
