The Complete Guide to Kitchen Expo, Ticket Routing, and Course Pacing

The expo pass is the point where a restaurant's kitchen and dining room actually meet. Every order that leaves the POS ends up there. It gets broken into station-level work, fired in the right order, cooked, plated, checked against the ticket, and handed to a runner. When that chain works, guests never think about it. They just notice that their food arrived hot, at the same time as everyone else at the table, and that the meal had a rhythm. When it fails, the symptoms show up everywhere at once: entrees dying under the heat lamp while one plate is still on the grill, a four-top where three people are eating and one is watching, servers hovering at the window, a saute cook buried in tickets while garde manger stands idle.

This guide is our attempt to lay out the whole system in one place. We build PlatePassr, a tool for expo ticket routing and course pacing, so we spend a lot of time talking with chefs, expediters, and operators about what actually breaks during service. Almost none of what follows requires our software or any software. It is organized into seven themes: the expediter role, ticket routing, course pacing and firing, station bottlenecks, table turns, measurement, and how to choose and set up an expo system. Each theme links to a deeper article. Read it straight through if you are rebuilding your pass from scratch, or jump to the theme that matches the problem you had last Saturday.

The expediter role and who owns the pass

The expediter, or expo, is the only person in the kitchen whose job is to see the whole picture. Cooks see their station. Servers see their section. The expo sees every open ticket, knows roughly where each item stands, calls the fires, checks each plate against the ticket, wipes rims, adds the final garnish, and hands the plate to a runner with the table and seat number. On a good night this looks effortless. On a hard night it is the single most demanding job in the building, because the expo is holding the state of twenty or thirty tickets in their head while talking to two different groups of people who each want something right now.

The question of who owns the pass gets answered differently in almost every restaurant, and that is fine as long as the answer is explicit. In a small kitchen, the chef or sous chef often expedites from the pass while also jumping on a station. In a higher-volume room, a dedicated expo is worth the labor cost on the busiest shifts because the pass cannot be a part-time job when tickets are stacked. The failure mode is not choosing the wrong person. It is letting ownership float, so that during the worst fifteen minutes of the night the chef is on the grill, the sous is plating, and nobody is reading tickets. If the pass changes hands during a shift, there should be a spoken handoff: how many tickets are open, what is fired, what is on hold.

The expo also needs real authority, and cooks need to know it. The expo can hold a plate that is not right, call a re-fire, and tell a station to stop starting new items and finish what is up. Without that authority, the position becomes a garnish station with a loud voice. Training a new expo takes weeks, not a shift. They need to know the cook time of every item on the menu, read the rail quickly, learn the calling cadence the line responds to, and practice on slower services before a Saturday. The articles below go deeper on the role itself and on why the pass tends to collapse during the dinner rush even when the same people run it fine at lunch.

Routing tickets to the right stations

Ticket routing is the unglamorous plumbing underneath everything else. A ticket arrives with a mix of items, and each item has to reach the station that cooks it, with its modifiers attached, without the cook having to read and mentally filter the entire ticket. With paper, that means either a printer at each station that prints only that station's items, or one printer at the pass with the expo calling items out loud. With a kitchen display system, it means routing rules that map each menu item or category to a screen. Either way, the goal is identical: every station sees exactly what it owns, and the pass sees the whole ticket.

Most routing problems are quiet and cumulative. A menu change moves a dish from saute to grill, but the routing rule still sends it to saute. A composed plate needs two stations, and the ticket only shows on one. A modifier like no dairy prints on the pass copy but not on the station chit. A rush or VIP flag exists in the POS but never shows in the kitchen. None of these produce an obvious crash. They produce a cook saying I never got that, an expo scrambling, and a table that waits. Clean routing means someone owns the mapping, reviews it after every menu change, and tests it by ringing in a few sample orders before the doors open.

Across a multi-station line, routing also has to carry timing information. When a plate needs a protein from grill and a sauce and vegetable from saute, both stations need to know they are working the same ticket and which item is the lead. The lead item is the one with the longest cook time, and it sets the clock for everything else on the plate. A well-routed ticket makes that obvious, either by ordering items on the chit or by calling it out at the pass. All-day counts, meaning the total number of a given item currently working across all open tickets, are a routing output too. A cook who can see six chicken all day organizes their station differently than one seeing tickets one at a time.

Course pacing and when to fire

Ordering and firing are two different events, and the distinction is the foundation of pacing. When a server sends a ticket, the kitchen knows what the table wants. When the expo fires a course, the kitchen starts cooking it. Appetizers are usually fired on order. Entrees are fired when the table is ready for them, which depends on how the appetizer course is going. The expo's job is to time the fire so that every plate on the course finishes within a short window, which means starting the longest item first and layering the shorter ones in behind it. A well-done steak, a risotto, and a seared fish do not start at the same moment if you want them to land together.

Large parties are where pacing skill shows. A twelve-top with a mixed order stresses every station at once, so the expo has to decide when to fire entrees based on how the table is actually eating, not on a stopwatch. The reliable signal is the appetizer course being cleared or close to it, confirmed by the server or a busser, not the moment appetizers were dropped. Firing too early means plates sit in the window and die. Firing too late means a long, awkward gap at the table. Techniques that help: splitting the ticket by station in advance, pre-plating garnishes, holding sauces warm, and staggering the fire so the constrained station is not asked for twelve proteins in the same sixty seconds.

Pacing only works when the front of house and the kitchen use the same signals. Servers need a clear way to say fire table twelve, whether that is a word at the pass, a button on the POS, or a note to the expo. The kitchen needs to know how coursing works for two-tops versus large parties, whether desserts are fired on order or on a call, and what happens when a table asks to slow down. These rules should be written down and posted, because the shift when they matter most is the shift when nobody has time to explain them. The two articles below cover pacing a table so it eats together and the specific problem of firing entrees for a big party.

Station bottlenecks and line balance

A bottleneck is any station whose capacity is lower than the demand the menu mix puts on it during a given hour. In many American restaurants that station is the grill or the fryer on a weekend night, because the best-selling items concentrate there. But bottlenecks also come from a single piece of equipment, like one salamander or one small flat top, from prep that ran short, or from one cook who is simply slower. The tickets themselves will tell you where the constraint is. Look at the rail or the KDS during the worst part of service and see which station's items are consistently the last to hit the window.

Diagnosing takes a little discipline. Count the items each station handles per hour on a busy night and compare it to a slow one. Track which station's items are last on tickets that ran long. You will usually find that late tickets on weekends cluster around the same one or two stations, and that the pattern is stable week to week. Once you know the constraint, the fixes are mostly operational: move an item or a component to a lighter station, prep more ahead of time, cross-train so a swing cook can step in during the peak, re-engineer the menu so the specials do not all live on the grill, or replace the one piece of equipment that caps throughput.

The expo plays a direct role in line balance. Rather than pushing every ticket the moment it arrives, a good expo sequences work so the constrained station gets a steady flow instead of bursts. That can mean holding a ticket for a minute while the grill clears, calling all-day counts so the cook can batch, or telling saute to slow down starting items that will only sit in the window waiting on grill. The goal is not to slow the kitchen. It is to keep the slowest station from dictating a stop-and-go rhythm for everyone else. When the pass falls apart in the rush, this sequencing is usually the first thing to go.

Pacing, table turns, and the dining room

Kitchen pacing and dining room revenue are the same conversation. A table that eats together finishes together, gets its check together, and leaves together. Long gaps between courses stretch the meal and delay the next seating. Courses that come too fast make guests feel rushed and cut into wine and dessert sales. The target is a consistent rhythm: appetizers within a few minutes of order, entrees landing when the table is ready, dessert offered promptly after clearing. Operators who track it tend to find that reducing the variance between tables does more for turn times than trying to shave minutes off any single course.

The kitchen can only pace what it can see, which is why the host stand matters more than most cooks realize. Seating in waves produces ticket waves, and ticket waves produce bottlenecks and long ticket times even when the total covers are manageable. Spreading reservations and walk-ins across the hour smooths the pass. Where seating cannot be smoothed, the expo needs advance warning: a party of ten being sat at 7:30 is information the kitchen should have at 7:15. Some rooms handle this with a quick verbal update from the host at set times; others surface upcoming seatings on a screen at the pass.

There are practical levers on the floor that affect the kitchen's job. Dropping dessert menus at the right moment, timing the check drop, and having servers ring in the entire order at once instead of trickling items all change what the expo sees. Coursing rules should differ by table size: a two-top can move faster than an eight-top without feeling rushed. When the kitchen and the floor agree on target course gaps and share the same view of what is fired and what is waiting, table turns improve without anyone feeling hurried. The articles below dig into how pacing changes turn times and how to get a table eating together in the first place.

Measuring service: ticket times and what they miss

Ticket time, the elapsed time from when an order is sent to when it is plated or bumped, is the most common kitchen metric because it is the easiest to capture. It is useful, but it is blunt. Different items have different inherent cook times, and a ticket with a well-done steak will always run longer than one with a salad. A single average hides the difference between a kitchen that is consistently a little slow and one that is fast most of the time and catastrophic for twenty minutes on Saturday. Ticket times also do not tell you whether the food was good, whether the table ate together, or whether the delay was the kitchen's fault at all.

Better measurement starts with segmenting. Look at ticket times by station, by item category, by day part, and by table size. Track the gap between courses at a table, not just the time for the first plate. Count re-fires and comps tied to timing. Measure hold time in the window, which shows plates waiting for a runner rather than a cook. Set target times per category rather than one number for the whole menu, and count how many tickets exceeded target rather than obsessing over the average. These views point to specific fixes: a station, a menu item, a seating pattern, a runner shortage.

How measurements are used matters as much as what is measured. A line that feels surveilled will game the numbers, bumping tickets early or ignoring timers. A line that reviews patterns together after service, looks at the worst hour and asks what happened, and treats outliers as information rather than accusations will actually improve. Ticket times are a fair way to evaluate a kitchen only when they are compared against realistic targets, segmented honestly, and read alongside what the dining room was doing. The article on whether ticket times are a fair measure covers this in depth, and the bottleneck article shows how to use the numbers to find the constraint.

Choosing and setting up an expo system

Every kitchen already has an expo system, even if it is a printer, a rail, and a person shouting. The question is whether the system carries the information the pass needs. At a minimum that means: a view of every open ticket, per-station routing so each cook sees only their items, a way to fire courses separately from ordering them, timers that show how long each ticket and course has been working, and all-day counts. Paper can do some of this with discipline. A basic kitchen display system bundled with the POS typically adds routing and timers. Dedicated expo and pacing tools add course-level fire control, cross-station coordination, and a pass view built for the expediter rather than the cook.

Setting up any of these follows the same steps. Map every menu item to a station and decide how multi-station plates are handled. Define coursing rules, including how large parties differ. Set target times by item category so alarms mean something. Train the expo and the cooks on what each screen or chit shows and what the fire calls mean. Then run it on a slow shift first. The common mistakes are predictable: too many screens with too much on each, alarms that go off so often everyone ignores them, routing rules that never get updated after a menu change, and rolling out on a Friday night.

We should be honest about what software can and cannot do. No expo tool fixes an understaffed line, a menu that piles everything on the grill, or a host stand that seats forty covers in ten minutes. What it does is take the memory load off the expo, give every station the same picture, and make timing visible instead of guessed. That is what we built PlatePassr to do, and it is also what a well-run paper pass does with a strong expediter. The articles below on routing, clean multi-station lines, and pass ownership are the right starting points whether you are buying software or simply tightening the system you already have.

More guides on this topic

Further reading from the PlatePassr blog, each answering one specific question in depth.

If service is breaking down, resist the urge to fix everything at once. Start by naming who owns the pass on every shift. Then check routing, because a surprising share of late plates trace back to an item going to the wrong screen or a modifier that never reached the station. Then look at firing: are entrees fired on a signal from the table or on a guess? Then find the constraint station and give it a steady flow. Only after those basics are solid does it make sense to add measurement and tools. Kitchens that go the other way, buying screens before fixing ownership and rules, usually end up with expensive timers that everyone ignores.

The pass is a system, and systems respond to small, consistent changes more than to heroics. A written coursing rule, a routing map that gets reviewed at every menu change, a spoken handoff when the expo steps away, and a Sunday review of the worst hour from Saturday will do more for your ticket times and your table turns than any single night of everyone trying harder. Use the articles linked throughout this guide as the deep dives, and come back to this page when you need the whole picture again.