Restaurant SOP: Complete Standard Operating Procedure Guide

An SOP (Standard Operating Procedure) is a written, specific description of how a task should be done — not a general principle, but the actual steps, in order, that produce a consistent result regardless of which staff member is doing it. Without SOPs, quality and consistency depend entirely on who happens to be working, which is a fragile way to run a restaurant.

Why SOPs Matter More Than They Seem

A restaurant without written SOPs relies on informal knowledge transfer — new staff learn "how we do things" by watching, which means every deviation, shortcut or misunderstanding gets passed forward and compounds over time. Written SOPs are the mechanism that keeps a dish, a greeting, or a cash-handling process consistent as staff change.

SOPs by Area

Opening — the sequence of tasks to prepare the restaurant for service, see Restaurant Opening Checklist.

Closing — the reverse sequence, securing the restaurant and reconciling the day, see Restaurant Closing Checklist.

Food preparation — standardized recipes, portion sizes and preparation methods, covered in depth in Restaurant Kitchen SOP.

Hygiene — handwashing, surface sanitation, food storage temperatures, and personal hygiene standards, applied consistently regardless of how busy service gets.

Ordering — how orders are taken, communicated to the kitchen, and modified if needed, covered further in Restaurant Service SOP.

Billing — accurate, consistent billing procedures including how discounts, complimentary items and corrections are handled.

Inventory — stock counting, ordering triggers, and how variance is investigated, tying back into daily operations.

Customer complaints — a defined process for how staff should respond to and escalate complaints, so resolution doesn't depend entirely on which staff member happens to handle it.

Cash handling — see Restaurant Cash Management for the detailed process.

Writing an SOP That Actually Gets Followed

1. Be specific — "clean the grill" is not an SOP; "scrape the grill surface, apply degreaser, scrub with the designated brush, rinse and dry" is
2. Keep it observable — an SOP should describe steps a manager can actually verify, not just intentions
3. Test it with a new hire — if someone unfamiliar with the task can't follow it from the written SOP alone, it's not detailed enough yet
4. Review and update it — an SOP that's never revisited drifts out of sync with how the restaurant actually operates over time
5. Train against it explicitly, rather than assuming staff will absorb it by osmosis

SOPs and Technology

Digital systems can reinforce SOPs directly — a POS that only allows discounts within a defined range, or a digital menu that prevents an unavailable item from being ordered, encode the SOP into the system itself rather than relying purely on staff memory and discipline.

FAQ

How many SOPs does a small restaurant actually need? Start with the highest-impact areas — food preparation, hygiene, and cash handling — rather than attempting to document every possible task before opening. Add more as specific gaps or inconsistencies reveal themselves.

Who should write a restaurant's SOPs? Ideally the people who actually do the work, with management input for consistency and business requirements — an SOP written entirely by management without frontline input often misses practical details that make the difference between a workable procedure and an ignored one.

How often should SOPs be reviewed? At minimum whenever the menu, equipment, or a process changes meaningfully — but a periodic review (every few months) even without a specific trigger helps catch drift between what's written and what's actually happening.