How to Write SOPs With AI and Actually Delegate
- Talk the process out loud and let AI write it down. Nobody ever writes the SOP they meant to write.
- Capture it while you do the task, not from memory afterwards.
- A good SOP includes what to do when it goes wrong. That is the part that makes delegation stick.
- Have the person who will do the job test the SOP without your help. Their questions are the missing steps.
Every owner knows they should document how things get done. Almost nobody does, because writing an SOP is boring and the payoff is months away.
The trick is to stop writing them. Talk instead, and let AI do the documenting.
Record yourself doing the job
The next time you do the task, narrate it. Voice memo on your phone, screen recording with the mic on, whatever is nearest. Say what you are doing and why as you go.
Do it while working, not afterwards. Memory smooths out exactly the fiddly bits that a new person will get stuck on, which are the bits that matter.
Turn the ramble into a draft
Paste the transcript in with this: “This is me talking through a process. Turn it into a numbered SOP a new employee could follow. Flag any step where I was vague or assumed knowledge, and list what you would need to ask me to fill those gaps.”
That last instruction is what makes this work. It hands you back a list of everything you left out, which is always more than you expect.
Answer the gap list
Go through its questions and answer them. Five minutes, and this is where the SOP goes from a nice document to a usable one.
The gaps are almost always the same categories: which tool to open, where a file lives, who to ask, and what “good enough” looks like.
Add the exceptions
Most SOPs describe the happy path and then fall apart the first time reality intrudes. Ask: “What could go wrong at each step, and what should someone do about it?”
Then add a short “if this happens” section. This is the single biggest difference between an SOP that gets used and one that gets abandoned in week two, because the first exception is when people give up and come ask you.
Test it on the person taking it over
Hand it to whoever will do the job and let them work through it while you say nothing. Write down every question they ask.
Every question is a missing step. Add them, and the second version is usually the one that holds.
Build a small library, not a manual
Do one SOP per week for the tasks you most want off your desk. In three months you have a dozen, which covers most of what you were dreading handing over.
Do not attempt a company handbook. Handbooks never get finished and never get read.
Where this pays off twice
Once you have written SOPs, you can load them into a custom assistant so the person doing the job can ask it questions instead of asking you.
That is the actual endgame. Not a document, but a process someone else can run without you being the help desk.
Want the back-office system?
The side hustle and small business guide covers handling the boring back office, pricing and getting paid, serving customers like a bigger company, and growing without burning out, along with pressure-testing an idea and launching cheap.