AI for Creating SOPs: How Consultants Document a Client's Process

Record the client's walk-through (screen and voice), transcribe it, then have an AI assistant turn the transcript into numbered steps with an owner, inputs, exceptions and a check for each stage. You then test the draft with someone who has never done the task, fix the gaps and get the client's sign-off before it is issued.

Most pages on this topic review SOP generators. The harder part for a consultant is not the tool; it is getting a faithful account of a process that lives in people's heads, in a form the next person can follow. The sequence that works runs from recording to sign-off, with a prompt at each AI step and a newcomer test that stops a tidy document from describing a process that does not exist.

Follow me on Instagram@sagnikteaches

The six stages from recording to issued SOP

1. Agree and prepare: scope, permission to record, what to mask, who signs off.
2. Record the walk-through: the person who does the task, doing a real example, talking aloud.
3. Transcribe and clean: a text version with timestamps, names fixed, personal data removed.
4. Draft with AI: transcript to numbered steps, then exception paths.
5. Test: a person new to the task follows the draft without help.
6. Sign off and hand over: client owner approves, review date set, versions controlled.

The first, fifth and sixth stages are the ones a tool cannot do, and they are what clients pay a consultant for. Before you start, check the process is stable enough to document: if two people do it two different ways and nobody has decided which is right, settle that first, or the SOP will set the confusion in writing. How to document your processes before adding AI gives the wider case.

Connect on LinkedInSagnik Bhattacharya

Stage 1: agree, mask and prepare

Before any recording, get the client's written agreement on what will be recorded, who will see the recording, where it is stored and when it will be deleted. Ask them to mask or use dummy data for anything personal: customer names, account numbers, payment details. If the recording contains personal data you did not want, delete the file and re-record rather than trying to edit it later. Check the rules that apply to recording the people on the call.

Subscribe on YouTube@sagnikteaches

Use a business-tier account for any tool that will see the transcript, with terms you have read; vendors describe business plans as not training on customer content by default, but check the page for the plan you hold. Keep client material in a project per client so nothing mixes between engagements, in the way described in reusing past client work with AI without leaking client data.

Prepare the person being recorded with three lines: pick a normal example, not the easiest one; say what you are doing and why as you go; and say out loud when you are about to do something that "depends". Those spoken "depends" moments are where the exception paths hide.

Stage 2: record a walk-through that contains the real process

A good walk-through is 10 to 25 minutes for one task. Longer than that, and you have several processes. Ask the person to do a real example, narrating. Interrupt with questions only at natural pauses: "What would you do if the supplier code was missing?" "How do you know that one is urgent?" "Who do you tell?"

If the task spans screens, record the screen with audio. If it is a physical or meeting-based process, record audio and take photographs. Capture also the inputs and outputs: the form they started with and the thing they finished with. An SOP without inputs and outputs is a description of activity, not a procedure.

A question list for the interview part

• What triggers this task, and how often does it happen?
• What do you need in front of you before you start?
• What is the first thing you check, and what do you do if it is wrong?
• Which steps do you do from memory that a new person would not know?
• Where do mistakes usually happen, and how do you spot them?
• When do you ask someone else, and who?
• How do you know you have finished?

Stage 3: transcribe and clean

Use any transcription tool whose terms you have checked, or the built-in transcription in your recording software. Export a text file with timestamps. Then clean it: correct product and system names, replace personal data with placeholders, and mark the points where the speaker was clicking silently, because an AI draft cannot guess what happened in silence. If you recorded the screen, note the screen names or page titles next to the timestamps where they changed.

For long recordings, split the transcript into chunks by task phase (set-up, main task, checks), and process each separately. A model is more reliable on a chunk of a few thousand words than on one long block, and chunking also makes your checking easier. Label each chunk with its phase and start and end timestamps, so every draft step can be traced back to the moment in the recording it came from.

Stage 4: from transcript to numbered steps

This is the stage where AI earns its keep. Give the assistant the transcript, tell it exactly what a good SOP looks like, and make it mark anything it is unsure of. The prompt below is the one to adapt.

You are helping a consultant write a standard operating procedure from a recorded walk-through. The transcript is below.
Write the SOP using ONLY what is in the transcript.
Format:
1. Purpose (one sentence), Owner (role), Trigger, Inputs needed, Output.
2. Numbered steps. Each step: one action starting with a verb, the system or place where it happens, and what "done" looks like. No more than one action per step.
3. A "Decision points" list: each place the person said "it depends" or made a choice, with the condition and the outcome.
4. An "If something goes wrong" table: problem, what to do, who to tell.
5. A "Check before finishing" list of 3 to 6 yes/no items.
Rules: where the transcript is unclear or a step seems to be missing, write [GAP: what is missing] in place of guessing. Do not add steps from general knowledge. Keep each step under 25 words. Use plain language a new starter would understand.
Transcript:
[paste]

The [GAP] rule is the key to a trustworthy draft. In an illustrative 18-minute recording, expect four to eight gaps: a login the person did silently, a rule they applied without saying so, a threshold they used by instinct. Each gap becomes a question for the client. Gaps are the product of the draft, not its failure.

A worked SOP: raising a supplier purchase order

Say a small manufacturer's buyer records a 14-minute walk-through of raising a purchase order for a regular supplier. The transcript is 2,100 words. After one pass with the prompt above, the draft below is produced, with the consultant's edits applied (illustrative).

SOP: Raise a purchase order for an approved supplier

Owner: Buyer. Trigger: stock level report shows an item below reorder point. Inputs: reorder report, supplier price list, approved supplier list. Output: purchase order sent to the supplier and logged.

1. Open the reorder report in the stock system and filter to items below reorder point.
2. Check each item is on the approved supplier list. If not, go to Decision point A.
3. Check the quantity: order the reorder quantity shown, rounded up to the supplier's pack size.
4. Open the supplier price list and confirm the unit price. If it differs from the system price by more than 5 per cent, go to Decision point B.
5. Create the purchase order in the stock system; select the supplier, add lines, enter the delivery date.
6. If the order total is above $2,500, send for approval to the operations manager and wait for the approval email before step 7.
7. Send the purchase order to the supplier by email using the template, attaching the PDF.
8. Log the order number and the date sent in the order tracker.

Decision point A (supplier not approved): do not order. Tell the operations manager and attach the item and the reason. Decision point B (price differs by more than 5 per cent): email the supplier to confirm the price before ordering; record the answer in the tracker.

Check before finishing: Is the order number in the tracker? Was approval obtained where the total exceeds $2,500? Does the PDF show the right delivery date?

Notice what the consultant did to the raw draft. Two [GAP] flags were resolved with the buyer: the $2,500 approval threshold (the buyer had said "anything big") and the 5 per cent price tolerance (the buyer said "if it looks off"). Both numbers came from the client, not the tool. Without the gap flags, the model would have written "above a significant amount" and the SOP would have been useless on day one.

Stage 5: exception paths and the "what if" pass

The main path is easy. SOPs fail on exceptions. After the first draft, run a second prompt that looks for them, then ask the client's team in a short session.

Here is the SOP draft. List up to ten things that could go wrong or differ from the normal case for each step, based on the transcript only. Then list questions I should ask the person who does this task to find out how they handle each one. Do not answer the questions yourself.

Expect questions such as: What if the supplier is closed? What if the system rejects the order? What if two people raise the same order? What if the item is discontinued? Take ten minutes with the buyer, record the answers, and add the ones that matter as rows in the "If something goes wrong" table. Cap the list: an SOP that handles 40 exceptions is a manual, and nobody reads it. Keep the five that happen most often, and link the rest to a person to ask.

A before and after on a single step

Raw transcript line: "So then I'll just check it's in the right place and sort it out if not." AI draft: "Check the item is in the right place." After the exception pass: "Check the item is listed under the correct supplier in the stock system. If it is listed under another supplier, change it only after confirming with the operations manager, because supplier codes drive the approval rules." The second version contains a reason the transcript only hinted at, found by asking.

Stage 6: test, sign off and hand over

The test is the single most valuable step and the one most often skipped. Give the draft to someone who has never done the task, ask them to do it using only the SOP, and watch without helping. Note every place they hesitate, ask a question or make a mistake. Each one is a defect in the SOP, not in the person.

Illustratively, a first test of the purchase order SOP might surface three problems: the "reorder point" report has two similar names; "pack size" is not defined; and step 6 does not say how long to wait for approval. Fix them, retest with a second person if the changes were substantial, and then ask the client owner to sign off.

The sign-off check

• The owner has read every step and confirms it matches what the team should do, not merely what they did on the recording.
• A newcomer completed the task using the SOP only, with no help.
• Thresholds, names and system labels are correct and current.
• The SOP names its owner, version, date and review date.
• Personal data and recording files have been deleted as agreed.

Version control is simple: a date and a number on the page, one master copy in the client's own document system, old versions archived. Set the review date to six or twelve months, depending on how fast the process changes, and name the person who owns the review. Without an owner, an SOP decays.

Tools: capture generators, transcripts and chat assistants

Search results for this topic are full of SOP generator tools. They fall into two broad kinds, and the difference matters.

For a software-based task, many consultants use a capture tool for the screenshots and a transcript for the reasoning, then merge them. Verify each tool's current pricing and data terms on its own page before you commit, because plans change often; for a chat assistant, ChatGPT Business is $25 per seat a month monthly or $20 billed annually, with a two-seat minimum, and a solo consultant can use an individual plan instead. For a fuller view of what a small consultancy needs, see the AI tool stack a one-person consultancy needs, and for another take on the recording-first method, creating SOPs from screen recordings.

Turning one SOP into a service

The routine above is repeatable, which makes it a packageable service. An illustrative pricing structure for a consultant: a fixed fee per SOP for single, well-bounded tasks; a day rate for a batch of five to ten related SOPs with a testing day; and a retainer for review and updates. Time per SOP in this illustration is about two hours for the interview and recording, 45 minutes to clean and chunk the transcript, 30 minutes to draft and run the exception pass, 90 minutes to resolve gaps with the client, 60 minutes to test, and 30 minutes for sign-off and handover. That is under seven hours, of which the AI-assisted drafting is less than an hour; the rest is judgement and client contact, which is the part clients value.

For wording that lets you add this to a proposal, see how consultants use AI to write proposals in under an hour. Tell clients how you use AI in the work: transcripts are processed in business-tier tools, you review every output, and recordings are deleted at handover.

Realistic mistakes and how they show up

• The tidy fiction. The SOP describes the process as the manager believes it works. It shows up in the test, when the newcomer cannot find a step. Cure: always test with a newcomer.
• The invented threshold. The assistant writes "a reasonable amount". It shows up as a vague step. Cure: the [GAP] rule and a read-through that hunts for adjectives such as "large", "soon" and "appropriate".
• One SOP, three processes. The walk-through covered raising, approving and receiving orders. Cure: split by trigger and output.
• Personal data left in. A customer name survived in the transcript. Cure: search for names and numbers before the transcript reaches any tool.
• Nobody owns it. The SOP is accurate for three months. Cure: owner and review date on the page.

If you would like help building this routine around your own client work, that is what my AI implementation consultation covers, and you can start at the contact page. The practical advice for a first attempt is small: pick one task that a client repeats weekly, record it once, and run the six stages end to end before you sell it as a service.

Using the finished SOP for training and automation

A signed-off SOP has two uses beyond the shelf. The first is training: turn the numbered steps and decision points into a short module with a handful of questions, as covered in turning your SOPs into short modules and quizzes. The second is automation. Each decision point with a clear rule, such as the 5 per cent price tolerance in the worked example, is a candidate for an automated check, and each judgement-only step is one to leave with a person. Because the SOP lists inputs, outputs and thresholds, it is the specification you would otherwise have to write before automating anything. A consultant who documents first and automates second sells two services from one set of recordings.

Keep an eye on drift. Ask the owner to log any time the team departs from the SOP and why. After three months, review the log: a departure that keeps recurring is either a better way of working that the SOP should adopt, or a training gap. Either way, the SOP stays a working document instead of a framed certificate, and the client has a reason to keep you on for the review.

Questions consultants ask about AI-written SOPs

Should I use an SOP generator tool or a chat assistant?

Generator tools capture screens and clicks and produce step lists with screenshots quickly, which suits software tasks. A chat assistant working from a transcript handles judgement steps, exceptions and wording better. Many consultants use both: capture for the clicks, transcript for the reasoning. Test each on one process before choosing.

Do I need the client's permission to record the walk-through?

Yes. Get written agreement before recording, say what will be recorded, who will see it and when it will be deleted, and mask personal data on screen. Check the recording rules that apply to your client and anyone on the call.

How long should an SOP be?

As short as the task allows. A routine task rarely needs more than one to two pages: purpose, owner, steps, exceptions and a check. If it runs to ten pages it is probably several procedures, or it includes policy that belongs elsewhere.

Who owns the SOP once it is delivered?

Agree it in your engagement terms. Usually the client owns the finished procedure, and you keep your methods and templates. Name an owner on the SOP itself, and a review date, so it does not decay.

What if the walk-through differs from what the team really does?

That is common and useful. Record the difference, ask the people doing the work which version is current, and write the SOP for the agreed way. Test it by having someone who has never done the task follow it without help.

Further reads

• How to Write SOPs With AI: From Rough Notes to Clear Procedures — Turn rough notes into clear procedures.
• Accounting Firm Standard Operating Procedures With AI: Record to Publish — Record, draft and review SOPs in a professional firm.
• Insurance Agency SOPs With AI: Turn Routines Into Procedures — Turn routines into procedures in an agency setting.
• How to Tell If a Process Is Ready to Automate With AI — Test a process before you automate it.
• How Consultants Use AI for Client Research Before Discovery Calls — Research a client before the discovery call.
• Automating a Broken Process: Why It Backfires and What to Fix — Why documenting a broken process backfires too.
• Employee Handbook Template for Clients: Build a Master Copy With AI — How an HR consultant builds one master handbook with UK and US modules, a clause library and client fields, plus a checklist for the employment lawyer.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI's business pricing page (ChatGPT Business seats, training default) and Anthropic's Claude pricing page, checked 4 November 2026; the worked SOP and all figures are illustrative.