Picture this: it's a Sunday night. The owner of a service business gets the call he's been dreading for years.
His best technician is giving two weeks' notice. The technician is the only person who knows how to handle the company's three biggest commercial accounts, how they like invoicing done, what their access codes are, which days they prefer service, which manager to call when something goes wrong. None of it is written down. All of it is in one person's head.
The technician isn't being difficult, he's being normal. Every small business has this person, and often it's the owner.
This is the problem SOPs solve. And the reason most owners don't have any is that SOPs sound like something a Fortune 500 HR department invented to make life harder.
They're not, actually a good SOP is a recipe.
What an SOP actually is
A standard operating procedure is a written description of how a specific task gets done in your business. Not a 40-page binder, not a flowchart with seven decision diamonds. Just a page or two that says: here's what we do, here's the order we do it in, here's what done looks like.
If a new hire could read it on Monday morning and produce roughly the same result you would, it's a good SOP. If they need to ask you three questions to make sense of it, it isn't done yet.
The test is simple: Could you go on vacation for two weeks and have someone follow this without calling you?
Why most owners don't have any (and why it costs them)
The reasons are always the same:
"I don't have time to write it down."
"Everyone already knows how to do it."
"It changes too much to document."
"I'd rather just train people in person."
Each of these sounds reasonable. Each one is a trap.
Without SOPs, your business has a ceiling. You can't hire because training takes forever and the new person makes different mistakes every week. You can't promote because nobody else can do what you do. You can't sell the business because the value lives in your head. You can't take a real vacation because something always goes wrong while you're gone.
The cost of not writing things down isn't the inefficiency, it's the ceiling. Your business is exactly as big as the things you personally hold in your head, and not one customer larger.
The 80/20 of SOP work
You don't need an SOP for everything. You need SOPs for the things that meet three tests:
It happens more than once a week. Daily and weekly tasks are where errors compound.
It matters if it's done wrong. A botched invoice costs money. A bad opening procedure costs a day.
Someone other than you does it, or should.
Run those three filters across your business and you'll probably end up with somewhere between 8 and 15 SOPs that genuinely matter. Not 50, not 100, about a dozen.
For a restaurant, those usually include: opening checklist, closing checklist, food order/par sheet, weekly inventory count, deposit procedure, scheduling routine, new hire training week one, and customer complaint response.
For a boutique: opening, closing, receiving new product, tagging and placement, end-of-day deposit, social media posting schedule, customer return policy, and email list maintenance. Not to mention, the process you use for your inventory!
For a service business: lead intake, quote generation, job scheduling, on-site arrival and walk-through, invoicing, follow-up, and warranty callbacks.
Twelve SOPs covers most of what actually happens in your business on a normal week.
The format that actually gets used
Most SOP templates fail because they're too formal. Owners look at them, sigh, and never write anything. The format that works is short and unceremonious:
Title. What is this for? "Friday Deposit Procedure," not "Standard Operating Procedure for End-of-Week Financial Reconciliation."
Purpose, one sentence. Why does this exist?
When it happens. Day, time, trigger event.
Who does it. Title, not name. Names change.
What you need before you start. Tools, access, information.
The steps. Numbered. Each step is one action. If a step has "and" in it twice, split it.
What done looks like. The result. How do you know it worked?
What to do if something goes wrong. The two or three things most likely to go sideways and how to handle them.
That's the whole template. Most SOPs that follow it run between half a page and two pages. Anything longer and you've probably wrapped two or three procedures into one.
Write your first one in 90 minutes
Pick the right one to start with. The best first SOP is something you do every week, something that's been done wrong by someone other than you in the last 60 days, and something that doesn't require any judgment calls, a procedural task, not a creative one.
Closing the shop, running payroll, Friday deposits, opening the kitchen, weekly inventory. Pick one of those.
Then:
Minute 0–15. Don't write yet. Do the task and narrate it out loud into your phone's voice memo. Every step, every "and then I check the…", every "I usually look at whether…". You'll catch steps you didn't know you were doing.
Minute 15–45. Transcribe the recording into the template above. Don't edit yet, just get the raw version down.
Minute 45–60. Edit for clarity and cut anything that's obvious. Split steps that have multiple actions, and add the "what done looks like" section.
Minute 60–90. Hand it to someone who's never done the task and ask them to do it from the document. Watch silently, then every time they have to ask a question, that's a hole in the SOP you should fix.
Tada! You have your first SOP.
What to do after the first one
Don't try to write all twelve in a weekend. You'll burn out and end up with four bad ones.
Write one a week. Pick the next most painful gap and document it. In three months, you have a binder. In six months, your business runs differently.
A few rules that keep the system healthy:
Put them somewhere everyone can find them. A shared Google Drive folder is fine. A binder on a shelf is fine. What kills SOPs is hiding them in an email or a manager's laptop.
Update them when they change. A wrong SOP is worse than no SOP. If you change the deposit process, the document changes the same day.
Review them quarterly. Pull each one out, read it, ask whether it still matches what you actually do, and fix anything that's drifted.
Have the person who does the task own the document. They know it best! The owner approves changes; the person doing the work proposes them.
The vacation test
Here's the test I give owners six months in: take a week off. Don't check your phone, don't email. Leave the SOPs with your team.
The first time most owners try this, three or four things go wrong. Each one is a hole in an SOP, and each one is fixable.
The second time, two things go wrong. By the third time, the business runs without you for a week, and you discover something important: the ceiling moved. You can grow now in ways you couldn't before. You can hire, you can delegate, you can sell the business if you ever want to.
That's what SOPs actually buy you. It's not just about efficiency, they buy you freedom.
If you've been meaning to write your operating procedures down for two years and haven't gotten past the first one, that's normal. The SOP Documentation Package builds the foundational set with you, in your voice, ready to use. Or book a discovery call and we can talk through which procedures matter most for your business.