Blog · Operations
How to Write a Standard Operating Procedure (SOP): A Simple Template for Small Businesses
The short answer
A standard operating procedure (SOP) is a short written guide to how a recurring task gets done in your business. A good one fits on one or two pages and covers the purpose, the owner, what starts the task, the numbered steps, and what "done" looks like.
The fastest way to write one: record the person who does the task best while they do it, turn the recording into steps, have someone else follow it, and fix what confused them. Most SOPs take under an hour. Start with the tasks that happen most often or cost the most when they go wrong.
Why small businesses need SOPs
- Consistency. Customers get the same quality no matter who does the work.
- Faster training. New hires get up to speed from a document instead of shadowing someone for weeks.
- Less owner dependence. If the work only lives in your head, the business can't run without you.
- Fewer errors. A checklist catches the step people forget when they're busy.
- A foundation for AI and automation. You can't automate a process nobody has written down. The SOP is the spec.
The 8 parts of a good SOP
| Section | What it answers | Example |
|---|---|---|
| Title | What task is this? | Onboard a new client |
| Purpose | Why does it matter? | Get every new client to a first result within 14 days |
| Owner | Who is responsible for it? | Client success manager |
| Trigger and frequency | What starts it, and how often? | A signed contract; about 6 times a month |
| Tools and access | What systems are needed? | CRM, project tool, shared drive, email templates |
| Steps | What exactly happens, in order? | 8 to 15 numbered steps, each starting with a verb |
| Definition of done | How do you know it's finished and right? | Kickoff held, access set up, first deliverable scheduled |
| Exceptions | What if something goes wrong? | If the contract is missing billing details, notify finance before kickoff |
Add a version date and the name of the last person who reviewed it at the top, so everyone knows whether it's current.
How to write an SOP in 7 steps
- Pick the process. Choose one task with a clear start and finish. "Onboard a new client" works. "Customer service" is too broad.
- Record it being done. Ask the person who does it best to share their screen and talk through each step while they work. Capture the real process, not the ideal one.
- Turn the recording into steps. An AI assistant can draft numbered steps from a transcript in minutes. Each step should start with a verb and describe one action.
- Add the decisions and exceptions. Wherever the expert says "it depends," write down what it depends on and what to do in each case.
- Add screenshots or links for steps that happen inside software, and links to templates the task uses.
- Test it. Have someone who doesn't normally do the task follow the SOP exactly. Every question they ask is a gap to fix.
- Publish and schedule a review. Store it where people actually work, name an owner, and review it every 6 to 12 months or whenever the tools change.
A simple SOP template
Copy this into a document and fill it in:
- SOP title:
- Version and date: · Last reviewed by:
- Purpose: one sentence on why this matters
- Owner: role, not just a name
- Trigger: what starts this task · Frequency:
- Tools and access needed:
- Steps: 1. Verb + action. 2. Verb + action. 3. …
- Definition of done:
- Exceptions and who to ask:
- Related SOPs and templates:
Which processes to document first
Score each recurring task on three questions, 1 to 3 points each: how often it happens, how much a mistake costs, and how many people do it or need to cover it. Write SOPs for the highest scores first. For most small businesses, the first ten look something like this:
- Responding to a new lead
- Sending a proposal or quote
- Onboarding a new client
- Delivering your core service or fulfilling an order
- Invoicing and following up on overdue payments
- Handling a customer complaint or refund
- Weekly reporting and KPI updates
- Onboarding a new employee
- Month-end close and bill payment
- Granting and removing system access
Common SOP mistakes
- Writing the ideal process instead of the real one. Document what people actually do, then improve it.
- Too much detail. If it's longer than two pages, split it into smaller SOPs.
- No owner. An SOP nobody owns goes out of date within months.
- Hiding them. SOPs buried in a folder nobody opens don't get used. Link them from the tools and checklists people work in.
- Never testing them. If a new person can't follow it, it isn't finished.
SOPs make AI and automation work
Every automation project starts by mapping the process step by step. If you already have an SOP, that work is mostly done. A written SOP shows:
- Which steps are repetitive rules that full automation can handle, such as creating records and sending onboarding emails.
- Which steps need judgment that AI can assist with, with a person approving the result.
- Where the handoffs are, which is usually where work gets stuck and where automation saves the most time.
SOPs also make AI assistants more useful. Give an AI assistant your SOP and it can answer team questions, draft the next step, or check work against the definition of done. An AI agent needs the same clear steps, limits, and exceptions to work safely.
Once a process is written down, you can estimate what automating it is worth with the automation ROI method, and see which steps fit which level of automation on the AI implementation page. If you're still deciding where to start, see where a small business should start with AI.
Frequently asked questions
What is a standard operating procedure?
A standard operating procedure (SOP) is a short written guide to how a recurring task is done in a business. It lists the purpose, the owner, what starts the task, the numbered steps, what done looks like, and how to handle exceptions, so anyone can do the task the same way.
What should an SOP include?
A good SOP includes a title, purpose, owner, trigger and frequency, the tools and access needed, numbered steps that each start with a verb, a definition of done, and exceptions with who to ask. Add a version date and the name of the last reviewer so people know it is current.
How long should an SOP be?
Most SOPs should fit on one or two pages, usually with 8 to 15 numbered steps. If an SOP runs longer, split it into smaller procedures that each cover one task with a clear start and finish.
How do you write an SOP quickly?
Record the person who does the task best while they talk through each step, use an AI assistant to turn the transcript into numbered steps, add decisions and exceptions, then have someone else follow it and fix whatever confuses them. Most SOPs take under an hour this way.
Which processes should a small business document first?
Start with tasks that happen often, cost the most when they go wrong, or are done by several people. For most small businesses that means responding to leads, sending proposals, onboarding clients, delivering the core service, invoicing, handling complaints, and onboarding employees.
Do you need SOPs before automating a process?
Yes. Automation and AI projects start by mapping a process step by step, and an SOP provides that map. It shows which steps follow fixed rules and can be fully automated, which need judgment and suit AI with human review, and where handoffs slow the work down.
Find out which processes to fix first
The free Profit Check estimates how many hours manual work is costing you and what automation could save, in about 3 minutes. The AI Operations & Profit Audit ($7,500, about 3–4 weeks) maps your key workflows, ranks the opportunities by margin impact, and gives you a 30/60/90-day plan.
Take the Free Profit Check See audit optionsThis article is general guidance on documenting business processes. Regulated industries may have specific SOP and recordkeeping requirements; check with your compliance advisor.