Staffing, Hiring and Training

Fixing Front-of-House and Kitchen Friction

Why servers and cooks clash and how to fix it: shared pre-shifts, clear ticket rules, a strong expo, a fair refire process and cross-shadow shifts.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Where the friction comes from
  2. Common causes and their fixes
  3. Write ticket rules both sides agree to
  4. Make expo the single voice at the pass
  5. A fair refire process
  6. Shared pre-shift and cross-shadow shifts
  7. Recognition, tips and fairness
  8. Scripts for the pass
  9. Example: a month to calm the pass
  10. What managers model
  11. Frequently asked questions
  12. References
Staffing, Hiring and Training: Fixing Front-of-House and Kitchen FrictionArticle coverSTAFFING, HIRING AND TRAININGFixing Front-of-Houseand Kitchen FrictionAva for RestaurantsInsightsStaffing, Hiring and Training: Fixing Front-of-House and Kitchen FrictionArticle coverSTAFFING, HIRING AND TRAININGFixing Front-of-Houseand Kitchen FrictionAva for Restaurants

Key takeaways

  • Most FOH and BOH conflict comes from unclear rules at the pass, not from bad people.
  • Write ticket rules for modifiers, allergies, fire times and refires, and enforce them on both sides.
  • Make expo the single voice at the pass during service, and hold one shared pre-shift.
  • Address the pay gap openly: recognize kitchen work, and check whether your tip policy can legally include cooks.

Where the friction comes from

Every restaurant has some tension between the dining room and the kitchen. Servers face guests who want changes, speed and explanations. Cooks face a rail full of tickets, a hot line and modifications they did not plan for. When something goes wrong, each side sees the other's mistake first. The server sees a late plate; the cook sees an order rung in wrong. Left alone, those moments harden into 'us and them'.

Pay differences add to it. The National Restaurant Association's tipped employee research puts the median hourly earnings of full-service waitstaff at $27.00 including tips[1]. By comparison, the median wage of restaurant cooks was $17.98 an hour in May 2025 and of dishwashers $16.73[2][3]. Kitchen staff often know that a server can out-earn them on a busy Saturday, while working the same hours in harder conditions. Ignoring that does not make it go away.

Median hourly pay: servers with tips vs kitchen rolesWaitstaff including tips (NRA, 2022); cooks and dishwashers before tips (BLS, May 2025)
Median hourly pay: servers with tips vs kitchen rolesColumn chart. Full-service waitstaff, incl. tips: $27; Restaurant cooks: $17.98; Dishwashers: $16.73.$0$10$20$30Full-service waitstaff, incl. tips: $27$27Full-service waitstaff, incl.tipsRestaurant cooks: $17.98$17.98Restaurant cooksDishwashers: $16.73$16.73DishwashersMedian hourly pay: servers with tips vs kitchen rolesColumn chart. Full-service waitstaff, incl. tips: $27; Restaurant cooks: $17.98; Dishwashers: $16.73.Full-service waitstaff, incl. tipsFull-service waitstaff, incl. tips: $27$27Restaurant cooksRestaurant cooks: $17.98$17.98DishwashersDishwashers: $16.73$16.73

Source: US Bureau of Labor Statistics, 2025[2]

Show the data
ItemValue
Full-service waitstaff, incl. tips$27
Restaurant cooks$17.98
Dishwashers$16.73

Common causes and their fixes

Common causes of front-of-house and kitchen friction
CauseWhat it looks likeFix
Unclear modifiersFree-text notes the kitchen cannot read, verbal changes at the passStandard modifier buttons, no verbal-only changes
Allergy confusionCooks unsure whether a note is a preference or an allergySeparate allergy flag on the ticket and a manager check
Bunched ticketsServers hold orders and fire several tables at onceRing orders as taken; course firing for pacing
Slow pickupPlates die in the window while servers are busyRunners at peak, a rule that anyone free runs food
Refire blameArguments about who caused a remakeFix first, discuss after service, log the cause
Separate informationKitchen hears about a large party at 7 p.m.Shared pre-shift with the book and pacing plan
Unequal recognitionOnly servers get thanked, tipped and celebratedPublic kitchen recognition and a fair tip policy

Notice that almost every fix is a rule or a routine, not a personality change. That is good news. It means a manager can fix most of this in a few weeks without replacing anyone.

Write ticket rules both sides agree to

Agree the rules in a short meeting with the chef, a senior server and the manager, then post them at the pass and in the server manual. The aim is that a ticket means the same thing to everyone.

  1. Every change goes on the ticket through the POS. No verbal-only modifications at the pass.
  2. Use the standard modifier buttons; free text only when no button exists, in plain words.
  3. Allergies use the allergy flag, never a general note, and a manager confirms with the kitchen.
  4. Ring orders as soon as they are taken. Do not hold tickets to fire tables together.
  5. Use course firing or a 'hold' note for pacing, not a delay in ringing.
  6. Rush or VIP tickets are approved by the manager, not declared by the server.
  7. Ask expo, not the line, about ticket status during service.
  8. Refires are rung as refires with a reason code, so the kitchen can track causes.

Make expo the single voice at the pass

Most shouting at the pass happens when several people try to run it. Name one expediter for every service, ideally a sous chef or experienced cook on busy nights and a trained manager on quieter ones. Expo calls tickets, checks plates against the ticket, calls for runners and answers servers' questions about timing. Cooks talk to expo; servers talk to expo. Nobody else directs the line.

  • Expo checks every plate for the correct modifier and allergy handling before it leaves.
  • Expo calls 'hands' for food pickup, and any free server, manager or runner responds.
  • Expo tells servers early when a ticket will be late, so they can warn the table.
  • Expo logs refires and their causes on a simple sheet for the post-service review.

A fair refire process

  1. Fix first

    The server tells expo what is wrong, expo calls the refire with priority, and the guest gets the corrected dish as fast as possible. No debate during service.

  2. Log the cause

    Expo records the refire with a reason: ordered wrong, cooked wrong, plated wrong, guest changed mind or allergy issue.

  3. Review after service

    The manager and chef look at the log for five minutes after close, without blaming individuals in front of others.

  4. Fix the pattern

    If one dish is often cooked wrong, retrain the station. If one modifier is often rung wrong, fix the POS button or retrain servers.

Track refire causes for a month before you decide where the problem lies. The data almost always shows a mix of front and back of house causes, which takes the heat out of the argument.

Shared pre-shift and cross-shadow shifts

Hold one pre-shift with both teams at the pass. The chef presents specials and 86s; the host presents the book and large parties; the manager agrees pacing for big tables. When both sides hear the same plan, fewer surprises reach the window. Rotate who speaks so it is not always the front of house delivering news to the kitchen.

Cross-shadowing builds empathy faster than any speech. Ask each new server to spend part of a shift beside expo or on a simple station, and each new cook to spend an hour following a server on a busy night. Servers learn why a well-done steak takes longer and why a late modification wrecks a station's timing; cooks see what a table of eight asking for changes looks like from the floor.

Recognition, tips and fairness

Thank the kitchen in front of the dining room team, by name and for specific things: the cook who handled a ten-top with three allergies, the dishwasher who kept up through a double turn. Share guest compliments about food with the kitchen the same night. Include cooks in incentives when the item being sold depends on their work.

Tip policy is a sensitive and legal question. Federal law bars employers, managers and supervisors from keeping any portion of employees' tips[4]. Whether cooks and dishwashers can share in a tip pool depends on whether you take a tip credit and on your state's rules, so check with the Department of Labor guidance and your adviser before changing anything. Some restaurants instead use a kitchen appreciation fee or a revenue-based kitchen bonus, which must be disclosed clearly and handled correctly as wages.

Scripts for the pass

Tension spikes in the moments when someone has to ask for something under pressure. Giving both sides a few agreed phrases removes the tone that turns a question into an argument.

  • Server to expo, checking timing: 'Table 22 is asking about their mains. What time should I give them?'
  • Expo to server, warning of a delay: 'Twenty-two is five minutes out; the lamb needs to rest. Can you let them know and top up their wine?'
  • Server reporting a problem: 'Seat two on table 9 says the steak is under. They ordered medium. Refire please.'
  • Cook asking about a modifier: 'Expo, ticket 41 says no sauce. Is that an allergy or a preference?'
  • Manager closing an argument: 'Let us fix the plate now and talk about it after service.'

Practice these at pre-shift during the first weeks, especially with new hires on both sides. They sound simple, but they set an expectation that everyone at the pass speaks to each other as colleagues working on the same guest.

Example: a month to calm the pass

Example (fictional): at a 130-seat gastropub, servers and cooks argue nightly at the pass, and two cooks have quit in two months. The GM and chef agree eight ticket rules, name a sous chef as expo on Thursday to Saturday, and start a refire log. In the first week the log shows 22 refires: nine rung wrong, eight cooked wrong, three plated wrong and two allergy clarifications.

The GM fixes two confusing POS modifier buttons and retrains servers on them, while the chef retrains the grill on temperatures. Every new server now spends an hour beside expo. By week four the log shows nine refires, and the shouting has mostly stopped because questions go to expo. At the next team meeting the GM shares the numbers, thanks both sides and asks what to fix next.

What managers model

Teams copy their managers. A manager who blames the kitchen in front of a guest, or a chef who mocks servers at the pass, undoes every rule on the wall. Agree as a management team never to criticize the other side publicly, and to settle disagreements after service. For more on building a shared culture, see our guides to restaurant burnout and building a culture staff want.

Frequently asked questions

Why do servers and cooks clash?

Usually because of unclear ticket rules, late modifications, bunched orders, slow food pickup and arguments over refires, made worse by pay differences and separate information.

How do you reduce FOH and BOH conflict?

Write ticket rules both sides agree to, make expo the single voice at the pass, hold a shared pre-shift, log refire causes and recognize kitchen work publicly.

Can kitchen staff share in the tip pool?

It depends on whether you take a tip credit and on state law. Managers and supervisors may not keep any portion of employees' tips. Check with your adviser before changing tip policy.

What does an expediter do?

The expediter runs the pass: calls tickets, checks plates against tickets, calls for runners and answers servers' timing questions, so the line hears one voice.

References

  1. National Restaurant Association (2022). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑

  2. US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025: Restaurant cooks median hourly wage (opens in a new tab) ↑

  3. US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025: Dishwashers median hourly wage (opens in a new tab) ↑

  4. Legal Information Institute (Cornell Law School), US Code (2026). 29 U.S. Code § 203 - Definitions (Fair Labor Standards Act) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo