Training
How to Write Standard Operating Procedures With AI - Turn What You Do Into Something Anyone Can Follow
How to write standard operating procedures with AI without producing a document nobody reads: the Narrate-Draft-Run loop, what to put in an SOP versus leave out, and the test that proves the SOP actually works.
Founder, AI Tools and Training Club · August 12, 2026 · 8 min read
The short version
- The hard part of an SOP was never the writing, it was getting the process out of your head - so narrate it out loud and let AI do the structuring.
- Run it as Narrate-Draft-Run: talk through the process as you actually do it, have AI turn that into a numbered procedure, then have someone else run it while you say nothing.
- The only test that matters is whether a person who has never done the task can complete it from the document alone. Everything else is formatting.
Why most SOPs never get written
Almost every small business owner knows they should document how things get done. Almost none of them do it, and the reason is not laziness - it is that writing an SOP means switching from doing the task to describing the task, in a formal structure, for an audience who is not in the room. That is a genuinely different skill, and it is the reason the SOP folder in most businesses has three documents in it from two years ago.
AI removes exactly that part. You already know the process perfectly. What you cannot easily do is convert what you know into ordered, unambiguous steps someone else can follow. Talking is easy. Structuring is the work, and structuring is what AI is genuinely good at.
The Narrate-Draft-Run loop
This is the three-step loop that turns a process living in your head into a document someone else can actually work from.
- Narrate - do the task once and talk through every step as you go, including the parts that feel too obvious to mention. Record it or type it out roughly. Do not organize anything yet, and do not clean it up. The messy version contains details the tidy version always loses.
- Draft - hand that narration to AI and ask for a numbered procedure with a purpose line, the tools or access needed, the steps in order, and a short section on what to do when something goes wrong. Ask it to flag anywhere your narration was ambiguous rather than guessing.
- Run - give the draft to someone who has never done the task and have them follow it while you watch in silence. Every place they hesitate is a gap in the document, not a gap in them. Fix those specific lines and you are done.
What belongs in an SOP and what does not
The most common failure is a document so thorough that nobody reads it. An SOP is an instruction sheet for someone mid-task, not a reference manual. If a line does not change what the person does next, it does not belong.
| Include | Cut |
|---|---|
| The exact click, field, or action, named specifically | Background on why the process exists at all |
| What access or tools they need before starting | History of how the process used to work |
| What a correct finished result looks like | Long explanations of company philosophy |
| What to do when the common thing goes wrong | Every rare edge case you can imagine |
What to include versus what to cut
Ask AI to keep the draft under one page wherever the process allows it. Length is not thoroughness. A one-page procedure that gets followed beats a six-page one that gets skimmed, and the six-page version is usually one page of instructions padded with context nobody needed mid-task.
Keeping SOPs alive after you write them
Documented processes go stale the moment the underlying tool or workflow changes, and a stale SOP is worse than none because people follow it and get the wrong result. The fix is small: put the date and the owner at the top of every procedure, and make updating it part of whatever change caused the drift. If you change how invoices get sent, the SOP edit happens in the same sitting, not later.
AI makes that update cheap too. Paste the current SOP and describe what changed, and you get a revised version in seconds rather than a rewrite you postpone for a month. The reason SOPs rot is that editing them used to cost as much as writing them.
Write the first one this week
Pick the single task people interrupt you about most often. Do it once while narrating every step out loud, hand the messy narration to AI for a numbered draft, then have someone else run it in front of you without help. You will have a working SOP in under an hour, and the interruptions for that task stop permanently.
Frequently asked questions
How do I write a standard operating procedure with AI?
Narrate the process out loud as you actually do it, including the obvious parts, then hand that raw narration to AI and ask for a numbered procedure with a purpose line, required access, ordered steps, and a short troubleshooting section. Then have someone who has never done the task follow the draft while you watch silently and fix every place they hesitate.
How long should an SOP be?
As short as the process allows, ideally one page. An SOP is read mid-task, not studied, so anything that does not change what the person does next should be cut. A one-page procedure people actually follow beats a thorough document that gets skimmed.
How do I stop my SOPs from going out of date?
Put the date and an owner at the top of each one, and make the update part of whatever change caused the drift rather than a separate task for later. AI makes revisions cheap enough that this is realistic - paste the current version, describe what changed, and you have an updated procedure in seconds.
Which process should I document first?
The one that generates the most interruptions, not the one that feels most important. If people ask you the same question three times a week, writing that procedure buys back real time immediately and proves the habit is worth continuing.