Restaurant SOPs: Build a Playbook Your Team Actually Uses

Keep each SOP to one task

A broad manual for 'kitchen operations' can be difficult to train from and update. Begin with one SOP per task: opening the bar, receiving a delivery, closing a cash drawer or handing over a section. Keep it short enough to use at the station, while retaining every necessary control. Split a long procedure into linked tasks where that makes the work clearer.

What every SOP needs

Each procedure should answer the same questions in the same order, so staff always know where to look.

The acceptance standard deserves care. 'Clean the counter properly' cannot be checked consistently. Specify the required steps, products, method and acceptance criteria from the approved cleaning procedure. Visual inspection may confirm that a counter is clear, but it cannot by itself verify that a food-contact surface has been sanitised correctly.

Escalation matters for a similar reason. Staff who do not know what to do when a step fails tend to improvise or stay quiet. Name the person to contact and the point at which they should be contacted.

An illustrative example: closing the cash drawer

The steps below are a sample to adapt to your own limits, approvers and records, rather than a policy to copy.

• Trigger: the last bill of the day is settled and the counter is closed to new orders.
• Owner: the closing duty manager, with a second team member present for the count.
• Calculate expected drawer cash: opening float + cash sales + authorised cash added − cash refunds − authorised payouts − cash removed to the safe or bank. Include each movement once, with its record. Keep card and digital receipts outside this cash calculation.
• List each authorised cash movement during the day, such as a supplier paid in cash or a float top-up, with the approver's name and the supporting slip.
• Count the drawer by denomination and write the counted total on the sheet before comparing it with the expected figure.
• Record any difference exactly as found, add a short note on possible causes, and have both people sign.
• If the difference is above the agreed limit, inform the person named in the SOP before leaving.

Two rules underneath the cash count

First, write down the amount actually counted, whether or not it matches. A matching figure does not prove the process was followed, just as a difference does not establish misconduct. Keep the count evidence and review exceptions fairly.

Second, nobody edits, voids or re-enters transactions to make the cash balance. If a bill was rung up wrongly, the correction follows its own approved process and is recorded separately, so the record of what happened stays intact. A logged difference is information to investigate. Small, recurring gaps often point to a process problem, such as change given from the wrong float or a petty cash payment that was never noted.

Train by showing, then watching

Asking someone to sign that they have read a document rarely changes what they do. Train each SOP in two stages. First, the owner or an experienced colleague demonstrates the task in the real setting and explains why each step exists. Then the trainee performs it while the trainer watches and checks the result against the acceptance standard, stepping in only if something is about to go wrong.

Repeat the observed practice at least once, ideally on a different shift, and note the date and who signed off. That way you know who is trained on which version.

Equipment and food-safety steps

For equipment such as combi ovens, dishwashers, fryers or coffee machines, base the SOP on the manufacturer's instructions and ask the kitchen team which steps they actually follow and where they get stuck. Where a procedure touches critical food-safety limits, such as cooking, holding or cooling, take those limits from the requirements that apply to your outlet and from your own verified food-safety procedures, and name that source in the SOP rather than writing figures from memory.

A one-week rollout you can adapt

This is a suggested pace for a first set of SOPs. Some teams will move faster and others, especially across several outlets, will need longer.

• Day 1: choose three to five tasks that cause repeated problems and name an owner for each.
• Day 2: owners draft each SOP and test it by doing the task once while reading it.
• Day 3: a second person checks each draft and confirms every acceptance standard can be observed.
• Days 4 and 5: demonstration and first observed practice with the staff who do the task.
• Days 6 and 7: a further observed practice on another shift, then a short discussion of anything unclear.

Review after incidents and changes

Review an SOP whenever something changes how the task is done: a new menu, supplier, piece of equipment or billing setup, or an incident such as a complaint, injury or unexplained cash difference. Ask whether the procedure was followed and, if it was, whether the procedure itself caused the problem. Update the version, retrain the people affected and keep the older version on file so you can see what changed. Give every SOP a fixed review date as well, so procedures for quiet tasks are not left untouched for years.

Using the SOP Builder and SOP Register

Use the SOP Builder to draft the trigger, owner, version, resources, steps, acceptance criteria and escalation. The SOP Register tracks one SOP and trainee combination per row, with demonstration, observed sign-off and review dates. Repeat an SOP row for each person who needs training, and update it when the procedure changes.

This gives the manager a record of who was observed doing which version. A template or an empty training date does not count as completed training.