Operations
Drafting Standard Operating Procedures with AI
The business shouldn't live in your head. If you're the only one who knows how to open up, close down, handle a refund, or restock the shelves, you're chained to the shop — and every new hire needs weeks of shadowing to get up to speed. AI can help you turn that know-how into written standard operating procedures: plain, step-by-step instructions anyone can follow.
What it is
A standard operating procedure (SOP) is just a written recipe for how your business does something: the steps, in order, with the details that matter. Writing SOPs has always been the kind of task owners mean to do and never get to, because starting from a blank page is painful. AI removes the blank page. You talk through how you do something — type it out roughly, or dictate it into your phone — and the AI turns it into a clean, numbered procedure with steps, checks, and notes.
You still own the content: the AI doesn't know that your oven runs hot on the left side or that the supplier in Dayton needs the order by Tuesday. What it does is take your rough brain-dump and shape it into something readable, spot the steps you skipped, and ask "what happens if the card reader fails?" so the document covers the cases a new person will actually hit.
The result is a library of procedures — opening, closing, refunds, deliveries, restocking, customer complaints — that a new hire can read on day one instead of shadowing you for three weeks. General AI chat tools like ChatGPT, Claude, or Gemini can do this job well; you don't need specialized SOP software to start.
Who it's for
This is for owners whose business depends on them personally: the tradesperson, the shop owner, the cafe manager who is the only one who knows the till routine. If you've ever thought "I can't take a day off because nobody else knows how," SOPs are your exit route from that trap.
It helps less if your work changes completely every day and routines are rare — creative and consulting work has fewer repeatable procedures. And it's not a substitute for real training: an SOP helps a trained person work independently, but it won't turn a total beginner into a skilled worker on its own.
What it costs
Most tools offer a free tier that is more than enough for SOP drafting. Paid plans for general AI assistants are usually billed per user per month, often roughly $10–$50/user/month — check the vendor's current pricing, since it changes. Dedicated SOP and documentation tools exist too, but a general AI chat tool plus a shared folder (Google Drive, or even printed binders) is all most small businesses need.
The real cost is your time: an hour or two per procedure to dictate, review, and test. That sounds like a lot until you compare it to training your tenth hire from scratch.
Target ROI: the honest math EXAMPLE
The payoff shows up in faster onboarding, fewer mistakes, and the owner's time freed from constant questions and shadowing.
Example: Suppose writing one procedure takes 3 hours and you need 10 of them — 30 hours, or $750 of your time at $25/hr. If AI drafting cuts the work in half, you save ~$375 against a $20/month tool. This is mostly a one-off benefit; the ongoing return is faster training and fewer staff mistakes — measure training time per new hire.
What to actually measure:
- Days from a new hire's start until they work a shift without close supervision
- Number of questions staff ask you per day about routine tasks
- Mistake or rework rate on tasks that now have written procedures
- How many procedures are written and actually in use after 90 days
How to set it up
- List the procedures that matter most. Write down the 5–10 tasks that only you know or that go wrong when you're away: opening, closing, refunds, handling a complaint, placing the supplier order, cleaning and safety checks. Start with the one that causes the most pain.
- Record yourself doing the task. Do the task with your phone recording voice notes, or just talk through it out loud for five minutes: what you do first, second, third, and the little judgment calls in between. Rough and rambling is fine — that's the AI's raw material.
- Ask the AI to turn it into a procedure. Paste your notes into a general AI tool and ask for a numbered step-by-step procedure written for a new employee, with any safety warnings or "if this happens" branches included. Ask it to flag steps you might have skipped.
- Fix what's wrong. Read the draft and correct the details only you know: the right temperatures, the right forms, the supplier names, the exceptions. The AI gives you structure; you give it truth.
- Have someone else test it. Hand the draft to your most junior team member and watch them follow it on a quiet day. Every point where they hesitate or get it wrong is a sentence that needs rewriting. This testing step is the difference between a document that works and one that just looks done.
- Store it where people will actually find it. Put the finished SOP in one shared place — a printed binder by the till, a shared folder, or pinned in your team chat. Name files so they're findable: "Closing the shop — evening shift," not "procedure_final_v2."
- Review once a year, or when something changes. SOPs go stale: suppliers change, equipment gets replaced, rules shift. Set a calendar reminder to re-read each one annually, and update it the same week a process changes.
Watch-outs and honest limitations
The AI will confidently write steps that sound right and are wrong — wrong temperatures, wrong legal requirements, wrong tool names — because it's guessing from your notes, not from your trade. Every SOP must be reviewed by someone who actually knows the work. For safety-critical procedures (food handling, electrical, driving), get a qualified person to sign off, not just the AI.
Don't feed the AI anything private about employees or customers while drafting. Use example names and anonymized details, and don't paste real customer data into a chat tool unless you understand its privacy policy.
Finally, an SOP is a tool, not a straitjacket. If staff start following a procedure that clearly isn't working, they need permission to tell you so. Build a simple feedback habit: "follow the sheet, but write down what's wrong with it."
What to measure in your first 30 days
- Number of procedures written, tested, and stored in the shared location
- How many times a staff member used an SOP without asking you first
- Errors or do-overs on tasks now covered by a procedure
- Hours you personally spend training or shadowing new hires
- Staff confidence on routine tasks, asked in a quick weekly check-in