Expeditor & Pass Management Standard Work
Clear, actionable standard work for expeditors and pass teams: pass layout, timing windows, plating QC, communication scripts, timing cards, escalation rules, and practical implementation steps to reduce remakes, late tickets and cold plates.
Purpose
This playbook defines standard work for the expeditor (expo), cooks, and front-of-house (FOH) staff to keep the pass flowing so dishes reach guests hot, complete, and on time. Use it to reduce remakes and slow tickets by clarifying pass responsibilities, timing expectations, communication scripts, and escalation steps.
Who does what (roles & responsibilities)
- Expeditor (Expo) — Owns the pass. Reads tickets, sequences plates, performs plating quality checks, calls for hold or expedite, communicates with cooks and servers, and escalates delays.
- Line cooks — Deliver finished items to the pass on time and clearly labeled. Respect plating and portion standards.
- Server/Runner — Monitors the pass, removes plates promptly, reports missing items or delays to expo, and communicates guest needs that affect timing.
- FOH Manager — Backs up expo during peak service, coordinates bussing/expedite coverage, handles guest-impact escalations, and reviews performance data after service.
Pass layout & organization rules
- Designate a single, clearly visible pass area with defined left-to-right workflow: Staging / Hot hold / Plating zones.
- Keep the pass clear of clutter; only plates, tickets, and necessary tools (tongs, garnish spoons, timers) are allowed.
- Ticket rail: newest ticket on the right, oldest on the left (or another consistent convention). Expo always pulls tickets from the same side.
- Assign visible station tags (meat, veg, grill, fry, garnish) and use color-coded ticket markers for priority (see Color & Ticket Markers below).
- One expo per pass during service; define a backup for when the primary expo is pulled away.
Timing Windows (example targets)
Adapt these to your menu and ticket complexity. Use them as starting targets and measure actual times to refine.
- Appetizers / Small plates: Expected completion 6–10 minutes from order accept. Escalate at 12 minutes.
- Entrees / Main dishes: Expected completion 10–18 minutes depending on prep. Escalate at 22 minutes.
- Desserts: Expected completion 4–8 minutes. Escalate at 10 minutes.
- Takeaway / To-go orders: Expected completion 8–12 minutes. Expo confirms with FOH if delay expected.
Define a target ticket time per menu category and print timing cards at the pass for quick reference.
Plating Quality Checklist (expo check before release)
- Correct dish and ticket match (name, modifiers, allergies).
- Portion size and protein temperature look correct.
- Presentation matches the standard-photo or plating card.
- No visible foreign objects, spills, or burn marks.
- All sides, sauces, and garnishes present and correctly placed.
- Allergen/marking tags attached when required.
- Plate wiped and edge cleaned.
- Hold or expedite decision: if an item fails QC, expo calls a remake or holds until corrected.
Communication scripts & patterns
Use short, consistent language so messages are clear over noise.
- Expo → Cook (priority call): "Fire 23 — seat 7, steak RD, time check: 7 min?"
- Cook → Expo (ready): "Ready — seat 7 steak RD, on the pass."
- Expo → Server (release): "Two for table 7, running hot."
- Expo → FOH Manager (escalation): "Delayed entree — table 12, steak overdue 10 minutes, guest waiting. Need cover on expo."
Use hand signals or light beeper where noise is extreme; keep language uniform across shifts.
Timing cards & escalation rules (leaderboard for attention)
Place quick timing cards at the pass to show expected and escalation thresholds. Example escalation flow:
- At target time + 20%: Expo warns cook — "Time check on ticket X."
- At escalate threshold (see Timing Windows): Expo marks ticket with orange marker and calls FOH manager if needed.
- At escalate + 5 minutes: Ticket marked red, manager intervenes (re-prioritize line, offer guest an update or complimentary item where appropriate).
Color-coded ticket markers & station tags
- Green — on time / normal.
- Yellow/Orange — near escalation (warning).
- Red — escalated; needs manager attention.
- Station tags: Use short labels (GRL, FRY, SAU, VEG) so expo can quickly route items and call for missing components.
Common problems & corrective actions
- Remakes for wrong mods: Add a readback step — cook repeats modifiers when ticket printed and expo verbally confirms for complex orders.
- Cold plates: Implement a short hot-hold policy (e.g., max 60–90 seconds at pass) and train servers to pick up promptly.
- Bottlenecks at one station: Reassign support or pre-stage components before rushes; cross-train staff.
Measurement & targets
Track these metrics for two to four weeks to set realistic targets:
- Average ticket time (order accepted → plate picked up).
- % of tickets hitting target window.
- Remake rate (per 100 tickets).
- Guest complaints tied to speed/temperature.
Implementation checklist (first 30 days)
- Print timing cards, station tags, and color markers; place at pass.
- Run one training session with expo, cooks, and servers to practice scripts and QC checklist.
- For one week, measure ticket times and remakes daily — capture causes for remakes.
- Hold a short post-shift huddle for three nights to discuss what slowed the pass and one improvement action each day.
- After two weeks, adjust timing windows and responsibilities based on real data.
Quick reference (expo pocket card)
- Match ticket → plate → modifiers → allergy tag.
- Plating QC: portions, presence, temperature, edge clean.
- Timing callouts: warn at target + 20%, escalate at escalation threshold.
- Color markers: Green = go, Yellow = watch, Red = escalate.
- Keep pass clear. One expo. Backup assigned.
Notes on adaptation
Tune timing windows to your menu complexity and ticket composition (e.g., multi-course vs. quick-serve). Test one change at a time and measure its impact during a defined trial period.
Training & culture
Make expo performance a team KPI and celebrate shifts where targets are met. Encourage constructive, specific feedback during post-service huddles rather than blame. The pass succeeds when everyone shares responsibility for timing and quality.
Discussion
Comments and conversation will live here.