How to fix front-of-house and kitchen communication in your restaurant

"The lamb is pink, they want well-done"

A server brings a perfectly cooked rack of lamb back to the pass. "Customer says it's pink. They wanted well-done."

The chef sighs. Lamb served well-done is shoe-leather — they know this, every chef knows this. But the customer asked. So the chef cooks it well-done. The plate goes out. The customer eats half of a tough lump of meat, leaves a poor review and a small tip. The server gets a sharper voice from the kitchen at the end of service for not handling it at the table.

Nobody won that exchange. The customer didn't get a good meal. The chef cooked a dish they knew would be poor. The server got blamed for something upstream of them.

And this exact scene — with the lamb, or the steak, or the tuna — plays out in independent UK restaurants every weekend. Not because anyone is bad at their job. Because the information that should have travelled with the order didn't travel.

If you ask most owners "why do front of house and kitchen fight in your restaurant?" the answer comes back in terms of personalities. The chef is intense. The new server is green. The floor manager and the head chef have a thing. Sometimes that's true. Most of the time it isn't — most of the time it's a process problem dressed up as a personality problem, and you can fix the process much more easily than you can fix anyone's personality.

The structural reason they actually fight

Before we get to the fix, it's worth being honest about why the friction is structural and not a personal failing on either side.

Kitchen and FOH come from different worlds. Front of house is more shift-based — students, second-jobbers, gig hospitality, people working it for a year before they move on. The kitchen tends to be the opposite: people who've made it their trade, often the same faces year after year, who care about the food in a way the floor sometimes cannot match. Different ages, different schools, different vocabularies for the same dish. One side is invested in the dish leaving the pass; the other is invested in what happens at the table.

That difference isn't going away. It isn't something to "fix." It's the structural shape of the workforce in independent hospitality. What you can fix is whether the two sides have a clear, written, shared understanding of how they hand information across the pass.

One important caveat: toxic chefs are a separate problem entirely. They exist. The screaming, the throwing, the personal humiliation of servers in front of regulars — that's not a process gap, that's a person who doesn't belong in your kitchen no matter how good their food is. Your job as the owner is to spot them fast and act fast. Don't tolerate it, don't excuse it, don't try to "manage around it." The rest of this article assumes the chef is reasonable. If they're not, fix that first.

The two non-negotiables

If you only put two rules in place between front of house and the kitchen — these two. Everything else is downstream.

Non-negotiable 1: Manage at the point of order, not at the point of return

Back to the lamb. The fix is not at the kitchen end — the chef has already done their job. The fix is upstream: the server should have managed the customer's expectation when they ordered, not when the plate came back. Which requires the server to know that the lamb is served pink as standard, and to volunteer that information at the table:

"Just to flag — our lamb is served pink as standard, that's how the kitchen recommends it. Did you want it that way, or shall I check what else they can do?"

Ten seconds. Order taken with no surprise. The customer either says "yes, pink is fine" — and they get a good meal — or they say "no, I really want it well-done" — and the server can communicate that to the kitchen with the option of recommending another dish. Either way, nobody is cooking a dish they know will be bad.

You'll have a short list of these "problem dishes" — the ones where the kitchen's cooking spec and the customer's intuition disagree. For most UK restaurants the list looks something like this:

• Lamb served pink (medium-rare standard) — well-done not offered, or only with an explicit warning
• Steak rare/blue means a cold-ish middle — flag at the point of order
• Tuna pink in the middle is the dish, not undercooked
• Burgers served pink-in-middle if the menu spec is "medium minimum"
• Pink chicken or pink pork would be a problem — make sure FOH knows which dishes are which
• Anything with a deliberate doneness floor (no "well-done" requests honoured for [specific dish])

The list isn't long. It isn't hard to teach FOH. It is hard if it's never written down — which it usually isn't, because it lives entirely in the head chef's head. Pin an A4 sheet of "problem dishes and the server line" on both sides of the pass. New FOH read it on day one. New chef reads it on day one. The whole category of friction it causes drops to near zero in a week.

Non-negotiable 2: Allergen information is on the ticket, never verbal. Ever.

This one isn't about comfort. It's about safety and the law.

In the middle of a busy Saturday service, FOH leans over the pass: "this table's a nut allergy, please flag it." The kitchen nods, half-hears. The ticket prints with no allergen note. The dish goes out. The customer eats. Maybe nothing happens. Maybe something happens that puts you on the phone with your insurer and the FSA on the same morning.

The rule is simple, and it has no exceptions: if it's not on the ticket, it doesn't exist. If FOH tries to tell the kitchen verbally, the kitchen stops service for ten seconds and asks them to re-input the order with the allergen tag. No exceptions for "the customer just told me." No exceptions for "we're slammed." No exceptions for the regular table where you "already know" what they always order — especially not that, because assumed knowledge is exactly where serious incidents happen.

The 14 UK regulated allergens are non-negotiable by law. Every one of them should appear on the kitchen ticket the moment the order is taken — not because the server remembered to mention it. If your tooling doesn't auto-tag allergens onto tickets from the menu and recipe, that's a gap worth closing. (This is one of the specific reasons we built Blueroll the way we did — the allergen is in the recipe, so it's on the menu PDF, on the kitchen ticket, and on the server's screen at the table. The information can't get dropped because the system carries it forward.)

This rule applies equally to the chef on their first day and the chef who's been with you ten years. The day a long-serving chef takes a verbal allergen handover "because we know each other" is the day the system breaks. Make the rule absolute, including for yourself.

The information-flow audit

If sparks are flying between front and back this month, before you blame anyone, audit the flow. Ask both sides the same three questions, separately, and listen to the gap between the answers.

1. What is each station's task during prep and during service? If the answers don't match between the chef and the floor manager, that's the first gap. The kitchen thinks FOH does X, FOH thinks the kitchen does X, neither does, the customer notices.
2. Who owns what decision when something goes wrong? A dish 86's mid-service — who tells FOH, how fast, what do they tell the table? A customer wants a modification — who decides yes/no, the server or the chef? A regular asks for something off-menu — who handles it? If both sides have a different answer, you have a chain-of-command gap.
3. What are the interdependencies? When FOH is slow, the kitchen suffers (cold plates on the pass waiting to be run). When the kitchen is slow, FOH suffers (tables waiting too long, tips dropping). If either side thinks they're independent of the other, the relationship is going to break.

Most of the answers should be obvious. The ones that aren't — write down. That's your gap list. Fix one a week, and within a month most of the daily friction has dropped.

The patterns that quietly destroy the relationship

Beyond the two non-negotiables, there are five patterns that wear down FOH-kitchen trust over weeks and months. None are dramatic. All are common. All are fixable once you can see them.

1. The owner damage-controls the customer but never the chef

A plate goes wrong. The owner steps in, charms the customer, comps the dessert. Excellent service recovery — and a complete miss on the second half. The chef never hears what actually went wrong. Was it a kitchen mistake? A FOH order mistake? An impossible request the server should have declined? If you only ever talk to the customer side of these incidents, the kitchen ends up assuming every comp is on them, and the resentment builds quietly.

The fix is symmetric: every comp, every returned plate, every customer complaint gets a 60-second post-mortem in the end-of-service debrief. Not blame — diagnosis. Where did the information drop?

2. Kitchen makes a face, FOH stops asking

A server has a legitimate question about an allergen. They walk to the pass. The chef sighs, rolls their eyes, mumbles an answer. The server feels stupid. The next time they have an allergen question, they guess instead of asking. That guess is now in the dish.

This pattern is invisible until something goes wrong. The chef thinks "they stopped bothering me, good"; in reality, they stopped asking questions they should have been asking. Train the chef explicitly: any allergen question is a question I want to be interrupted for, every time, no signal that it was unwelcome.

3. FOH dumps a 6-top mid-rush without warning

The reverse mistake. A table of six walks in, FOH sits them straight away and orders comes in 15 minutes later as one giant ticket while the kitchen is already on the back foot. The kitchen blows up, plates go out late, the service stretches. Could have been mitigated with a 10-second heads-up: "six just walked in, ordering in 10."

The fix is a single signal both sides agree on. A whiteboard tally next to the pass. A printed flag on the ticket rail. Anything that gives the kitchen 10 minutes of warning to brace.

4. The owner takes sides

An incident happens, the owner publicly sides with one side ("the chef is right, the server messed up" in front of the team). The other side feels the verdict before they've made their case. By next week, the team has split into "the chef's people" and "the floor's people" — and the next incident will be argued from those camps before anyone looks at what actually happened.

The fix is private. Investigate the incident with each side separately. Decide privately. Communicate the resolution to both sides factually, never publicly assigning blame in front of the team unless you've already had the private conversation. The team copies the owner's tone: if you're judgemental, they'll be judgemental.

5. The tip pool fight

Independent restaurants in the UK have many tip-distribution models, all of them imperfect. Whichever you've picked, the moment one side feels the split is unfair the friction shows up everywhere else — slow ticket times, ignored requests, passive-aggressive comments at the pass. It's not actually about the lamb in those weeks; it's about the £40 someone feels was taken from them.

The fix isn't to find the perfect tipping model — there isn't one. The fix is to be explicit about how the model works, why you chose it, and to revisit it openly at least once a year so it doesn't become the silent grievance underneath every other dispute.

The 5-point day-one briefing sheet

The single most useful artefact to put between FOH and the kitchen: a one-page A4 sheet, pinned on both sides of the pass, that new chefs and new servers read on their first day. Both sides have the same reference. Both sides know the other side has the same reference. The handshake is explicit.

What goes on the sheet:

1. The "problem dishes" list — every dish where kitchen spec and customer intuition disagree, plus the standard server line for each ("the lamb is served pink — that's the kitchen's recommendation — would you like that or shall I check what else they can do?")
2. The allergen-on-ticket rule — written, in bold, no exceptions, including for regulars and including for verbal mentions in the middle of service. If allergen isn't on the ticket, the dish doesn't go out.
3. The 86 protocol — when a dish runs out: who tells FOH, how fast (within 60 seconds of the kitchen knowing), and what the standard server line is for the table ("just to flag — the lamb has just sold out tonight, here's what we'd suggest in its place")
4. Service-pace signals — how the kitchen tells FOH "we're 10 minutes behind on mains" without anyone yelling. A whiteboard tally, a flag on the ticket rail, a chalk number on the pass — pick one, use it consistently.
5. The "let me check with the chef" template — when a customer asks for a modification the kitchen will probably refuse, FOH defers rather than over-promising. Better to say "let me check" and come back with no than to say yes and have the kitchen blow up.

Print one sheet. Pin one in the kitchen, one at the FOH station. New starter on either side reads it on day one and acknowledges it explicitly: "I've read the briefing sheet — any questions?" Two minutes. Prevents months of friction.

When the owner steps in — and when they stay out

Most FOH-kitchen incidents shouldn't involve the owner at all. The end-of-service debrief is where they get worked out, by the people involved, with the owner present as a witness rather than a referee.

Step in immediately if any of these:

• Shouting at a team member in front of others, by either side
• Allergen-rule violations (no exceptions on this one)
• A walkout threat — kitchen or floor
• The same friction with the same people for the third time in a week

Stay out of these:

• A single returned plate that both sides understand the cause of
• A one-off bad shift where both sides know it was a bad shift
• Ego clashes between people who'll work them out themselves
• Anything that gets resolved at the end-of-service debrief without your intervention

The owner's actual job in chronic friction isn't to take sides on individual incidents. It's to fix the system that produced the friction. Was the recipe documented? Was the allergen on the ticket? Did FOH know the spec? Did the kitchen signal the 86? Almost every recurring incident has a system gap underneath. Refereeing the same incident more than twice means the system is broken, not the people.

What good actually looks like at six months

If you put the two non-negotiables in place, drill the briefing sheet on every new hire, and audit the information flow once a month, here's what the kitchen and floor look like by month six:

• The pass is quiet. Few raised voices. Almost no verbal allergen handovers.
• Tickets print with allergens auto-tagged. The kitchen never has to ask "is anyone on this table allergic?"
• FOH knows the problem-dish list cold and uses the server lines without thinking.
• When a dish 86's, FOH knows within 60 seconds and stops selling it.
• The end-of-service debrief is 10 minutes about specific incidents, not personalities.
• A new chef or a new server walks into a team that already has shared reference points, so they can integrate in 14 days instead of 6 weeks. (For the chef side specifically, see how to onboard a new chef in 14 days.)
• Regulars notice none of this directly. They just notice that the service is smooth and the food is consistent.

That's it. That's the whole thing. None of it is dramatic. None of it is hard once it's written down. Almost all of it is broken in independent restaurants because nobody ever sat down on a quiet Tuesday and decided to make it explicit.

Free download: the FOH ↔ Kitchen Briefing Sheet

A one-page A4 sheet you can pin on both sides of the pass and hand to every new hire on day one. The 5 sections from this article — problem dishes, allergen rule, 86 protocol, service-pace signal, "let me check" template — laid out as a working reference, with blanks to fill in your own kitchen's specifics.

What to do this week

1. Write the "problem dishes" list for your menu. Eight to twelve items max, with the server line for each.
2. Tell every server and every chef: from today, allergen information is only on the ticket. No verbal exceptions. Including for regulars.
3. Pin one A4 briefing sheet (the 5 points above, customised) on both sides of the pass.
4. At Sunday's debrief, ask the kitchen and the floor each: "what was the friction this week, and what was the system gap underneath it?"
5. Look at your allergen flow. If a server can take an order without the allergen automatically arriving on the ticket, that's the first thing to fix structurally.

If you want a tool that handles the recipe documentation, allergen tagging, and ticket-side allergen flagging that this whole article depends on — try Blueroll free for 14 days. The FOH-kitchen handshake is one of the specific reasons we built it the way we did.

Related guides

• How to onboard a new chef in 14 days, not 6 weeks
• First-week onboarding checklist for new restaurant staff
• The 14 EU allergens — complete UK guide
• How to launch a new menu in 15 minutes (not 15 hours)
• Why your regulars visit less — the 80/20 menu refresh framework