Front of house and back of house, same side

At nine o'clock on a busy night, a server comes to the pass for the third time to ask where table twelve's mains are. The chef snaps that the floor sent six tables at once. The server snaps back that the guests have been waiting forty minutes. Both are right, both are frustrated, and the argument will happen again next week, with different tables and the same words.

Every restaurant has some version of this. The floor thinks the kitchen is slow and rigid; the kitchen thinks the floor is careless and makes promises it cannot keep. The truth is usually simpler: each side is missing a piece of information the other has.

This guide covers the four arguments front of house and back of house have most often, the information each side is missing in each, and the habits that put both sides on the same team. Every venue and figure in it is an example.

Front of house and back of house see the same service from opposite ends. The floor sees guests: their mood, their waiting, their questions. The kitchen sees tickets: how many, how complicated, how fast they are arriving. Neither sees what the other sees.

Under pressure, each side fills the gap with assumptions. The floor assumes the kitchen is slow; the kitchen assumes the floor is careless. Those assumptions harden into a story, and the story becomes the culture.

Most of the arguments go away when each side can see what the other sees. That is a matter of kitchen communication, routines and a few shared numbers, not of personalities.

The most common argument is about speed. The floor says the food is slow; the kitchen says the orders arrived all at once. Both are usually describing the same event: several tables seated together, ordering together and their tickets landing together.

The floor is missing how the kitchen's load builds. The kitchen is missing why the tables arrived together, and what the guests have been told. Neither side alone caused the wait.

The fix is shared information about pacing. The host can see how bookings are spread across the evening and seat with the kitchen in mind. The kitchen can tell the floor when it is stretched, so servers set expectations at the table. Our guide to table pacing: stopping four tables ordering at once covers the floor's side.

The second argument is about mistakes. A dish goes out wrong, and the floor says the kitchen did not read the ticket while the kitchen says the ticket was wrong. Often the truth is somewhere in between: a change entered as a vague note, an allergy buried at the bottom, a dish rung in under the wrong table.

The floor is missing what the kitchen actually receives. The kitchen is missing what the guest actually said. Each blames the other for a step neither can see.

The fix is a shared look at the evidence. Trace each wrong plate to its step: the order, the ticket or the pass. Our guide to ticket accuracy: where the wrong plate comes from covers how. Once both sides see where mistakes start, the argument turns into a fix.

The third argument is about running out. The kitchen runs out of a dish and the floor keeps selling it; or the kitchen 86s a dish and the floor finds out only when a guest orders it. The floor feels embarrassed in front of guests; the kitchen feels ignored.

The floor is missing the kitchen's count: how many portions are left, and when the last one goes. The kitchen is missing how quickly the floor needs to know.

The fix is an 86 that reaches everyone at once, the moment the dish runs out, and a warning before it does. Our guide to 86 an item so nobody orders it at five past covers the routine.

The fourth argument is about courses. The kitchen sends mains while starters are still on the table, or the table waits twenty minutes with empty plates. The floor says the kitchen ignored the fire; the kitchen says the fire never came, or came too late.

The floor is missing how long each dish takes. The kitchen is missing how the table is getting on. Course timing depends on both, and neither has the full picture alone.

The fix is clear course firing: mains held when ordered, fired by the floor when the table is ready, with the kitchen telling the floor which dishes need an early fire. Our guide to course firing: mains away when the starters clear covers who fires and when.

Remakes cause their own argument. A dish comes back, and the floor wants it remade at once while the kitchen wants to know what was wrong. If the floor says only "it's wrong", the kitchen may remake it the same way.

Agree how remakes are requested: the server says what was wrong, the kitchen remakes it as a priority, and the reason is recorded. A remake with a reason is a lesson; one without is just a second plate.

The floor and the kitchen often use different words for the same thing. The kitchen talks about tickets, stations and fires; the floor talks about tables, guests and courses. A server who says "table nine is waiting" and a chef who hears "another ticket" are describing the same problem from different ends.

Agree a few shared words for service: what "fire" means, what "86" means, what "all day" means, how tables and seats are numbered. Shared language makes messages faster and less likely to be misunderstood.

The floor needs a few things from the kitchen to do its job well. Early warning of what is running low. Honest timings when the kitchen is stretched, so servers can tell guests. A list of slow dishes that need an early fire. And a quick answer when a guest asks what is in a dish.

None of these is complicated. Most can be shared at the pre-shift briefing and updated during service with a word at the pass or a message.

The kitchen needs a few things from the floor in return. Orders that arrive complete, with every change and allergy in the right place. Fires sent when the table is ready, not forgotten. Warning of large tables and bunched arrivals. And honest feedback from guests, both good and bad.

The last one is often forgotten. Kitchens hear about the complaints but rarely about the compliments. A floor that passes on praise as readily as problems builds a kitchen that trusts it.

Many kitchens communicate by shouting, because it is fast. But shouting carries tension, and messages shouted across a noisy kitchen are often missed. Good kitchen communication uses the right channel for each message.

Routine information belongs on the tickets and the screens: what to cook, for which table, when. Urgent information needs a word at the pass: an allergy that is severe, a guest who is waiting too long. Planning information belongs in the briefing. And a quiet word afterwards is the place for feedback, not the middle of service.

When the kitchen falls behind, the floor should know straight away, with an honest estimate. A chef who says "mains are running fifteen minutes behind" lets servers tell their tables and manage expectations. A chef who says nothing leaves the floor to find out from the guests.

The floor's part is to pass the message on calmly, offer bread or a drink to the tables affected, and avoid adding pressure by asking the kitchen every two minutes. One clear message each way works better than ten anxious ones.

Sometimes the floor is the problem: plates waiting at the pass because servers are busy, a section with too many tables, a server who is new and struggling. The kitchen sees food going cold and grows frustrated.

The fix is the same in reverse: the floor says it is behind, the manager moves help to where it is needed, and someone runs food from the pass. A kitchen that sees the floor asking for help, rather than hiding the problem, is far more patient.

The pass is where the two sides meet. Whoever runs it is the link between the floor and the kitchen: calling tables, checking plates, telling servers what is ready and telling cooks what is coming.

A strong pass reduces arguments, because both sides have one person to go to. Servers ask the pass, not the cooks. Cooks tell the pass, not the servers. The person at the pass sees both sides and can explain each to the other.

The pre-shift briefing is the one moment each day when both sides can be in the same place. Five minutes before service, the floor and the kitchen share what they need to know: covers, large tables, specials, shortages, slow dishes and anything to do better than yesterday.

A briefing that includes both sides makes them one team for the evening. Our guide to the pre-shift briefing, in five minutes covers what belongs in it.

Arguments based on impressions are endless; arguments based on numbers can be settled. Share a few numbers with both sides: ticket times at the busiest hour, the number of remakes and their causes, how many dishes ran out and when.

When both sides see the same numbers, the conversation changes from "you are slow" to "the grill's tickets took longest between eight and nine, so what do we change?" Numbers take the blame out of the conversation.

Service standards are often written for the floor alone. Write some for the handover between floor and kitchen too: how orders are sent, how fires are called, how 86s are shared, how remakes are requested, how praise is passed on.

Standards that cover both sides make the expectations clear and fair. Each side knows what it owes the other, and neither has to guess.

Feedback between the two sides often runs one way: the floor passes on complaints to the kitchen. Make it run both ways. The kitchen should be able to tell the floor when tickets arrive incomplete, when fires are late or when a table was promised something the kitchen cannot do.

Give feedback after service, specifically and kindly, and in both directions. A team where each side can tell the other what would help, without it becoming an argument, improves quickly.

One of the simplest ways to build understanding is to let each side spend time on the other's side. A new server spends twenty minutes at the pass during service, watching tickets arrive. A cook spends a few minutes on the floor at the start of service, seeing the room fill.

People who have seen the other side's evening argue less and help more. Many good restaurants make it part of every new starter's first week.

Staff culture between the floor and the kitchen is built in small moments: a chef who thanks a server for a clean order, a server who brings a guest's praise back to the kitchen, a manager who sorts out a problem without blaming either side.

It is also damaged in small moments: a shout, a sneer, a joke at the other side's expense. Managers set the tone. If they treat the two sides as one team, the team follows. Our guide to staff retention: the four reasons people leave covers why culture matters so much.

Managers set the tone. A manager who always takes the floor's side, or always the kitchen's, makes the other side feel unheard and deepens the divide. Stay neutral: listen to both, look at the evidence and decide on the problem, not the people.

Managers who have worked on both sides often find this easier. Those who have not can learn it by spending time at the pass and on the floor during service, seeing each side's pressures for themselves.

One of the oldest ways to bring the two sides together is the staff meal. When the floor and the kitchen sit down together before service, even for fifteen minutes, they talk, laugh and see each other as colleagues rather than opponents.

A staff meal also gives the floor a chance to taste dishes they will sell, and the kitchen a chance to hear how guests describe them. Few things build a single team as cheaply.

Staff culture is shaped by the rota as much as by any meeting. Shifts that start and end at different times for the floor and the kitchen mean the two sides rarely overlap except under pressure. Overlapping start times, so both sides are in the building before service and can share a briefing and a staff meal, help a great deal.

Our guide to staff scheduling against the trading curve covers building a rota around the busy hours.

New starters on the floor and in the kitchen often arrive with the old arguments already learned in previous jobs. Introduce them to the other side on their first day, explain how the two work together here and show them the routines that prevent the usual arguments.

A new cook who has met the servers, and a new server who has stood at the pass, start on the same side.

When an argument does happen, settle it after service, not during. Hear both sides, look at the evidence and agree a change. Resolve it as you would any conflict at work: about the problem, not the people.

Most arguments end with a small change to a routine: a new step in the briefing, a clearer way to send a fire, an earlier warning when a dish is running low. Record the change and check a week later that it worked.

An invented bistro has a long-running feud between the floor and the kitchen. Every busy night ends with complaints on both sides: the kitchen is slow, the floor is careless. Two servers and a chef have left in the past year, each mentioning the atmosphere.

The manager starts a five-minute briefing with both sides before every service, shares ticket times and remakes each week, and asks new servers to spend twenty minutes at the pass in their first week. The floor starts passing on guests' praise to the kitchen. 86s are made on the till the moment a dish runs out.

Within two months, the arguments at the pass are rare. The chef says the orders are cleaner; the servers say the kitchen warns them when it is stretched. Nobody leaves that quarter.

In servearound, the floor and the kitchen work from the same orders: what a server sends is what each station's screen shows, with the guest's allergies at the head of the ticket, held courses marked held and a voided dish struck through. A dish 86'd on the till comes off every guest menu at once and the team is told. Servers can also send the kitchen a compliment from the till, about the whole meal or a dish, in quick words or the guest's own, and it appears on every station's board.

Each venue has a team chat in Messages, where both sides can post and share files, and kitchen analytics show ticket times by station and hour and the remake rate, which gives both sides the same numbers to talk about. See Order Fulfillment.

They see the same service from opposite ends, and each is missing information the other has.

Speed, mistakes on tickets, dishes running out without warning and the timing of courses.

Share information about pacing: spread seating, warn the floor when the kitchen is stretched and set expectations at the table.

Routine information on the tickets, urgent information at the pass, planning in the briefing and feedback after service.

Yes, especially with both sides present. It makes them one team for the evening.

Ticket times at the busiest hour, remakes and their causes, and when dishes ran out.

Yes. A few minutes on the other side's shift builds understanding quickly.

After service, with both sides heard, the evidence on the table and a small change agreed.

Front of house and back of house argue because each sees half the service. The four common arguments, slow food, wrong tickets, dishes running out and course timing, each come from a missing piece of information: pacing, what the kitchen receives, the kitchen's count and how the table is getting on.

Share that information through clear tickets, a strong pass, an 86 that reaches everyone, a briefing with both sides, a few shared numbers and standards that cover the handover. Pass on praise as well as problems, let each side see the other's evening, and settle arguments after service, about the problem rather than the people.