How to Write an SOP Your Team Will Actually Follow
Updated: 1 hour ago
Every small business owner has said it: "It's faster if I just do it myself." And it is, the first time. By the fiftieth time, you've spent hours doing a job someone else could have done, if only it had been written down.
That's what a standard operating procedure (SOP) is: a written, step-by-step description of how one task gets done in your business. Good SOPs let you hand work off, train new people faster, and get the same result no matter who's doing the job.
The trouble is, most SOPs don't get followed. They're too long, too vague, or out of date by the time anyone reads them. This guide shows you how to write ones that actually get used.
Start With the Right Process
Don't try to document everything at once. You'll run out of steam by process number four.
Instead, start with the one or two processes that matter most right now. Look for a task that is:
Done often. Weekly or more. A daily task documented once saves time every single day.
Easy to get wrong. If mistakes cost you money, customers, or rework, it's a priority.
Stuck with one person. Anything only you (or one employee) knows how to do is a risk every time that person is sick, on holiday, or leaves.
Good first candidates for most small businesses: booking a new job or appointment, sending invoices, onboarding a new customer, opening or closing for the day, and handling a complaint.
Let the Person Who Does It Write It
Business owners are often the worst people to write SOPs. You know the task so well that you skip steps without noticing.
Instead, ask the person who does the task every day to talk you through it while they do it. Record the screen or take photos as they go. Then turn that into written steps. You'll capture the small details that make the difference, like "check the unit number twice because the system autofills the last one."
What Every SOP Should Include
Keep the same structure for every SOP so your team always knows where to look.
Title: a plain name for the task, starting with a verb. "Book a new service call," not "Service call booking procedure."
Purpose: one sentence on why this matters. "So every job is booked with the right details and the customer gets a confirmation."
When it's used: the trigger. "Whenever a new customer calls or emails to book."
Who does it: the role responsible, and who to ask for help.
What you need: any tools, logins, or forms.
The steps: numbered, in order.
Check it's done right: how the person knows the task is finished correctly.
If something goes wrong: the common problems and what to do about each.
Owner and review date: who keeps this SOP up to date, and when it was last checked.
How to Write Steps People Can Follow
One action per step. "Open the schedule, find a free slot, and book it" is three steps. Split them up. People lose their place in long, crowded steps.
Start every step with a verb. Open, enter, check, send, call. It makes each step an instruction, not a description.
Be specific. "Send the confirmation" leaves questions. "Send the confirmation email using the 'New Booking' template" doesn't.
Show, don't just tell. A screenshot of the right screen, with the button circled, beats a paragraph of explanation.
Mark the decisions. Where the process branches, say so clearly: "If the customer is new, go to step 5. If they're an existing customer, go to step 8."
Keep it to one page if you can. If an SOP runs past two pages, it's probably two processes. Split it.
A Worked Example: Book a New Service Call
Purpose: So every job is booked with complete details and the customer gets a confirmation the same day. When: A new or existing customer calls or emails to book a job. Who: Office coordinator. Ask the operations manager if unsure.
You'll need: Scheduling software login, the "New Booking" email template.
Steps
Search for the customer's name or phone number in the scheduling software.
If they're new, create a customer record with their name, phone, email, and service address. Read the address back to them.
Ask what the job is and choose the matching job type from the list.
Ask about access: parking, gate codes, pets, or tenant contact details.
Offer the next two available slots. Book the one they choose.
Note anything unusual in the job notes, such as parts to bring or a customer who prefers texts.
Send the confirmation email using the "New Booking" template within an hour.
Check it's done right: The job appears on the schedule with a job type, an address, and access notes, and the confirmation shows as sent.
If something goes wrong:
No slots in the next five days: offer the waitlist and flag the booking for the operations manager.
Customer is disputing a past invoice: take a message, don't book, and pass it to the operations manager the same day.
Owner: Operations manager · Last reviewed: [date]
Pick the Right Format
Not every process should be a numbered list. Match the format to the task:
Checklist: for routine tasks where the order barely matters but nothing can be missed, like opening or closing for the day, or a vehicle safety check.
Step-by-step: for tasks done in a set order, like booking a job, sending an invoice, or onboarding a customer. This is the format in the example above.
Flowchart: for processes with lots of decisions and branches, like handling a complaint or approving a refund. A picture shows the "if this, then that" far better than paragraphs.
Short video: for anything that happens on a screen or with your hands. A three-minute screen recording with narration often beats a page of screenshots. Keep a short written summary alongside it, so people can scan it later without rewatching.
Whatever the format, keep the same header on every SOP: title, purpose, when, who, owner, and review date. That's what makes a library of mixed formats still feel like one system.
Test It Before You Roll It Out
Hand the SOP to someone who has never done the task and watch them try it. Don't help. Every time they hesitate, ask a question, or make a mistake, you've found a gap. Fix it, then test again.
This one step is the difference between an SOP that looks good and one that works.
Keep Your SOPs Alive
An out-of-date SOP is worse than none, because people follow it and get it wrong. Build three habits:
Give every SOP an owner. One person responsible for keeping it accurate.
Update it when the process changes. New software, new price, new supplier? The SOP changes the same week.
Review everything once a year. Put a date on every SOP and check the ones older than twelve months.
Keep all your SOPs in one place your team can reach easily: a shared folder, a binder in the office, or a single index document that links to each one.
Getting Your Team to Actually Use Them
Writing SOPs is the easy part. Getting them used takes a few deliberate habits:
Train with the SOP in hand. When you teach someone a task, work through the SOP together. Now it's the reference they learned from, not a document they've never opened.
Answer questions with a link. When someone asks how to do something, send them the SOP rather than just the answer. If the SOP doesn't answer the question, fix the SOP.
Make updating everyone's job. Anyone who spots a mistake or a better way should flag it to the SOP's owner. People follow the documents they helped improve.
Praise the process, not just the result. When someone handles a tricky situation exactly as the SOP says, notice it out loud.
A 90-Day Rollout Plan
Trying to document your whole business in a weekend is how SOP projects die. Pace it instead:
Month 1: Write and test your two highest-priority SOPs. Use them in real work every day, and fix what doesn't work.
Month 2: Add three to five more, written by the people who do the work. Set up one shared place to keep them all.
Month 3: Cover the rest of your weekly processes, add owners and review dates to everything, and start training new hires from the SOPs.
After 90 days, most small businesses have their ten to fifteen most important processes written down. That's usually enough to take a real holiday without the business stalling.
Get a Head Start
You don't need special software to write great SOPs. A clear template and an hour of focus is enough to document your first process.
Comments