Business
SOP Audit & Rewrite AI Prompt
Audit and fix your messy SOPs with this AI prompt. Find gaps, cut bloat, and rewrite procedures teams will follow. Built for founders, managers, and teams.
The prompt
ROLE: You are an operations auditor who finds why SOPs fail in practice. CONTEXT: Here is my current SOP: [PASTE_SOP]. How it is actually used: [REALITY]. Known problems: [PROBLEMS]. Who uses it: [USERS]. TASK: Audit this SOP and rewrite it. FORMAT: 1. Audit Findings Table (issue, severity: critical/major/minor, evidence from the text). 2. What to Cut (bloated or obsolete sections). 3. What is Missing (gaps a new hire would hit). 4. Rewritten SOP (full clean version: purpose, scope, roles, numbered steps, checkpoints, exceptions). 5. Implementation Notes (how to roll out the new version, training needed). End with 3 signs that indicate this SOP needs its next review. CONSTRAINTS: The rewrite must be shorter than the original unless critical content was missing. Preserve any compliance-required language and flag it. Write for the actual users described, not an idealized reader. If any variable is unclear or missing, ask up to 3 targeted clarifying questions before producing the output, and clearly mark every assumption you make with [ASSUMPTION].
Variables to fill in
Replace each [variable] in the prompt with your own details:
[PASTE_SOP] [REALITY] [PROBLEMS] [USERS]
Example input
PASTE_SOP=[paste current SOP], REALITY=nobody reads it, team uses a Slack thread instead; PROBLEMS=12 pages, outdated screenshots, no owner; USERS=warehouse staff, many non-native English speakers
How to use this prompt
Paste the SOP plus honest notes on how it is really used, then pilot the rewrite with two users before replacing the old version.
Tips for the best results
- If the team uses a workaround, the workaround is the real process; document that instead of the fiction.
- Use simple language and visuals for frontline SOPs; reading level matters more than completeness.
- Date-stamp every SOP and name an owner; undated, ownerless SOPs rot silently.
Frequently asked questions
How often should SOPs be audited?
Annually at minimum, plus after any incident, process change, or when users report confusion.
Should I keep the old version?
Yes, archive it with the date. Version history protects you in disputes and shows what changed.