Restaurant standard operating procedures worth writing down

Restaurant standard operating procedures have a bad reputation because most of them are written to sit in a binder. The ones that work are short, specific to your room, and attached to a moment in the day — opening, changeover, close — rather than to an abstract category of activity. A kitchen does not need a hundred-page manual. It needs eight procedures and two checklists that get done.

Hospitality has the highest staff turnover of almost any sector, and that is the real argument for writing things down: procedures are how a new starter reaches useful in days rather than weeks, and how a shift survives when the person who always does it is not in.

The restaurant standard operating procedures that matter

• Opening: unlock, alarms, fridge and freezer temperature check with the reading recorded, equipment on, prep list, float counted.
• Closing: clean-down by station, waste recorded, temperatures again, gas and equipment off, cash reconciled, doors and alarm.
• Food safety: deliveries checked and temperature-probed on arrival, labelling and date rotation, allergen handling, cleaning schedule per surface and frequency.
• Service: table turn, order flow to the pass, timing between courses, how a fired-back dish is handled.
• Complaints: who decides on a remake or a comp, at what value, and what is said to the guest.
• Cash and till: floats, voids, refunds, banking, and who can authorise each.
• Staff: shift start and finish, break rules, uniform, sickness reporting, and the return-to-work rule after illness.
• Emergencies: fire, injury, power loss, kitchen fire — one page each, posted, not filed.

Food safety records are not optional paperwork. Most jurisdictions require documented temperature checks, cleaning schedules and allergen controls, and the records are what an inspector asks for first. Check the rules where you operate — this list is a starting point, not a compliance regime.

Making them stick on a busy shift

1. Write each procedure to fit one page, in the language the team actually uses, including the words for equipment that only your kitchen uses.
2. Attach it to a moment: opening, changeover, close. Procedures with no moment belong to nobody.
3. Turn the recurring ones — temperatures, cleaning, waste — into a checklist with a name and a time against each line, not a document to read.
4. Post the emergency and allergen pages where they are needed. Everything else can live in one place people know.
5. Train by doing the procedure alongside the new starter once, then watching them do it once. Handing over a document is not training.
6. Review after any near miss, complaint or failed check, and after any menu change — those four events invalidate more procedures than time does.
7. Keep the completed checklists. The value is not in filling them in, it is in being able to show three months of them.

Checklists that produce a record

Paper checklists on a clipboard work, right up to the moment you need last month's temperature logs and they are in a drawer, damp. The improvement that costs least is to keep the same short checklist but submit it, so each completion is timestamped and searchable, and the ones nobody completed are visible without an archaeology exercise.

Ettex Forms fits this shape: a short form per checklist — opening, closing, delivery check — with the fields you already write on paper, a file-upload question for a photograph of a probe reading or a damaged delivery, and every submission landing in one searchable, timestamped inbox with a live summary and export to CSV or XLS when the inspector or the accountant asks. The procedures themselves belong in Ettex Docs, with comments so a head chef can correct a step in place and version history so you can see what the procedure said in June. Rotas and shift patterns sit in Ettex Calendar.

Plainly: Ettex is not a hospitality system. There is no EPOS integration, no stock or recipe costing, no HACCP module, no Bluetooth temperature probes, no automatic reminder when a checklist is missed, and no rota engine that handles availability and labour cost. What you get is short forms that produce timestamped records, documents with comments and history, and a shared calendar. For a single site that is often enough; a group with compliance reporting across venues needs specialist software.

Where restaurant procedures fail

• Copied from a template written for someone else's kitchen, so half of it does not describe your equipment or your menu.
• Written once at opening and never touched, while the menu changed four times.
• A binder instead of eight posted pages, which means nobody reads it during service.
• Checklists signed in a batch at the end of the week, which is worse than no checklist because it is a false record.
• No named owner per procedure, so corrections are mentioned verbally and lost.
• Allergen information kept only in someone's head — the one failure that is both the most common and the most serious.

Restaurant standard operating procedures work when they are short, local to your room, attached to a moment in the day, and completed in a way that leaves a record. Write eight, post the ones that matter, and keep the checklists you can produce three months later.