Playbooks

A pre-shift staff meeting is a short briefing held right before an event's doors open, where the captain or lead walks the team through the run-of-show, headcount, key details, and anything unusual about the night. Done well, it takes five to ten minutes. Done badly, it either eats into setup time or skips the details that actually prevent problems.

The goal isn't to cover everything. It's to cover the handful of things that change every single event and can't be assumed.

Keep it under 10 minutes, every time

The single biggest mistake is letting a pre-shift meeting run long because the captain wants to over-explain. Staff working a mixed team — some who've worked with you for years, some who are new — don't need the basics repeated every time. They need this specific event's variables: guest count, timeline, any VIPs, dietary flags, and who to go to if something breaks.

If a pre-shift briefing regularly runs past ten minutes, that's a sign it's covering training-level information that should have happened before the event, not tonight.

The five things every pre-shift meeting should cover

Run-of-show timeline: when doors open, when the meal or key moments happen, when the event ends. Headcount and any last-minute changes from what was planned. Role assignments: who's on which section, bar, or task, especially if it changed from the original schedule. Anything unusual: a VIP table, a dietary restriction affecting service, a room layout quirk. And a single point of contact: who staff should flag problems to during the event, so issues don't get lost.

Introduce new staff, briefly

If you're working with people who haven't worked your events before — common when staffing through a marketplace or during a busy season — a 30-second round of names and roles matters more than it seems. It's the difference between a team that operates like strangers all night and one that can actually communicate when something goes sideways.

Assign a real point of contact, not "ask around"

Every pre-shift meeting should end with a clear answer to "if something goes wrong, who do I tell?" Vague answers like "just find someone" waste time exactly when speed matters most. Name the captain, name the backup if the captain's unreachable, and make sure new staff specifically hear it — regulars usually already know.

Do it standing up, near the floor

A pre-shift meeting held sitting down in a back office takes longer and loses urgency. Do it standing, close to where service will actually happen, ideally with the room already set. It keeps the energy tight and lets people visually connect the briefing to the actual space they're about to work.

Adjust for team size and familiarity

A five-person team that's worked together for months might need two minutes and a nod. A twenty-person team assembled partly through new hires needs the full run-through. Reading the room here matters more than following a rigid script — the goal is alignment, not ceremony.

A sample script for a mixed-familiarity team

For a team combining regulars and new hires, a workable flow looks like: "Tonight's a 220-guest plated dinner, doors at 6, dinner service starts at 7:15. Headcount's confirmed at 220, no last-minute changes so far. [Names] are on the north section, [names] on south, [names] on bar. Table 12 has a nut allergy flagged — no shared serving trays for that table. If anything comes up, find [captain name] — I'll be by the kitchen pass most of the night. New folks, quick round: names and what section you're on, so we're not learning that mid-service." That's under two minutes spoken, covers every essential category, and takes the guesswork out of who does what.

What happens when you skip it

Skipping the pre-shift meeting doesn't usually cause a visible disaster — it causes a dozen small ones. A server who doesn't know about the allergy flag. Two people who both think they're covering the same section while another goes uncovered. A new hire who doesn't know who to flag a problem to, so a small issue sits unresolved for twenty minutes instead of two. None of these individually sinks an event, but together they're the difference between a floor that runs smoothly and one that feels chaotic without anyone being able to point to a single cause.

FAQ

How long should a pre-shift staff meeting be? Five to ten minutes for most events. Longer than that usually means training-level content is bleeding into what should be a quick briefing.

Should every staff member attend, including setup crew? Setup crew who finish before doors open don't need to be there. Anyone working during guest hours should be, including new hires meeting the team for the first time.

What's the most commonly skipped but important item? Naming a single point of contact for problems during the shift. Without it, staff waste time during the event figuring out who to flag an issue to.

Should the pre-shift meeting happen at the same time for every event? Roughly 15-20 minutes before doors is a reliable default, giving staff time to absorb the briefing and take their positions without a long gap where details get forgotten. Adjust earlier for larger or more complex events that need more settling time afterward.

A tight pre-shift meeting is one of the cheapest ways to prevent a chaotic night. It costs ten minutes and buys you a team that's actually aligned before the first guest walks in.