Front of house vs back of house: who owns what

At nine on a Saturday, a plate sits on the pass for four minutes. The kitchen says the floor is too slow to collect it. The floor says nobody called it. The guest says the food was lukewarm. Twenty minutes later, a server tells the kitchen that table twelve has a nut allergy, after the main has already gone out with a nut crumb on it. By the end of the night, each side is sure the other let them down, and both are partly right.

Most of the friction between the floor and the kitchen comes from the moments where work passes from one team to the other: the order, the pass, the dish sent back. When nobody clearly owns those handovers, each side assumes the other will handle them, and problems fall into the gap. When ownership is clear, the same moments run smoothly, and the two teams start to feel like one.

This guide covers the comparison of front of house vs back of house in terms of what each owns, the handovers between them, the three that cause most of the friction and how to make each one clear. Every venue and figure in it is an example.

Front of house is everything the guest sees: the door, the floor, the bar and the people who work there, hosts, servers, runners and bartenders. Back of house is everything the guest does not see: the kitchen, the stores, the dish wash and the people who cook, prep and clean.

Each side has its own skills, pressures and rhythms. The floor works with guests, in public, managing moods and timing. The kitchen works with heat, time and precision, behind a door. Both are needed for a single plate to reach a happy guest.

Friction happens because each side sees only half of the service. The kitchen sees tickets arriving in bursts and plates waiting to be collected. The floor sees guests waiting and asking where their food is. Neither sees the other's pressure clearly, so each blames the other when things go wrong.

The fix is not to make the two sides the same, but to make the handovers between them clear: who owns each moment, what each side needs from the other and what happens when something goes wrong.

The floor owns the guest's experience from arrival to departure: the welcome, the seating, taking the order accurately, timing the courses with the guest's pace, delivering food promptly, checking back, handling complaints and taking payment. It also owns the information the kitchen needs about each table: allergies, preferences, special requests and when the guests are ready for the next course.

The floor is the kitchen's eyes and ears in the dining room. If the floor does not pass on what it sees, the kitchen cooks blind.

The kitchen owns the food: its quality, its consistency, its timing once an order is fired and its safety, including allergens. It also owns the information the floor needs: what is available, what has run out, what the specials are, how long dishes take and anything that will delay a table.

The kitchen is the floor's source of truth about what can be promised to a guest. If the kitchen does not tell the floor that the fish has run out, a server will promise it to a table.

Most of a service passes through a handful of handovers. The briefing before service, where the kitchen tells the floor about specials and shortages. The order, where the floor tells the kitchen what each table wants. The pass, where finished food goes from the kitchen to the floor. The dish sent back, where a problem returns from the floor to the kitchen. And the end of service, where both sides close down.

Each handover needs an owner and a clear way of working. Three of them cause most of the friction: the order, the pass and the dish sent back.

The order is the first and most important handover. A ticket that is unclear, missing a modification, missing an allergy or sent at the wrong time causes problems that the kitchen cannot fix on its own.

The floor owns the order's accuracy: every dish, every modification, every allergy, clearly recorded. The kitchen owns reading it properly and asking at once if something is unclear. Neither should guess.

Clear orders come from habits. Record every allergy on the order itself, not in a separate note. Use the same words for modifications every time. Send courses when the table is ready, and hold them when it is not. Mark special occasions and anything the kitchen should know.

Our guide to sending an order to the kitchen properly covers the habits that make orders easy for the kitchen to read and cook.

Allergies are the handover where a mistake can hurt a guest, so they need the clearest ownership of all. The floor owns asking, recording the allergy on the order and telling the kitchen in person as well. The kitchen owns checking every dish against it, preventing cross-contact and confirming that the dish is safe.

Agree a single routine and follow it every time. An allergy that relies on someone remembering to mention it at the pass is an allergy waiting to be missed. Our guide to an allergy mistake: the next ten minutes covers what to do if one is.

The pass is the second handover: the point where finished food leaves the kitchen. Food that waits on the pass goes cold, wilts or dries, and a plate that waits for four minutes undoes the kitchen's timing.

Agree who owns the pass at each moment. In many kitchens, a head chef or expeditor calls each table and a runner or server collects at once. In smaller venues, the kitchen calls and the nearest server collects. Either works, as long as everyone knows.

The pass works when the kitchen calls food clearly and the floor collects it promptly. A bell, a call or a screen can signal that food is ready; what matters is that someone on the floor is always listening.

On busy nights, assign a runner to the pass if you can. A person whose only job is to collect and deliver food keeps plates moving while servers look after their tables.

The dish sent back is the third handover, and the most emotional. A guest unhappy with a dish puts the server in the middle: the guest wants it fixed, the kitchen may feel criticised and the server has to manage both.

Agree in advance how it works. The floor owns listening to the guest, apologising and bringing the dish back with a clear reason. The kitchen owns fixing it quickly, without argument. The manager or shift leader owns any decision about comps.

Returns go badly when they become arguments. A chef who argues with a server about whether the steak was really overcooked wastes time while the guest waits. A server who blames the kitchen in front of the guest damages the venue.

Fix first, discuss later. Remake the dish, look after the guest, and talk about what happened after service, calmly, with the aim of preventing the next one.

The briefing before service is a handover that prevents many of the others. The kitchen tells the floor about specials, shortages, dishes to push and anything that might slow down. The floor tells the kitchen about large parties, allergies on the bookings and special occasions.

Ten minutes together, before the doors open, means both sides start the service with the same picture. Kitchens and floors that brief separately often discover during service that they were planning different evenings.

When a dish runs out, the kitchen owns telling the floor at once, and the floor owns not selling it from that moment. A dish sold after it has run out means a server going back to a guest to apologise, and a guest who may not order again.

Make running out visible to everyone: a call from the pass, a note on a board, a change on the till. The quicker the floor knows, the fewer awkward conversations at the table.

Course timing is shared. The floor knows when a table is ready for its main course; the kitchen knows how long it takes to cook. When the floor sends mains as soon as starters go out, the kitchen may rush them; when it waits too long, the table waits.

Agree how courses are held and fired. A floor that tells the kitchen when a table is ready, and a kitchen that cooks to that signal, produces meals that arrive at the guest's pace.

The host and the kitchen have a handover of their own. The bookings decide when the kitchen will be busiest, and a host who seats three large parties at the same time can overwhelm the kitchen before the first ticket arrives.

Agree how the host paces large parties and walk-ins with the kitchen in mind. A host who knows the kitchen's limits, and a chef who knows the evening's bookings, prevent many of the night's problems before they start.

When the kitchen falls behind, the floor needs to know at once, so servers can warn tables, offer bread or a drink and slow down new orders. A kitchen that hides the delay until guests complain leaves servers apologising without warning.

Agree a simple signal for "we are behind" and what the floor does when it hears it. Most guests accept a short delay that is explained; few accept one that is ignored.

Kitchen communication, how information moves between the kitchen and the floor during service, decides much of how a night goes. Shouting across the pass works in some kitchens and fails in others; tickets, screens, a bell and a few agreed phrases often work better.

Agree the words and signals both sides use: how a table is called, how an allergy is flagged, how a delay is warned. Consistent signals reduce the noise and the misunderstandings.

Service standards apply to both sides. The floor has standards for greeting, ordering, serving and clearing. The kitchen has standards for each dish's look, temperature and timing. Each side's standards affect the other's.

Write them down and share them across both teams. A server who knows how a dish should look can spot a mistake before it reaches the guest; a cook who knows how long a table has waited can prioritise its ticket.

Clear staff roles make ownership clear. The head chef owns the kitchen's food and timing; the floor manager or shift leader owns the guest's experience and the decisions about comps; the expeditor, if there is one, owns the pass; servers own their tables' orders.

When everyone knows their role, handovers have owners. Our guide to staff roles and the permissions that follow covers how to set them out.

The end of service is a handover too. The kitchen tells the floor when the last orders must be in; the floor tells the kitchen when the last table has ordered. Both close down their sides and hand over to the next shift.

Agree the last order time and keep to it. A kitchen that closes while the floor is still seating guests, or a floor that takes orders after the kitchen has closed, starts the next day's friction tonight.

After service, talk briefly: what went well, what did not, what to change. Five minutes with the head chef and the floor manager, before everyone goes home or at the next day's briefing, turns the night's problems into fixes.

Keep it about the handovers, not about people. "Plates waited on the pass between eight and half past" invites a fix; "the floor was too slow" starts an argument.

Specials need both sides. The kitchen decides and cooks them; the floor sells them. A special the floor cannot describe, or does not know is limited, sells badly or runs out mid-table.

Tell the floor at the briefing what each special is, what is in it, its allergens, how many portions there are and how to describe it. Let servers taste specials where possible. A server who has tasted a dish sells it far better than one reading from a card.

How the two sides speak to each other shapes the whole service. Shouting, sarcasm and blame across the pass make every handover harder. Calm, clear language, even under pressure, makes them easier.

Set the standard from the top. A head chef and a floor manager who speak to each other with respect, especially when things go wrong, teach both teams how to work together.

The deepest fix for friction is building one team rather than two. Shared staff meals, briefings together, credit shared when a service goes well, cooks who spend a shift on the floor and servers who spend an hour in the kitchen all help each side understand the other.

Our guide to front of house and back of house, same side covers the habits that bring the two teams together.

New starters learn how the floor and the kitchen work together from what they see in their first weeks. A new server who is shouted at across the pass, or a new cook who sees servers blamed for the kitchen's delays, learns that the two sides are opponents.

Introduce every new starter to both sides on their first day. A new server who has spent an hour in the kitchen, and a new cook who has watched a busy service from the floor, understand the handovers far better from the start.

Tips are a common source of tension between the two sides. If tips go only to the floor, the kitchen may feel its work is not recognised; if they are shared, the floor may feel its effort is diluted. Either way, an unclear or unfair system breeds resentment.

Agree the tip policy openly, write it down and apply it consistently. Our guide to tip distribution that the team believes in covers how to set one up.

An invented brasserie's floor and kitchen blame each other most Saturdays: plates wait on the pass, allergies are mentioned late and returned dishes start arguments. The manager and head chef list the handovers and agree an owner for each: servers record every allergy on the order and tell the pass, the head chef calls each table and a runner collects on Fridays and Saturdays, and the shift leader decides every comp.

Briefings become joint, ten minutes before service, and returns are fixed first and discussed after service. Within a month, plates no longer wait on the pass, no allergy has been mentioned late and the post-service chat has become a list of small fixes rather than a list of complaints.

In servearound, the floor and the kitchen work from the same orders: what a server sends is what each station's screen shows, oldest first with its age counting, with the guest's allergies at the head of the ticket, removals and notes on each dish, held courses marked held and a voided dish struck through. A dish marked sold out on the till shows as sold out on every menu it is on at once, so running out reaches the guests' menus straight away.

Servers can send the kitchen a compliment from the till, about the whole meal or a dish, and it appears on every station's board. Each venue has a team chat in Messages where both sides can post, and kitchen analytics show ticket times by station and hour and the remake rate, which give both teams the same numbers to talk about. See point of sale and kitchen.

Front of house is everything guests see; back of house is the kitchen and everything behind it.

The order, the pass and the dish sent back.

The floor, with the kitchen asking at once if anything is unclear.

Both: the floor records and tells; the kitchen checks and confirms.

The manager or shift leader, not the server or the chef alone.

Fix it first, look after the guest and discuss it after service.

Yes. Ten minutes together before service prevents many problems.

Shared meals, joint briefings, shared credit and a fair tip policy.

Front of house vs back of house is less a contest than a set of handovers: the briefing, the order, the pass, the dish sent back and the end of service. Most friction comes from three of them, the order, the pass and the return, when nobody clearly owns them. Give each an owner, agree how it works and the same moments that caused arguments start to run smoothly.

Make allergies the clearest handover of all, brief together before service, agree the signals for kitchen communication and write down service standards for both sides. Use staff roles to make ownership clear, fix problems first and discuss them after, and build front of house and back of house into one team rather than two.