Almost every restaurant has SOPs somewhere. Often it's a binder in the office, written years ago, that nobody has opened since. Then the restaurant wonders why the same dish tastes different on Tuesday and Saturday, why closing takes an hour longer than it should, and why new hires take weeks to find their feet.
The problem usually isn't a lack of standards. It's that the standards were written for the office, not the line. Here's how to write SOPs and run training that hold up in real service.
Why most SOPs fail
- They're too long. A ten-page document on opening procedures won't be read during opening.
- They're in the wrong place. If a cook has to leave their station to check a standard, they won't.
- They're written in the wrong voice. Corporate language doesn't stick. Clear, short, practical language does.
- Nobody owns them. Menus change, equipment changes and people change, but the SOPs don't.
- They're taught once. A standard explained on day one and never reinforced fades fast.
Principles for SOPs that get used
Write them from the line
Draft each SOP with the people who actually do the job. Ask your best closer how they close. Ask your fastest prep cook how they set up. You'll get better procedures, and the team will feel ownership because they helped write them.
One task, one page
Keep each SOP to a single task: opening the bar, closing the fryer, receiving a delivery, plating a dish. If it doesn't fit on one page, it's probably two tasks.
Show, don't just tell
Photos beat paragraphs. A plating photo next to a spec, or a picture of a correctly set station, communicates more in a second than a page of text. Short phone videos work brilliantly for anything with movement.
Use checklists
For anything with a sequence, such as opening, closing, line checks and cleaning, use a checklist that's actually ticked and signed each shift. Checklists catch the steps people skip when they're tired.
Put them where the work happens
Laminated cards at stations, a tablet on the pass, or a QR code on the wall that opens the right page on a phone. The standard should be within arm's reach of the task.
Make language accessible
Many kitchens are multilingual. Use simple words, short sentences and plenty of visuals. Where it helps, translate key SOPs into the languages your team speaks.
Training that sticks
Show, tell, do, check
A simple and effective training sequence:
- Show the task done correctly, at normal speed and then slowly.
- Tell why each step matters, whether it's food safety, consistency, speed or cost.
- Do: the trainee performs the task while the trainer watches.
- Check against the SOP, give feedback, and repeat until it's right.
Only sign someone off on a station once they can do it to standard without help.
Build a structured onboarding plan
New hires shouldn't learn by osmosis. Map out their first two weeks: which stations, which SOPs, which shifts, and who's responsible for training them. A simple sign-off sheet that tracks each skill gives both the trainee and the manager a clear picture of progress.
Use pre-shift huddles
Five minutes before service is one of the most valuable training slots you have. Use it to cover specials, 86'd items, one standard to focus on today, and any feedback from the last shift. Short and regular beats long and rare.
Train front of house on the menu
Servers who have tasted the food and know the story behind each dish sell better. Regular tastings and short menu quizzes make a real difference, especially for the dishes you most want to sell. Our guide to menu engineering explains how to choose them.
Keeping standards alive
Audit regularly
Spot-check stations, dishes and checklists. Not to catch people out, but to find where an SOP is unclear or unrealistic. If everyone skips a step, the step might be the problem.
Give every SOP an owner
Assign each SOP to a person, usually the chef or manager responsible for that area. When the menu or equipment changes, they update it. Put a "last reviewed" date on each one.
Recognise good work
Call out people who hold the standard, especially under pressure. What gets noticed gets repeated.
Where technology helps
Digital checklists, shared folders and simple apps make SOPs easier to find and update. Increasingly, restaurants are also turning their recipes, specs and SOPs into an AI assistant staff can ask questions of, such as "What's the spec for the carbonara?" or "How do we break down the slicer?" Done well, that puts the right standard in front of the right person at the right moment. You can read more in our guide to how restaurants can use AI.
Start small
Don't try to write every SOP at once. Pick the three procedures that cause the most problems, whether that's an inconsistent dish, a slow opening or a messy close. Write them properly with your team, put them where the work happens, train them with show-tell-do-check, and audit them for a month. Then pick the next three.
Need help building SOPs and a training program? Our staff training and SOP services cover it end to end, on-site across the GTA or remotely. Book a free consult to get started.