Front of House and Back of House Alignment

Every operator I meet describes the friction between the front of house and the back of house in personality terms. The chef is impossible. The general manager does not understand the kitchen. The servers do not read the specials. The cooks do not know what a VIP table is. I have made every one of those complaints myself at some point in my career, and every time I made it, the truth was more boring and more fixable than I wanted to admit.

Front of house and back of house alignment is not a personality thing. It is a communication cadence problem, and the cadence is designable. The kitchens where I have seen FOH and BOH run as one operation are the kitchens that have installed a specific rhythm of touchpoints across the shift. The kitchens where the two sides are constantly at war are the kitchens where those touchpoints do not exist and the two sides only communicate by shouting at the pass.

Why the two teams pull apart

The FOH and BOH are running two related operations with two different rhythms, two different pressures, two different pay structures, and often two different first languages. The FOH is optimizing for the guest and their tip. The BOH is optimizing for the plate and their ticket time. Neither is wrong. Neither has full visibility into the other. Without a codified communication cadence, that visibility gap turns into blame at the pass.

A specific version: the server drops a table's food twenty minutes after firing because the runner was slow. The guest complains. The server tells the manager the kitchen was slow. The kitchen sees the complaint the next morning and thinks the FOH is throwing them under the bus. Nobody has the full picture. The pass gets colder over the next few services, and by the end of the month the chef and the general manager are barely speaking.

Every one of those chains is preventable with a protocol. The rest of this piece is the protocol.

1. The joint pre-shift

Fifteen minutes before doors, both teams stand together. Not the FOH by themselves. Not the BOH by themselves. Both. The general manager runs it. The chef speaks.

The agenda is short and identical every day:

• Menu changes and specials. The chef describes tonight's specials, the components, the price, the temperature they should be served at, and one line about how to sell them.
• 86s from prep. Everything the kitchen already knows is out or short. Server should stop trying to sell it.
• Allergen alerts already on the books. Any reservation with a noted allergen, called out by table.
• VIP tables and special requests. Celebration tables, regulars, industry guests, media, anything that changes the touch.
• Staffing gaps or coverage adjustments. Anyone out. Anyone doubled. Anyone new on the floor.
• One operational focus for the shift. One thing. Not five. "Table turns are running slow on Fridays. Tonight we watch the 8pm turn."

Fifteen minutes maximum. Standing. If either team is missing, the pre-shift did not happen and service will pay for it inside the first hour. I have watched more service disasters begin at 5:15pm because the pre-shift got skipped for staffing than for any other single cause. The cost of skipping the pre-shift is always higher than the cost of running it.

2. The in-service protocols

Three protocols do most of the work of keeping FOH and BOH aligned during a running service. Every operator should be able to describe all three, and every server and cook should be able to execute them without thinking.

The 86 protocol

When something is 86'd mid-service, the kitchen updates the point-of-sale immediately so it cannot be ordered. The manager on duty announces it verbally to the whole floor. Every server acknowledges by voice or a physical hand-up so the announcement was received. Then a small physical marker (a magnet, a sticker) goes on a shared 86 board in the server station.

Verbal-only 86s that half the floor did not hear are the single most common source of pass-side friction. A server sells the special that was 86'd two hours ago, the guest orders it, the ticket lands at the pass, the kitchen sends it back, the server has to walk back to the table, and the chef and the server are angry at each other for the rest of the shift. All of that is preventable with a real 86 protocol.

The allergen protocol

Allergen alerts go on the ticket in a specific dedicated field, never verbally at the pass. Every allergen ticket gets a physical marker on the ticket rail (a colored clip works). Expo verifies the allergen against the modification before firing the ticket to the station. The plate gets a marked ramekin or plate liner so the runner knows which guest at the table it belongs to.

Verbal-only allergen handoffs cause hospitalizations. This is the one protocol that has zero tolerance for shortcuts. Every kitchen I have run has treated this one as a hard line.

The seconds it takes to put a clip on the ticket and mark the plate are cheap compared to a guest going to the hospital and a restaurant losing a license.

The comp and recovery protocol

Every comp is authorized by the manager on duty, logged in the point-of-sale with a reason code, and communicated to the kitchen the same night. No secret comps. No back-channel recoveries where the server just tells the kitchen "we're going to comp table 12" without logging it.

When the kitchen sees the comp in the log the next morning with a clear reason, the pattern becomes learnable. If the salmon has been comped three times in a week for being overcooked, that is a training issue on the fish station, and the chef can fix it. If comps never get logged, the kitchen feels the servers are covering their mistakes with kitchen food, and the servers feel the kitchen does not care that their table walked away unhappy. The log fixes the loop.

3. The joint post-shift debrief

Ten minutes after the last cover has left the dining room, both teams stand together again. The manager on duty runs the debrief. The chef or sous chef speaks.

The debrief has three points, and only three:

1. One win. One thing the shift did well. Called out specifically, not generically. "The 7:30 push, we did 45 covers in an hour with no send-backs. Both sides."
2. One miss. One thing that went wrong. Not a blame session. A system observation. "Table 22 waited fourteen minutes for entrees. The ticket got stuck on the pass because expo was working two 911s at once."
3. One thing to fix tomorrow. One specific change. "Tomorrow expo has a runner shadow during the 7pm push."

Ten to fifteen minutes maximum. Both teams. Every night. This is where the day's information becomes tomorrow's improvement, and it is where the two teams see themselves as one operation with a shared outcome. Skip the debrief and the day's lesson evaporates by morning.

The chef and general manager weekly meeting

Thirty minutes weekly, off the floor, at a fixed time. Standing agenda: last week's service quality, this week's menu changes, staffing on both sides, one issue each. This is where the two leaders align on the standard before their teams have to.

When the chef and general manager visibly agree on the standard, the teams follow. When they visibly disagree, the teams pick sides and the war begins. The meeting is cheap insurance against a leadership split that the teams will notice inside a week.

The one rule I run in this meeting: no issue goes to the team until the chef and general manager have decided together what the answer is. If the two leaders take an unresolved disagreement to the floor, the floor picks a side, and the disagreement becomes a rift. Resolve at the leadership level. Communicate as one voice to the team.

The tip pool question

The tip pool structure is often the invisible cause of FOH-BOH tension. A traditional structure where servers keep all tips and kitchen cooks earn a wage produces a systemic imbalance that no amount of pre-shift alignment fixes. The server who worked six hours on a Friday goes home with several hundred dollars in tips. The cook who worked twelve hours on the same Friday goes home with an hourly wage that is a fraction of that. Both did the work. Only one gets the reward, and both know it.

Whichever tip pool model the operator chooses (traditional, service-charge model, shared pool where legal), transparency about the split is what keeps the resentment low. Both teams need to see how the pie is cut and why. Operators who avoid the tip conversation because it is uncomfortable end up with a version of the resentment that gets expressed as FOH-BOH friction at the pass, which no protocol will fully fix.

What I would do differently

Two changes I made after learning the hard way.

I would make the post-shift debrief non-negotiable from day one. Early in my career I let the debrief drop when a shift ran long, on the theory that everyone was tired. That theory was wrong. The tired shift is exactly the shift that needs the ten-minute debrief. The debrief resets the team, closes the loop on the day, and keeps small issues from becoming grudges. Skip it once and everyone learns it is optional. Do it every night for a month and the teams start looking forward to it.

I would put the chef and general manager on the same physical office footprint, not opposite sides of the building. Whenever the chef's office was in the kitchen and the general manager's office was near the host stand, the two leaders talked less. When we redesigned unit four to have a shared operations office visible from both the pass and the floor, the two leaders were in each other's ear all day, and the whole team saw them as one leadership unit. Physical layout does more work here than most operators realize.

The point

Front of house and back of house alignment is a cadence problem, not a personality problem. The kitchens that hold alignment are the ones that run a joint pre-shift, codify their 86, allergen, and comp protocols, and end every night with a joint debrief. The chef and general manager meet weekly off the floor. The tip pool is transparent. The leadership pair speaks with one voice to the team.

Do those things and the FOH-BOH war stops being a war and starts being a working operation with two specialties inside one restaurant. The plates come out on time, the tables get greeted right, the comps get logged, and the two teams go home the same night as one team. That is the whole game. Cadence beats personality. Every time.