A restaurant pre-shift meeting should prepare the team for service, not become another long meeting that employees stop listening to.
The best pre-shift briefings are short, specific and connected to what will actually happen during the next service period. In ten minutes or less, a manager should be able to align the team on expected volume, staffing, menu changes, reservations, service priorities and the few operating risks that matter that day.
This guide shows how to structure a practical restaurant pre-shift meeting that improves execution without slowing the team down.
What a pre-shift meeting is for
A pre-shift meeting is a short operational briefing held before service begins.
Its purpose is to make sure the team starts with the same information.
A useful briefing should answer questions such as:
- How busy do we expect to be?
- Are there any large bookings or events?
- Are any menu items unavailable?
- What are today’s service priorities?
- Are there any staffing gaps?
- What problem from the previous shift needs attention?
The meeting should reduce confusion during service, not create more administration.
Keep it short enough that the team respects it
If a pre-shift meeting regularly takes 25 minutes, it will eventually become background noise.
A useful target is usually around five to ten minutes.
That is long enough to cover important information but short enough to protect prep time and maintain attention.
The manager should prepare the talking points before gathering the team.
Use the same structure every day
Consistency helps the team know what to expect.
A simple structure might be:
- Expected business level
- Staffing and station assignments
- Reservations, events or large orders
- Menu availability and product issues
- Service focus
- Safety or operational alert
- One quick team check
The details change every day, but the structure remains familiar.
Start with expected sales and volume
The team should know whether the shift is expected to be slow, normal or unusually busy.
You do not always need to share a full financial forecast.
The useful operational information is:
- expected covers or transactions,
- expected peak time,
- large reservations,
- delivery demand,
- known local events,
- weather conditions if they materially affect traffic.
This helps front-of-house, kitchen and management prepare for the same demand pattern.
Confirm station assignments
Do not assume everyone knows where they are working.
Clarify:
- who is on each station,
- who is covering breaks,
- who is responsible for takeout or delivery packing,
- who is the shift lead,
- who handles guest escalations,
- who is responsible for closing specific areas.
This is especially important when the team has new staff, call-outs or last-minute schedule changes.
Call out staffing gaps before service
If the restaurant is operating short-handed, the team needs to know how the shift will be adjusted.
Examples:
- one station may be combined with another,
- a manager may support the line during peak time,
- side work may be delayed,
- break timing may be adjusted,
- certain low-priority prep tasks may be moved.
It is better to explain the plan before service than to improvise under pressure.
Review reservations and large orders
Large parties, catering pickups and group bookings can change the shape of a shift.
The team should know:
- arrival time,
- party size,
- special menu or package,
- allergies or confirmed dietary requests,
- assigned server or section,
- production timing,
- payment arrangements where relevant.
For catering-heavy operations, the same briefing principle can be applied to dispatch and production orders.
Review item availability
One of the fastest ways to damage service is for staff to discover an unavailable item after the guest orders it.
Before the shift, confirm:
- sold-out items,
- items running low,
- approved substitutions,
- limited-quantity specials,
- temporarily unavailable modifiers.
Front-of-house staff should know the information before speaking with guests.
Discuss only important menu changes
If a price, recipe, garnish or plating standard changed, mention it.
But do not turn the pre-shift meeting into a full training class.
Complex training belongs in a separate session.
During pre-shift, the goal is to communicate changes that affect today’s service.
Choose one service priority
A strong pre-shift meeting often includes one specific service focus.
Examples:
- greet tables within the expected standard,
- reduce ticket-time delays,
- confirm allergy communication,
- improve beverage attachment,
- check takeout bags before handoff,
- reduce missed side items.
One clear focus is more useful than five vague reminders.
Base the focus on actual problems
The manager should not invent a theme every day just to have something to say.
Use real operating information.
If yesterday produced several missing delivery items, today’s focus might be final bag checks.
If ticket times rose during dinner, the focus may be station coordination.
If discount usage increased, the focus may be approval procedure.
Daily reports can help identify the right issue. See our Restaurant Daily Sales Report guide for the management review process behind this.
Include a safety or quality alert when needed
Not every shift requires a safety lecture.
But if there is a specific risk, mention it clearly.
Examples:
- slippery floor near the dish area,
- equipment operating with a temporary restriction,
- high-risk allergy booking,
- new chemical storage location,
- heat issue on a kitchen station.
Specific warnings are easier to remember than generic reminders.
Use yesterday’s exceptions, not yesterday’s entire history
A pre-shift meeting is not the place to replay every mistake from the previous shift.
Choose only the issues that matter today.
For example:
Useful: “We ran out of burger buns at 8:15 last night. Today we have enough stock, but the shift lead must check the par at 7:00.”
Less useful: “Yesterday was a mess and everyone needs to do better.”
The first statement gives the team something actionable.
Avoid blaming individuals in front of the team
Public correction during pre-shift can make the meeting defensive.
If one employee needs coaching, handle it privately unless the issue is a general operating standard that applies to everyone.
The team meeting should focus on execution, not embarrassment.
Ask one quick confirmation question
At the end of the briefing, ask a short operational question.
Examples:
- “What item are we out of today?”
- “Who is covering delivery packing?”
- “What time does the large reservation arrive?”
This confirms that the important message was understood.
Use a written pre-shift sheet
A simple pre-shift sheet prevents the manager from relying on memory.
It can include:
| Section | Example |
|---|---|
| Forecast | Busy dinner, peak 7:00–9:00 |
| Staffing | One server absent; manager covering section 4 |
| Bookings | Party of 18 at 7:30 |
| Unavailable items | Salmon sold out |
| Service focus | Final check on delivery bags |
| Operational alert | Ice machine under observation |
The example above is illustrative.
The sheet should take only a few minutes to prepare.
Build the briefing from existing operating information
The manager should not create a separate data system just for pre-shift.
Use information already available from:
- reservation list,
- staff schedule,
- daily sales report,
- inventory or stock-out notes,
- maintenance log,
- manager logbook.
This keeps the process simple.
Front-of-house and kitchen need some shared information
Front-of-house and kitchen teams do not need identical briefings, but they should share key facts.
Both sides should understand:
- expected volume,
- large parties,
- item availability,
- special menu changes,
- major operational risks.
Separate station-specific details can be handled afterward.
Use a kitchen huddle for production details
The kitchen may need a short additional briefing covering:
- prep gaps,
- station readiness,
- batch quantities,
- expected high-volume items,
- equipment issues,
- special orders.
This should connect with the restaurant’s prep plan. See our restaurant prep list guide for the production-planning side.
Use a front-of-house huddle for guest-facing details
Front-of-house may need additional information on:
- reservations,
- VIP or large groups,
- promotions,
- sold-out items,
- service recovery issues,
- table assignments.
Keep both huddles aligned with the same main priorities.
Do not use pre-shift as unpaid training time
The briefing is part of work and should be handled consistently with the restaurant’s employment practices and applicable labor rules.
Managers should avoid treating required operational meetings as informal off-the-clock activity.
The exact legal requirements vary by location, so operators should follow their local employment rules and professional advice where needed.
Track recurring issues from pre-shift meetings
If the same topic appears every day, the business may have a system problem.
Examples:
- repeated stock-outs,
- repeated late prep,
- repeated missing delivery items,
- repeated station confusion,
- repeated maintenance warnings.
A pre-shift reminder is not a permanent fix.
Repeated issues should move into a proper corrective action or process change.
Link the briefing to the manager log
At the end of the shift, the manager should record important outcomes.
For example:
- Did the large party arrive as planned?
- Did the delivery-bag error rate improve?
- Did the equipment issue worsen?
- Did the staffing adjustment work?
That information becomes input for the next shift briefing.
This creates a simple feedback loop:
Previous shift → manager log → pre-shift briefing → current shift → next manager log
Do not overload the team with numbers
Managers often know many KPIs, but the team does not need all of them before service.
Share only the numbers that affect execution.
For example:
- expected covers,
- expected peak time,
- one sales target if useful,
- one service metric if it is today’s focus.
Detailed financial analysis belongs elsewhere.
Use recognition carefully
A short positive note can reinforce good behavior.
Examples:
- strong recovery after a busy rush,
- zero missing items on delivery orders,
- excellent guest feedback,
- clean closing handover.
Recognition should be specific and connected to a behavior the team can repeat.
A sample 10-minute pre-shift agenda
A practical briefing might look like this:
| Time | Topic |
|---|---|
| 1 minute | Expected volume and peak time |
| 2 minutes | Staffing and station assignments |
| 2 minutes | Reservations, events and large orders |
| 1 minute | Sold-out items and menu changes |
| 2 minutes | Service priority and previous-shift exception |
| 1 minute | Safety or equipment alert |
| 1 minute | Questions and confirmation |
The exact timing can vary. The important principle is focus.
What should not happen in a pre-shift meeting
Avoid:
- long speeches,
- public arguments,
- unplanned training sessions,
- reading every KPI,
- discussing confidential employee issues,
- repeating the same generic message every day.
If the team can predict every sentence before the manager says it, the briefing has probably lost its value.
Train managers to brief, not lecture
A good pre-shift meeting is a management skill.
The manager should be able to:
- identify the important information,
- communicate it clearly,
- avoid unnecessary detail,
- check understanding,
- end on time.
This is especially important when several supervisors run different shifts. The restaurant should have one standard for what the briefing covers.
Use the same discipline as opening and closing checklists
Pre-shift meetings work best when they are part of a broader operating rhythm.
Opening checklists confirm readiness.
Pre-shift briefings align the team.
Daily reports measure the result.
Closing checklists secure the handover.
Our guide on restaurant opening and closing checklists explains the checklist side of this operating cycle.
Use a pre-shift readiness gate before the briefing ends
The meeting should not finish with important operating gaps still unresolved. Before the team breaks, the manager should be able to answer five readiness questions:
- Are all critical stations covered by a named person?
- Are sold-out or limited items known by both front-of-house and kitchen?
- Are large bookings, allergy notes and special orders assigned to an owner?
- Are any equipment, safety or supply problems serious enough to change the service plan?
- Does everyone know the one service priority for this shift?
If the answer to any of these is no, fix the gap before service rather than assuming the team will work it out during the rush.
Build a one-page pre-shift worksheet
A strong pre-shift sheet should be short enough to complete in a few minutes but specific enough to leave a record of what the manager communicated. A practical worksheet can contain:
| Field | What to record |
|---|---|
| Date and shift | Lunch or dinner, manager on duty |
| Expected volume | Covers, transactions or broad demand level |
| Peak window | Expected busiest period |
| Staffing gaps | Call-outs, combined stations, manager support |
| Large bookings or orders | Time, size, owner and special requirements |
| 86 / low-stock items | Unavailable items, substitutions, limited quantities |
| Service priority | One measurable focus for the shift |
| Safety / equipment alert | Only current issues that affect this shift |
| Owner | Named person responsible for each exception |
| Post-shift result | What happened and what carries into the next shift |
This worksheet should connect with the daily sales report, the restaurant prep list and the opening and closing checklist. The goal is one operating loop, not four separate forms.
Use a worked pre-shift example
Assume a Friday dinner is forecast to be busy from 7:00 to 9:00 p.m. One server has called out, a party of 16 arrives at 7:30, salmon is sold out, the fryer is running normally but one prep refrigerator is being monitored, and the previous shift had several delayed takeout orders.
A useful briefing would not repeat every detail in the manager log. It would turn those facts into assignments:
- Volume: busy dinner; expect the main peak from 7:00 to 9:00.
- Staffing: section 4 is redistributed and the manager supports table touches during peak.
- Large party: server, kitchen lead and payment plan confirmed before 7:15.
- Availability: salmon is unavailable; the approved substitute is communicated before doors open.
- Operational alert: prep refrigerator temperature is checked at the agreed interval and product is moved if the control limit is not met.
- Service priority: reduce takeout delay by assigning one person to final handoff during the peak window.
The value of the briefing is not that the team heard six facts. It is that each fact produced an operating decision.
Turn the service priority into a measurable check
A vague focus such as “be faster tonight” is difficult to manage. Whenever practical, attach the focus to something observable.
| Weak focus | Stronger operational focus |
|---|---|
| Improve speed | Watch ticket-time delays during the peak and escalate stalled checks quickly |
| Improve takeout | Complete a final bag check before every handoff |
| Sell more | Offer the agreed add-on where it fits the guest interaction |
| Communicate better | Call 86 items and major delays through the agreed channel immediately |
If slow orders are the recurring problem, use the process in Restaurant Kitchen Ticket Time rather than repeating “move faster” at every briefing.
Know when a pre-shift issue needs escalation instead of a reminder
Some problems cannot be solved by mentioning them in the huddle. Escalate the issue when it changes the restaurant’s ability to operate safely or consistently.
Examples include an equipment problem that threatens safe holding or production, a critical station with no qualified coverage, an allergy communication breakdown, a major unresolved stock shortage, or a recurring service failure that has already been discussed several shifts in a row.
The pre-shift meeting is a communication control. It is not a substitute for maintenance, staffing action, training, purchasing or corrective management.
Close the loop after service
At the end of the shift, spend two minutes checking the items that mattered in pre-shift. Did the staffing adjustment work? Did the large party run on time? Did the sold-out item create guest confusion? Did the service priority improve? Did the equipment alert worsen?
Record only meaningful exceptions. That gives the next manager a clean starting point and prevents the same problem from being rediscovered every shift.
Restaurant pre-shift meeting FAQ
How long should a restaurant pre-shift meeting be?
Keep it as short as the shift allows while still covering the information needed for service. For many operations, roughly five to ten minutes is enough when the manager prepares the talking points in advance. Complex training and individual coaching should be handled separately.
What should be included in a restaurant pre-shift meeting?
Cover expected business volume, staffing and station assignments, large bookings or orders, unavailable items, one service priority, and any current safety or equipment issue that affects the shift. Add only information the team can act on.
Should kitchen and front-of-house attend the same briefing?
They should share the facts that affect both sides, such as expected volume, large parties, item availability and major operational risks. Station-specific kitchen or front-of-house details can be handled in short follow-up huddles.
Who should lead the pre-shift meeting?
The manager or shift leader who owns the upcoming service should normally lead it. The person needs enough authority to assign responsibilities, clarify exceptions and make operating decisions before service begins.
What should not be discussed in pre-shift?
Avoid confidential employee matters, public criticism of individuals, long training sessions, full financial reviews and unrelated announcements. The briefing should stay focused on the upcoming shift.
How do you know whether pre-shift meetings are working?
Look for fewer avoidable surprises, clearer station ownership, fewer repeated questions during service and better follow-through on the shift’s stated priority. If the same issue appears in every briefing, move it into a permanent corrective action instead of treating it as a communication problem.
A pre-shift meeting should make the shift easier
The test is simple.
After the briefing, should employees have fewer surprises, fewer unanswered questions and a clearer idea of what matters during service?
If yes, the meeting is doing its job.
If the meeting is long, repetitive and disconnected from real operating conditions, shorten it and rebuild it around the actual shift.
The goal is not to hold a meeting. The goal is to start service with an aligned team.
Operational note: This guide is intended as a practical management framework. Staffing, scheduling, safety and employment practices should be adapted to the restaurant’s local legal requirements and internal policies.