Create an SOP with AI from One Person's Know-How
- Difficulty
- Beginner
- Time
- 1 hour, including the expert's time
Before you start
- The person who knows the process, and 20 to 30 minutes of their time
- A way to record what they say: a recording tool with a transcript, or a colleague taking notes
- An AI chat assistant your company has approved for internal documents
- A second person who has never done the task, for the test in Step 5
This playbook shows you how to create an SOP with AI from what one person already knows. Most processes that only one person can do are never written down because writing is slow. Talking is fast. So the expert talks, and the AI turns the transcript into a standard operating procedure and a checklist. The AI may only use what the expert said, because a model asked to fill gaps will invent plausible steps (hallucination). Every gap is marked so a person fills it.
Step 1: Record the expert doing or describing the task
Ask before you record, and tell the expert where the recording and transcript will be kept and who will see them. Then ask the expert to do the task while saying each step out loud, or to walk through the last time they did it. Prompt them with: what do you check first, what do you click, what can go wrong, what do you do when it does, how do you know you're done?
Use the AI assistant your company has approved for this kind of work, and follow your company's AI policy. If you don't know which tool is approved, ask before you paste anything. If the task involves passwords, keys or customer data, describe where they are kept (for example, "the shared password manager") and never read them out or paste them in.
Step 2: Turn the transcript into an SOP
Below is a transcript of [name] explaining how they do [task].
Write a standard operating procedure from it.
- Purpose: one sentence.
- When to do it and how often, only if the transcript says.
- What you need before starting.
- Steps: numbered, one action per step, in the order described.
- What can go wrong, and what to do.
- How you know it's done.
Use ONLY what the transcript says. Where a step is implied but not
explained, or the order is unclear, write [GAP: confirm] and what is
missing. Do not fill gaps with general best practice.
Transcript:
[paste]
Step 3: Close the gaps with the expert
Send the expert the draft with every [GAP: confirm] highlighted. Ask them to answer each one in a sentence and to correct any step that is wrong. Update the SOP by hand. This check is the step that makes the document trustworthy.
Step 4: Make the one-page checklist
Turn this SOP into a one-page checklist for someone doing the task.
One line per step, starting with a verb. Keep warnings next to the step
they belong to. Do not add or remove steps.
SOP:
[paste]
Step 5: Test it cold
Give the checklist to someone who has never done the task and watch them try it, without the expert helping. Every time they stop, ask, or guess, that's a missing or unclear step. Fix it in both the SOP and the checklist.
What to do next
Store the SOP where your team keeps its procedures, with an owner and a review date. When the process changes, the owner updates it. This works for any repeat task: a month-end close, onboarding a new hire, shipping an order. Customer-facing answers belong in your help center instead; see the ticket-to-article playbook.
Rather have someone set it up for you?
That's a fair call. LTFI, the agentic business operating system from Kief Studio, can set up the work these guides describe and run it with you. No website yet? Kief Studio will build you one for free.

