Turn your messy training notes into a real staff manual with AI

Every restaurant has a “standard operating procedure” — it just usually lives inside one server’s brain and walks out the door when they quit. Pulling it out is the single highest-ROI documentation task you can do, and AI cuts it from a 40-hour project to one focused afternoon.

What a real SOP solves

A new hire who can read your SOP saves you:

• 8–12 hours of hands-on shadowing per role.
• The “wait, who showed you that wrong way?” rework cycle.
• The compounding inconsistency that erodes guest experience.

You don’t need a corporate-grade binder. You need a clean Google Doc that a smart 17-year-old could read in 90 minutes and not embarrass you on shift.

The afternoon workflow

Block 3 hours. Coffee, your veteran server or chef de cuisine, a recording app, and ChatGPT. The structure:

Hour 1 — Capture the brain dump

Don’t write anything yet. Sit with the person who knows the most about a role and record (with their permission). Walk through one full shift in their head, from clock-in to closing, narrating everything they do without interrupting. Use your phone’s voice memo or any transcription app.

Then transcribe. ChatGPT, Claude, or any tool that takes audio → text works fine.

Hour 2 — Let AI structure it

This is where AI shines. You hand it 5,000 words of stream-of-consciousness, you get back a structured SOP draft.

The output won’t be perfect, but it’ll be ~70% there.

Hour 3 — Reality check + house rules

Now sit with your veteran again. Read the document together. Three things to do:

1. Fill in every [[NEEDS CLARIFICATION]]. These are your real institutional knowledge — capture them now, not later.
2. Add house rules the transcript didn’t catch. “We always re-fire if pasta sits more than 90 seconds.” Things that became automatic and aren’t said out loud.
3. Mark the deal-breakers. Use a clear visual flag (a 🚨 emoji works) for the 3–5 things that, if a new hire gets wrong, must be re-trained immediately.

Common mistakes

• Writing the SOP from scratch yourself. You’ll miss the tribal knowledge that lives outside your head. Always start from a transcript of someone else.
• Trying to document every role in one session. Pick one role, finish it, ship it, and use the next two weeks to test it on actual new hires before doing the next.
• Letting AI invent rules. AI will fill in plausible-sounding but wrong rules (“standard practice is to…”). The [[NEEDS CLARIFICATION]] instruction is what prevents this — keep it in the prompt.

Roles, in order of ROI

If you’re starting from zero, document in this order:

1. Server / FOH front-line. Highest turnover, highest guest impact.
2. Bartender. Specs and signature drinks especially.
3. Line cook by station. One station per session.
4. Host. Often “trained” in 20 minutes; deserves more.
5. Manager opening / closing. This protects you on days off.

A note on sharing

Once your SOP exists, two distribution rules: print one copy laminated for the back of house, and put the digital version in a Google Drive folder new hires get on day one. Email attachments rot. Drive links don’t.

That’s it. One afternoon, three hours, and you’ve turned tribal knowledge into an asset that survives turnover.