Back of House (BOH)

Back of house runs on a different rhythm from the dining room. Prep lists, line checks, tickets, and fire times replace greetings and table touches. It is also the part of a restaurant that receives guest information through the narrowest channel, which is why an allergy known at the host stand can still be unknown on the line.

How does guest information reach the kitchen?

Through two channels, and only two. The first is the ticket. Whatever a server rings into the point of sale prints or appears on the chit, so an allergy, a coursing instruction, or a birthday reaches the line if somebody typed it into the order. The second is the pre-shift briefing, which is where the kitchen learns about the night in advance rather than ticket by ticket.

Everything else stops at the pass. A shellfish allergy sitting on a guest profile, a note in the reservation book, a tag applied by the marketing team: none of it is visible to a cook unless a person carries it across. This is the failure that matters most, because it is the one with a safety consequence. Guest data can be perfectly accurate and still arrive nowhere useful.

The practical implication is that guest records should be judged by whether they reach the ticket and the pre-shift, not by how complete they look in a dashboard. Pre-shift reporting in a restaurant CRM exists for this reason. It pulls the night’s bookings with their tags and notes into one briefing that goes out before service, so the kitchen works from the same information as the host stand.

What does the kitchen need to know about tonight’s guests?

Less than the dining room does, but the parts it needs are specific.

• Allergies and dietary restrictions. The only guest data with a safety consequence, and the reason accuracy in the reservation note matters to the kitchen at all.
• The covers forecast. Bookings on the book drive prep quantities, ordering, and how many hands are called in. An overstated book means food bought against demand that never arrives.
• The tables where something is expected. A regular’s anniversary, a chef’s-table booking, a guest the owner asked to look after. The kitchen usually needs a handful of these, not the whole guest list.
• Timing and course pacing. A party of ten at 8pm changes how the line plans the middle of service.