Quick answer
An SOP is a written, step-by-step instruction for one repeatable task, so the work gets done the same way every time. To write one: pick one task, watch it being done, name an owner, write the steps in order, add screenshots or a short video, test it with someone new, and set a review date.
Step 1: Pick the first task to document
Start with the task that costs you the most when it goes wrong. One task per SOP.
An SOP, or standard operating procedure, is a written, step-by-step instruction for one repeatable task. It exists so the work gets done the same way every time, without you explaining it again. You don’t need one for everything. Start with these:
Repeated tasks.
Anything done every day or every week: orders, client onboarding, invoices.
Error-prone tasks.
Where a skipped step means a refund, a rework, or an unhappy customer.
Tasks stuck in one person’s head.
If only one person knows how, that’s a risk, not a skill.
Tasks you explain more than once.
If you’ve walked someone through it twice, write it down.
Written processes are what keep a business running when people leave or the work changes. At the company Lockhold’s founder bootstrapped and sold, a heavily regulated product meant specs and records had to be right on every run. That only works when the process is written down and followed.
Step 2: Write it step by step
Watch the task being done, write the steps in order, then test the page on someone new.
Name the task and its trigger.
One sentence on why it exists, one on what starts it. If it covers two tasks, split it.
Watch it being done.
Sit with the person who does it today and note every step, including the ones they do without thinking.
Name an owner.
The role that keeps the SOP up to date, not a person’s name.
Write the steps in order.
Start each one with a verb. Name the role, not the person.
Add screenshots or a short video
for the step where people usually get stuck.
Write what done looks like,
and what to do if something goes wrong.
Test it with someone new.
Every question they ask is a gap to fix.
Set a review date
and put it on the calendar.
Step 3: Use a one-page format
Every SOP covers the same six things on one page. If it runs longer, it covers more than one task.
Purpose
- What it covers
- Why the task exists, in one sentence.
- Example line
- Return the money when the request meets the rules, and close the ticket.
Scope
- What it covers
- What starts it, and what it covers.
- Example line
- Starts when a refund request arrives in the inbox.
Owner
- What it covers
- The role that keeps the SOP current.
- Example line
- Customer support lead.
Steps
- What it covers
- The work in order, each starting with a verb.
- Example line
- Check the order date. Confirm it’s inside the refund window. Process the refund.
Tools
- What it covers
- The systems and logins the task uses.
- Example line
- The order system and the support inbox.
Definition of done
- What it covers
- How you know it’s finished.
- Example line
- The refund is processed and the customer has the confirmation.
Examples for a small business
Order fulfillment
Every example names a trigger, a short list of steps, and a clear finish line.
- TriggerA new order is paid.
- StepsConfirm the address, pick and pack the items, print the label, mark the order shipped, send tracking.
- DoneThe customer has tracking and the order shows shipped.
Client onboarding
If you can’t write the trigger, steps and finish line, the process needs work before the SOP does.
- TriggerA client signs.
- StepsSend the welcome email, set up their account and folders, schedule the kickoff, share what you need from them.
- DoneThe kickoff is booked and the client has everything they need to start.
Month-end close
Short, specific, and the same every month.
- TriggerThe last business day of the month.
- StepsReconcile the bank and card accounts, review open invoices and bills, categorize anything unmatched, send the summary to the owner.
- DoneThe books are reconciled and the summary is sent.
Closing a location
A task people already know, where the risk is skipping a step. A checklist fits.
- TriggerThe scheduled closing time.
- StepsClose out the register, secure cash, check equipment is off, set the alarm, lock up.
- DoneThe closing checklist is signed off and the alarm is set.
The one-page SOP template
The format from this guide, ready to fill in. Works in Word and Google Docs.
- One page per task: purpose, trigger, steps, who, tools, and what “done” looks like.
- Built-in upkeep: an owner, a review date and a change log.
- A worked example: a customer refund request, filled in.
- Plus the one-page guide: How to write an SOP your team actually uses, ready to print or share.
Here's your SOP template.
Plus the one-page guide: download the PDF.
Check your inbox and click Confirm. Then we’ll email you a copy, and you’ll get our monthly operator note.
That didn't go through. Please try again, or email hello@lockhold.com.
Step 4: Get the team to use it
Write it with the people who do the work, keep it short, and put it where they work.
Most SOPs that get ignored fail for the same few reasons:
It’s too long.
Keep it to one page.
It covers more than one task.
Split it.
It names people, not roles.
Name the role, so it survives turnover.
It was never updated.
Review it when the work changes.
It sits in a folder nobody opens.
Put it where the work happens.
Checklist, SOP, or full process doc?
Most small businesses need a handful of good SOPs before anything bigger. Mapping how work moves across the whole business is where our operations consulting starts.
Step 5: Keep it current
One owner, a review date, and one home for every SOP.
One owner per SOP.
Someone is responsible for keeping it current.
A review cadence.
At least once a year, and any time the process changes.
One home.
Every SOP lives in one place the team knows, linked from where the work happens.
When something changes, update the SOP first, then tell the team. If the page and the practice disagree, people trust the practice. The simplest review is to have someone follow it exactly as written. If they get stuck, fix the page, not the person.
Once a process is documented, it can be automated. Our guide on how to automate business processes covers what to automate first.
FAQ
What is an SOP?
An SOP, or standard operating procedure, is a written, step-by-step instruction for one repeatable task. It exists so the work gets done the same way every time, by anyone trained on it.
How long should an SOP be?
As short as it can be while someone new can still follow it, usually no more than one page. If it’s getting longer, it probably covers more than one task and should be split.
Who should write SOPs in a small business?
The person who does the work, with someone who owns the process reviewing it. The people closest to the task know the real steps, and a fresh reader catches the gaps.
What’s the difference between an SOP and a checklist?
A checklist reminds someone who already knows the task not to skip a step. An SOP teaches the task: the purpose, the trigger, the steps in order, and what done looks like. Many SOPs end in a checklist.
Want it built and running?
SOPs take time most owners don’t have, and they work best when they’re built with the people who do the work.
We document your processes with your team, simplify them, and put them where the work happens, so steps stop getting skipped.
Related guides and work
How to automate business processes
Which processes to automate first, how AI automation fits, and a step-by-step way to automate without breaking what works.
Read the guide Guide
How to build a KPI dashboard
The numbers to track, sales first, and how to build a dashboard your team checks every week.
Read the guide Service
Systems & SOPs
We document, simplify and hand off the processes that still run through you.
Read →