Writing restaurant SOPs that people actually use

Four failure patterns account for nearly all of it.

Written for the wrong reader. Most manuals are written by someone with fifteen years of experience for a reader they imagine also has fifteen years of experience. The real reader is nineteen, three shifts in, and needs to know whether the chicken goes in before or after the sauce.

Organized by department instead of by task. A manual with chapters called Kitchen, Front of House and Administration requires the reader to know where to look. A system organized by task lets them search for the thing they are doing right now.

Too long to consult mid-shift. If the answer takes ninety seconds to find, nobody looks. They ask the nearest person instead, which is exactly the informal knowledge transfer the manual was meant to replace.

Never tested. The manual is written by an expert, approved by another expert, and handed to a novice who cannot follow it. Nobody discovers this because nobody watched.

One task, one page. If it needs two pages it is probably two tasks. The structure below is deliberately rigid, because consistency of format is what lets someone find an answer quickly under pressure.

1. 01

   Task name

   Written as the person would say it. Not “Protein Preparation Protocol” but “Prepping the grilled chicken”.

2. 02

   When and who

   When it happens, who owns it, how long it should take. Sets the expectation before the first step.

3. 03

   What you need

   Equipment, ingredients, tools, forms. Everything gathered before starting, so the procedure is not interrupted halfway.

4. 04

   The steps

   Numbered, one action each, in the imperative. “Set the fryer to 350F.” Not “The fryer should be maintained at an appropriate temperature.”

5. 05

   The standard

   What correct looks like, with a photograph. This is the single most valuable element and the most commonly omitted.

6. 06

   Common errors

   The three things that usually go wrong and how to tell. Written by whoever has fixed them most often.

Nobody documents everything, and attempting to is why most efforts stall in month two. Prioritize by two criteria: how expensive the task is when done wrong, and how often it is done by someone new.

• Food safety and handlingNon-negotiable, legally exposed, and the most costly failure available to you. Always first.
• Your ten highest-volume recipesThese determine what most guests experience. Getting the top ten exactly consistent matters more than documenting all sixty.
• Opening and closingDone daily by whoever is scheduled, frequently by someone relatively new, and the source of most equipment and cash problems.
• Cash handling and compsWhere loss happens quietly, and where an undocumented process is indistinguishable from no process.
• Guest recoveryThe moment that decides whether a bad experience becomes a bad review. Should not be improvised.
• Inventory and orderingDirectly drives food cost, and usually the least consistent process in the building.

Six areas properly documented and genuinely used beats sixty written and ignored. Extend from there once the habit exists.

This is the step that separates a used system from a shelf document, and it takes an afternoon.

Hand the SOP to someone who has never done the task. Say nothing. Watch them attempt it. Every question they ask is a defect in the document, not in the person. Rewrite, then test again with someone else.

Two or three cycles is normally enough. The result reads differently from anything written by an expert alone, because it has been shaped by the actual points of confusion rather than the imagined ones.

SOPs decay. Menus change, equipment is replaced, a better method emerges on the line and never makes it back into the document. Within eighteen months an unmaintained system is actively misleading, which is worse than having none.

• Name an ownerOne person per area is accountable for their SOPs being current. Not a committee.
• Version and date every pageAnyone should be able to see at a glance whether they are reading something current.
• Review on a scheduleQuarterly for food and safety, twice a year for everything else. Put it in the calendar or it will not happen.
• Make updating easyIf changing a procedure requires reprinting a binder, nobody will change it. Digital, searchable, editable by the owner.
• Tie it to trainingThe SOP is the training material and the certification standard. If those are separate documents they will diverge.
• Capture improvementsWhen a manager finds a better way there must be a route for it to become the standard, or your best practice stays in one store.

Documentation is the least glamorous work in a restaurant business and the one that most determines whether it can grow. Every expansion decision eventually reduces to a single question: can someone who was not here at the beginning run this correctly?

It is also one of the three conditions in our readiness gate. A brand cannot be franchised on the strength of good food and a strong founder. It is franchised on the strength of a system that survives the founder not being in the room, and that system has to exist in writing before anyone will pay for the right to use it.