A restaurant SOP is the written version of how your best people already do a job. With one location, a lot of that knowledge lives in the GM's head and gets passed along shift by shift. Open a second location and you find out fast how much of your standard was really one person. Below is what every SOP should include, which ones to write first, and how to keep them holding up across three, five, or twenty addresses.
Why SOPs Drift Between Locations
Most SOPs fail for ordinary reasons.
- They were written at a desk. The person who wrote the closing procedure hasn't closed in years.
- They're too long. Nobody reads a six-page procedure in the middle of close.
- They live in a binder. The binder sits in the office, and the office is locked during service.
- Nobody owns them. Without a version date, no one knows which copy is current.
- They were trained once. A new hire hears it on day one and never sees it again.
Then each location adapts a little. One store skips a step, another adds a shortcut, and a year later your standard means four different things. Guests often notice before you do, and they say so in reviews that compare one location to another.
What a Restaurant SOP Should Include
Keep every SOP to one task and about one page. Use the same fields every time, so a server at your third location knows exactly where to look.
| Field | What goes in it | Example: bar close |
|---|---|---|
| Title | One task, named the way your team says it | Bar close |
| Purpose | One line on why it matters | The morning crew opens to a clean, fully stocked bar |
| Who | The role that does it and the role that checks it | Closing bartender, checked by the closing manager |
| When | The time or trigger | After last call, before checkout |
| Tools | What they need on hand | Sanitizer, par sheet, keys, clean towels |
| Steps | Numbered, in the order they happen | 1. Wrap and refrigerate garnishes. 2. Restock wells to par. 3. Wash the mats. |
| Standard | What done looks like, with numbers | Wells at par, mats washed, garnish cooler at 41°F or below |
| Photo | A picture of done | The back bar, stocked and wiped down |
| Version | Number, date, and owner | Version 3, March 2026, beverage director |
Write it the way the work happens
- Watch first. Have your best closer do the task while someone writes down every step in order. You'll catch the small moves that make it work.
- Lead with verbs. Pull, wipe, check, log. One action per step.
- Put numbers on the standard. Temperatures, times, counts, and pars leave less room for interpretation than a word like clean.
- Add a photo of done. A picture of a correctly set station settles arguments faster than a paragraph.
- Write for your newest hire. Use short sentences and plain words, and add a Spanish version if part of your team reads Spanish first.
- Give the why in one line. People follow steps they understand, and they speak up sooner when a step stops making sense.
The SOPs to Write First
You don't need two hundred SOPs before you open a second location. Begin where a miss hurts a guest or costs you money.
| SOP | Why it comes first | Review it |
|---|---|---|
| Opening and closing checklists, FOH and BOH | Sets up every shift and secures the building | Quarterly |
| Line checks and temperature logs | Food safety and consistency on every plate | Every menu change |
| Allergen handling | One miss can put a guest in the hospital | Every menu change |
| Steps of service | Defines what a guest gets at every table | Twice a year |
| Server checkout and cash handling | Protects your deposits and your team | Yearly, and after any variance |
| Receiving and storage | Catches short deliveries and keeps rotation tight | Yearly |
| Side work by shift | Keeps closing fair and the next crew set up | When stations change |
| Reservations and walk-ins | Keeps the book, wait quotes, and seating consistent | When policies change |
For food safety SOPs, your health code sets the numbers. Many local codes follow the FDA Food Code, which calls for cold holding at 41°F or below and hot holding at 135°F or above. Your health department's version is the one inspectors use, so check it before you print anything.
After that core set, build out the rest of the library: cleaning schedules, waste logs, equipment care, incident reports, and host stand procedures. Policies belong in your employee handbook, and SOPs cover how the work gets done. Keep them separate and link between them.
How to Make SOPs Hold Up at Every Location
Keep one master library
Every SOP has one master version. When a location needs something different, like a walk-in on the other side of the kitchen or a different dish machine, add a short local note at the bottom of the master. The core steps stay the same everywhere, and every local difference sits on one page where you can see it.
Date and version everything
Each SOP carries a version number, a date, and an owner. When something changes, update the master, note what changed, and retire the old copy at every location on the same day. One kitchen working from last year's printout is exactly how drift starts.
Train to it, then check it
An SOP only matters if it shows up in training. Build each one into onboarding so a new server at your fourth location learns the same steps of service as a server at your first. A short quiz and a trainer's sign-off on the key SOPs show you who's learned them. Our server training checklist lays out how that works over a new hire's first ten days.
Audit on a schedule
Pick three or four SOPs a month and check them at every location with the same checklist, scored the same way, so the results compare. When one location keeps missing the same step, look at two things: whether that team was trained on it, and whether the step works in that kitchen.
Let the people doing the work flag problems
Line cooks and servers spot broken steps first. Give them a simple way to flag one, and have the SOP owner answer within a week. When a cook at your second location finds a faster, safer way to break down the fryer, make it the standard for everyone.
Where Software Helps
A binder works for one kitchen. Across several, a digital SOP library means one update reaches every location at once, every hire sees the current version on a phone or tablet, and you can see who's been trained on what.
Some standards work best built into the tools your team already uses every shift. When we build software for a restaurant, house rules like turn times by season and party size live in the admin tools, and the training academy records which version of the handbook each person signed. That's the heart of good multi-unit restaurant management: the standard lives in one place, and every location works from it.
How Monarch Helps
We write SOPs from the way your best location already runs, build them into training your team can open on any phone, and roll one standard out to every address as part of a multi-location rollout. You review and approve every page before your team sees it. For a quick read on where your operation stands today, take our free AI assessment.
Want help with this?
Monarch handles multi-location for restaurants as part of one white-glove team. We do the work. You guide the process. See how multi-location works with us.
Get Your Free AI Assessment