A restaurant's pre-service briefing should change how the next few hours are run, not merely repeat the menu while staff wait to begin. The most useful discussion makes everyone aware of unusual bookings, unavailable dishes, responsibilities, safety-sensitive updates and matters that require a manager's decision. In a small restaurant, five focused minutes can help a team begin service with the same operational picture, provided the information is current and the questions that matter are answered.
This is a suggested briefing process rather than a statutory script. Restaurants must follow their own food-safety management system and relevant requirements. The Food Standards Agency's allergen checklist helps managers, kitchen staff and front-of-house colleagues understand allergen communication. The ICO's data-minimisation principle is relevant when booking notes include customer information.

Begin with the service the team is about to deliver
Start with the practical shape of the shift: significant bookings, large parties, expected arrival patterns, events affecting space and any unusual timing. Avoid long forecasts that suggest the restaurant knows exactly how many walk-ins will arrive. Staff need to understand likely pinch points, especially when a large booking overlaps with normal evening trade. If the dining room layout has changed, show the plan and make sure employees know which tables remain available for other guests.
For example, a hypothetical restaurant has an eighteen-person group arriving just before its usual dinner rush. The briefing should identify that group's agreed seating and meal arrangement, how it affects the kitchen's timing, and who owns the group contact. It should not promise that other tables will be served in a fixed number of minutes if kitchen capacity is uncertain. This illustrates the value of shared operational awareness, not a measured claim that pre-service meetings eliminate delays.
Check current menu availability and approved changes
Ask the kitchen to report unavailable items, limited portions, legitimate substitutions and anything changed since the last service. Staff should know the source of the current menu information and who can update it during trading. A dish that was available at lunchtime may not be available by dinner. If a supplier delivered a different ingredient or a recipe was revised, a front-of-house employee must not assume earlier information still applies.
Record the changes in the maintained menu or service system and avoid relying solely on spoken recollection. Reconcile online menus and ordering channels where applicable. If availability is uncertain, employees should know to check before accepting an order or making a promise. The briefing is valuable because it connects kitchen decisions to customer-facing information, not because it encourages staff to memorise an entire menu each day.
Make allergen communication an explicit control
Allergen-related questions require accurate ingredient information and a consistent route between customers, servers and kitchen staff. The government's food-allergy guidance states that food businesses must provide accurate information and manage cross-contamination. Brief the team on relevant changes without assuming a spoken message replaces approved written records or staff training. Employees should know how to check a dish and whom to ask when the information is incomplete.
Do not announce that an item is 'allergy safe' merely because a colleague believes a substitute is similar. Distinguish dietary preferences from allergies, protect customer privacy and use the established food-safety process when recording individual requirements. A useful question at the briefing is whether any changed recipe, new product or unavailable ingredient requires an update to customer-facing allergen information. The correct answer must come from the maintained data and the responsible kitchen team.
Assign roles and cover the gaps between stations
Identify who greets arriving guests, manages bookings, covers sections, supports larger tables and coordinates with the kitchen pass. Flexibility matters in small teams, but it works best when everyone knows their starting responsibilities. If one person must cover two functions at a particular time, establish who can provide backup and what takes priority. Otherwise two employees may each assume the other will welcome a party or handle a special request.
Assign a clear decision owner for disputes, booking conflicts and significant changes during service. A server should know who is authorised to agree a menu exception or change a commercial term. The briefing can use a short checklist of responsibilities without prescribing a rigid staffing pattern that would not suit every venue. If someone is absent, revise the plan visibly rather than quietly leaving an uncovered section in place.
Protect booking information whilst briefing the right people
Bookings may contain contact details, accessibility requests, dietary information, family celebrations or other personal details. The team should learn what is necessary to provide the agreed service, but not every employee needs to hear the organiser's entire message. Refer to the approved booking record and share relevant operational requirements with the people responsible. Do not circulate screenshots of private messages through informal personal channels merely because they are convenient.
For a larger group, staff may need the confirmed headcount, arrival timing, layout, menu and the existence of special arrangements. More sensitive details should move through the proper restricted route. When an organiser changes the plan, make sure the briefing reflects the authorised new version and does not contradict a printed sheet left from an earlier date. The ICO's guidance supports minimising unnecessary data duplication.
Surface equipment, supplier and staffing exceptions
A broken piece of equipment, incomplete delivery or changed access route can affect service. Distinguish what has been observed from what a responsible person has verified or approved. If equipment has been taken out of use under restaurant procedures, employees should not improvise a way around the restriction. If a menu component is unavailable, note the source of the decision and the agreed response when customers ask about it.
Keep the briefing focused on actions staff can take. A maintenance report belongs in its proper record, but the people serving guests may need to know how the service plan has changed. Likewise, a delayed supplier delivery may require an availability update rather than repeated speculation about when it might arrive. Assign ownership to unresolved problems and establish when a supervisor will review them. An honest limit is more useful than a confident workaround nobody has checked.
Agree escalation and communication during the rush
Discuss what should happen if a large party arrives early, a reservation appears twice, a customer asks for an unapproved substitution or the kitchen falls behind. Team members need to know who will decide and which information should be checked before a promise is made. A quick verbal rule such as 'all unusual booking changes go through the duty manager' can prevent several people making conflicting commitments.
Encourage brief updates during service if conditions materially change. The pre-service plan is the starting position, not an immutable script. When the kitchen reports a delay or a dish sells out, front-of-house staff should receive the updated position promptly. If something cannot be confirmed, explain that uncertainty to customers rather than inventing a specific timeline. Good coordination means the business adjusts visibly as real information arrives.
End with a readiness check and learn after service
Allow staff to ask questions that reveal unresolved issues. Can everyone identify the source of current allergen information? Does the team know where the large booking sits and who owns changes? Is an equipment problem still awaiting a safe decision? A useful briefing closes gaps rather than testing whether people memorised a manager's speech. Record only the unresolved action items and assign owners before doors open.
After service, compare the anticipated difficulties with what actually happened. Did the seating plan work? Were customers given consistent information about an unavailable dish? Did confusion arise because a booking changed too late? Improve the next briefing by bringing forward the information that would have helped, while cutting topics that no longer add value. The objective is a short conversation connected to real operational decisions, not a ritual that takes staff away from their work without changing anything.
Supporting evidence: front-of-house briefings should cover current food-safety and service exceptions
Food Standards Agency guidance supports keeping staff informed about current food-safety controls, including allergens and any changes that affect service. That aligns with a short front-of-house briefing covering menu changes, unavailable items, allergen-sensitive updates, large bookings and operational exceptions before service begins.
ICO data-minimisation principles also support limiting customer information in a briefing to what staff genuinely need to deliver the service. Sensitive or unnecessary booking details should stay in the appropriate system rather than being repeated broadly.
Evidence boundary: there is no mandatory briefing script. The exact content should match the restaurant's menu, bookings, staffing and food-safety management system.
Sources
Additional illustrative image link: a prepared restaurant table photographed by Shinetungalag, CC0 1.0. This complements the ART1 kitchen view by illustrating the dining-room arrangements that front-of-house teams brief before service.