The 4 Step Method for Turning One Task Into a Written Procedure

There's at least one task in your business that only goes right when you do it yourself. If you handed it to someone on your team tomorrow with nothing but a written set of instructions, would they get it right, or would your phone start ringing before lunch?

That question is the difference between a business that can run for a week without you and one that can't. You can fix it one task at a time, and AI has made the hardest part much faster. The catch is that AI has also made it easier to produce a document that looks finished and still doesn't work. Here's how to write an SOP for a small business that your team can actually follow, using AI the right way.

Why most standard operating procedures never get used

Three things get in the way, and they're the same three in almost every service business.

The first is time. You're the person who knows how everything works, which means you're also the busiest person in the building. Writing a procedure from scratch takes a quiet, focused hour most owners don't have, so it lands on the someday list.

The second is sneakier. When procedures do get written, they're written by the one person who doesn't need them. Think about the elementary school exercise where kids write the instructions for a peanut butter and jelly sandwich and the teacher follows them exactly. The knife goes into a closed jar, because nobody wrote "open the peanut butter." We don't write "log into the software first," because we've been logged in since seven this morning. The document describes the version of the task that happens in your head, and the person following it keeps hitting walls you can't see.

The third reason costs the most. We don't test them. We write the procedure, we save it, and we call it done. Six months later a new hire makes a mistake and we're frustrated, because it's all written down. But nobody ever checked whether someone new could follow those instructions and get the right result.

Now layer AI on top. It solves the time problem beautifully and hands you a draft in seconds, but it doesn't know your software, your pricing rules, or the three exceptions that make your process yours, so it fills the gaps with steps that sound reasonable and aren't true. Generic is what fails the first time a real person picks it up.

An SOP isn't finished until someone else can follow it

Here's the standard worth borrowing. A procedure isn't finished when it's written. It's finished when someone else can follow it and get the result you want, without you.

That comes from my years in the hospital laboratory, fifteen as a medical laboratory scientist and about a decade in laboratory quality and patient safety as a Lean Six Sigma Black Belt. In a regulated lab, a procedure doesn't become official because somebody typed it up. It gets reviewed and approved, people get trained on it, and then they demonstrate they can perform it.

You don't need a hospital level quality system to run an HVAC company or a lawn care business, but the heart of it transfers. Writing it down is step one. Proving it works is the step that makes it real. And everyone who needs it has to find it in seconds, because when people have to hunt for something, they give up and wing it.

If you like the mountain picture, think about route notes. The notes climbers actually trust were written by someone who made the climb, then checked by the next climbers who came back and said the trail washed out at the second switchback. That's what you're building. Route notes that have been climbed. [INTERNAL LINK: the Business Mountain Framework]

Talk it, draft it, test it, fix it

Pick the right task first. Just one. Look for a task that checks at least two of these boxes: it happens at least weekly, it causes a real backlog or expense when it goes wrong, only one person can do it right now, and you get asked about it over and over. If that person were out unexpectedly, would your week fall apart? That's your task.

Talk it. The next time you do the task, record yourself with the voice memo app on your phone, or a free screen recorder for a computer task. Narrate it like you're training someone sitting next to you. Don't just say what you're clicking. Say why, and say what you'd do if something looked off. If the task belongs to someone else on your team, let that person record it, because they're the expert.

Draft it. Turn the recording into a transcript. Most phones and AI tools will do it, and Descript will do it free if yours won't. Paste it into whichever AI tool you use and give it real direction instead of "make this an SOP." Tell it to act as an operations manager for your kind of business and turn the transcript into a procedure a brand new employee could follow, including the purpose, who owns it, the tools and logins needed, numbered steps, decision points written as if this happens then that, what done looks like, and common mistakes. Then add the two lines that matter most: do not add any steps I didn't say, and when something is unclear, don't guess, make me a list of questions instead.

That second instruction turns AI into a thinking partner. It'll ask what should happen if the technician doesn't answer the text, and you'll realize you never decided. One caution before you paste anything in: strip out customer names, addresses, phone numbers, passwords, and account numbers. The procedure works fine without them.

Test it. This is the step that turns a document into a system, and it's the one everybody skips. Hand the draft to someone who has never done the task and ask them to work from the paper alone. Then keep your hands in your pockets. No pointing, no explaining, no rescuing. Ask them to say their questions out loud and write every one down. Every place they stop is a gap in the document, and that's good news, because documents are easy to fix.

Fix it. Take your notes back to the AI tool, paste in the current version, and tell it exactly where the person got stuck and what they asked, with instructions to address each one and change nothing that worked.

The four things a finished procedure needs

Give it an owner, so one person is accountable for keeping it accurate. Give it a date and a version at the top, so nobody wonders whether they're reading the old one. Give it a home where the person doing the work will find it, whether that's your field service software, a clearly named folder, or a laminated card in the truck with a QR code. And give it a trigger for review: a software change, the same mistake twice, a new person getting trained, plus an annual check. A perfect procedure nobody can find is the same as not having one. [INTERNAL LINK: building an org chart that actually works]

Documentation is a kindness, not a trust issue

Some owners hesitate because writing things down feels like saying they don't trust their people. Think about what it's like to be new somewhere. You want to do a good job, you don't want to ask the same question three times, and you really don't want to guess and get it wrong in front of a customer. Clear instructions that have been proven to work tell your team you want them to succeed. Brene Brown says clear is kind and unclear is unkind, and that's the whole thing in one sentence.

It's also freedom for you. At Cavalry Appliance Service, our technician recall rate used to be calculated by hand, with Joe working through every call during payroll. Now it comes from a report in ServiceWorks and a quick sort in Excel, written down so we get it the same way every time. When the process lives in a tested document instead of your head, you stop being the bottleneck, and your job shifts from being the process to improving it.

So pick your one task this week and talk it. You don't have to finish all four steps by Friday. Just start the climb.

Your next step

If you want help with the drafting part, my own policy writing and procedure writing tools are free at https://www.outcomeacademy.com/sops. One writes policies, which is your rule and the reason behind it, and one writes procedures, which is the step by step of how the work gets done. They come as custom GPTs if you use ChatGPT and as skills if you use Claude, so grab whichever fits how you already work.

Not sure which systems your business needs first? The Find Your Camp quiz at [QUIZ LINK] shows you where you are on the mountain and the hazards to watch for at your stage. If you'd rather do this work alongside other owners on the same climb, the Eight Thousander Expedition™ is where that happens.

Resources mentioned

Descript, a free tool that turns a recording into a transcript in a couple of minutes, at descript.com.

The free policy writing and procedure writing tools at https://www.outcomeacademy.com/sops.