--- layout: default_v3 language: default permalink: i18n_link: 9701 updated: 2025-12-12 #--- article key-values ---# collection: default_articles category: restaurant-management tags: Team communication type: article page_id: 9701 hreflang_id: 9701 date_published: 2025-12-11 date_modified: 2025-12-12 #--- javascript schema ---# javascript_schema: - script: jquery_3_2_0_min - script: bootstrap_min - script: article_infinite_scroll - script: article_mix_infinitescroll - script: article_mix - script: article_mix_faq - script: article_mix_toc #--- section schema ---# section_schema: - section: nav-main_menu - section: nav_submenu_iconview_v2 - section: article_body_v2 - section: footer - section: footer-sticky_cta_bar - section: schedule_demo_cta #--- page key-values ---# meta_tags: t_meta_title: How to Improve Team Communication Between FOH and BOH t_meta_description: Strong FOH-BOH team communication reduces mistakes, speeds service, lowers costs, and turns daily restaurant chaos into smoother, consistently predictable shifts. t_meta_abstract: Strong FOH-BOH team communication reduces mistakes, speeds service, lowers costs, and turns daily restaurant chaos into smoother, consistently predictable shifts. i_meta_image: og_how-to-improve-team-communication-between-foh-and-boh.png article_body: json-ld_article: v_date_published: 2025-12-11 v_date_modified: 2025-12-12 author: p_author_id: 254 t_author: Derrick McMahon p_author_url: derrick-mcmahon.html i_author: 254.jpg t_author_description: Derrick McMahon is a writer and restaurant technology enthusiast. He holds a Bachelor's degree in Hospitality Management from UNLV, where he developed a passion for the food service industry. p_author_facebook: //www.facebook.com/altametrics/ p_author_twitter: https://twitter.com/https://twitter.com/altametrics?lang=en p_author_linkedin: p_author_instagram: podcast_section: v_links: podcast_links: - t_title: Iheart Radio v_url: i_icon: iheart_radio_icon.png - t_title: Amazon Music v_url: i_icon: amazon_music_icon.png - t_title: Youtube Music v_url: i_icon: youtube_music_icon.png - t_title: Spotify v_url: i_icon: spotify_icon.png feature_snippet: p_type: text t_title: Which software tools keeps FOH and BOH aligned? t_description: POS and KDS are key - use structured modifiers and clear allergy flags, and let expo screens manage timing and fire order. Messaging, manager log, and scheduling tools can share shift notes, 86 lists, and daily priorities so everyone sees the same information. content: heading: t_title: How to Improve Team Communication Between FOH and BOH t_description: Strong FOH-BOH team communication reduces mistakes, speeds service, lowers costs, and turns daily restaurant chaos into smoother, consistently predictable shifts. image: i_image: team-communication-1765470300-3121.png t_image_description: v_image_attribution: v_image_license: v_video: paragraphs: - t_headline: How Miscommunication Shows Up t_text: Busy services don't usually fall apart because people stop caring. They fall apart because FOH and BOH stop hearing each other clearly.

Servers are trying to keep guests happy, quote realistic times, and handle last-minute changes. The kitchen is trying to push food out in the right order, manage ticket volume, and protect quality. When communication between those two worlds breaks down, you see it immediately - wrong plates at the table, long waits, confused guests, stressed staff, and finger-pointing on both sides.

For an owner, this isn't just a "people problem." It shows up in hard numbers - comps, refunds, overtime, wasted product, and turnover. The good news is that you don't need a bigger staff or a brand-new concept to fix it. You need clear standards, simple routines, and better use of the tools you already have.

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: - t_headline: Map the Gaps t_text: Before you can fix FOH-BOH communication, you need to see clearly where it's failing right now. Most owners already feel the pain in a general way - "the kitchen and servers are always fighting" - but it helps to get specific.

Start with the most common problem areas -

1. Order entry - Are servers skipping modifiers, forgetting seat numbers, or typing free-form notes instead of using proper buttons?
2. Allergies and special requests - Does the kitchen get clear, obvious alerts for "no dairy," "no nuts," or "gluten-free," or do those details get buried in tiny text?
3. Quote times - Does FOH know how backed up the line is, or are they guessing and over-promising to guests?
4. 86'd items and menu changes - How quickly does BOH tell FOH when something is out, and how quickly does that message reach every server?

Next, look at your patterns instead of just one bad night. Pull a week or month of basic data -

- How many voids and comps were due to kitchen mistakes vs. order-entry mistakes?
- How many remakes happened because the ticket wasn't clear?
- When were your ticket times longest, and what was happening then?

Talk to your team as well. Ask line cooks, expos, and servers where they feel "left in the dark." You'll probably hear the same issues repeated - unclear tickets, late communication on 86s, confusion about table priorities, or sudden menu changes that never reached the floor.

When you combine data (voids, comps, ticket times, remakes) with real feedback from staff, the picture becomes clear. You're no longer dealing with a vague "communication problem." You can point to specific gaps - and that's what you'll fix in the next steps.

p_headline_type: h2 image: i_image: map-the-gaps-1765479118-3475.png t_description: restaurant BOH v_attribution: restaurant BOH v_license: WER4984 callout_text: call_to_action: p_type: purchase t_title: Cut Down Prep Time and Boost Accuracy t_text: Automate Your Kitchen with Altametrics! t_button_text: Schedule a Demo p_button_url: https://altametrics.com/schedule-demo.html p_button_color: ff0000 v_form_id: v_product: altametrics background: type: color i_image: p_video: p_color: 0000FF - t_headline: Set Clear Standards t_text: Once you see where communication breaks down, the next step is to remove guesswork. Most FOH-BOH conflicts come from people doing things "their way" instead of "our way." Your job as the owner is to turn that into one clear playbook everyone follows.

Start with non-negotiables. These are the simple rules that protect speed and accuracy -

- How every order must be entered in the POS (no handwritten tickets, no "misc" buttons unless approved)
- How allergies and serious dietary needs are flagged
- How specials, 86'd items, and substitutions are handled

Write these down in plain language. For example - "All allergy orders must use the allergy button and a short note in the POS" is much clearer than make sure allergies are obvious. When expectations are written, it's easier to train, coach, and hold people accountable.

Next, agree on standard phrases for key moments. Under pressure, people tend to snap or get vague. Simple scripts help -

- "I'm 10 minutes behind on grill; please quote 25 minutes on well-done steaks."
- "We're 86 on salmon after this ticket - please stop selling it and offer chicken or shrimp instead."
- "This is a severe nut allergy - can you confirm you saw it?"

These phrases might seem small, but they reduce emotion and make it clear what action is needed.

Finally, create a simple Service Flow checklist both FOH and BOH accept. It can be one page that covers -

1. Pre-shift - who checks 86s, specials, and station readiness
2. During shift - how quote times are updated and communicated
3. Post-shift - who notes recurring issues for tomorrow

When everyone works from the same playbook, arguments drop, ticket quality improves, and new hires ramp up faster. Clear standards turn "They should know better" into "We all agreed to this - and it's written down."

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: - t_headline: Use Pre-Shift Huddles to Align the Team t_text: A lot of FOH-BOH drama starts before the first ticket is even fired. People show up, clock in, and jump straight into the rush without a shared plan. A short pre-shift huddle can fix that. It doesn't need to be long or formal - 5 to 10 minutes is enough if you stay focused.

The key is to bring both FOH and BOH (or at least a lead from each) into the same quick conversation. Pick a consistent time- for example, 15 minutes before lunch and dinner service. Make it a normal part of the shift, not something you only do when things go wrong.

Cover the basics every time -

1. Expected volume - reservations, large parties, events, or weather that might impact traffic
2. Menu notes - 86'd items, limited quantities, specials, or items that are slower than usual
3. Staffing gaps - if you're short a cook or server, explain how that will affect pacing and quote times
4. Promo or discount changes - anything that might change what guests are ordering

The goal is for everyone to leave the huddle with the same picture of the night ahead. That way, servers don't oversell an item you're almost out of, and the kitchen isn't surprised by a big group at 7.00.

Have one person - usually a manager or lead - write down key points on a small board, in a shift log, or in your software (scheduling app, manager log tool). That way, people who arrive a little late can still see what was discussed.

Keep the tone calm and practical. The huddle isn't a place to vent; it's a place to plan. When you run these consistently, you'll notice fewer surprises, fewer heated conversations on the line, and smoother transitions when the rush hits. Over time, your team starts to think ahead together instead of just reacting in the moment.

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: - t_headline: Leverage Software Tools t_text: You're probably already paying for tools that could dramatically improve FOH-BOH communication - you just may not be using them to their full potential.

Start with your POS. Make sure servers are using proper buttons, modifiers, and allergy flags instead of typing long free-text notes. Create a short POS standard -

- All allergies must use the dedicated allergy button
- "On side," "no salt," "extra spicy," etc. Must use modifiers
- Avoid vague notes like "make it good" or "they're in a hurry"

Clear, structured tickets are easier for cooks to read at speed and reduce remakes.

If you use a kitchen display system (KDS) or expo screen, treat it as the control center for the line. Ensure -

- Tickets are grouped logically (by course, by table, or by time)
- Rush or VIP tickets are clearly marked
- BOH has a simple way to pause or throttle incoming orders when the line is backed up

Next, look at team messaging and manager log tools. Instead of relying on random group texts, use one system for -

- Daily notes about 86'd items, specials, and prep levels
- Shift recaps. what broke tonight and what to fix tomorrow
- Quick FOHBOH updates during the day without shouting across the kitchen

Finally, use your scheduling or timekeeping software to attach shift notes so every server and cook sees the same expectations before they arrive. A few lines like "Short on grill tonight - quote well-done steaks at 25 minutes" can prevent a lot of tension later.

If you want a single platform that ties scheduling, timekeeping, and communication together so FOH and BOH stay aligned, explore how Altametrics can support your restaurant's daily operations by clicking "Book a Demo" below.

p_headline_type: h2 image: i_image: leverage-software-tools-1765479118-2425.png t_description: software tools v_attribution: software tools v_license: EWRT47984 callout_text: call_to_action: p_type: purchase t_title: Maximize Your Time and Minimize Labor Costs t_text: Simplify Prep with Altametrics! t_button_text: Request a Demo p_button_url: https://altametrics.com/schedule-demo.html p_button_color: FF0000 v_form_id: v_product: altametrics background: type: color i_image: p_video: p_color: 008000 - t_headline: Train for Communication Skills t_text: Most restaurants train people on what to do - how to ring orders, plate dishes, or close the line - but rarely on how to talk to each other when things get busy. The result- smart people with good intentions who still clash during every rush.

Start by making communication a formal part of training, not something you hope people "figure out." When onboarding a new server, don't just show them the menu and POS. Show them -

- How to approach the line or expo without interrupting
- How to ask for a quick favor ("Can you prioritize Table 12's burger?")
- How to double-check allergy tickets with calm, clear language

Do the same for BOH. New cooks should learn not just recipes and station setup, but also -

- How to tell FOH when they're in the weeds
- How to ask for clarification on a confusing ticket
- How to push back on unrealistic quote times without starting an argument

Short role-play exercises can help. Take 10 minutes before or after a shift and run through common scenarios -

- The kitchen is 15 minutes behind on grill
- A guest suddenly shares a severe allergy
- A large party walks in right as the line is slammed

Have staff practice specific phrases that keep the focus on solutions, not blame. For example - "I'm 10 minutes behind on these tickets - please quote 25 minutes on all new well-done steaks" is far more useful than "I'm drowning back here."

Reinforce these habits in daily life. When you see someone handle a tense moment well, call it out - "That's exactly how we talk to each other here." Over time, your team learns that communication is not an extra - it's part of being great at their job.

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: - t_headline: Create Feedback Loops After Each Shift t_text: Even with good tools and training, FOH-BOH communication will never be perfect. The key is not to chase perfection in one night, but to get a little better after every shift. That's where simple feedback loops come in.

Start with a quick debrief after your busiest services - this can be 5-10 minutes with a manager, a FOH lead, and a BOH lead. You don't need a big meeting. Just ask three questions -

- What went well tonight?
- Where did communication break down?
- What's one change we can try tomorrow?

Keep it focused on specific moments, not personal attacks. Instead of "Servers never listen," look for concrete issues like "86s weren't written anywhere - only shouted," or "Expo didn't update quote times when the grill backed up." The more specific the feedback, the easier it is to fix.

Capture the main points in a shift log or digital manager report. Note things like -

- 86 salmon by 7.15 - need better prep levels on Fridays."
- Ticket times spiked when third-party orders hit - consider a limit or separate station.
- Allergy communication improved when servers used the POS allergy button every time.

This becomes your running list of small adjustments. At your next pre-shift huddle, bring up one or two of these items and explain what you're changing. That way, your team can see that their feedback leads to real action, not just talk.

Encourage staff to share ideas, not just complaints. Line cooks might suggest a better way to format tickets; servers might propose clearer wording for specials. When people see their suggestions put into practice, they feel more ownership over communication and the guest experience.

Over time, these small daily loops - observe, discuss, adjust - turn communication into something you actively manage, not just something you react to when things go wrong.

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: - t_headline: Make Good Communication Part of Your Culture and Metrics t_text: If you want FOH-BOH communication to last, it can't just depend on who is working that night. It needs to be part of how your restaurant runs every day - built into your culture, your training, and even your numbers.

Start by setting the expectation clearly - in this restaurant, we speak to each other with respect, share information early, and fix problems together. Say it in interviews, repeat it in orientation, and reinforce it in pre-shift huddles. New hires should understand that communication is not optional; it's part of the job.

Next, reward the behaviors you want. When a server calmly double-checks an allergy ticket instead of rushing, or when a line cook gives clear, early updates about long ticket times, call it out. A simple "Thanks for looping everyone in - that really helped the shift" from an owner or manager goes a long way. You can also -

- Mention good communication in shift notes
- Include it as a line item in performance reviews
- Use small rewards (preferred sections, early cut, small gift cards) to reinforce the habit

Then, connect communication to hard metrics. Track things like -

- Average ticket times during peak hours
- Number of remakes due to unclear tickets
- Voids and comps linked to miscommunication
- Guest complaints related to speed or wrong orders

When those numbers improve, point it back to better communication, not just "luck" or "a good night." This helps your team see the real impact of their effort.

Finally, keep communication changes alive over time. Review your playbook and scripts every few months. As your menu, volume, or staffing changes, your communication routines may need to adjust as well. Involve both FOH and BOH in these updates so they feel ownership, not surprise.

When communication becomes part of how you hire, train, measure, and reward, it stops being a project and becomes "just how we do things here." That's when FOH and BOH start acting like one team - and your guests feel the difference.

p_headline_type: h2 image: i_image: t_description: v_attribution: v_license: callout_text: call_to_action: p_type: purchase t_title: Simplify Multi-Channel Ordering t_text: Get Started with Altametrics to Streamline your POS! t_button_text: Book a Demo p_button_url: https://altametrics.com/schedule-demo.html p_button_color: ff0000 v_form_id: v_product: altametrics background: type: color i_image: p_video: p_color: 0000FF event_body: json-ld_event: t_name: Employee Scheduling for Restaurant Managers t_description: Attendees will learn how create excellent schedules. The class teaches managers how to estimate the number of employees they need to staff their locations; how to accurately forecast their customer demand; how to quickly and accuaratly write and communicate schedules to employees; and how to evaluate the accuracy and optimization of their schedules to make adjustments. v_start_date: 2022-08-08 i_image: p_location_name: Altametrics Online Webinar Course p_address: webinar.altametrics.com?site=altametrics v_price: 10.00 t_offer_description: Priority Registration v_registration_url: webinar.altametrics.com?site=altametrics faq: t_faq_title: Frequently Asked Questions faq_ask: - t_question: How can I use my POS data to improve FOH-BOH communication? t_answer: Review reports on voids, comps, remakes, and ticket times. Look for patterns by day-part, menu item, or station. Use those findings in your huddles and training - "We had six remakes on burgers Saturday; let's check how we're entering modifiers and timing the grill."

- t_question: What should I look for in a kitchen display system (KDS)? t_answer: Look for a KDS that shows ticket timing, course order, and priority flags clearly. It should allow expo or BOH leads to bump, hold, or rush tickets quickly, and ideally show how long each ticket has been open so FOH can give honest quote times.

- t_question: Can scheduling software improve FOH and BOH communication? t_answer: Scheduling tools can do more than just shifts. Many platforms let you add shift notes, send messages, and share updates with the entire team. You can include information about expected volume, menu changes, and staffing gaps so FOH and BOH walk in already informed.

- t_question: How can I tell if my FOHBOH communication is broken? t_answer: Look for patterns- frequent remakes, repeated guest complaints about wrong or late food, tension between servers and cooks, and ticket times that spike during rushes. Pull basic data on voids, comps, and remakes, and ask your team where they feel "left in the dark."

---