FoH vs BoH — The Restaurant Front + Back of House Operator Guide (2026)

What is FoH (front of house)?

FoH means front of house — the guest-facing half of the restaurant. If a guest can see it, sit at it, order from it, or speak to it, the foh restaurant meaning covers it. That includes the host stand, dining room, private dining rooms, the bar, the cashier station, and the manager walking the floor. Everything from the moment the guest opens the door to the moment they walk out with a receipt is FoH's job.

The core FoH mandate breaks into five things:

• Hospitality — greeting, warmth, name recall, reading the table
• Order accuracy — capturing exactly what was asked, with modifiers and allergy notes intact
• Service pace — courses arrive at the right interval, no dead time, no rushing
• Table turnover — a 40-cover casual dining outlet needs 2.5-3 turns per lunch service to hit revenue targets
• Upsell — starter to the shared plate, second beverage, dessert, add-ons

What is FoH not? It is not marketing, not menu design, not procurement, not costing. Those live in the office or in BoH. FoH executes the guest experience within the constraints the operator sets.

What is BoH (back of house)?

BoH means back of house — everything the guest never sees. The boh restaurant meaning covers the kitchen line, prep area, cold and dry stores, receiving dock, dishwash, staff canteen, and (in most outlets) the back office. If a guest walked through it, health inspectors and the operator would both have a problem.

The core BoH mandate is production:

• Receive — ingredients in from suppliers, checked against PO, temperature-logged for perishables
• Store — FIFO rotation, correct temperature zones, no cross-contamination
• Prep — mise en place before service, portioned and labelled
• Cook — to spec, on time, at pass temperature
• Plate — consistent presentation matching the menu photograph
• Clean — wares, surfaces, extraction, floors, deep-clean cycles

Everything BoH does is measurable: food cost percentage, kitchen ticket time, waste percentage, plate consistency. What is BoH not? It is not guest recovery, not billing, not upsell. Those are FoH's domain.

FoH roles and salary bands (India)

Front of house restaurant roles form a clear hierarchy. Salary bands below are for tier-1 and tier-2 India cities in 2026 — Delhi NCR, Mumbai, Bengaluru, Pune, Hyderabad, Chennai, Ahmedabad. Tier-3 cities run 15-25% lower.

Fine dining outlets and premium casual dining add sommelier, dedicated beverage manager, and reservations manager roles. QSR and cloud kitchens collapse most of these into a single "counter staff" role at the entry band.

BoH roles and salary bands (India)

Back of house restaurant roles follow the classical brigade structure, adapted to Indian cuisines and outlet scales. Salary bands are 2026 tier-1/tier-2 India.

Cloud kitchens with a single cuisine collapse the brigade into 1 head chef, 1-2 CDPs, 2-3 commis, 1 dishwasher. A 100-cover fine dining outlet may run a full brigade with 3-4 CDPs (tandoor, curry, cold, dessert), 5-6 commis, and 2-3 kitchen porters per shift. For a first-time hire at the top of the boh org chart, we've written a dedicated guide on how to hire your first head chef in India in 2026.

The FoH-BoH handoff — where restaurants break

The seam where boh and foh meet is the KOT — kitchen order ticket. Every guest experience problem that isn't a food-quality problem lives somewhere in the KOT flow. Trace it:

1. Server takes the order. Verbal from the guest, keyed into the POS.
2. POS sends the KOT. To a printer at the kitchen pass, or to a KDS screen on the line.
3. Kitchen reads the KOT. CDP for the relevant section starts prep.
4. Expo checks the plate. Against the ticket — right dish, right modifiers, right table.
5. Runner or server delivers. To the correct guest at the correct table.

Every step is a chance to lose information. Common losses:

• Verbal modifier not typed — "no onions" said out loud, never made it into the POS. Guest gets onions. Complaint.
• Allergy note buried in "comments" — POS shows it but the CDP glanced at the top of the ticket only. Anaphylaxis risk.
• Printer jam mid-service — KOT never arrived at pass. Guest waits 40 minutes for a starter.
• Modified order not resent — guest changed their mind, cashier updated the bill but forgot to fire a KOT correction. Kitchen sends the old dish.
• Bill voided after KOT fired — kitchen still produced the dish. Food cost lost, no revenue.

Most of these disappear when the handoff is digital end-to-end. A POS-KDS integration passes structured data (item + modifier + allergy tag + table) instead of paper tickets that get lost. The expo role — expeditor — sits at the pass and is the single point of coordination between boh and foh during peak. Small outlets fold expo into the head chef; 60+ cover outlets staff it separately during dinner service.

The cultural divide — tips, energy, grind

The FoH vs BoH cultural gap is real and it has structural causes. In India, service charge (traditionally 10%) is distributed by outlet policy — some pool across FoH and BoH, some hand only to FoH, some retain and pay a "service bonus" via payroll. Where FoH walks with cash tips at the end of a shift and BoH doesn't, resentment builds within weeks. Every operator eventually faces the question of whether to pool.

The other structural gap is the nature of the work. Front of house restaurant staff perform in public, get direct thank-yous from guests, and see the reward of their work in real time. Back of house restaurant staff work in 42°C at the tandoor, get no direct guest feedback, and only hear from FoH when something is wrong (a returned plate, a complaint). Over a 12-hour shift this asymmetry compounds.

Three fixes that actually move the needle:

• Pooled or partially-pooled tips. Where legal in your jurisdiction, split service charge across FoH and BoH by a documented formula. Employees see it in their salary slip.
• Cross-training weeks. New FoH hires spend their first 3 days in BoH — prep, plating, understanding fire times. New BoH hires spend 1 day on floor with a captain to see how their food is received. Reduces conflict in the long run — see our restaurant staff retention playbook for the full onboarding cadence.
• Post-shift huddle. 5 minutes at end of dinner service — head chef and floor manager together, whole team present, three wins and one fix from the shift. Costs nothing, builds shared language.

FoH-to-BoH ratio benchmarks by format

The right FoH vs BoH staffing ratio depends on format. Here are the benchmarks we see holding up across India operators in 2026, per full peak-service shift.

These are peak-shift starting points, not gospel. Actual staffing needs to flex with daypart — a casual dining outlet that turns 3× at lunch and 2× at dinner needs different FoH counts across the two services. For a weekly labour model that costs each shift and shows exactly where you are over- or under-staffed, use our restaurant weekly staffing labour model.

Common FoH-BoH problems and fixes

The same four problems show up in every restaurant every week. They are all fixable in under 30 days with discipline.

Problem 1 — Servers don't know the menu

Guest asks "is the paneer tikka spicy?" and the server says "I'll check." Trust drops. Upsell dies. The kitchen gets a second interrupt because the server ran back to ask.

Fix: 10-minute daily pre-shift briefing before every service. Head chef or sous chef walks the FoH team through: 3 new items or specials of the day, 1 dish that is 86'd (out of stock), 1 dish being upsold this week, any allergen changes. Tasting encouraged. Costs 10 minutes, saves 90 minutes of confusion during service.

Problem 2 — Kitchen sends wrong order

Verbal orders shouted across the pass, handwritten KOTs in five different hands, modifiers lost in translation. Guest gets the wrong dish, plate goes back, food cost is written off.

Fix: a KDS (kitchen display system) connected to the POS. Order is entered once by the server, appears on the kitchen screen in structured form (item, modifiers, allergy, table, timer). No paper, no verbal, no interpretation.

Problem 3 — Long ticket times

Guest waits 25 minutes for a mains that should take 12. Not because the kitchen is slow, but because there's no expo calling fire times, and orders come out in the order they were entered rather than the order that groups a table's dishes.

Fix: assign an expo role for dinner service. Expo reads incoming tickets, calls "fire" times so all dishes for one table arrive within a 60-second window, quality-checks plates at the pass. Set target ticket times per section (starters 6 min, mains 12 min, dessert 8 min) and post them on the KDS.

Problem 4 — Bad shift handoff

Lunch team leaves at 4 PM. Dinner team arrives at 5 PM. Nobody tells dinner that the walk-in freezer had a 2-hour outage this morning, that the paneer supplier delivered short, that a regular table 12 is coming at 8 PM with a birthday. Chaos ensues.

Fix: a written pass-down log. One page, printed or shared digitally, covering: 86'd items, kit issues, supplier notes, reservations of note, staff callouts, cash-drawer status. Manager on duty signs off before leaving.

How POS + KDS make FoH and BoH work together

Every problem above has one common thread: information gets lost between front of house restaurant staff and back of house restaurant staff because there is no single shared record. A POS plus KDS is that shared record.

Here is what the handoff looks like when both sides run on one system:

• Server takes the order on POS. Item, modifier, allergy, table — structured data, not paper.
• KDS shows the order on the line. Colour-coded by wait time (green under 5 min, yellow 5-10, red 10+). Section-filtered so the tandoor CDP sees only tandoor items.
• Kitchen fires and marks ready. Server's POS shows "ready to pick up" — no shouting needed, no runner asking "is table 12 up?"
• Server marks delivered. Course timer resets for the next fire time. Expo sees the full board.
• Void or modification. Cashier updates the bill; POS auto-cancels or updates the KDS ticket. Kitchen sees the change in real time.

Every step that was verbal, handwritten, or dependent on memory becomes a digital handoff. Not because technology is magic — because a shared record removes the interpretive loss between two teams that don't share a physical space.

Frequently Asked Questions

What is FoH in a restaurant?

FoH means front of house — every part of the restaurant the guest interacts with. That covers the host stand, dining room, bar, cashier station, and the manager working the floor. The foh restaurant meaning is essentially hospitality plus service execution: greet, seat, take orders, deliver food, resolve complaints, collect payment. If a guest can see it, hear it, or speak to it, it is FoH.

What is BoH in a restaurant?

BoH means back of house — everything the guest never sees. That covers the kitchen line, prep area, dishwash, receiving dock, dry store, cold store, and the back office. The boh restaurant meaning centres on production: receive ingredients, prep, cook, plate, and clean. BoH roles run from the head chef down through sous chef, chef de partie, commis, and kitchen porter.

What is the difference between FoH and BoH?

FoH vs BoH is guest-facing vs production. Front of house restaurant staff sell hospitality — pace, warmth, order accuracy, upsell, complaint recovery. Back of house restaurant staff produce the product — consistent food, on-time, within cost. Both halves need each other; a great kitchen with a rude host loses guests, and a warm host with a slow kitchen loses guests too.

What roles fall under front of house?

Front of house restaurant roles typically include host or hostess, captain, steward or server, bartender, sommelier in fine dining, cashier, floor manager, and general manager. In India casual dining, entry-level FoH salary bands run ₹14,000-22,000/month for stewards, ₹22,000-32,000 for captains, ₹35,000-55,000 for floor managers, and ₹65,000-1,20,000 for a general manager depending on outlet size.

What roles fall under back of house?

Back of house restaurant roles include head chef, sous chef, chef de partie or CDP, commis chef, prep cook, dishwasher, kitchen porter, and receiving or storage staff. India salary bands run ₹12,000-18,000/month for kitchen porters and dishwashers, ₹16,000-24,000 for commis, ₹28,000-42,000 for CDPs, ₹45,000-70,000 for sous chefs, and ₹70,000-1,80,000 for a head chef depending on cuisine and outlet scale.

What is the ideal FoH to BoH ratio?

For a 40-cover casual dining outlet, plan on 6-8 FoH and 6-8 BoH per full shift — close to 1:1. QSR and cloud kitchens run heavier BoH (roughly 1 FoH per 3-4 BoH) because there is little floor service. Fine dining runs heavier FoH (up to 2 FoH per 1 BoH) because table-side service, wine service, and hosted pacing need bodies. These are starting points; adjust to actual cover volume by daypart.

Why do FoH and BoH clash?

The traditional split — FoH gets tips, BoH does not; FoH is public-facing energy, BoH is grind behind a hot line — creates a real cultural gap. Add poor communication (verbal orders, no KDS, no expo) and small mistakes turn into shouting matches by 9 PM. Fix with a shared tip pool where legal, cross-training so FoH understands prep timing, and one system (POS + KDS) that both sides read from.

How does the FoH to BoH handoff work?

The handoff is the KOT — kitchen order ticket. A server enters the order into the POS; the POS sends a KOT to the kitchen printer or KDS screen; the kitchen produces the dish; the expo checks it against the ticket; the runner or server delivers it. Every place information can be lost — misspelled modifier, verbal-only order, missing allergy note — is where guest experience breaks. A digital KDS integrated with the POS removes most of those loss points.

What is the expo role?

Expo is short for expeditor — the bridge role that stands between the pass and the FoH runners. Expo reads incoming tickets, calls the fire time for each dish, quality-checks plates as they come off the line, and matches plate to table before it leaves the kitchen. In a busy service the expo is the single point of coordination between boh and foh. Small outlets combine expo into the head chef or senior CDP role; 60+ cover outlets usually staff it separately during peak.

How does a POS plus KDS help FoH and BoH?

A POS plus KDS gives one shared record of every order. Server enters the order on the POS; the KDS shows it to the kitchen in real time, colour-coded by wait time; the server sees status updates (fired, ready, delivered) on the same POS. No paper KOTs to lose, no shouting across the pass, no verbal modifiers to forget. This one integration removes the majority of foh vs boh friction in a typical shift.