There’s a subtle but decisive difference between a pre-shift meeting that works and one that becomes empty ritual. That difference has a name: structure. Without it, the pre-shift becomes a manager monologue while the staff watches the clock. With it, it’s the moment when six people transform into a coordinated team.
This is a practical, minute-by-minute guide to running a fifteen-minute pre-shift. It works for a 40-cover bistro and for a 120-cover concept restaurant. The logic is the same; only the numbers change.
Quick framing. If you’re not yet clear on why the pre-shift meeting matters, start with our pillar on pre-shift meetings and Will Guidara’s lessons. This article is the tactical companion — how to do it, not why to do it.
The 15-minute agenda, broken down
The fifteen-minute block splits into five sections with strict timing. Stick to the times: discipline on duration is discipline on the team’s attention.
Minutes 0–2 — Opening and team check-in
The manager (or whoever leads the pre-shift) gathers everyone in a circle or seated. Headcount. Acknowledges new hires or anyone returning from a day off. Confirms the planned closing time.
The opening is short but deliberate. The signal is: the pre-shift is on, we’re focused now. No phones, no still-polishing-glasses energy.
Minutes 2–5 — Tonight’s numbers
Three key data points, in order.
Reservations on the books. How many for each turn (lunch or dinner), how many tables, distribution across rooms. With a reservation system, these numbers are visible at a glance.
Walk-in estimate. Based on historical average for the day of week and season. “Wednesday night, no events: expect 8–10 walk-ins, mostly the two-tops near the window.”
Pressure points. Are turns evenly distributed or are there spikes? If you have 30 reservations clustered between 9:00 and 9:15 PM, the team needs to know in advance. Knowing that the second evening turn can make or break the night shapes how you set up early service.
Minutes 5–9 — Special guests and VIPs
This is the section that separates an operational pre-shift from one that produces hospitality.
For every “special” table of the night, the manager says three things: who they are (name + brief story), why they’re special (allergy, anniversary, first date, regular, reviewer), and what to do (concrete action).
Example. “Table 12, 8:30. The Davis family, third visit in two months. Mrs. Davis is celiac: full GF dinner, kitchen has the bread already prepared. It’s their daughter’s birthday: house dessert with a candle at the end of the meal, Marco brings it.”
Three or four special tables per service is the norm. If you have ten, summarize the rest and let the team consult the full list during the pre-shift.
Where does this information come from? From a restaurant CRM connected to reservations and from server notes maintained every night. Without these two pieces, the special-guest section reduces to whatever the manager happens to remember — and personal memory doesn’t scale.
Minutes 9–12 — Menu and kitchen
The chef (or sous-chef, or manager if the kitchen isn’t in pre-shift) covers:
- Specials and new dishes. A sentence on how it was conceived and what to pair it with.
- 86 — items running out or out of stock. Explicit: “The salmon is gone after 10 orders, then drop it from the verbal.”
- Menu modifications. Ingredient swaps, substitutions, allergen flags.
- Push items. What dish you’d like to push tonight and why — for example, to balance food cost or to move a fresh ingredient before it spoils.
Three minutes is enough if the kitchen comes prepared. If the kitchen is improvising every night here, something’s off: kitchen-floor dialogue should happen earlier in the day.
Minutes 12–14 — Operational notes and questions
Everything else: logistical details (a wobbly table, a sticky door, a burnt-out spotlight in zone B), turn-rotation flags, staff schedule changes, communications from management (training, events, procedural changes).
Critical: leave 30–60 seconds for questions from the team. Without questions, the pre-shift is purely top-down. With questions, it becomes a dialogue that improves operations.
Minute 15 — The closing
One sentence. Just one.
“Tonight, table 7 is the couple who came for their first anniversary last year. They’re back for the second. Let’s make them feel like it’s their tenth.”
“Mauro, you handled that difficult table last night beautifully. Tonight is going to feel easy by comparison. Let’s go.”
“Quiet service, 38 covers. Let’s use this night to take care of the details we never get to on Saturdays. Let’s go.”
The closing isn’t mandatory, but it changes everything. It’s how the pre-shift ends with an idea the team carries onto the floor.
Who speaks during the pre-shift
An effective pre-shift isn’t a monologue. But it isn’t a town hall either.
The manager (or floor director) leads. Opens, closes, manages timing, communicates numbers and special guests.
The chef or sous-chef takes minutes 9–12. That’s their window.
Floor staff chime in during the question period, but can also intervene earlier with relevant information (a regular who called for a change, a flag on another table).
The owner or general manager shouldn’t be present every night — their presence raises the formality level and changes the dynamic. They should drop into the pre-shift only when they have something specific to say (procedural change, training, group communication).
The 5 most common mistakes
1. Starting late. If you said 6:45 and you start at 6:55, you’ve already lost. The pre-shift is a covenant on team discipline. Starting on time is the first proof.
2. Glossing over special guests. If the VIP section reduces to “remember table 4 is Davis,” you’re not running a pre-shift. You’re doing a handoff. Special guests need actionable detail.
3. Having an unprepared chef. If every night the chef shows up to the pre-shift not knowing what to say, the menu block becomes “the salmon is out.” The chef needs to prep their three sentences — even mentally — before walking in.
4. Turning it into a sermon. If the only content is yesterday’s problems, the team checks out. Problems get handled in a post-shift debrief (we cover this in a dedicated piece), not in the ten minutes before service.
5. Always saying the same thing. The pre-shift isn’t a script. Every night has something unique — a guest, a dish, an event. If your Monday pre-shift sounds like your Saturday one, you’re not using the tool.
Printable template
Here’s the skeleton you can print and keep at the pass.
PRE-SHIFT MEETING — [date] — [shift]
▢ Opening (2')
- Headcount: ___________________
- Closing time: ________________
▢ Numbers (3')
- Reservations: ____ across ____ tables
- Expected walk-ins: ____
- Pressure points: ___________________
▢ Special guests (4')
1. Table ___ at ___ — _________________
What to do: _____________________
2. Table ___ at ___ — _________________
What to do: _____________________
3. Table ___ at ___ — _________________
What to do: _____________________
▢ Menu (3')
- New dishes: ___________________
- 86 / running out: ___________________
- Push: ___________________
▢ Notes and questions (2')
___________________________________
▢ Closing (1')
"___________________________________"What happens after two weeks
The first few nights will feel forced. The team will glance at the clock. The chef will show up unprepared. You, as the manager, will feel like you’re talking to yourself.
Stick with it. After two weeks, something interesting happens: if you skip the pre-shift one day, somebody calls it out. “Hey, are we doing it tonight?” That’s the moment you know the ritual has entered the team’s DNA.
And once it’s in the team’s DNA, it shows up in the guest experience. Because an aligned team makes fewer mistakes, anticipates more, and creates moments that without the pre-shift could never have happened.
Coperti is the reservation system that puts the data your team needs at pre-shift right in front of them: tonight’s reservations, VIP guests, allergies, anniversaries, visit history. All in one glance, on any device. See how it works or request a demo.