You've worked a Saturday night rush. You know the sound — tickets printing faster than you can tear them, the grill guy yelling "fire two ribeyes medium," a server weaving through the window with three plates balanced on one arm, and somewhere in the middle of it all, one person standing at the pass with a marker, a timer, and a look that says I see everything.
That person is the FOH expeditor. And if you've never had a good one, you've felt the chaos.
The primary function of the FOH expeditor role isn't just "calling tickets" or "wiping plates.Here's the thing — they catch mistakes before they hit a table. " It's the nervous system of a busy service. In real terms, they translate kitchen chaos into dining room flow. They protect the line cooks from drowning and the servers from walking cold food. When it works, you barely notice them. When it doesn't, the whole room feels it.
What Is a FOH Expeditor
FOH stands for front of house. They're not a line cook. The expeditor — sometimes called the expo, the pass runner, or just "the person at the window" — sits at the literal and figurative intersection of kitchen and dining room. They're not a server. They're the bridge Small thing, real impact..
In a traditional brigade, the chef or sous chef runs the pass from the kitchen side. Here's the thing — the FOH expeditor mirrors that role on the floor side. They read every ticket. They track every table's progress. They know which appetizers need to fire so the entrees don't sit under a heat lamp. They know Table 12 has a shellfish allergy and Table 4 is celebrating an anniversary and needs the dessert plate written in chocolate.
It's not a glorified food runner. A runner grabs plates and goes. In practice, an expeditor manages the pass. They decide what leaves, when it leaves, and in what order. They're the last set of eyes before food hits a guest.
The pass isn't a handoff — it's a conversation
Most people picture the pass as a conveyor belt. Kitchen puts up food, expo wipes the rim, server takes it. Real service doesn't work like that. Here's the thing — the pass is a negotiation. The kitchen says "we're three minutes out on the halibut.That's why " The expo says "hold the risotto, fire the salads now, Table 7 needs their apps before the wine arrives. " That dialogue — constant, quiet, high-stakes — is the job That's the part that actually makes a difference..
Why It Matters / Why People Care
You can run a restaurant without a dedicated FOH expeditor. The GM jumps on the pass during the rush. " The chef yells orders from the line. A senior server "helps out.In real terms, plenty of places do. It works — until it doesn't The details matter here..
The primary function of the FOH expeditor role becomes obvious the moment you lose one.
Ticket times stretch without anyone noticing
Servers get double-sat. The expo catches all of it. A well-done steak sits dying under the lamp while the medium-rare goes out first. They forget to fire a course. They're the only person in the building whose only job is watching the board and the clock simultaneously.
Food quality holds or dies at the pass
A sauce breaks. Still, a garnish is missing. A plate is chipped. And the line cook didn't see it — they're firing six tickets at once. The server didn't see it — they're pouring water at Table 3. The expo sees it. They send it back. They fix it. They protect the standard Less friction, more output..
The dining room stays in rhythm
Ever had a table get their entrees before their apps? On top of that, or watch one guest eat while three others wait? Now, that's an expo failure. The primary function of the FOH expeditor role includes pacing — knowing when to hold, when to fire, when to stagger. They keep the meal moving like a conversation, not a traffic jam.
Servers trust the system
When servers trust the expo, they stop hovering at the window. Consider this: they stop asking "where's my food? " They stop running to the kitchen to check. They stay on the floor, taking care of guests. That trust is earned shift after shift. It's fragile. One missed allergy, one cold plate, one "I thought you fired that" — and the servers start micromanaging the pass again. Chaos returns And that's really what it comes down to. Still holds up..
How It Works (or How to Do It)
The job looks different depending on the restaurant. Think about it: a 200-seat casual spot with a dedicated expo station runs differently than a 40-seat fine dining room where the captain expedites. But the core mechanics stay the same.
Reading the board like a language
The ticket rail tells a story. Day to day, a good expo doesn't just see "Table 14 — 2 apps, 3 entrees. On top of that, " They see: *Table 14, four-top, two kids — apps need to fire together so parents can eat while kids eat. One gluten-free pasta, mark it red. Dessert order already in, prep the plates now.
Quick note before moving on.
They memorize the board. They know which tables are at what stage without looking. They anticipate the kitchen's bottlenecks — the grill station backing up, the pastry chef plating three desserts solo — and adjust firing times before the crash happens.
The firing rhythm
"Fire" isn't a suggestion. Too late and the table waits. It's a command. Now, the expo decides when each dish starts cooking. Too early and it dies. The primary function of the FOH expeditor role here is timing — backward planning from the desired plate-up moment.
They factor in:
- Cook times per station (grill, sauté, fry, cold)
- Current ticket load per station
- Table pace (are they lingering over wine? Now, crushing apps? )
- Special requests (allergies, temps, splits)
- Server bandwidth (can this server run three hot plates solo?
A new expo fires everything at once. And an experienced one staggers. "Fire apps now. Hold mains. Walk in two minutes — fire the fish, hold the pasta. Table 9 just ordered — fire their apps with Table 14's mains.
Quality control at the window
Every plate stops at the expo. Every single one. They check:
- Temperature (touch the plate, not the food)
- Presentation (sauce lines, garnish, wipe marks)
- Accuracy (modifiers, allergies, substitutions)
- Completeness (side dishes, bread, condiments)
They're the last line of defense. If a line cook puts parsley on a dish that says "no green," the expo catches it. If a steak comes up rare-plus instead of medium, the expo sends it back — before the server sees it And it works..
Communication that doesn't shout
The best expos talk quietly. " "Hold the risotto, 86 the scallops.Because of that, "Walk-in, Table 3, two minutes. They use hand signals, ticket markers, a few precise words. " "Allergy flag — Table 11, shellfish Still holds up..
They don't argue at the pass. Also, they don't blame. But if a mistake happens, they fix it and debrief later. The pass stays calm because the expo keeps it calm.
Managing the runner team
In larger rooms, the expo directs food runners — assigning plates, sequencing drops
In larger rooms, the expo directs food runners — assigning plates, sequencing drops, tracking which runner took which table so nothing gets double-dropped or forgotten. In practice, they know each runner’s capacity: who can carry four plates clean, who needs two trips, who reads the room well enough to intercept a refill request before it becomes a complaint. The expo matches workload to ability in real time, adjusting on the fly when a runner gets pulled to bus a spill or walk a high-chair to Table 22 It's one of those things that adds up..
Easier said than done, but still worth knowing.
The server feedback loop
Servers don’t just pick up food. They deposit intelligence. “Table 6 wants to slow down — hold their mains.” “Table 18 is celebrating, bring the sparklers with dessert.” “Guest at 31 hates cilantro — did the kitchen catch it?Consider this: ” The expo absorbs this, updates the mental model, relays adjustments to the line. They’re the translator between the dining room’s chaos and the kitchen’s precision. Still, when a server says “fire Table 7,” the expo knows whether that means now or in three minutes after they clear apps. They protect the line from vague urgency and protect the floor from kitchen surprises Simple as that..
The 86 board as strategy
Eighty-sixing isn’t defeat — it’s damage control. A sharp expo watches inventory like a hawk. They know the last three portions of branzino are gone before the line yells it. They 86 it proactively, brief servers on the pivot (“push the chicken, it’s strong tonight”), and adjust firing patterns so the grill doesn’t sit empty. In real terms, they coordinate with the sous on cross-utilization: “Trim from the strip steaks — run a special on steak frites, move 20 covers. ” The 86 board becomes a sales tool, not a failure list.
Closing the loop
At shift end, the expo doesn’t just wipe the rail. They debrief. On the flip side, which station drowned? Which modifier got missed twice? Which runner crushed it? They log it — mental or written — for tomorrow’s prep meeting. In real terms, the best expos build institutional memory. They know Chef’s new dish will bottleneck at the pass on Fridays. Now, they know Server Maria needs extra lead time on large parties. Which means they know the dishwasher’s break schedule dictates when the silverware runs thin. This knowledge compounds. A restaurant with a veteran expo runs differently than one with a rotating fill-in. The difference shows in ticket times, comp rates, server retention, and the quiet confidence of a dining room that never feels rushed — even when it’s slammed.
The invisible architecture
No one posts “Expo Wanted” on the marquee. And guests don’t ask for the expo by name. But when the food arrives hot, correct, and together — when the server smiles instead of sweating — when the line cook finishes the night without throwing a pan — that’s the expo’s signature. Because of that, they are the metronome. On the flip side, the filter. The calm in the storm. In practice, a restaurant can survive a bad host, a slow bartender, even an off-night chef. But a broken expo breaks the room. In practice, a great one? Think about it: you never notice them. You only notice that everything works.
