Everything in the last topic lived in one person's head and hands. That is the weakness of even good training: it walks out the door when the person who knows how to do it leaves, calls in sick, or gets busy. This topic is about moving the knowledge out of heads and onto paper, once, so the work trains for you from then on. It is the least glamorous topic in the course and the one that pays the longest.
📝 The document that trains for you
A written procedure — call it an SOP, a standard, a station guide, whatever you like — is just a task from the last topic, broken into its steps, written down where anyone can read it. You already did the hard part when you broke the task down to teach it. Writing it is capturing that so you never have to reconstruct it from memory again.
The restaurant kinds worth having, roughly in order of how much pain they save:
- Recipe cards. Ingredients, quantities, method, and what the finished plate looks like. The single best defence against a dish tasting different depending on who is on.
- Prep lists. What gets made, how much, and to what standard. Turns "do the prep" into something a new person can actually do.
- Station guides. How each station is set up, run, and closed. What the last topic taught, made permanent.
- Opening and closing checklists. The steps that must happen at each end of the day, so they happen the same way whoever is holding the keys.
✂️ Written to be used, not to look impressive
The trap is writing a beautiful manual nobody opens. A procedure that lives in a binder in the office is decoration. The ones that work look different from the ones that gather dust.
| Gathers dust | Gets used |
| Long paragraphs of prose | Short numbered steps, one action each |
| In a binder in the office | Laminated at the station where the task happens |
| Written once and never touched | Marked up when reality changes, dated so you know it is current |
| Assumes knowledge the reader lacks | Names the invisible steps a beginner would miss |
| A photo of the plate nobody can match | A photo of the plate as it should actually leave the pass |
A picture earns its place here more than in almost any other document. A cook can match a plated photo faster and more reliably than they can interpret a paragraph describing where the sauce goes.
🧩 Start with the pain, not with everything
Nobody documents an entire restaurant in a week, and trying to is how the project dies. Start where the absence hurts most: the task exactly one person knows, the dish that comes back different when a certain someone is off, the close that goes wrong whenever the usual closer is away. Write that one. Then the next most painful. A handful of good, used procedures beats a complete manual nobody reads, and you can build it in the quiet stretches instead of pretending you have a free week.
A cheap way to build it: the next time you train someone on a task, have them write the procedure as they learn it. A beginner writes better procedures than an expert, because they still notice the steps an expert has stopped seeing — and you get the document as a side effect of training you were doing anyway.
🔁 Keep it alive
A procedure is only true until the day the work changes — a new supplier, a menu tweak, a better way someone found. A document that no longer matches reality is worse than none, because it teaches the wrong thing with authority. So date them, put one person in charge of each, and make "fix the card" a normal reflex when someone spots that the card is wrong rather than a special project. The manual that stays true is a small ongoing habit; the manual written once and frozen quietly becomes fiction. With the work written down and kept current, the next question is whether more than one person can actually do each thing — which is topic 5.