How to Build SOPs for Multi-Unit Restaurants with Examples

Your signature burger tastes perfect at your original location. At location two, it’s a little different. By location three, you’re not even sure what’s happening back there. This is the consistency problem that kills multi-unit growth, and it’s almost always a systems problem, not a people problem.

Standard operating procedures are how you fix it. This guide covers the SOPs every multi-unit restaurant needs, how to write them so your team actually follows them, and ready-to-use examples you can adapt for your locations.

What are restaurant standard operating procedures?

Standard operating procedures for multi-unit restaurants cover food safety, financial reconciliation, and brand consistency across all locations. An SOP is a written document that explains exactly how to complete a specific task the same way, every time, at every location.

When you’re running one restaurant, you can answer questions in real time. You can catch mistakes before they become habits. But the moment you open a second location, you can’t be everywhere at once. That’s where SOPs come in.

Here’s the difference between the two documents you’ll hear about:

• SOP: Step-by-step instructions for completing a specific task, like closing the register or receiving a delivery
• Operations manual: A collection of all your SOPs plus policies, organized by department

Think of SOPs as individual recipes. Your operations manual is the whole cookbook.

Why multi-unit restaurants need standard operating procedures

Running multiple locations without documented procedures is like trying to cook the same dish in two kitchens with two different cooks who’ve never talked to each other. The results will vary. And in restaurants, variation is the enemy of consistency.

“Consistency is not just important; it is vital,” says Mark Steele, Founder of Restaurant Hospitality Institute. “There are zero off days. Guests don’t just want a great experience. They want the same great experience every time. The moment that changes, you’ve introduced doubt.”

Training gets faster across every location

Without documented SOPs, training depends entirely on whoever happens to be working that day. Your new server at location two learns a completely different approach than the one at location one, because different trainers have different habits.

With written procedures, a new hire at any location learns the same way. Training time drops because you’re not reinventing the wheel every time someone starts.

Your food and service stay consistent everywhere

Guests expect the same experience regardless of which location they visit. If your signature cocktail tastes different at your downtown spot than your suburban location, you’ve got a problem.

SOPs lock in the details: exact portions, plating specs, greeting scripts, table touch timing. The stuff that makes your restaurant yours.

Labor costs drop when everyone follows the same process

Clear procedures reduce mistakes, re-work, and wasted time. When your closers know exactly what to do, and in what order, they finish faster. When your prep cooks follow the same portioning specs, you’re not throwing away food.

Compliance becomes predictable instead of stressful

Health inspections, food safety audits, labor law requirements. SOPs create documentation you can point to. They show inspectors that you have systems, not just good intentions.

Essential restaurant SOPs every multi-unit operator needs

Not every task needs an SOP. Focus on the procedures that affect consistency, safety, and money.

Opening and closing procedures

Opening covers: unlocking and disarming, equipment checks, cash drawer counts, prep verification, and pre-shift meeting structure. Closing covers: last call procedures, checkout steps, cleaning tasks, cash reconciliation, equipment shutdown, security walkthrough, and lockup.

Food prep and recipe standards

This is where consistency lives or dies. Your prep SOPs cover portioning, plating, prep timelines, and ingredient specs. If your signature sauce calls for 2 tablespoons of garlic, that’s what goes in, not “a couple spoonfuls.”

Food safety and sanitation procedures

Temperature checks, handwashing protocols, allergen handling, cleaning schedules, FIFO rotation. Many of these food safety topics are required by health codes, so you’re documenting them anyway. Make them usable.

Customer service standards

Greeting scripts, complaint handling steps, table touch timing, checkout procedures. Guests get the same experience whether they’re served by your best server or someone on their second week. See our free server checklist to get started.

Shift handoff procedures

What’s 86’d, VIP guests in-house, prep status, equipment issues. Without a handoff SOP, critical information gets lost in the chaos of shift change.

New employee onboarding

First-day checklists, training schedules, who signs off on what. Every new hire gets the same foundation with onboarding procedures, regardless of which manager happens to be working.

Cash handling and payment processing

Drawer counts, void procedures, tip-out processes, end-of-day reconciliation. Money procedures protect both you and your team.

Inventory management procedures

Receiving, storage, rotation (FIFO), and waste tracking. Inventory SOPs keep food costs in check and prevent the “we’re out of chicken” surprise during Friday dinner rush.

How to write restaurant SOPs your team will actually follow

The graveyard of restaurant operations is full of beautifully written SOPs that nobody reads. Here’s how to write ones that actually get used.

1. Identify the processes that cause the most problems

Start where inconsistency hurts most. Look at customer complaints, common mistakes, or tasks that take too long. If your closing team regularly forgets to restock the bar, that’s your first SOP.

2. Document what your best performers already do

Watch your top closer or fastest prep cook. Write down exactly what they do, in order. You’re not inventing a new process. You’re capturing what already works.

“Most restaurants don’t have a people problem, they have a systems problem,” says Mark Steele. “Every employee walks in with habits from somewhere else. If you don’t give them a clear, structured way of doing things, they’ll default to what they know.”

3. Get input from the team who will use it

Have servers review server SOPs. Have cooks review kitchen SOPs. They’ll catch what doesn’t work in practice, like the step that’s impossible during a rush, or the equipment that’s never where the SOP says it is.

4. Choose a simple format everyone can follow

Keep it scannable: numbered steps, short sentences, one action per line.

Format	Best For	Example Use
Numbered steps	Sequential tasks	Opening procedures
Checklist	Verification tasks	Health inspection prep
Flowchart	Decision-based tasks	Complaint escalation

5. Write for the newest person on your team

If someone on their first week can’t follow it, it’s too complicated. Use plain language. Skip the jargon. One action per step.

6. Test it before you roll it out

Have someone unfamiliar with the task try to follow the SOP. Watch where they get confused. Fix those spots before you roll it out to everyone.

Restaurant SOP examples you can adapt for your locations

Here are actual SOPs you can customize for your restaurants.

Opening procedures SOP example

Purpose: Ensure the restaurant is fully prepared before service begins.

1. Unlock front door and disarm security system
2. Turn on all lights and HVAC
3. Check voicemail and email for reservations or issues
4. Verify cash drawer matches previous night’s count
5. Walk the floor, check for cleanliness, reset any moved furniture
6. Confirm prep list completion with kitchen
7. Review reservations and large party notes
8. Hold pre-shift meeting 15 minutes before service

Closing procedures SOP example

Purpose: Secure the restaurant and prepare for the next day’s service.

1. Announce last call 30 minutes before close
2. Process final checks and close out all tabs
3. Complete side work assignments
4. Count cash drawer and reconcile with POS report
5. Document any variances over $5
6. Shut down kitchen equipment per posted checklist
7. Complete cleaning checklist
8. Walk the floor, check restrooms, patio, storage areas
9. Set security alarm and lock all doors
10. Confirm lockup via manager text thread

Customer complaint handling SOP example

Purpose: Resolve guest issues quickly while protecting the restaurant.

1. Listen without interrupting, let the guest finish
2. Apologize sincerely
3. Offer a specific solution (comp, remake, discount)
4. If guest refuses solution, escalate to manager on duty
5. Document the complaint in the shift log
6. Follow up with guest before they leave if possible

Food safety SOP example

Purpose: Maintain food safety standards and inspection readiness.

1. Check walk-in cooler temps at open, mid-shift, and close
2. Log temps on posted sheet (target: 40°F or below)
3. Date-label all prepped items with prep date and use-by date
4. Rotate stock using FIFO (first in, first out)
5. Discard any items past use-by date
6. Report equipment issues to manager immediately

What to include in a standard operating procedure template

Every SOP follows the same basic structure:

• Title: What task this covers
• Purpose: Why this SOP exists (one sentence)
• Scope: Who follows this and when
• Materials/equipment needed: What they’ll need before starting
• Step-by-step instructions: The actual procedure
• Responsible party: Who’s accountable
• Version date: When it was last updated

Keep the template simple. If it takes longer to fill out the template than to write the procedure, you’ve overcomplicated it.

How to roll out SOPs across multiple restaurant locations

Writing SOPs is the easy part. Getting consistent adoption across locations is where most operators struggle.

1. Start with one location as your pilot

Test at your strongest location first. Work out the kinks before rolling to others. Your best team will give you honest feedback about what doesn’t work.

2. Train your managers first

Managers need to know SOPs cold before teaching their teams. Schedule dedicated training time, not a quick walkthrough during a busy shift.

3. Make SOPs accessible from anywhere

Paper binders get lost, damaged, and ignored. Digital access ensures your team can pull up a procedure on their phone when they need it. Tools like 7shifts can help centralize team communication and training materials in one place.

4. Set clear expectations and deadlines

Give specific dates: “All FOH staff trained on new closing SOP by June 15.” Vague timelines lead to vague compliance.

5. Track completion and compliance

Verify who’s been trained and follow up on gaps. Daily checklists help confirm procedures are actually being followed, not just acknowledged.

Common restaurant SOP mistakes and how to avoid them

Writing SOPs without team input

Procedures created in an office rarely work on the floor. The people doing the work know what’s realistic during a Friday rush.

Making procedures too complicated

If an SOP is three pages long, no one will read it. Break complex processes into multiple shorter SOPs.

Storing SOPs where nobody can find them

A binder in the back office doesn’t help the new hire on the line. Make access easy, ideally on their phone.

Never updating after the initial rollout

Menus change. Equipment changes. Staff changes. Review SOPs at minimum twice a year, or whenever you change something significant.

How to keep restaurant SOPs updated across all your locations

SOPs are living documents. Assign ownership, someone responsible for reviewing each category of SOPs. Set a review schedule (quarterly works for most restaurants). Create a simple feedback loop so staff can flag when something doesn’t work anymore.

Version control matters: date every update and archive old versions. You don’t want location two following last year’s procedures while location three uses the current ones.

Build restaurant SOPs that scale with your locations

SOPs aren’t bureaucracy. They’re how you grow without losing what makes your restaurant work. Start with one SOP this week. Pick your biggest pain point. Document what your best people already do. Test it, refine it, and roll it out.

The restaurants that scale successfully treat SOPs as a competitive advantage, not paperwork. Your future locations will thank you for the systems you build now.

Ready to make operations easier across all your locations? Start a free trial of 7shifts to centralize scheduling, communication, and training in one place.

FAQs about restaurant standard operating procedures

What is the 30/30/30 rule for restaurants?

The 30/30/30 rule is a budgeting guideline suggesting restaurants allocate roughly 30% of revenue each to food costs, labor costs, and all other operating expenses, leaving the remaining portion as profit. It’s a starting point, and your actual targets depend on your concept and market.

Can I use ChatGPT to write restaurant SOPs?

AI tools can help draft SOPs, but you’ll need someone with hands-on restaurant experience to review and refine them. Generic instructions won’t capture your specific equipment, layout, or standards.

How many SOPs does a typical restaurant need?

Most restaurants need between 15 and 30 core SOPs covering opening, closing, food safety, customer service, and key operational tasks. The exact number depends on your concept and complexity.

What is the difference between a restaurant SOP and a checklist?

An SOP explains how and why to complete a task with detailed steps. A checklist is a quick verification tool to confirm tasks were completed. SOPs train; checklists verify.

How often should restaurant SOPs be updated?

Review SOPs at least twice a year or whenever you change menus, equipment, software systems, or receive feedback that a procedure isn’t working.

Who should be responsible for writing and maintaining restaurant SOPs?

Typically the general manager or operations director owns SOPs, but the people who actually perform the tasks contribute to writing them and flag when updates are needed.