How to Run a Pre-Shift Briefing That Actually Prepares Your Team

Why briefings fail before service starts

The most common version of a pre-shift briefing is a broadcast. The manager talks. The team listens — or appears to. Information is covered, which means nobody can say it was skipped. But covering information is not the same as preparing a team.

A briefing that covers everything typically achieves nothing specific. When the focus is split across twelve things, the team walks onto the floor with a vague sense of what the night holds and no clear idea of what they are actually supposed to do differently tonight.

Information overload is not the same as preparation. A team that heard everything is not the same as a team that knows what matters.

The other common failure is drift. No structure means the briefing runs long, conversations branch, someone asks a question that opens a ten-minute tangent, and by the time service starts the team is half-engaged and the manager is already behind.

Both of these problems come from the same place: no architecture.

What a briefing is actually for

A pre-shift briefing is not a debrief from last night. It is not a training session. It is not a morale exercise.

It is a control mechanism. Its job is to align the team around one outcome before the doors open, so the manager spends less time correcting during service and more time operating.

When a briefing does this well, it creates a moment of shared clarity. Everyone walks out knowing what good looks like tonight. Accountability has a name attached to it. The team is not just informed — they are pointed.

That is what preparation actually looks like.

Seven minutes is enough

Briefings run long because they have no architecture. Give a manager ten minutes with no structure and they will use all of it and still feel like they ran out of time. Give the same manager seven minutes with a clear framework and service will run tighter.

Seven minutes works. The constraint is the point. When time is fixed, priority becomes clear. What actually matters rises to the top. Everything else gets handled another way.

Here is what seven minutes can hold.

The structure, minute by minute

Minute 0–1: Set the room.

Before you say anything about service, control the environment. Everyone present, phones away, side conversations stopped. Stand where you can see everyone.

Then say: "This will take seven minutes. Then we work."

That line does something. It signals that what follows is deliberate. It tells the team that you have prepared — which raises the expectation that they should be ready to receive it. Start on time, every time. If someone is late, they catch up. Waiting trains the team that timing is negotiable. It is not.

Minutes 1–2: State the context.

Context is operational data, not storytelling. What is tonight? Full house from 6:30, large tables in sections B and D, a corporate group in the private room who confirmed late changes to the set menu, bar running one person short. Whatever affects execution tonight — say it, keep it brief, move on.

Context sets the frame. Without it, the team makes assumptions. Some of those assumptions will be wrong, and you will spend the middle of service fixing them.

Minutes 2–4: Name the one focus.

This is where most briefings get it wrong. Instead of one focus, managers give five. Instead of a specific behaviour, they give a general directive. "Be attentive" is not a focus. "Check back within three minutes of mains landing" is a focus.

One focus per briefing. Make it specific, make it observable, make it achievable tonight.

Why one? Because the team can actually hold one thing in their heads during a busy section. Two things compete. Five things disappear. One focus, done consistently across a week, creates a real behavioural shift. Five focuses, rotated nightly, create noise.

The focus should come from something you observed — a pattern from recent services, a gap in execution, a specific standard that has been slipping. It should feel relevant, not arbitrary.

Minutes 4–5: Assign ownership.

A focus without a name attached to it is optional. Ownership makes it visible.

Name who is accountable for what. If table timing is the focus, the floor lead tracks it from 5 to 7 and calls it if sections fall behind. If the objective is wine guidance at the table, name which sections are on it and who reports back at the end of service.

This is not about pressure. It is about clarity. When there is a name attached to an outcome, the team knows it will be reviewed. That alone changes how it is approached.

Minutes 5–6: One service note.

Covers, 86s, specials, anything the team needs before the floor opens. Keep it short. This is not the main event — context and focus are. If you find yourself spending most of the briefing on logistics, the structure has collapsed back into broadcasting.

Minute 6–7: Close cleanly.

Do not reopen discussion. Do not end with a question unless something critical is genuinely unclear. Close it.

Say: "That's the focus. If we execute this, service runs smoother. Let's go."

Then stop talking. Movement reinforces authority. Dragging the close signals uncertainty about what was just said.

What to avoid

No training in the briefing. Training has its place — it is not the two minutes before service. If something needs to be trained, schedule it separately.

No rehashing last night's problems unless they directly affect tonight's execution. Briefings are forward-facing.

No adding reminders at the end. "Oh, one more thing" weakens everything that came before it. If it did not make the briefing, it was not important enough for the briefing.

No checking for enthusiasm. "Everyone good? Let's have a great one." The team does not need permission to be motivated. They need direction.

What changes when you run it consistently

Run this structure without deviation for two weeks. What tends to happen: mid-service corrections decrease because the focus was set before service started. Accountability conversations get easier because ownership was named in front of the whole team, not discovered during the debrief. The briefing itself gets tighter, because the team starts anticipating the structure and stops expecting drift.

None of this is complicated. It is repeatable, which is more valuable.

The underlying principle

Consistency in service does not come from personality. It does not come from hiring good people and hoping for the best. It comes from systems that repeat — and a briefing, done correctly, is the daily system that makes everything else hold.

Seven minutes, one focus, a name on the outcome. That is the structure. What the manager brings to it is the judgement about what matters tonight.

That judgement is what separates a manager running the room from a manager reacting to it.

The Pre-Shift: The 7-Minute System playbook covers the full briefing framework in detail, including how to set the focus, assign ownership, and close cleanly under service pressure. Available at The Glass Pour.

Pre-Shift Notes is a weekly note on wine, service, and standards — without the fluff. Subscribe below.