How to Run a Restaurant Pre-Shift Meeting That's Actually Useful

Pre-shift meetings have a reputation problem in restaurants. At their worst, they feel like a waste of time — the manager rambles for ten minutes while the team stands there wanting to get to work. At their best, they take five minutes and prevent an entire shift's worth of miscommunication.

The difference isn't about enthusiasm or leadership charisma. It's about structure. A good pre-shift meeting covers specific information the team needs, skips everything they don't, and gets people to their stations quickly.

Here's how to run one that people actually listen to.

Why Bother With a Pre-Shift Meeting

If your team has ever walked into service not knowing about a large reservation, discovered a menu item was 86'd mid-rush, or had two people show up to the same station because nobody assigned positions — that's what pre-shift meetings prevent.

The goal isn't motivation. It's information transfer. You have five to ten minutes to make sure every person on the shift knows what they need to know before service starts. That's it.

Without this briefing, information travels through the kitchen and dining room the slow way — one conversation at a time, one question at a time, one mistake at a time. Pre-shift compresses all of that into a single moment.

The Five-Minute Format

You don't need an agenda template or a slide deck. You need to cover five things, in this order, every shift.

1. Attendance and Stations (30 Seconds)

Confirm who's here. Assign stations. If someone called out and coverage was arranged, say so now. If you're short-staffed and adjusting, explain the plan.

This is purely logistical. Don't belabor it. "Marcos on grill, Sofia on sauté, Devon on prep. Front of house: Aisha's got sections one and two, James has three and four, Priya on bar. We're short a runner tonight so everyone's pitching in on food delivery."

Done.

2. Specials and 86s (60 Seconds)

What are today's specials? Describe them briefly — name, key ingredients, price point. If the FOH team needs to describe or upsell a special, give them enough detail to do it confidently.

What's 86'd? If anything from the regular menu isn't available, say it clearly. Nothing erodes guest trust faster than a server suggesting something and then coming back to the table to say it's unavailable.

If there are new menu items or changes since the last shift, cover them here.

3. Notes From Last Shift (60 Seconds)

This is where the shift handoff feeds into the pre-shift meeting. What did the previous shift flag that this team needs to know?

Equipment issues being monitored. A customer complaint that needs follow-up. An inventory shortage that affects today's service. A prep item that's running low and needs to be replenished.

If your closing manager writes handoff notes (and they should), this is where those notes become actionable. Read the key points, assign follow-up if needed, and move on.

4. Today's Specifics (60 Seconds)

Anything unusual about today's service that the team should know:

Large party reservations and their timing. VIP guests or special requests. Events or promotions running. Shortened or extended hours. Expected delivery during service. A health inspection scheduled (or possible).

This is the "heads up" section. No one should be surprised by something the manager already knew about.

5. Quick Reminder or Focus Area (30 Seconds)

One thing. Not five. One area you want the team to pay extra attention to today.

Maybe it's a food safety reminder because you noticed a habit slipping. Maybe it's a service standard that needs tightening up. Maybe it's a genuine compliment — "we got great feedback from a guest last night about the speed of service, let's keep that energy."

Resist the temptation to turn this into a lecture. One clear, specific point lands better than a laundry list of reminders that nobody retains.

Common Mistakes That Kill Pre-Shift Meetings

Going too long. If your meeting runs past seven or eight minutes, you've lost the room. People start shifting their weight, checking their phones, and mentally clocking out. Five minutes is the sweet spot. If you can't cover it in five minutes, you're covering too much.

Being vague. "Let's have a great service tonight" isn't information. "We have a 12-top at 7:30 and they pre-ordered the prix fixe — kitchen needs to have those courses timed" is information. Be specific or don't say it.

Skipping it when you're busy. The busiest shifts are the ones where the pre-shift meeting matters most. Skipping it to "save time" costs you far more time in mid-service confusion. Even a two-minute version is better than nothing.

Turning it into a lecture. If the team associates pre-shift with getting scolded, they'll tune out before you've said anything. Save performance conversations for one-on-ones. Pre-shift is for information, not discipline.

Not reading the handoff notes beforehand. If you're reading the closing manager's notes for the first time during the meeting, you're wasting everyone's time while you process information in real time. Read them before the meeting. Show up prepared.

Making It a Habit

The hardest part of pre-shift meetings isn't the content — it's doing them consistently. They're easy to skip when things feel routine, and they're easy to let slide when you're rushed.

Two things help. First, make it a fixed time — not "when everyone's here" but a specific clock time that the team can count on. "Pre-shift is at 10:45, every day, no exceptions." Second, keep a simple format that doesn't require preparation beyond reading the handoff notes and checking the reservation book. The five-point structure above takes almost no prep time.

If you want the handoff notes to be there when you need them, make sure your closing managers are writing them consistently. Our guide on building a shift handoff routine covers how to make that happen.

What About Multiple Shifts?

If your restaurant runs two or three shifts, each one should get its own pre-shift meeting. The content will differ — the dinner pre-shift focuses on different specials, different reservations, and different handoff notes than the lunch pre-shift.

The format stays the same. The five-point structure works regardless of which shift you're running.

For the mid-day transition (when lunch hands off to dinner), the pre-shift meeting for the incoming team should incorporate notes from the lunch shift — not just the previous night's closing notes. This is where real-time issue logging helps, because the information is captured as it happens rather than reconstructed from memory at shift change.

Calm Kitchen gives managers a real-time view of issues logged during any shift — so when you step into a pre-shift meeting, you're working from the actual record of what happened, not secondhand recollections.

Start your free 14-day trial →

---

Frequently Asked Questions

How long should a restaurant pre-shift meeting be?

Five minutes is the target. Seven to eight minutes maximum. Anything longer and you lose the team's attention. If you can't cover everything in that window, you're either including too much detail or handling things that belong in one-on-one conversations instead.

What should a restaurant pre-shift meeting cover?

Five things: attendance and station assignments, specials and 86'd items, notes from the previous shift, anything unusual about today's service, and one focused reminder or area of emphasis.

Should every shift have a pre-shift meeting?

Yes. Each shift has its own context — different specials, different reservations, different issues from the preceding shift. A pre-shift meeting ensures the incoming team starts with full information, regardless of which shift they're working.

How do you keep pre-shift meetings from feeling repetitive?