“Fire table twelve.” “Heard!” “Where’s my fish, six minutes on that fish!” “Coming up now, thirty seconds!”
Stand near the pass in a busy kitchen for five minutes and it sounds like nobody’s in charge. It’s the opposite. Every one of those shouted lines is part of a system, and the person standing at that counter, calling out tickets and tracking a dozen dishes at once, is usually the only reason a table’s appetizer and entrée don’t end up arriving twenty minutes apart.
That person has a job title: expediter, or “expo” for short. In older kitchens the French term was aboyeur, which just means “barker.” Whatever it’s called, the role exists because timing during a rush doesn’t take care of itself. Somebody has to own it.
Why Timing Is the Hardest Part of Service
Cooking one dish well is a skill. Cooking twenty dishes at once, for eight different tables, so that every plate on the same table finishes within seconds of each other, is a completely different problem. The grill station might need eleven minutes for a steak. The sauté station needs four for the vegetables. The garde manger station plates the appetizer in under a minute. Left to their own pace, none of those stations would naturally sync up.
That’s what the pass is for. It’s the counter between the kitchen and the dining room, and it’s where all those separate timelines get forced into one. The expo stands there and decides, out loud, when each station needs to start cooking so that everything for one table lands at the same moment.
Calling Tickets: Turning Separate Jobs Into One Shared Clock
When an order comes in, the expo reads it out to the whole kitchen, not just the station it applies to. Every cook hears it, whether or not it’s their dish. That’s deliberate. A grill cook who knows a table’s app just went out can guess roughly when their protein needs to be ready, even before the expo calls it directly.
Cooks respond with a short “heard,” confirming the instruction actually landed. It sounds almost military, and there’s a reason for that. In the middle of a loud rush, an instruction nobody acknowledges might as well not have been given. The kitchen runs on this loop, call and response, dozens of times an hour, because it’s the only way one person’s timing plan turns into ten people acting on it at once.
What Happens When Timing Isn’t Owned by Anyone
Picture the same kitchen without someone running the pass. Every station cooks at its own pace, focused only on its own dish. The steak finishes when it finishes. The vegetables finish when they finish. Nobody’s tracking whether they land together, because tracking that isn’t any single station’s job.
The result has a name in kitchen slang: a plate “dying under the lamp,” sitting there going cold and grey while the rest of the table’s order catches up. Multiply that across fifteen tables on a Friday night and you get exactly the kind of service that makes a restaurant feel chaotic, even when every individual cook is doing solid work. The problem was never the cooking. It was the absence of anyone owning the coordination between all of it.
It’s a Coordination Job, Not Just a Rank
It’s tempting to assume the head chef always runs the pass, since it looks like the most senior job in the room. Sometimes that’s true, especially in smaller kitchens. Just as often, a sous chef or a dedicated expediter takes it on instead, freeing the chef to actually cook or check quality elsewhere. What matters isn’t who holds the title. It’s that exactly one person is deciding the timing for the whole kitchen, instead of ten people each deciding it for themselves.
This connects to the same idea running through how mise en place creates consistency before a single order comes in and why restaurants write down recipes even the chef has memorized. All three are really the same strategy applied at different moments: take a decision that would otherwise get made under pressure, by guesswork, and give ownership of it to one clear system instead. Prep removes the guesswork before service starts. Recipes remove it from the plate itself. Expediting removes it from timing, once every station is moving at once. Together, that’s most of what restaurants rely on to stay consistent during daily service.
What a Home Cook Can Actually Use From This
Nobody needs an expediter for a weeknight dinner. But the same coordination problem shows up the moment a home cook tries to serve more than one dish at the same time, a roast, a side, a sauce, all needing to hit the table together. Left unmanaged, exactly what happens in an under-run kitchen happens at home too: one dish sits waiting while another still needs ten more minutes.
The fix scales down the same way the problem does. Work backward from the moment everything needs to be ready, and decide out loud, even if it’s only to yourself, when each part needs to start. That’s really all an expo is doing at a much larger scale: turning several separate timelines into one shared one, on purpose, instead of hoping they happen to line up.