Skip to content
Home / How to Use AI to Write Standard Operating Procedures Your Team Will Follow

Writing

How to Use AI to Write Standard Operating Procedures Your Team Will Follow

AI can draft an SOP in minutes — but most SOPs die unread in a shared drive. Here is how to write procedures your team actually follows: short, specific, and built from how the work really gets done.

Colleagues reviewing a checklist document together in a modern office.
Colleagues reviewing a checklist document together — the moment a procedure stops being a file and starts being how the team works. Photograph: Darlene Alderson / Pexels.

Most SOPs die in a shared drive. Someone writes one because a manager asked for it, saves it as “SOP_Final_v2_FINAL.pdf”, and nobody ever opens it again. New hires ask the person sitting next to them instead. The old hands do it the way they’ve always done it. The document exists so the company can say it has one — and that’s all it does.

I’ve written SOPs with AI help for a small team now, and the ones that actually get followed look nothing like the ones that get filed away. The difference isn’t the AI. It’s whether the procedure describes the work as it’s really done, in steps a real person can follow, with the judgment calls left in.

Here’s the method I use.

1. An SOP is a recipe, not a policy document

The first mistake is writing a policy and calling it a procedure. “Employees must ensure all client onboarding is completed in a timely and professional manner” is a policy. It tells nobody what to do on Tuesday morning.

A procedure tells you what to do on Tuesday morning. Open the CRM. Create the client record. Send the welcome email from the template. Book the kickoff call. Check the contract is signed before you start the work. One action per step, in order, with the exact names of the tools and files involved.

Before I ask AI to write anything, I decide which kind of document I’m making. If the answer is “something a new person could follow without asking anyone a question,” it’s a procedure. If it reads like a rulebook, I’ve written the wrong thing — and AI will happily polish the wrong thing into something that looks very professional and helps nobody.

2. Start with the person who does the job, not the AI

AI can’t interview anyone. It has never watched your team process a refund, onboard a client, or publish a post. Everything it knows about your process comes from what you feed it — and if you feed it a vague description, you’ll get a vague procedure back.

So I start with the person who actually does the task. Twenty minutes, no more. I ask them to talk me through it as if they were training a new hire, and I record it or take rough notes. Not a formal interview — just “show me what you do, in order, and tell me where it usually goes sideways.”

What comes out is messy, and that’s the point. “First I check the inbox, unless it’s a Friday, then I check the shared drive because Sarah posts the updates there.” “I always double-check the discount code because the system applies the wrong one about once a month.” That mess is the real procedure. The polished version in someone’s head — the one where everything works first time — is fiction.

I feed that rough walkthrough to the AI, not a summary of it. The summary is where the exceptions get lost, and the exceptions are the most valuable part of any SOP.

3. Ask for steps, not paragraphs

Left alone, AI writes procedures as essays: three paragraphs of introduction, a paragraph of background, then some bullet points that bury the actual instructions. Nobody follows an essay.

The prompt I use is specific about the shape I want: “Turn this walkthrough into a standard operating procedure. Format: one sentence of purpose, then who does it, then when it happens, then numbered steps with one action each, then what ‘done’ looks like, then what to do when it goes wrong. Keep every step under 25 words. Use the exact tool and file names from the walkthrough.”

The word limit matters. It forces the AI to stop explaining and start instructing. “Log into the CRM and open the client’s record” beats “it is important to ensure that the client’s information has been properly accessed within the customer relationship management system” — and it’s not close.

I also ask for the failure section explicitly, because AI defaults to the happy path. “List the five most common things that go wrong with this task and what to do about each.” That section is the one your team will actually open the document for.

4. Test it on someone who has never done the task

A procedure you haven’t tested is a guess. I hand the draft to someone who has never done the task — ideally the newest person on the team — and ask them to follow it, out loud, while I watch. No helping, no hints. Just watch where they stop.

They always stop somewhere. A step that assumes they know where the template lives. A tool name that means one thing to the team and nothing to a newcomer. A step that says “check the report” without saying which report, or what “checked” even means.

Every stop is a fix. Add the link. Name the file. Define the word. The test takes fifteen minutes and it catches everything the writer couldn’t see, because the writer already knows how it works. That’s the curse of knowledge: the person who writes the procedure is the person who least needs it.

When the new person can get through the whole task without asking a question, the SOP is done. Not before.

5. Make it short enough to use

A fourteen-page SOP is a manual, and manuals don’t get read. If a procedure runs past three pages, it’s probably two procedures wearing a trench coat. Split it. One task, one document, one page if you can manage it.

Short also means honest about what doesn’t belong. Background, rationale, company history, the reason the process exists — all of it goes in a separate note, or in the one-sentence purpose line at the top. The steps are for doing. Everything else is for reading, and nobody opens an SOP to read.

I also put three things at the top of every SOP: the owner (one named person, not a department), the date it was last reviewed, and the next review date. An SOP with no owner rots. An SOP with no date is a fossil nobody trusts. AI can help here too — paste the old version in once a quarter and ask “what in this procedure no longer matches how we work?” — but only a human can answer that question truthfully.

6. Keep it where the work happens

The best-written SOP in the world is useless if it’s buried three folders deep in a drive nobody opens. I keep ours where the task happens: linked from the tool itself, pinned in the channel where the team asks questions about that task, printed (yes, printed) next to the desk for the one task people do once a month and always forget.

And when someone asks a question the SOP already answers, I don’t just answer the question. I answer it, then I point at the SOP. Gently, the first few times. The goal isn’t to be difficult — it’s to make the SOP the fastest route to the answer. If asking a colleague is faster than reading the procedure, people will ask the colleague every time. Make the document faster.

The honest truth

AI will draft you an SOP in about ninety seconds. It will look clean, complete, and professional. And it will be wrong in all the ways that matter — the exceptions, the real tool names, the step everyone skips, the thing that goes wrong once a month. The machine can’t know any of that, because it has never done your team’s job.

Use it the way I do: as the fastest drafting assistant you’ve ever had, working from a real walkthrough by the person who does the work, in short numbered steps, tested on someone who has never done the task. Real process first, AI draft second, a live test third, and a named owner keeping it current after that. That order is the whole trick. Get it right and your SOP stops being a document you file away. It becomes the thing your team actually opens — because it works.

Frequently Asked Questions

Can AI write a complete SOP on its own?

It can draft one from a good description, but it can’t know your tools, your exceptions, or your team’s habits. Feed it a real walkthrough from the person who does the task, then test the result on someone who has never done it. The draft is the easy part. The walkthrough and the test are the work.

How long should an SOP be?

As short as the task allows. One page is ideal; if it runs past three pages, split it into separate procedures. If a step needs explaining, the step is probably two steps. Background and rationale go in a separate note, not in the steps.

How do I get my team to actually use SOPs?

Keep them where the work happens, keep them current, and make them genuinely faster than asking a colleague. Put the owner and last-reviewed date at the top, and when someone asks a question the SOP answers, answer it — then point at the SOP. If the document is harder than asking, people will ask.

How often should SOPs be updated?

Every time the process changes, plus a scheduled review — quarterly works for most teams. Put a “last reviewed” date and a named owner on every one. An SOP with no owner rots, and an SOP with no date is a fossil nobody trusts.

Try it on your draft. Repetition finder runs in your browser. Paste your SOP draft in before you share it — it surfaces the words you lean on too often, so your procedure reads plainly instead of like a policy manual.

Continue your workflow

Was this guide helpful?

Your selection stays on this page. To send feedback to the publication, use our contact form.

About this publication

From Text Craft Pro

Practical guidance on clear writing, thoughtful editing, and useful web content. Our guides use illustrative examples and original diagrams, with AI-assisted drafting and editing.

Read our editorial approach About Text Craft Pro

Published 21 November 2026 · Text Craft Pro · AI-assisted educational writing. Editorial policy · Suggest a correction

Scroll to Top