Your most experienced person just gave two weeks notice. And everything they know about how the actual work gets done is sitting in their head, their inbox, and a Slack thread from 2022 that nobody can find.

This is the problem AI SOP prompts were made for. Not replacing the expertise. Just getting it out of one person's skull and into a document before it walks out the door.

Standard operating procedures are where most operations documentation goes to die. They take forever to write, they go stale instantly, and the people who need them most hate writing them. AI doesn't fix all of that. But it can cut the draft time down dramatically, ask the questions you forgot to ask, and turn a rambling brain dump into something that looks like a process.

Here's how to do it without making a bigger mess than you started with.

What AI SOP prompts can actually do (and what they can't)

AI is fast. That's the whole thing. It can take your messy notes from an onboarding call, a Loom transcript, or a half-finished Google Doc and turn them into a structured first draft in under a minute. It's genuinely useful for scaffolding: headings, checklists, role-specific versions, quality criteria, exception documentation.

What it cannot do is know your business. It doesn't know that the vendor portal times out after 10 minutes and you have to re-authenticate. It doesn't know that the finance team actually approves this, not the ops manager, even though the org chart says otherwise. It doesn't know which steps the outgoing person skipped because they had 10 years of context and didn't need them.

Rule #5 in Don't Replace Me says it plainly: it's not smart, it's fast. Speed is not operational truth. The SOP draft AI hands you will look clean and organized. That doesn't mean it's accurate.

Your job is to supply the reality. AI's job is to structure it.

Before you paste anything: what not to put in an AI tool

Before the prompts, a hard stop on data safety.

Do not paste any of the following into a general AI tool like ChatGPT or Claude unless your organization has explicitly approved that tool for sensitive data:

If you're not sure whether your company has approved a particular AI tool for business use, ask before you paste. Check your AI workplace policy first. This is not paranoia. It's just the actual rules of using tools responsibly.

Anonymize your notes before using them. Replace names with roles. Replace system names with generics if needed. The prompt still works.

The reusable AI SOP prompt formula

Every good SOP prompt follows the same structure. Memorize this and you can build your own:

Role (who's writing this) + Context (what process, what system, what team) + Source material (your notes, transcript, or existing doc) + Output format (what you want back) + Constraints (what AI must not invent)

That last part is the one people skip. Always tell the AI what it's not allowed to make up. Otherwise it will fill gaps with plausible-sounding nonsense, and plausible-sounding nonsense in an SOP is genuinely dangerous.

This came from a book.

Don't Replace Me

200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.

Get the Book →

10 AI SOP prompts you can copy and use today

Prompt 1: Turn messy notes into a first SOP draft

You are an operations writer. I'm going to give you rough notes about a workflow 
our team runs. Turn them into a structured SOP draft with: a one-paragraph 
process overview, numbered steps, the role responsible for each step, and a 
"common mistakes" section at the end.

Do not invent steps, owners, system names, or approval paths. If something is 
unclear in my notes, flag it with [NEEDS CLARIFICATION] instead of guessing.

Here are my notes:
[PASTE YOUR NOTES HERE]

Prompt 2: Extract steps from a transcript

I have a transcript from an interview with a team member explaining how they 
run [PROCESS NAME]. Extract every distinct action step they mention and list 
them in order. Number them. Where the speaker jumps around, reorganize 
chronologically. Mark any step that seems implied but wasn't stated explicitly 
with [ASSUMED - VERIFY].

Do not add steps that weren't in the transcript. 

Transcript:
[PASTE ANONYMIZED TRANSCRIPT HERE]

Prompt 3: Find the missing context

I have a draft SOP for [PROCESS NAME]. Read it and give me a list of questions 
I need to answer before this document is safe to publish. Focus on: missing 
owners, unclear triggers ("when does this process start?"), undefined terms, 
absent approval steps, unstated assumptions, and steps that could go wrong 
without more detail.

Format your output as a numbered list of specific questions.

SOP draft:
[PASTE DRAFT HERE]

Prompt 4: Create a checklist version

Take this SOP and produce two things: 
1. A one-page quick-reference checklist for someone doing this process 
 for the first time.
2. A shorter checklist for someone who knows the process and just needs 
 a reminder of the sequence.

Use checkboxes. Keep language action-oriented. Do not add steps that aren't 
in the source SOP.

SOP:
[PASTE SOP HERE]

Prompt 5: Document exceptions

I'm going to describe the normal version of our [PROCESS NAME] SOP and also 
give you notes on common exceptions we handle. Create an "Exceptions and 
Edge Cases" section that lists each exception, what triggers it, how it 
differs from the standard process, and who needs to be involved.

Flag any exception where you're missing information about the correct 
resolution with [ESCALATION PATH UNCLEAR].

Normal process notes:
[PASTE NOTES]

Exception notes:
[PASTE EXCEPTION NOTES]

Prompt 6: Define "done" and quality checks

Based on this SOP draft, write a "Definition of Done" section and a 
"Quality Checks" section. 

Definition of Done: what does a completed, correct instance of this 
process look like? What can the person check to confirm they're finished?

Quality Checks: what should a reviewer look for when auditing this work? 
What are the most common errors?

Do not invent quality criteria. If the source material doesn't contain 
enough information to define a quality check, say so.

SOP draft:
[PASTE HERE]

Prompt 7: Create a role-specific version

I have a full team SOP for [PROCESS NAME]. Create a role-specific version 
for [ROLE NAME] only. Include only the steps this role is responsible for, 
with clear handoff points to other roles marked as [HANDOFF TO: ROLE NAME].

Add a brief "What you're responsible for" intro paragraph and a 
"What happens before/after your part" section.

Full SOP:
[PASTE HERE]

Prompt 8: Turn an SOP into onboarding material

Take this SOP and turn it into an onboarding guide for someone joining 
the team and running this process for the first time in their first 30 days.

Include: a plain-English "why this process exists" intro, the steps in 
beginner-friendly language, tips for common mistakes, and a "who to ask 
if you're stuck" section (I'll fill in the names, just leave [NAME/ROLE] 
placeholders).

Do not soften or skip steps to make it seem simpler. Accuracy matters 
more than friendliness.

SOP:
[PASTE HERE]

These onboarding-ready outputs pair well with the AI onboarding prompts and AI training prompts we've covered separately. They're different enough to be worth treating as distinct workflows.

Prompt 9: Review an existing SOP for risk

You are an operations auditor. Review this SOP for risks. Look for: 
steps with no named owner, approval paths that are vague or missing, 
compliance or legal language that wasn't reviewed by a qualified person, 
steps that assume access or permissions without specifying how to get them, 
and outdated system references.

Output a risk log. For each risk, note the specific section, the type of 
risk, and what action is needed to resolve it.

Do not provide legal, compliance, or security guidance. Flag those areas 
for human expert review.

SOP:
[PASTE HERE]

Prompt 10: Make a lightweight update log entry

I made the following changes to our [PROCESS NAME] SOP:
[DESCRIBE WHAT CHANGED AND WHY]

Write a concise update log entry for this change. Include: date placeholder 
([DATE]), what changed, why it changed, and who approved the change 
([APPROVER NAME] placeholder).

Keep it under 100 words. Use past tense. This is a record, not an 
announcement.

What to do after AI drafts your SOP

The draft is not the SOP. This is the mistake people make. They get a clean, well-formatted document back from Claude or ChatGPT and think the work is done. It isn't.

Before any AI-drafted SOP becomes official documentation, someone who actually does the work needs to read it step by step and verify it's real. Not skim it. Read it like a new hire would follow it on their first day. Walk through the actual system. Check that the access paths, tool names, and approval flows are accurate.

Then you need an owner. Not "the team." One person whose name is on the document and who is responsible for keeping it current. Set a review cycle. Quarterly for high-frequency processes, annually for stable ones. And store the SOP in your actual source-of-truth system, whether that's Notion, Confluence, SharePoint, or wherever your team actually looks things up. A great doc that lives in someone's Google Drive is just elaborate folklore.

An AI-generated SOP that nobody validated is just polished chaos with better formatting.

For anything touching compliance, security, legal commitments, or customer-facing guarantees, human expert review is not optional. The prompts above will flag these areas. Do not skip those flags.

If you're looking for how this connects to broader documentation work, the AI documentation prompts article covers the wider set. And if you're trying to fix broken workflows before documenting them, start with the AI workflow audit prompts first. Documenting a broken process just makes the broken process official.

The thing AI will never give you

Taste. The ability to look at a step in a process and know it's the one that will quietly burn the building down if someone skips it. The judgment to know which exceptions are genuinely rare and which ones happen every Tuesday. The institutional memory of why the process was built the way it was in the first place.

That's the stuff that lives in the head of your person who's leaving. AI can help you get it out of their head faster. It cannot replace it once they're gone.

The prompts above are tools for extraction and structure. The validation, the context, the accountability, and the taste: that's still yours.

Frequently asked questions

Can I use ChatGPT to write SOPs for my company?

Yes, with clear limits. ChatGPT is useful for drafting structure, checklists, role-specific versions, and exception documentation. It cannot verify that the steps it generates are accurate for your actual systems and workflows. Every AI-drafted SOP needs human validation before it goes live. Sensitive data including credentials, PII, confidential strategy, and legal content should never be pasted into a general AI tool.

How do I make sure an AI-written SOP is accurate?

Have someone who actually does the process walk through the draft step by step, in the real system, not just by reading it. AI drafts look polished. That's the danger. Accuracy comes from verification against reality, not from formatting. Use Prompt 3 above to surface missing context before you do that review.

What's the difference between an SOP and a process doc?

They're often used interchangeably, but an SOP (Standard Operating Procedure) typically implies a higher bar: a specific output standard, a named owner, approval authority, a version date, and a review cycle. A process doc can be informal. An SOP is the official version. AI documentation prompts can help with both.

How do I document tribal knowledge before someone leaves?

Record an interview or a Loom walkthrough of the process. Get the person to narrate what they're doing and why. Then use Prompt 2 (extract steps from a transcript) to pull the structure. Follow up with Prompt 3 to find what's missing. This won't capture everything, but it captures far more than asking someone to write it down themselves.

Should I use AI to update existing SOPs?

Yes, carefully. Prompt 10 above gives you a lightweight update log format. Prompt 9 will audit an existing SOP for stale or risky content. The risk with AI-assisted updates is the same as with new drafts: it can generate plausible-sounding updates that don't reflect how the process actually works now. Always validate against current reality before publishing an update.

What should I never let AI decide in an SOP?

Don't let AI invent: process owners, approval authority, access permissions, compliance requirements, legal obligations, customer commitments, system behavior, security controls, or anything with regulatory implications. AI can suggest placeholders for all of these. The actual values need to come from the people with the authority to define them.