The SOP Extractor: Turn Messy Process Notes Into a Procedure Nobody Has to Guess About
Why this prompt matters
When the one person who knows a process leaves, the knowledge doesn't get archived — it just disappears with them. Replacement hires spend weeks re-deriving steps by trial and error, mistakes that used to get silently caught by an experienced person now reach customers or the books, and the next departure repeats the entire cycle because nothing was ever written down properly the first time. A rushed handover document that skips the exceptions and edge cases doesn't actually transfer the knowledge — it just transfers the assumption that everything will go smoothly, which is exactly when it won't.
What we use it for
You're an operations manager at a 40-person logistics company, and the warehouse shift lead who has personally run the end-of-day inventory reconciliation for three years just gave two weeks' notice. The only existing documentation is a half-finished Google Doc from 2023 and a Slack thread where she explained parts of the process to a coworker six months ago. You need a real SOP before her last day, built from whatever fragments of explanation you can gather — not written from scratch.
Prompt
Act as an operations documentation specialist who has written SOPs for teams where a missed step causes real financial or safety consequences, not just inconvenience. CONTEXT: Raw process notes: [PASTE YOUR ROUGH NOTES, CHAT THREADS, OR VOICE MEMO TRANSCRIPT HERE] Who will follow this SOP: [ROLE OR TEAM, e.g. "new warehouse shift leads with no prior training"] What breaks if a step is skipped or done wrong: [CONSEQUENCE, e.g. "inventory counts don't reconcile and we can't close the books until someone manually re-checks every bin"] TASK: Read the raw notes and extract the actual procedure being described, even if it's currently scattered across multiple messages, said out of order, or left half-explained. Do not invent steps that aren't implied by the notes. Where a step is ambiguous or a decision point isn't explained, mark it clearly rather than guessing what was meant. CONSTRAINTS: - Every step starts with an action verb (Check, Enter, Confirm, Escalate — not "You should...") - Number every step; group related steps under short subheadings if the process has distinct phases - Do not smooth over contradictions in the source notes — flag them - Keep each step to one action; split compound steps into separate numbered items - Assume the reader has zero prior context beyond what's in the notes OUTPUT FORMAT: 1. Title & Purpose — one line stating what this SOP accomplishes and why it exists 2. Applies To — who should be following this procedure 3. Numbered Procedure — the extracted steps, phase-grouped if needed 4. Edge Cases & Exceptions — situations mentioned in the notes that deviate from the main path 5. NEEDS CLARIFICATION — a bullet list of every point where the source notes were ambiguous, contradictory, or silent on what should happen next
Result
End-of-Day Inventory Reconciliation — Warehouse Shift Close
Purpose: Ensures physical inventory counts match system records before the warehouse closes for the night, so the morning shift starts with accurate stock data and finance can close the books without manual re-checks.
Applies To: Warehouse shift leads closing the evening shift.
Phase 1: Physical Count
- Walk all active bins in Zones A through D using the handheld scanner.
- Scan each bin's location barcode before scanning item barcodes within it.
- Flag any bin where the physical count doesn't match the scanner's expected count on-screen.
- Photograph any flagged bin before adjusting anything.
Phase 2: System Reconciliation
- Open the WMS reconciliation dashboard.
- Enter physical counts for all flagged bins from Phase 1.
- Confirm the variance report generates with no bins over a 2% discrepancy threshold.
- Escalate any bin over the 2% threshold to the inventory control lead before closing the shift — do not adjust the system count yourself.
Phase 3: Shift Close
- Submit the end-of-day reconciliation report in the WMS.
- Lock the scanner devices in the charging cabinet.
- Send the shift handover Slack message to the morning lead, including any bins still pending escalation.
Edge Cases & Exceptions: If a scanner fails mid-count, switch to the backup handheld in the office drawer and note which bins were counted on which device — mixed-device counts occasionally cause sync delays. If a flagged bin can't be resolved because product was moved without a transfer scan, do not guess the correct count — escalate immediately rather than entering an estimate.
NEEDS CLARIFICATION:
- The notes mention a “manager override” for large discrepancies but don't specify who counts as a manager for this purpose or how the override gets logged.
- It's unclear whether Zone E, mentioned once in passing, is included in the nightly count or only counted weekly.
- No guidance was given on what to do if the WMS dashboard itself is down at close — is there a manual fallback process?
Most SOP-writing advice assumes you're starting from a blank page. In practice, you're starting from three Slack threads, a half-finished Google Doc, and whatever the departing employee remembers to say out loud in their last week. This prompt is built for that reality — it doesn't ask you to write a procedure, it asks you to extract one from material that's already scattered, informal, and incomplete.
Why extraction, not generation
The instruction to not invent steps that aren't implied by the notes is the single most important line in this prompt. A model asked to “write an SOP for warehouse reconciliation” will happily generate a plausible-sounding procedure from its training data — which is exactly the wrong output, because it won't match what your team actually does. Anchoring the model to the source notes and forcing it to flag gaps rather than fill them keeps the output honest about what it actually knows versus what it's guessing.
Why NEEDS CLARIFICATION is a separate, mandatory section
Every real handover has holes in it — the departing employee explains 90% of the process fluently and glosses over the 10% that only comes up occasionally, which is usually the 10% that matters most when something goes wrong. A generic SOP-writer prompt will smooth those gaps into confident-sounding prose. This one forces every ambiguity into its own visible list, so whoever is training the new hire knows exactly which questions still need to be asked to the person walking out the door — while there's still time to ask them.
Why steps must start with action verbs
“You should check the variance report” is instruction. “Confirm the variance report generates with no bins over a 2% threshold” is a checklist item someone can literally check off. The constraint forces the model to produce something operational rather than descriptive, which is the difference between a document someone reads once and a document someone actually follows on their third night shift when they're tired and the reconciliation isn't matching.