How to Write Restaurant SOPs That New Hires Actually Follow
Most restaurant SOPs fail for the same reason: they're written the way an owner wishes the job were done, not the way the job actually gets done. This guide fixes that.
Reading time: approximately 8 minutes
Why most restaurant SOPs get ignored
There are two kinds of restaurant SOPs. The first kind is written at a desk by an owner who hasn't worked a shift in 18 months. It says things like “ensure all food is stored properly” and “maintain cleanliness throughout the shift.” New hires read it once and forget it because there's nothing to remember — no specific temperatures, no times, no consequences stated.
The second kind is written by someone who actually knows what the job requires. It says things like “walk-in cooler must read ≤ 38°F before the first ticket — if it doesn't, call the GM immediately and do not open service.” New hires remember this one because it tells them exactly what to do when something goes wrong.
The only difference between those two SOPs is specificity. The goal of this guide is to give you the framework to write the second kind — fast.
The 6 SOPs every restaurant must have
You could write 50 restaurant SOPs. But if you have zero right now, these 6 are the ones that protect you from the most common and most expensive failures:
1. Morning opening procedure
Covers: alarm disarm, equipment startup order, temperature logging, par check against prep list, staff station setup, floor walk before door unlock. The most important SOP in the building, because a bad open creates problems that compound for the entire day. If you only write one, write this one.
2. Pre-service line check
Covers: protein temperature check (logged, not guessed), sauce taste, par levels against the 50% threshold, equipment test at each station, expo setup. The line check is the last gate before quality hits a plate. An unexecuted line check creates 86s, food safety risks, and mid-rush surprises.
3. Closing procedure
Covers: last seating protocol, check close and cash count, food storage and dating, temperature logging, kitchen clean, dining room reset, cash drop, final security walkthrough, alarm set. The closing procedure determines what the morning opener walks into.
4. Food receiving procedure
Covers: delivery verification against the PO, temperature check on cold items at receiving (poultry ≤ 40°F at delivery — reject if over), inspection for damage or contamination, labeling and dating before storage, documentation of any rejected items. Accepting a warm poultry delivery without documentation is the fastest path to a health inspection violation.
5. Server sidework
Covers: per-station opening duties (stocking, setup), per-shift duties (running, keeping topped), and closing duties (restocking for the next shift, cleaning). Sidework without a written SOP becomes a negotiation between every server about who does what. With a written SOP, it's an assignment.
6. New employee training rundown
Covers: what a new hire must know before working solo — menu knowledge standard, POS proficiency, uniform standard, the opening and closing procedures listed above, food safety basics, emergency contacts. Not a 50-page training manual. A 2-page checklist the trainer signs off on.
The fastest way to write a restaurant SOP
The slowest way to write an SOP is to sit at a computer and try to remember the procedure from memory. The brain fills in gaps with “best practice” language instead of specific steps, and you end up with the useless kind.
The fastest way is to walk the procedure while describing it out loud — as if you're explaining it to someone who has never done it. You naturally include specific details (“the fryer needs 15 minutes to preheat, not 10 — if you put food in early the oil temperature drops and the first batch is ruined”) because you're in the physical space where those details matter.
That description — spoken in plain language, with all the specific details — is the raw material of a good SOP. The formatting into numbered steps, quality checks, and trainer notes can be done by AI. The expertise has to come from you.
TalkNDone does exactly this: you describe the process, and it structures your words into a formatted SOP PDF. The output is usable immediately — you can print it, post it, and train from it the same day.
What makes a restaurant SOP actually stick
An SOP that lives in a binder nobody opens is the same as no SOP. Here's what separates the SOPs that change behavior from the ones that don't:
Posted where the work happens
The opening procedure goes on the inside of the manager office door. The line check goes on the expo station. The sidework list goes at each server station. A binder in the back office is not accessible during the 3-minute window a new opener has to remember step 4.
Specific enough to be unambiguous
“Check temperatures” is ambiguous. “Log walk-in cooler temp on the temp sheet — must read ≤ 38°F. If it reads over 40°F, call the GM immediately before proceeding.” is not ambiguous. Write every step at the second level.
Trained in person before solo
Handing a new hire an SOP and saying “read this” is not training. The SOP is the reference for the first three supervised shifts, then the check item for the solo evaluation. If the opener can complete the SOP without asking a question, they're ready.
Updated when the process changes
An SOP that reflects how you used to do it is worse than no SOP, because it actively trains the wrong behavior. Review each SOP every 90 days. If something in the procedure changed, update the document before the next training cycle.
Free restaurant SOP templates to start with
If you want a working example before you write your own, these are real SOPs built for restaurant operations — not generic templates:
Get your SOP written today
Describe it. We format it. Done.
Walk through your opening procedure out loud. TalkNDone structures it into a formatted PDF SOP. Free preview, $49 to own it.
Write my restaurant SOP →