Standard Operating Procedure (SOP) Template for Small Business

SOPs are how you scale your business beyond yourself. If a process lives only in your head, your business can't grow.

SOP Template

Essential SOP Sections

1. Purpose - Why does this process exist? What does it accomplish?
2. Scope - Who does this apply to? When is this procedure used?
3. Definitions - Define any terms that might be unclear.
4. Responsibilities - Table with roles and what they do in this process.
5. Procedure - Step-by-step actions with sub-step details.
6. Exceptions - When does this procedure NOT apply? What to do in unusual circumstances?
7. Related Documents - Links to related SOPs, forms, or resources.
8. Revision History - Version, date, changes, author.

What Processes Should You Document First?

• Anything you do repeatedly (weekly, monthly)
• Anything you'll eventually delegate to someone else
• Anything that affects customer experience
• Anything with compliance or legal implications

The Only Real Test of an SOP

Hand it to someone who has never done the task and leave the room. If they can complete it without asking you a question, it is an SOP. If they cannot, it is a reminder written for someone who already knows — which is the form almost every first draft takes.

Write It While Doing the Task

Do not write an SOP from memory. Memory smooths over the exact steps that trip up a newcomer: which menu, which login, what the button is actually labeled. Open the task, do it, and narrate every action including the ones that feel too obvious to write down. Those are the ones that generate questions later.

Structure That Survives Staff Turnover

1. Purpose — one sentence on why this task exists. People follow steps better when they know what the step protects.
2. Trigger — what starts it. A date, an email, a customer action.
3. Who — the role, not the person's name. People leave; roles stay.
4. What you need first — access, files, tools, approvals.
5. Steps — numbered, one action each, in the order performed.
6. Done looks like — the observable end state.
7. When it goes wrong — the two or three failures that actually happen and what to do about them.
8. Owner and last reviewed date — on every document, without exception.

One Action Per Step

"Log in, pull the report, and email it to accounting" is three steps pretending to be one. Split them. A person who is interrupted mid-task needs to know precisely where they stopped, and compound steps make that impossible.

Screenshots Age Faster Than Words

Screenshots are useful and they are also the reason SOPs go stale, because interfaces change and nobody wants to redo the images. A practical compromise: describe the action in words that survive a redesign ("open the billing settings and choose the export option"), and use screenshots only where the interface is genuinely confusing.

Where to Keep Them

An SOP nobody can find is an SOP that does not exist. One location, one naming convention, and a link to it from wherever the work actually starts. If your team lives in email, the SOP link belongs in the recurring email. If they live in a task board, it belongs on the task template.

Review on a Schedule, Not on a Crisis

Put a review date on every SOP — quarterly for anything touching money or compliance, annually for the rest. The person who owns the task owns the review. Reviewing is usually a two-minute confirmation that nothing changed, which is exactly why it never happens unless it is scheduled.

Start With These Five

If you have no SOPs at all, the highest-value ones are almost always the same in a small business:

• Opening and closing, whatever that means for your operation
• How a new customer gets set up, invoiced, and delivered to
• How money moves — who can approve, who can pay, who reconciles
• How a new hire gets access, and how a departing one loses it
• What to do when the thing you depend on is down

Those five cover most of the situations where an absence, a resignation, or a bad week turns into a real problem.