Restaurant SOP Template (2026): Kitchen, FOH, Opening & Closing

Ask a restaurant owner why service feels different when they're not in the building and the answer is rarely one big thing. It's thirty small things: the fryer filter skipped on a slow Tuesday, the prep list done from memory instead of par levels, a new server seating parties wherever the floor looks empty. Each deviation costs a little. Together they cost consistency — and consistency is the only product a restaurant actually sells.

Standard operating procedures are how consistency survives your absence. The problem is that most SOP advice online is written for office managers, not for a hot line at 6:45 PM on a Friday. This guide gives you restaurant-specific SOP templates for the stations where structure matters most — kitchen, front of house, opening, closing — with realistic examples you can copy and adapt tonight.

What Makes Restaurant SOPs Different

An office SOP describes a process someone performs occasionally, sitting down, with time to consult the document. A kitchen SOP describes actions performed rapidly, repeatedly, under heat and noise, by staff who may have worked there for three weeks. That difference drives every design decision below:

• Checklists beat prose. A line cook at full speed will never read paragraphs. Numbered steps of five to nine words each get followed; anything longer gets skimmed into oblivion.
• Location matters as much as content. An SOP that lives in a binder in the office is decorative. The ones that work are printed at the station, laminated, and readable from standing distance.
• Verification needs to be physical. Office SOPs end with "done." Restaurant SOPs need initials on a printed sheet, temperature logs signed, photos uploaded. The food-safety audit you pass next year is built from today's initialed checklists.
• Version control is a safety issue. When a supplier changes a product spec or a health code updates, last month's laminated sheet becomes actively dangerous. Every SOP needs a version date printed on it and a single owner who updates it.

The Core Template: Anatomy of a Station SOP

Whatever the station, a usable restaurant SOP contains six parts. Here's the skeleton, then filled examples:

Header block. SOP name, station, version number, effective date, who approved it, and when it's next reviewed. Thirty seconds of admin that makes the document auditable.

Purpose and scope. One or two sentences: what this procedure controls and which roles it applies to. "Controls receiving and storage of all perishable deliveries; applies to sous chefs and prep cooks on AM shift."

Tools and standards required. The probe thermometer, the sanitization concentration (e.g., sanitizer solution at 50–100 ppm), the forms used. New staff can't follow standards they don't know exist.

Numbered procedure steps. The heart. Short imperative sentences, in execution order, with critical limits called out: temperatures, times, quantities. Anything a health inspector could cite deserves bold text.

Escalation and exceptions. What to do when reality deviates: delivery arrives at 48°F instead of below 41°F, the dish machine's final rinse reads low, the assigned closer doesn't show. Staff without an exception path improvise one, and improvisation during service is how incidents happen.

Verification record. Who checks completion and how: initials, log sheets, manager sign-off. A step that isn't verified is optional in practice, whatever the document says.

Kitchen SOP Examples

Food Receiving and Storage

The receiving dock is where most food-safety failures enter the building, so it earns the tightest SOP:

1. Check delivery against invoice — count, weights, product names.
2. Probe temp chilled goods: reject above 41°F (5°C). Frozen: reject above 0°F (-18°C) or with thaw signs.
3. Inspect packaging — reject swollen cans, broken seals, ice crystals inside frozen packs.
4. Check dates — reject anything within 2 days of its use-by date unless agreed with the chef.
5. Move to storage within 15 minutes of receipt. FIFO rotation: new stock behind existing.
6. Log temps, discrepancies, and driver name on the receiving sheet. Initial.
7. Rejects: photograph, note on invoice, refuse politely, call the supplier before the truck leaves.

The escalation clause does quiet work here: "driver disputes the rejection → note it, take the photo anyway, notify head chef — never accept product you'd fail an inspection over."

Prep List and Par Levels

Prep from memory is why you run out of the Sunday special at 7 PM. The SOP converts prep from intuition to numbers:

1. Print sales mix report for the same weekday last week.
2. Walk the line — count current stock against par levels on the prep sheet.
3. Calculate prep quantity = par minus on-hand plus projected covers adjustment.
4. Label every container: product, date prepped, use-by date, initials (day-dot rule — no unlabeled containers anywhere in the walk-in).
5. Store by cook temperature order: ready-to-eat top, then seafood, whole beef/pork, ground meats, poultry bottom.
6. Sous chef verifies labels and rotation at 3 PM; missing labels = retrain that day, logged.

Closing the Kitchen

1. Break down line: wrap, label, date all held products — discard anything past hold time.
2. Empty, clean, sanitize all low-boy and reach-in units' exteriors; check temps before shutdown.
3. Filter fryers (Tues/Fri) — oil log signed; full clean Sundays.
4. Run dish machine final rinse temp check — log reading; strip and reassemble spray arms.
5. Floors: sweep, mop under and behind every unit — grease accumulation is the fire inspection failure waiting for you.
6. Grease trap lid secured, cardboard broken down and baled, wet towels laundered not binned.
7. Line check walk with closing chef: pilot lights, gas valves, equipment switches. Both initial the closing sheet.

Front of House SOP Examples

Opening the Dining Room

1. Lights, music, HVAC to service settings 45 minutes before open.
2. Count and set place settings to the floor plan photo — alignment to house standard.
3. Polish glassware and cutlery from the rack, spot-check for water spots under light.
4. Walk the dining room as a guest would: entrance sightline, sticky chair legs, dead bulbs, restroom supplies and cleanliness.
5. Verify POS float, print reservation sheet with dietary notes highlighted, brief specials — every server recites the day's specials and the two upsell targets before doors open.
6. Manager unlocks door exactly on time. Early seating without table-ready confirmation is the classic first-review killer.

Service Standards and Table Management

Rather than scripting personality, codify the non-negotiables: greet within 60 seconds of seating; drinks order taken within 3 minutes; check-back after first bite ("how's everything tasting?") at every two-top; dessert and coffee offer made explicitly, never assumed away; bill delivered within 2 minutes of request, processed within 3. These five timings alone move review scores more than any script, because guests experience timing long before they notice technique.

Closing Front of House

1. Section-by-section breakdown once final guests depart — chairs down, floors, restrooms final check.
2. POS close-out: cash counted by two people together, variance noted and signed, drop safe witnessed.
3. Reservation book annotated: no-shows flagged, large parties confirmed for tomorrow.
4. Lost and found logged with date and location found.
5. Alarm set, lights off, lock-up witnessed by two staff — the pairing rule exists for both security and false-alarm disputes.

How to Roll Out SOPs Without Mutiny

Writing the documents is 20% of the work. Getting them followed is the other 80%, and it has a known playbook:

• Co-author with the people executing. Draft each SOP with your best line cook or lead server, not for them. Two benefits: the steps match reality (they know the walk-in's cold spot), and the author defends the document to peers in a way no manager memo ever will.
• Launch one station at a time. Receiving SOP this week, prep next week. A big-bang rollout of fifteen documents produces zero compliance and maximum eye-rolling.
• Train by demonstration, verify by doing. Show the procedure, watch them perform it, sign them off. The signature doubles as training evidence for insurance and labor compliance.
• Audit weekly at first. Ten-minute spot checks against the verification records — missing initials are coaching moments, not disciplinary ones, until the habit sets. After four consistent weeks, monthly audits suffice.
• Review quarterly. Menu changes, equipment changes, supplier changes, and health-code updates should each trigger a revision with a new version date. Retire superseded prints physically — old laminated copies left at stations undo everything.

Common Mistakes

• Writing novels. If a step list runs past roughly fifteen items, split it — one SOP per task, not per shift.
• SOPs that contradict reality. A document requiring a thermometer nobody can find trains staff to ignore documents. Fix the tool supply before publishing the standard.
• No named owner. "Management keeps SOPs updated" means nobody does. Every document gets a name.
• Training by handover. New staff told "just watch Mateo" inherit Mateo's shortcuts, including the ones causing your inconsistency. SOPs are the curriculum; shadowing supplements them.
• Treating verification as distrust. Frame initialed logs the way pilots frame checklists — professional discipline, not surveillance. The tone you set in rollout determines whether logs get signed honestly.

Your Restaurant SOP Starter Checklist

Use this to sequence the rollout:

• Write the receiving & storage SOP first (highest safety leverage)
• Add prep/par-level SOP with labeled-container rule
• Publish kitchen closing checklist with dual sign-off
• Publish FOH opening checklist tied to the floor plan photo
• Codify the five service timings for all servers
• Create FOH close-out with two-person cash count
• Assign a named owner and review date to every SOP
• Print, laminate, post at point of use — office binders don't count
• Train by demo, collect sign-offs as training records
• Schedule weekly audits for the first month, then monthly
• Diarize the quarterly review linked to menu/supplier changes

Wrapping Up

Restaurant SOPs aren't bureaucracy — they're how a good shift becomes the default shift instead of a fortunate one. Start where the stakes concentrate: receiving, prep labeling, closing verification. Keep every procedure short enough to follow mid-service, verified enough to survive an inspection, and owned by someone with their name on it.

If writing these from scratch is what's been stopping you, AiDocX generates station-specific restaurant SOPs — receiving, prep, opening, closing, service standards — from a plain description of how your venue runs. They stay editable and versioned in a shared workspace, export to printable formats for lamination, and support e-signature training sign-offs so your records are audit-ready from day one.