How to Write an SOP Your Team Will Actually Use (4 Steps)
To write an SOP your team will actually use, don't document the perfect day. Interview your best person with four questions. Have AI organize the answers. Add a decision rule for when things go wrong. Then train it until they can do it without you.
You wrote the SOP. You saved it in the shared drive.
And your team still walks over to ask you what to do.
That's not a people problem. It's an SOP problem.
Most SOPs explain the perfect day. The second something changes, the document stops helping. Then you become the answer again.
So owners add more pages. More screenshots. More training. That's backwards.
This isn't your fault. Nobody told you a good SOP has to cover what happens when the plan breaks.
Key Takeaways
An SOP fails when it only describes the perfect day. A good one tells your team what to do when things go wrong.
Don't record your best employee. Interview them with four questions, then have AI organize the answers without making anything up.
Add a decision rule, like a dollar limit, so your team can act without calling you.
Reading an SOP is not training. Explain it, show it, watch them do it, and correct them.
Watch: How to Create SOPs (So Your Team Stops Asking You Everything)
In this 6-minute video, I walk through all four steps. I also show the AI prompt on screen so you can copy it.
What Is an SOP?
An SOP is a standard operating procedure. It's a written set of steps for one specific process in your business.
A good SOP answers three questions. What does done look like? What are the steps? What do you do when something goes wrong?
Most SOPs only answer the second one. That's why they collect dust.
A Simple SOP Format
You don't need a fancy SOP format. An effective SOP has five parts:
The outcome. What done right looks like.
Roles and responsibilities. Who owns each step.
Work instructions. Simple steps, in order, written in active voice.
A checklist. What to check before moving on.
Troubleshooting. What to do when things go wrong, and who decides.
Add a revision date at the bottom. When changes are made, everyone knows which version to follow.
A flowchart can help with a long workflow. For most processes, a checklist is enough.
Why SOPs Matter for Service Business Owners
If you run a service business, you are probably still the answer to every question.
Every one of those questions is a decision your business never wrote down.
That costs you hours every week. It also caps your growth. Your team can only move as fast as you can answer them.
I know this one from the inside. My wife and I built and sold a seven-figure service business. For years, I was still the answer to every single question.
If that sounds familiar, read Is Your Business Too Dependent on You?
Why Most SOPs Don't Work
EOS, E-Myth, Business Made Simple, and Systemology all say to document your core processes. Most tell you to record someone doing the job.
That works. But it's slow and a little painful. If you're like me, it's hard to finish.
And a recording only captures one good day. It misses the day the battery dies or the part is out of stock.
Many SOPs also read like a compliance document. Nobody wants to follow the procedure, so nobody does.
That gap is exactly what your team brings to your office.
What to Look for Before You Write an SOP
Pick the right process first. Look for these three signs:
Your team asks you about it at least once a week.
One person on your team already does it well.
When it goes wrong, it costs you money or a customer.
If a process checks all three boxes, start there. One process. Not twenty.
You don't need a 50-page operations manual. You need one SOP that works.
How to Write an SOP in 4 Steps
I use four steps: Capture, Decide, Redirect, and Train.
Here's the shift. You're not inventing the process. You're pulling the real one out of your best team member's head.
1. Capture: Interview Your Best Person
This is the fastest way to write a standard operating procedure that matches real life.
Don't record. Interview. Sit down with your best team member for about 15 minutes and ask four questions:
What does done right look like?
What do you do first?
What do you check before moving on?
What normally goes wrong?
Here's how that played out with a current client in construction. The process was getting a crew ready for tomorrow's job.
Done right: The crew clocks in, loads up, and heads to the job site within five minutes. Nobody hunts for tools.
First: Check tomorrow's project. List every tool, material, and supply it needs.
Check before moving on: Everything is loaded, fueled, and charged.
What goes wrong: Someone forgets the extra batteries for the laser level.
Now it's 8:15. The battery is dead. The whole crew stands around while someone drives to Home Depot.
That answer is your SOP. "Get the crew ready" leaves people guessing. "Out the door in five minutes with every tool" lets them check their own work.
Next, paste the answers into ChatGPT or Claude. Don't say "write me an SOP." Say "here's how my best person does it, organize it without making anything up."
Here's a prompt you can copy:
Below are my best team member's answers about how they do [process]. Turn this into a standard operating procedure with four parts: what done looks like, step-by-step instructions, checks before moving on, and what to do when things go wrong. Use only what is written here. Do not invent steps. If something is missing or unclear, list it as a question for me instead of guessing.
That last line matters most. Sometimes the gap AI finds isn't a missing step. It's a decision your business never made.
2. Decide: Set a Rule for When Things Go Wrong
No SOP covers everything. Your team will hit something the document never mentions.
Then they have three choices. Guess. Stop. Or come find you.
Back to the construction crew. Someone realizes the only level is on another job site. Now what?
A good SOP doesn't need to predict that exact problem. It just needs to tell people how to decide.
My client set one simple rule. If the fix costs under $250, the crew lead handles it and writes it down. Over $250, it comes to him.
Now the SOP isn't just instructions. It's a line your team can make decisions under. No stopping. No calling. No texting you.
This is the same problem behind Why Every Decision Still Comes Back to You.
3. Redirect: Send Questions Back to the Process
This habit can ruin a perfect SOP.
My director used to walk into my office four or five times a day. He asked questions we had already answered. And almost every time, I just answered him.
It was faster. I felt helpful. But I was teaching him one thing: when you're stuck, go ask Buck.
So I changed my response. Instead of giving the answer, I asked two questions:
Where did you look?
What do you think the answer is?
Then I sent him back to the process.
At first, it felt slower. I felt a little cold. But if you always answer, your team learns to ask you. When you send them back to the process, they learn to look.
4. Train: Reading an SOP Is Not Training
Handing someone a document is not training. Here's what is:
Explain it.
Show it.
Watch them do it.
Correct them.
Have them do it again.
That's what cut our training from a year down to four months.
I didn't hire smarter people. I built a better process, and I got good at teaching it. Even our newest team members could follow it and add value on day one.
AI can help here too. See Will AI Replace Your Employees, or Help You Hire and Train Them Better?
Which Approach Is Right for Your Business?
Under 10 employees: You are probably the best person. Have someone interview you with the four questions. Start with the process you get asked about most.
10 to 50 employees: Have each department lead run the four questions with their best person. You review the decision rules, not every step.
No one has time to build this: That's when outside help makes sense. A fractional COO can run the interviews, set the decision rules, and train your leads. I do this hands-on with service businesses in Bryan–College Station and across Texas.
Common SOP Mistakes to Avoid
Writing only the perfect day. If the SOP never says what to do when something breaks, your team will come find you.
Copying someone else's best practices. Write SOPs from what your best person actually does, not what a template says.
Letting AI fill the gaps. Tell it to ask you, not guess.
Answering questions the SOP already answers. Every answer you give teaches your team to skip the document.
Building twenty at once. Finish one. Then start the next.
How to Know If Your SOP Is Working
The questions about that process stop coming to you.
When someone does ask, they can tell you where they looked first.
New hires do the task right without someone standing over them.
Your team makes the small calls on their own and writes them down.
If the questions keep coming, watch where people get stuck. That spot is the missing step or the missing decision. Fix that one line. Don't rewrite the whole thing.
Documenting the work is step one. The next step is knowing where everyone is without asking. I cover that in How to Track Your Team's Work in 10 Seconds.
Get the Business Out of Your Head
This was never about writing operating procedures. It's about getting the business out of your head, so nobody has to remember every task.
Pick one process today. Ask the four questions. Run the answers through the prompt. Then train someone on it.
That way the business stops owning you, and you start owning it. You can take a Tuesday off, and nothing breaks.
Make good choices. Build systems that carry them out.
Frequently Asked Questions About Writing an SOP
How do you write an SOP for a small business?
Pick one process your team asks you about every week. Interview your best person with four questions. What does done look like? What do you do first? What do you check? What goes wrong? Have AI organize the answers without adding anything. Then add a decision rule and train someone on it.
Can ChatGPT write an SOP?
Yes, but only if you give it the real process. Paste in your best team member's answers and tell it to organize them without making anything up. If you just say "write me an SOP," you'll get a generic template that doesn't match how your business works.
How long does it take to create an SOP?
The interview takes about 15 minutes. AI can organize the answers in a few minutes. Training takes longer. Your team needs to do it, get corrected, and do it again before the SOP sticks.
Related Reading
Work With a Fractional COO in Bryan–College Station
I'm Buck Paolino. I'm based in College Station, Texas. I work hands-on as a fractional COO with service business owners in Bryan–College Station and across the state.
If your team still runs every question through you, apply for an AI Operations Build. We'll fix one process together.
Not ready to talk? Take the free What To Automate First checkup and see where your time is leaking.
Comments