Skip to content
Search
7 min read

How to Write an SOP With AI: Turn How You Work Into a Checklist

Meelie Gagne

TL;DR: Describe the job out loud or in rough notes, ask the AI to turn it into numbered steps with a question list for every gap, then have someone new follow it while you watch. The AI does the typing while you and your team supply every fact.

Learning how to write an SOP with AI is one of the fastest wins for anyone in operations. An SOP, or standard operating procedure, is a written set of steps for a job your team does again and again: opening the shop, onboarding a new client, closing the month, shipping a return. Many never get written down, because writing them takes time and the person who knows the job best is often the busiest.

An AI assistant is very good at the slow part. It can take a rambling voice note or a page of rough notes and turn it into a clean, numbered checklist much faster than you could type it. What it can't do is know how your business works. This lesson shows you how to split the work so the AI writes and your people decide.

What an AI-written SOP gets right, and where it goes wrong

An AI SOP draft is good at structure. It breaks a job into steps, puts them in order, uses the same format every time and writes in plain language. That's most of what makes a checklist easy to follow.

Where it goes wrong is detail. If your notes skip a step, the AI may fill the gap with a step that sounds reasonable but isn't what your team does. The invented step reads as smoothly as the real ones, so you can't spot it by tone. This is called hallucination, and the fix is to give the AI only your notes and ask it to flag every gap instead of filling it.

In an SOP that's a real problem. A made-up step in a cleaning checklist, a safety procedure or a payment process can be followed for months before anyone notices. So the method below does two things: it tells the AI not to guess, and it makes a person test every step.

Before you start: what stays out of the chat

Follow your company's AI policy, and use only the AI assistant your company approves. Then keep these out of anything you paste or record:

  • Passwords, door codes, alarm codes, safe combinations and Wi-Fi keys
  • API keys, login links or screenshots of admin screens
  • Customer or employee names, addresses, phone numbers or account numbers
  • Bank, card or payroll details

Your SOP doesn't need any of them. Write "enter the alarm code (kept in the manager's vault)" instead of the code itself. A good SOP points to where a secret lives. It never contains the secret, which also keeps the document safe to share with new hires.

Step 1: Get the job out of someone's head

Ask the person who does the job to talk through it, start to finish, as if they're training a new hire. A voice memo transcribed by your approved tool works well. So do messy bullet notes written while they actually do the job. Don't tidy anything yet. Include the odd bits: "if the printer jams, I do this", "on Fridays we also check that".

A few minutes of talking can be enough for a short task. If the job is long, record it in parts, one part per stage of the job. It's the same idea behind prompt decomposition, where one big prompt is split into several smaller ones: each part is easier to get right on its own.

Step 2: Turn the notes into a checklist

Paste the notes into the prompt below.

The Prompt:

You are helping an operations team write a standard operating procedure (SOP).

Turn the NOTES below into an SOP with these parts:
1. Title and one-sentence purpose.
2. Who does it, how often, and roughly how long it takes.
3. What you need before you start (tools, access, documents).
4. Numbered steps. One action per step, starting with a verb. Add "If..., then..." lines for the exceptions in the notes.
5. How you know it's done (what the finished result looks like).

Rules:
- Use only what is in the NOTES. Do not add steps, tools, times or rules that are not there.
- Where the NOTES are unclear or skip something, write [QUESTION: ...] in that spot instead of guessing.
- If the NOTES mention a password, code or key, replace it with [WHERE IS THIS KEPT?].
- Plain words. No step longer than two sentences.

NOTES:
"""
[paste the transcript or rough notes here]
"""

Why This Works: The fixed five-part structure gives every SOP the same shape, so people learn where to look. The "use only what is in the notes" rule stops the AI from padding the list with steps it thinks are normal. The [QUESTION] markers turn every gap into something a person has to answer, which is exactly where invented steps would otherwise appear.

What you get back: A one-page checklist with numbered steps, a few "If..., then..." branches and a scattering of [QUESTION] markers, such as "[QUESTION: who signs off the cash count?]". Those questions are the most valuable part. They show you what the person who does the job knows but never wrote down.

Step 3: Answer the questions, then test it on a real person

Take the draft back to the person who does the job and answer every [QUESTION] together. Then run a simple test: hand the SOP to someone who has never done the job and watch them follow it, without helping.

Every time they hesitate, ask a question or do something different, write it down. Those are the steps to fix. When you've collected the notes, you can paste them back into the AI:

Here is our SOP and the notes from a test run by a new person. Update the SOP to fix each problem in the notes. Mark every changed step with [CHANGED] so I can review it. Do not change steps the notes don't mention.

Read every [CHANGED] step before you accept it. If you'd like the AI to check its own work first, the verification prompt pattern shows how to add that check.

Step 4: Keep it current

An SOP that's out of date is worse than none, because people trust it. Give each SOP an owner, a "last checked" date at the top and a review date. If you're not sure how often, start with every three months and adjust to how often the job changes.

When a tool, supplier or rule changes, update the SOP that day. The AI makes this quick:

This step changed: [describe the change]. Update the SOP below. List every other step that might be affected by this change, and mark each with [CHECK] instead of editing it.

That last instruction matters. It asks the AI to point out knock-on effects without quietly rewriting them, so a person still decides.

A few SOPs to start with

Pick jobs that are frequent, done by one person and painful when they go wrong. Common first choices:

  • Opening and closing checklists
  • New client or new employee onboarding
  • Handling a return, refund or complaint
  • Month-end tasks that only one person knows
  • What to do when a key system is down

Start with one. When the first SOP survives a test run, the next one goes faster, because you can paste the finished SOP into the prompt as the example to copy.

Where to go next

For more lessons written for your job, go back to the operations track, or browse the Applied pillar for AI by role.

Frequently asked questions

Can AI write an SOP for me?

AI can write the draft. It's fast at turning rough notes into numbered steps in a consistent format. It doesn't know how your business works, so the facts have to come from the people who do the job, and the draft has to be tested by someone following it for real before you rely on it.

What should an SOP include?

A clear title and purpose, who does it and how often, what you need before you start, numbered steps with one action each, what to do when something goes wrong, and how you know the job is done. Add an owner and a "last checked" date so people know whether to trust it.

How do I stop AI from adding steps we don't do?

Tell it to use only the notes you gave it, and to write a question in any spot where the notes are unclear instead of guessing. Then have the person who does the job answer each question and check every step.

Is it safe to put company procedures into an AI tool?

Use only the AI tool your company has approved, and follow your company's AI policy. Remove passwords, codes, keys and any customer or employee details first. A well-written SOP should only say where a secret is kept, never the secret itself.

How often should SOPs be updated?

Update an SOP the day the process changes, and review it on a set schedule even if nothing seems to have changed. If you're not sure how often, start with every three months and adjust to how often the work changes.

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.