Restaurant SOP Guide: Write Procedures Staff Actually Follow

A restaurant SOP (standard operating procedure) is a short, step-by-step standard for a repeatable task. Start with:

1. Opening
2. Closing
3. Critical food-safety tasks
4. Top guest-facing procedures (ticket flow, complaint recovery, cash close)
5. One high-variance kitchen build if quality swings by cook

Keep each SOP to roughly one page and 5–9 steps. Train to it (staff training), inspect it, and review monthly. Pair daily open items with your opening checklist.

⚠️ Local rules vary. Food-safety steps must meet your local health code. This guide is educational, not a substitute for local regulatory requirements.

SOPs turn “how we do it here” into trainable, inspectable work. Without them, every trainer teaches a slightly different restaurant. Guests notice. New hires drown. Managers answer the same questions every shift.

This guide shows how to write restaurant standard operating procedures people will actually follow — short, station-visible, owned, and versioned — plus a copyable template and two filled examples.

For how SOPs fit the wider system, see restaurant operations.

Well-written restaurant SOPs deliver:

SOPs are not corporate theater. In independents, they are how quality survives turnover.

Step 1 — Pick critical processes only

List every recurring task, then rank by risk × frequency × variance. Start with 5–7. Expand later.

Typical first library:

• Opening procedure
• Closing procedure
• Kitchen ticket / expo flow
• Cash drawer open and close
• Cooling / temp logging (or your highest food-safety risk)
• Guest complaint recovery
• One signature menu item build

Step 2 — Draft 5–9 clear steps

Each step should be an action someone can do without asking a manager. Include:

• Tools or stations needed
• Temps, times, or counts where relevant
• What “done” looks like

Avoid novels. If a step needs a paragraph, split it or add a photo callout.

Step 3 — Add exceptions and escalation

Write what to do when reality breaks: 86 item, equipment down, cash variance, guest allergy. Name who to call.

Step 4 — Assign a document owner

Every SOP needs a human owner (often GM or chef) responsible for accuracy and review date — not “the team.”

Step 5 — Train, then audit

Train using the SOP (training system). Spot-check monthly. If people skip a step, either fix the process or remove the fiction.

Step 6 — Version and store where work happens

Put a date on every SOP. Store printed copies at the station or on a tablet at the pass — not only in email.

---

Practical asset — One-page SOP template

SOP TITLE: ________________________________
Purpose: _________________________________
Who performs: ____________________________
When: ____________________________________
Tools / stations: ________________________

Steps:
1.
2.
3.
4.
5.
6.
7.

Quality check (what “done” looks like):
Exceptions / escalate to:
Document owner: ________  Version date: ________

Every restaurant SOP should fit the same skeleton so staff recognize the pattern across stations.

Library build order (risk × frequency × variance)

1. Opening · 2. Closing · 3. Critical food-safety · 4. Ticket/expo flow · 5. Cash open/close · 6. Guest complaint recovery · 7. One high-variance menu build

Checklists confirm; SOPs teach. Pair with your opening checklist and training path.

• Short beats complete. One page people use beats ten pages people ignore.
• Write with the best operator, not only the owner. Capture how the work really happens, then raise the standard.
• Align with the handbook. SOPs must not contradict attendance or safety policies in the employee handbook.
• Update when the menu changes. New item = new or revised build SOP.
• Audit monthly. Pick three SOPs; watch one shift perform them.
• Connect to checklists. Checklists confirm; SOPs teach. Use both with your opening checklist.
• Version visibly. Date every page; retire old printouts the day a new version ships.
• Train before you enforce. An unread SOP is not a performance standard.

1. Writing SOPs nobody trains — unread PDFs are decoration.
2. Updating the menu without updating the SOP — variance returns overnight.
3. SOPs that contradict the handbook — staff learn to ignore both.
4. Too much detail — novels do not get read during a rush.
5. No owner / no date — stale procedures become dangerous.
6. Skipping closing SOPs — messy closes create unsafe opens (a classic first-year mistake).

Example A — Opening SOP (filled skeleton)

Example B — Closing SOP (filled skeleton)

Example C — Guest complaint recovery

Example D — Kitchen ticket / expo flow

1. Ticket prints / appears on KDS at the correct station
2. Lead acknowledges and assigns priority (course timing)
3. Station cooks to build card / recipe SOP
4. Expo checks plate against ticket (modifiers, allergens)
5. Runner / server delivers; ticket marked complete
6. 86s communicated to FOH immediately when stock hits threshold

Example E — Cash close

1. Run end-of-shift report
2. Count drawer with a second person when possible
3. Record variance; escalate above house threshold
4. Secure cash per house policy
5. Reset float for next open
6. Sign closing checklist cash line

Example F — Cooler temp logging (food-safety critical)

Write temps to your local health-code requirements — this pattern is educational, not a code substitute.

• [ ] Rank processes by risk × frequency × variance; pick first 5–7
• [ ] Copy the one-page template for each; keep 5–9 steps
• [ ] Fill opening, closing, ticket flow, cash close, and one food-safety SOP
• [ ] Add complaint-recovery and one signature build SOP
• [ ] Assign a document owner and version date on every SOP
• [ ] Place laminated or tablet copies at the station
• [ ] Train and sign off using staff training
• [ ] Spot-audit three SOPs this month; fix fiction or remove steps
• [ ] Align wording with the employee handbook
• [ ] Review SOPs after every menu, layout, or equipment change

What is a restaurant SOP vs a checklist?

An SOP teaches how. A checklist confirms that required items happened. You need both for open, close, and food safety.

How many SOPs does a small restaurant need to start?

Usually 5–7 critical procedures. Add more only after those are trained and followed.

Who should write SOPs — owner or staff?

Draft with the people who do the work; the owner or GM approves the standard. Pure top-down SOPs often miss real constraints.

How detailed should each step be?

Detailed enough that a newly signed-off employee can succeed without asking — not so detailed that the page becomes unread.

How often should SOPs be reviewed?

At least monthly for critical food-safety and cash SOPs; after any menu, layout, or equipment change for the rest.

Should SOPs be printed or digital?

Either works if they are at the station and versioned. Many independents use laminated one-pagers plus a master digital file.

What’s an example kitchen SOP structure?

Purpose → who/when → tools → numbered steps (including temps/times) → plating/quality check → exceptions → owner/date. Same template as FOH.

• Restaurant Operations — Where SOPs sit in the ops stack
• Restaurant Opening Checklist — Daily open companion to opening SOPs
• Restaurant Staff Training — Train and sign off to the SOP
• Employee Handbook for Restaurants — Policies vs procedures
• Common Restaurant Mistakes — What happens when SOPs are missing
• How Restaurants Can Get More Customers — Growth after procedures stick
• Restaurant Knowledge Hub — Ops + Growth lanes
• About WhateverAsk — How we write experience-driven Knowledge Products

Restaurant SOPs work when they are short, trained, inspected, and owned. Start with opening, closing, food safety, and a few guest-facing procedures. Use the one-page template, put documents where work happens, and improve one SOP a week. That is how procedures stick — and how restaurant operations stop depending on a single hero.

2026-07-10. Educational guide for operators. Not legal or health-code advice. Align food-safety steps with your local authority requirements.