How to Write an SOP with AI
At Larkspur Coffee Roasters, a 12 kg drum roaster runs 24 kg of green coffee every Tuesday, and the difference between a repeatable batch and a scorched one is whether the closing shift remembered to log the drop temperature. When that knowledge lives in three people’s heads — Iris on roast, Tomas on bar, Maya on close — a new hire learns the job by watching and hoping.
This workflow turns those head-knowledge habits into a written standard operating procedure you can hand to anyone. Six prompts, each doing one job: fix the scope, convert real shifts into ordered steps, remove the guesswork from any step a beginner would fumble, add measurable control points, formalize the cleaning cadence, then test the draft against a deliberately bad day. The example throughout is Larkspur’s roast-and-clean SOP, but the same sequence fits a warehouse, a clinic back office, or a support desk.
What a Finished SOP Package Contains
Before prompting anything, agree on the shape of the deliverable. A usable SOP is not a paragraph of good intentions. It is a set of artifacts a shift lead can pick up and follow.
For Larkspur that means a one-page scope statement naming who does what and on which equipment; a numbered procedure for roast day with time, temperature, and quantity at each step; a cleaning schedule split by daily, weekly, and monthly cadence; a control-point table with pass or fail limits; and a revision block carrying a version number and an owner. If your draft is only prose, you do not have an SOP yet.
The reason to settle this up front is that models default to essay structure. Left alone, ChatGPT writes a confident narrative about the importance of consistency. The prompt has to demand the artifact instead. If you already build prompts as reusable templates, the habits in our structure output format guide apply directly here.
Step 1 — Lock the Scope, Roles, and Equipment
An SOP that tries to cover everything covers nothing. Start by making the model argue the boundary back to you.
You are an operations writer who drafts standard operating procedures for food and beverage businesses.
Ask me the ten questions you need answered before you can write a roast-day SOP for a small coffee roastery.
Focus your questions on: who performs each task, which equipment is involved, what triggers the procedure, and what is explicitly out of scope.
Do not write any part of the procedure yet. Ask the questions, then wait for my answers.You get a short interrogation instead of a draft. Answer it in plain notes — “Iris runs the 12 kg drum, Tomas covers bar, Maya closes” — and you now hold the raw material for every later step. Skipping this is why most generated SOPs stay vague: the model was never told who holds the screwdriver.
Step 2 — Convert Real Shifts into Ordered Steps
Feed the model an actual shift, not an idealized one. Real shifts carry the detail that makes a procedure followable.
Below are my rough notes from a Tuesday roast day.
Turn them into a numbered procedure with one action per step.
Rules:
1. Every step starts with a verb and names the person or role who performs it.
2. Add the time, weight, or temperature wherever my notes mention one.
3. If a step depends on the previous step finishing, say so at the end of the step.
4. Mark any place my notes are ambiguous with [CHECK] instead of guessing.
Output a numbered list only, with no introduction and no closing summary.You get fifteen to thirty numbered steps in sequence. The [CHECK] markers are the most valuable output: each one is a question you can resolve in ten seconds with the person who does the job, and each unresolved marker is a place a new hire would quietly invent their own method.
Step 3 — Strip the Guesswork from Beginner Steps
Then reread the procedure as if you had never seen a drum roaster. This pass catches instructions that assume silent knowledge.
Read the procedure below as a brand-new hire on their first Tuesday.
List every step a beginner could carry out two different ways, and for each one:
- quote the step,
- explain what is ambiguous,
- rewrite it so there is exactly one correct action, and
- state what the person should see, hear, or smell when it went right.
Hunt especially for unstated quantities, phrases like "until it looks right", and tools named without their location.You get a rewritten step list plus sensory confirmation for each action. “Charge the drum” becomes “charge 12 kg of green beans into the drum at 400 degrees Fahrenheit, and confirm the bean probe reads above 190 within 90 seconds.” The second version survives a new hire. The first one does not.
Expect ten to fifteen ambiguous steps on the first pass. Do not delete them. Each one is a gap between how the team thinks the job works and how the job actually works, which is the exact gap an SOP exists to close.
Step 4 — Add Control Points and Tolerance Limits
An SOP without a pass-or-fail test cannot be audited. Add the numbers that reveal drift before a customer tastes it.
Add a control-point table to the procedure.
Columns: control point, target value, acceptable range, how it is measured, who checks it, and what to do if it is out of range.
For this roastery include at minimum: charge weight, drop temperature, roast duration, cooling time, and grinder purge amount.
Keep the table to the points that actually change the product. Do not add a control point that cannot be measured with the equipment on site.You get a compact table that makes quality measurable instead of aspirational. The “what to do if out of range” column is the part people forget, and it is the part that matters at 06:40 when the first batch runs 40 seconds long.
Step 5 — Formalize the Cleaning and Sanitation Cadence
Cleaning is where SOPs quietly fail. It is repetitive, easy to skip, and impossible to reconstruct from memory after a busy Saturday.
Build a cleaning schedule for the same roastery and bar area.
Split it into three cadences: after every shift, weekly, and monthly.
For each task give: the task, the tool or chemical used, the surface or part it applies to, the person responsible, and a sign-off field.
Note which tasks must happen before food-contact surfaces are used again, and which tasks require the machine to be off and cooled.You get a checklist with a sign-off column, which converts cleaning from a promise into a record. The capture habits in our note-taking systems for AI notes pair well with this step: photograph the paper sign-off sheet weekly and file it next to the schedule.
Step 6 — Stress-Test the Draft Against a Bad Day
A procedure that only works on a calm Tuesday is not a procedure. Break it on purpose.
Simulate four failure scenarios against this SOP and tell me where it breaks:
1. The lead roaster calls in sick and a barista runs roast day alone.
2. The drum roaster trips a breaker mid-batch at 8 minutes.
3. A green coffee delivery arrives 40 kg short.
4. The closing shift starts 30 minutes late.
For each scenario list the steps that become impossible, the steps that get skipped under time pressure, and the single sentence you would add to the SOP to prevent the skip.You get a list of realistic gaps: steps that assume Iris is present, a missing recovery branch for a mid-batch power loss, a substitution rule that does not exist. Each gap converts into one added line. Two rounds of this and the SOP holds under pressure.
Add the compensating line while the scenario is still on screen. The rule is one scenario, one edit, one retest. If you collect five scenarios and try to patch them in a single pass, you will lose track of which line answers which failure, and the next revision will quietly remove it.
Final Deliverables Checklist
- A scope statement naming the trigger, the roles, and what is out of scope.
- A numbered roast-day procedure with times, weights, and temperatures.
- Beginner-proof rewrites with sensory confirmation for each critical step.
- A control-point table with target, range, measurement method, and out-of-range action.
- A cleaning schedule in three cadences with sign-off fields.
- A failure-scenario log with the compensating line added for each gap.
- A revision block with version number, owner name, and review date.
Where AI-Written SOPs Fall Apart
Trap 1 — prompting for prose. Ask for a document and you get an essay about consistency. Ask for a numbered list, a table, and a checklist, and you get something a shift lead can use.
Trap 2 — idealizing the shift. A procedure written from a clean mental model will miss the 06:40 reality. Feed real notes, including the messy parts and the interruptions.
Trap 3 — no owner and no date. An SOP with no named owner rots within a quarter. The revision block is not decoration; it is the line that tells you who to ask when a step stops matching reality.
Trap 4 — control points you cannot measure. “Good extraction” is not a control point. “18 to 22 grams in, 36 to 44 grams out, in 26 to 32 seconds” is.
For a wider set of drafting prompts to reuse across documents, see our ChatGPT writing prompts list.
Sources & Notes
The scope, step, control-point, and stress-test sequence is our own framing of standard procedure-writing practice, reviewed on 2026-10-09. Larkspur Coffee Roasters, Iris, Tomas, and Maya are illustrative names, and the equipment figures are plausible examples rather than specifications for your own machine. Food-safety rules vary by jurisdiction, so validate any cleaning or sanitation schedule against your local requirements before adopting it. Model behavior shifts between versions, so re-run the stress test whenever you switch models or replace the source notes.
