The Restaurant SOP Checklist Every Outlet Needs

Every restaurant has standards. Most have them stored in one person’s head, which means the restaurant is one resignation away from a different restaurant.

An SOP is just that knowledge written down in a form somebody can follow on a bad night. Here is the minimum set, and the way to write them so they get used instead of filed.

The twelve that matter

Kitchen

1. Opening checklist, per station. Temperatures logged, gas checked, mise en place quantities confirmed, oil level and condition, sanitiser prepared.
2. Standard recipe cards. Ingredients in grams, method in steps, yield, plating photograph, cost per portion.
3. Prep par levels. How much of each item to prepare against day of week, and what to do with the balance at close.
4. Storage and labelling. Receiving checks, date labels on everything, FIFO order, raw-below-cooked, allergen separation.
5. Closing checklist. Cool-down and storage of leftovers, equipment shut-down, cleaning schedule, fridge temperatures logged.

Service

6. First thirty seconds. Greeting, seating, water, menu, and the timing target for each.
7. Order taking. Repeating the order back, allergen question, modifier handling, course sequencing to the kitchen.
8. Timing and handover. Gap between courses, what to do when the kitchen is behind, how the pass calls a table.
9. Complaint recovery. What a server can do without a manager, what needs escalation, and the follow-up on the bill.

Management

10. Daily numbers. Covers, sales, average ticket, wastage, and who records them.
11. Weekly audit. Fifteen line items the manager physically checks — hygiene, stock, par levels, checklist compliance.
12. Roster against covers. Staffing by hour based on actual demand, not the same six people every shift.

How to write one people will use

One page maximum. If a procedure needs three pages, it is three procedures.

Checklists over paragraphs. A box to tick gets ticked. A paragraph gets skimmed once during induction and never again.

Photographs over descriptions. Shoot the correct plate in your own kitchen, with your crockery, under your lights. “Garnish neatly” means nothing; a photograph is unambiguous.

The language the team actually speaks. A kitchen SOP in English for a team that works in Hindi is decoration. Write it in the language of the station.

Name the owner and the frequency. Every SOP says who does it and when. An unowned procedure is a suggestion.

Where SOPs die

They die in the drawer. The manual is written, printed, signed off, and then never mentioned again, because nobody checks it.

The fix is the weekly audit — fifteen items, five minutes, the same day every week, done by a person whose name is on it. Standards survive exactly as long as someone is checking them, and not one week longer.

They also die when reality moves and the document does not. A supplier changes, a dish is dropped, a station is rearranged, and the SOP now describes a restaurant that no longer exists. Review quarterly, edit in ten minutes, move on.

Start with three, not twelve

Writing twelve SOPs in a week guarantees that none of them gets used. Start with the three where inconsistency costs you most — usually recipe cards, the kitchen opening checklist, and complaint recovery — and roll them out properly with training before writing the next three.

A restaurant with three SOPs people follow is in far better shape than one with a beautiful manual nobody opens.

---

We write these for a living, in the language your team speaks, with photographs from your kitchen: SOP development. The rollout and training that make them stick is staff training.