5 Ways to Turn Your Best Employee's Know-How Into Written SOPs With AI

To create SOPs with AI, record your best employee doing the task and talking through it, transcribe the recording, have ChatGPT or Claude draft a step-by-step procedure from the transcript, add photos of the key steps, then have that employee and a newer hire review it. Store the approved version where staff already look, with a version number and an owner.

The AI does the writing, which is the part everyone avoids. It does not know your business. Every useful SOP still comes from a person who has done the job hundreds of times, and it still needs that person to say "yes, that is right" before anyone else follows it. Treat AI as a fast scribe, not an expert.

Quick facts

• Best for tasks one or two people "just know": closing the register, receiving a delivery, prepping a treatment room, starting a service call.
• Tools needed: a phone that records video or audio, a transcription tool, and a chat assistant like ChatGPT or Claude.
• A first draft can come out of a single recorded walkthrough. Review is where the time goes, and it should.
• Photos beat paragraphs for anything physical (where the valve is, which shelf, what "clean" looks like).
• Version and date every SOP. An old SOP nobody knows is old is worse than none.

1. Record a walkthrough while the work happens

Do not ask your best employee to "write up how you do it." Ask them to do it, on a normal day, while someone records.

Set it up so the recording captures both hands and voice. A phone on a small tripod or in a shirt pocket is enough. Ask them to narrate as they go, and have a second person ask three questions at every step:

• What are you checking right now?
• What goes wrong here?
• What would a new person get wrong?

Those answers are where the real know-how lives. The steps themselves are usually obvious. The judgment calls ("if the count is off by more than a few dollars, stop and recount before you touch the safe") are what disappear when that person leaves.

Record one task per session. A closing routine and a delivery check are two SOPs, not one. If you are starting with opening and closing, our guide on how to automate opening and closing procedures with AI shows how the written SOP turns into a daily checklist afterward.

2. Transcribe, then let AI draft

Run the recording through a transcription tool. Many phones, meeting tools and AI assistants can do this; check what you already pay for before adding anything. The AI Tools Directory lists options by category if you need one.

Then paste the transcript into ChatGPT or Claude with a structured prompt. The structure matters more than the tool. Here is a template to start from.

SOP drafting prompt template

``` You are writing a standard operating procedure for a small [business type]. Use ONLY the transcript below. Do not add steps, tools, times, or rules that are not in the transcript. If something is unclear, list it under "Questions for reviewer" instead of guessing.

Format: Title: Purpose (one sentence): Who does this: When / how often: Before you start (tools, supplies, access needed): Steps (numbered, one action per step, start each with a verb): - After any step with a judgment call, add "Check:" with what to look for - After any step with a common mistake, add "Watch out:" with the mistake If something goes wrong (who to contact, what to do): Done means (how you know the task is complete): Questions for reviewer:

Write at a level a new hire on their first week can follow. Plain words. No filler.

Transcript: [paste transcript] ```

The "use ONLY the transcript" and "Questions for reviewer" lines are the guardrails. Without them, AI tools tend to fill gaps with generic steps that sound right and are not how your shop works.

3. Add photos at every step someone could get wrong

Text tells people what to do. Photos show where, and what right looks like.

Mark every step that involves a location, a setting, a label, or a "looks right" standard, and take a clear photo of each: the right breaker, the correct dial position, a properly stocked shelf, the finished paperwork. Stills from the walkthrough video work if the angle is good. Keep each photo next to its step, not in an appendix.

What AI does not do here: it will not reliably tell you which steps need a photo, and image-generating tools should never create "example" photos of your equipment. Use real pictures from your real location.

4. Run a two-person review loop

Every AI-drafted SOP gets two reviews before anyone relies on it.

The expert review. The employee you recorded reads it and fixes anything wrong. They also answer the "Questions for reviewer" list. Expect them to catch steps in the wrong order and missing judgment calls.

The new-person test. Someone who does not normally do the task follows the SOP, start to finish, with the expert watching and not helping. Every time they hesitate or ask a question, that is a gap. Add it.

Then paste the corrections back into the AI with a short instruction: "Revise the SOP with these corrections. Do not change anything else." Review the result one more time.

This loop is the step people want to skip. Do not. An SOP never tested by a new person is a draft.

5. Version it and store it where staff already look

The best SOP fails if nobody can find it at 9 pm on a Saturday.

Put SOPs where your team already goes during a shift: a clearly named shared folder, a pinned Slack or Teams channel, a wiki, an ops checklist app, or a QR code next to the equipment. One home, not three.

Every SOP needs:

• A version number and date at the top ("v1.2, updated March")
• An owner (the person who approves changes)
• A review trigger (new equipment, a new rule, or a mistake that the SOP did not prevent)

When something changes, record a short update walkthrough, run it through the same prompt with the old SOP attached, and ask the AI to produce a revised version with a "What changed" note at the top. Staff read the change note, not the whole document.

At a certain volume (many locations, many SOPs, frequent changes) this is worth automating: new recording in, transcript and draft out, review request sent to the owner, approved version published. SOP documentation and team training are included in our n8n workflow automation service, and our build vs. buy guide for ops documentation automation covers when that makes sense. For a real example of the payoff when documented processes become automated ones, see how we cut ops overhead 68% with n8n automation.

A starter checklist for your first SOP

• [ ] Pick one task that only one or two people know well
• [ ] Record them doing it on a normal day, narrating, with questions
• [ ] Transcribe and run the prompt template above
• [ ] Add real photos at every "where" or "looks like" step
• [ ] Expert review, new-person test, revise
• [ ] Add version, date, owner and review trigger, and store it in one place
• [ ] Repeat for the next task next week

One SOP a week gives you a real operations manual within a season, written by the people who know the work.

Training your team to do this themselves

The skill here is not technical. It is knowing how to prompt, how to check AI output, and how to keep the model from making things up. That is teachable. Our AI Enablement for Small Business Teams course is a general course for mixed small business teams: 10 live hours at $3,000 per trainee with a two-seat minimum.

State programs can help pay for training (not for the documentation work or software). In Massachusetts, the Workforce Training Fund Express Program can reimburse up to 100% of live training for employers with 100 or fewer Massachusetts W-2 employees, within caps of $3,000 per employee per course and $15,000 per company per calendar year, if approved. Two trainees in one course is $6,000 in tuition, well under that annual cap. Other New England states run different programs with different rules; start with ways to get your New England team AI-trained on the state's dime or browse AI training grants by state.

FAQ

How do you create SOPs with AI?

You create SOPs with AI by recording an experienced employee doing the task, transcribing the recording, and having ChatGPT or Claude draft a numbered procedure from the transcript using a structured prompt. You then add real photos, run an expert review and a new-person test, and store the approved version with a version number and an owner. The AI writes the draft, but the knowledge has to come from the employee; without a recording, it fills gaps with generic steps from other businesses.

Which tasks should I turn into SOPs first?

Start with tasks that only one or two people know well and that would hurt most if those people left, such as closing the register, receiving a delivery or starting a service call. Tasks done every day or checked by inspectors come next. If you run a regulated business, our list of compliance logs to automate first is a good place to start.

How much does it cost to create SOPs with AI?

The tools usually cost little or nothing extra, because most businesses already have a phone that records, a transcription option and a chat assistant. The real cost is staff time for the recording and the two reviews. If you want your team trained to do this well, our courses are $3,000 per trainee, and Massachusetts employers with 100 or fewer Massachusetts W-2 employees may be reimbursed up to 100% if approved; the rules are on our Massachusetts AI training grants page.

How long does it take to create an SOP with AI?

A first draft can come out of a single recorded walkthrough, so the drafting itself is fast. Review takes longer, and it should, because the expert review and the new-person test are what make the SOP usable. At one SOP a week, you have a working operations manual within a season.

Is it safe to put our procedures into ChatGPT or Claude?

Procedures are usually fine, but check your account's data settings and your industry rules first. Leave out customer or patient information, passwords, alarm codes, safe combinations and anything personnel-related. Use placeholders like "[alarm code]" in the SOP and store the real values separately.

Should I use an AI SOP generator app or a general assistant like ChatGPT or Claude?

A general assistant with a good prompt works well for most small businesses, because the structure of the prompt matters more than the tool. A dedicated app can help with storage, versioning and sign-offs once you have many SOPs. Whichever you pick, keep one owner per SOP so updates do not drift.

How do I get started creating SOPs with AI?

Pick the one task that would hurt most if the person who knows it quit tomorrow, and record them doing it this week. Run the transcript through the prompt template in this post, add photos, and complete both reviews before anyone relies on it. When you have a stack of SOPs, how state grants can fund the skills behind automated operations shows how to train the team that will turn them into automations.

Next step

Pick the one task that would hurt most if the person who knows it quit tomorrow, and record it this week. When you want to turn a stack of SOPs into checklists, logs and automated handoffs, book a free AI audit and we will map where documentation should feed automation first.