How do I use AI to write SOPs and train employees?

Step 1: capture how the work actually gets done

Most small businesses don't have SOPs because writing them is miserable. The person who knows the job is busy doing the job, and a blank document is a terrible interviewer. AI changes the math because you no longer have to write. You just have to talk.

Pick the capture method that fits the task:

• Voice memo. Good for tasks done away from a computer, like opening the shop or prepping a job site. Ten minutes in the car is enough.
• Screen recording with narration. Best for computer work: entering an order, running payroll reports, posting a job listing. Record it once while doing it for real, talking out loud.
• A 20-minute interview. For anything with judgment calls. Someone (or an AI on a call) asks questions while the expert answers.

Good interview questions to ask:

1. What triggers this task? How do you know it's time?
2. What do you need open or in hand before you start?
3. Walk me through it, step by step, like I've never done it.
4. Where do new people usually mess this up?
5. What do you do when something's off? Who do you ask?
6. How do you know it's done right?

Question 4 is gold. The mistakes new hires make are the reason SOPs exist.

Step 2: let AI write the first draft

Transcribe the recording (most AI tools and meeting apps do this now), then give the AI the transcript with clear instructions. Here's a prompt you can adapt:

You are writing a standard operating procedure for a small business.
Use ONLY the transcript below. Do not add steps, tools or rules
that are not in the transcript. If something seems missing or
unclear, list it under "Questions for the expert" instead of guessing.

Format:
- Title, purpose (one sentence), who does it, how often
- What you need before starting
- Numbered steps, one action each, in plain language
- Common mistakes and how to avoid them
- What "done right" looks like
- Who to ask when something's off
- Questions for the expert

Write for a new employee in their first week. Short sentences.

Transcript:
[paste here]

The "Questions for the expert" line is the most important part. It turns the AI's guesses into a list of things to confirm instead of confident fiction.

A finished SOP outline looks something like this:

• Title: Closing out a completed job in the scheduling app
• Purpose: So the customer gets invoiced and the crew gets credit
• Who / when: Crew lead, same day the job finishes
• Before you start: Job photos taken, materials list updated
• Steps: 1 through 8, one action each
• Common mistakes: Forgetting after-photos; marking done before the customer walk-through
• Done right: Status is "Complete," photos attached, office notified
• Questions: Escalation contact and review date

Step 3: verify with the person who does the job

AI drafts sound confident whether they're right or wrong. So the expert reads the draft and fixes it. That usually takes far less time than writing it from scratch would have.

Then do the real test: hand the SOP to someone who has never done the task and have them follow it exactly, out loud, while the expert watches without helping. Every place the new person hesitates is a missing step. Fix it in the document, not in a verbal side note.

Only after that does the SOP count as published.

Free checklist: 50 tasks you can hand to AI agents this weekSorted by department. Read it free or get the printable PDF.
Get the checklist

Step 4: publish it somewhere people will actually search

The best SOP is useless if nobody can find it. Pick one home for all of them: a shared drive folder, a wiki tool, or the knowledge base inside software you already use. Don't scatter them across email attachments and someone's desktop.

A few rules that help:

• Name files the way people search. "Close out a completed job" beats "SOP-Ops-v3-FINAL."
• One task per SOP. Long manuals don't get read.
• Link the recording. A short screen recording next to the written steps helps visual learners.
• Put an owner and a review date at the top. Every three or six months, the owner rereads it. If the process changed, the SOP changes the same week.
• Make updates easy. When someone finds a wrong step, they tell the owner, and the owner fixes it right away.

A change in software, staff or pricing should trigger an SOP review on its own, without waiting for the calendar.

Step 5: add a Q&A helper and turn SOPs into training

Once your SOPs live in one place, you can put an AI helper on top of them. Employees ask a question in plain English ("how do I handle a customer who wants to reschedule same-day?") and get an answer drawn from your documents. This can be as simple as a shared project in a business AI plan with the SOPs uploaded, or a bot inside your team chat.

Set three rules for it:

1. Answer only from the SOPs. No outside guessing.
2. Always name the SOP the answer came from, so people can check.
3. If the answer isn't in the SOPs, say so and name the person to ask.

Those "not in the SOPs" moments are useful. Log them, and you have a list of the next SOPs to write.

The same documents become training material. AI can turn a set of SOPs into a first-week checklist, short quizzes for new hires, and practice scenarios like "a customer calls upset about a late crew. What do you do?" A manager still signs off that the new person can do the job, but the reading and quizzing no longer depend on someone's free afternoon.

This whole loop is what I set up as a fractional AI manager doing AI SOPs and training work, and it's one of the items in my 50 tasks to hand AI agents list.

What this looks like in a real small business

Example: picture a 15-person commercial cleaning company with steady turnover. The office manager has run the place for nine years, and most procedures live in her head. Every new hire means a week of her time, and every time she's out, things break.

Over a month, she records one voice memo or screen recording a day, ten minutes each: opening a new client account, scheduling a crew, handling a key handoff, reporting damage, supply ordering. AI turns each recording into a draft with a list of questions. She answers the questions, fixes the drafts, and a newer employee test-follows each one.

The SOPs go into one shared folder with plain names, each with her name as owner and a review date. A Q&A helper sits on top, so crew leads can text a question at 9 p.m. instead of calling her.

New hires get a first-week checklist and short quizzes built from the SOPs. She still trains them in person on the hands-on work. She just stops repeating the same twenty answers. Nobody's job went away; the one person everything depended on got some of her time back. (More on that worry in will AI replace my employees?)

The honest part

AI can only write down what someone said. If the expert skips a step in the recording, the draft will skip it too, and it will read just as confidently. The verification step is where quality comes from.

Hands-on skills still need hands-on training. An SOP can tell someone the order of steps for a floor finish; it can't give them the feel for it. Use SOPs to support shadowing, not replace it.

If a process changes every week, don't document it yet. Stabilize it first.

The Q&A helper can be wrong, too. Keep it to everyday operational questions. Safety procedures, legal or compliance requirements, and anything regulated need sign-off from whoever is responsible for them, and staff should go to a person for those.

And SOPs only work if someone owns them. Without an owner and a review date, they quietly go stale. That decay is how most SOP projects die.