Expeditor & Pass Standard Work: Timing Rules & Communication

Purpose & scope

This playbook gives the expeditor (expo) a clear set of standard work, timing rules, and communication patterns to keep the pass flowing during normal service and peak periods. Use it to reduce remakes, accelerate ticket throughput, improve plating consistency, and provide a reliable escalation path when things go wrong.

Who should use this

Expeditors, expo assistants, lead cooks, front-of-house leads, and managers. The playbook is written so any location can adopt and tailor timing targets to menu complexity and kitchen equipment.

Core responsibilities

• Ownership: The expeditor owns the pass. That means controlling ticket sequence, ensuring plates meet standard, matching orders, and coordinating server pickup.
• Quality gate: Confirm each plate for portion, temperature, garnish, and timing before it reaches the server.
• Paced release: Hold or release plates to keep courses coordinated and service steady.
• Escalation: Resolve or escalate issues immediately using the dispute flow below.

Pass cadence & rhythm

Adopt a predictable cadence so cooks and servers know what to expect. Use these simple rules as defaults and adjust by shift as needed.

1. Keep tickets visually ordered on the rail from left (oldest) to right (newest).
2. Announce order status with short, consistent language: "Expo ready," "Holding for salads," "Pick-up now," "Remake—expo."
3. Use one-line calls for pickup. Repeat table number and leave if pickup is confirmed.
4. When a ticket ages past the defined threshold, treat it as urgent and prioritize a check-in with the line or manager.

Ticket aging thresholds & sample timing charts

Start timers when the ticket is printed/entered and visible at the pass. Targets below assume a typical small-medium restaurant. Tailor to your menu, equipment, and service model.

Use the urgent threshold to trigger quick recovery actions: reassign a cook, cancel/change a modifier, or prepare a temporary filler (e.g., an on-the-house salad) while a long-item finishes.

Mise checks & plating standard checklist

Before a plate leaves the pass, run the expo mise check:

• Match ticket to plate(s): items and modifiers correct.
• Portion check: protein, sides, garnishes meet standard portions.
• Temperature check: hot items hot, cold items chilled.
• Appearance: no spills, clean edges, correct plating order (e.g., sauce under protein if specified).
• Allergens & special instructions clearly noted and communicated to the server.

Plating standards (practical rules)

• Assign a visible label for each plate: ticket number + seat where applicable.
• Stack similar plates to make pickup easier, but never cover a plate’s critical visual garnish.
• Maintain a clean pass: wipe spills immediately and remove abandoned plates after a defined hold time (usually 60–90 seconds) unless a server confirms pickup.

Server pickup rules

• Servers must pick up within 60–90 seconds after the expo announces pickup. If no server appears, expo should call the server by name and table number once, then mark the ticket as awaiting pickup and inform the manager if delay continues.
• If a plate is returned for remaking, the server must immediately place the ticket back on the rail and clearly state the issue: "Returned—wrong temp" or "Returned—missing side".
• Servers must not remove plates without confirming the ticket number and any special items to avoid mismatches.

Communication patterns and language

Short, consistent phrases reduce confusion. Examples:

• "Expo ready—table 12" (plate is fully checked and ready).
• "Holding salads for 12" (holds a course for coordination).
• "Pickup now—two plates 7" (immediate pickup requested).
• "Remake expo—steak med-rare but served well-done" (clear reason and responsibility).

Dispute & escalation flow

Handle disagreements quickly, calmly, and the same way every shift:

1. Server returns plate and states concise reason. Expo places plate and ticket on the rail with a "returned" marker.
2. Expo inspects the returned plate and checks ticket history. If it's clearly an expo/cook error (wrong temp, missing item, wrong side), mark Remake—expo and prioritize remake. If unclear, escalate to lead or manager immediately.
3. Manager decision: remake, comp, or server-customer resolution. Manager documents the incident (see Capability notes below for adding a simple incident log form).
4. After resolution, run a 60-second micro-huddle with involved staff to capture the root cause and a one-line countermeasure (e.g., "Use timer on steak station", "Call allergies louder").)

Quick pass checklist (shift start)

• Labels for rails and temperature control in place.
• Expo station stocked with garnish, towels, markers, and discard bin.
• Ticket rail cleared and ordered left-to-right.
• All servers reminded of pickup rules and language for the shift.

KPIs to track

• Average ticket time (ticket to pickup).
• Number of remakes per 100 tickets.
• Count and duration of "stalled" tickets (exceeding urgent threshold).
• Server pickup compliance (picked up within 90s after "pickup now").

Implementation tips & testing

Run a 3-shift pilot using these thresholds. During the pilot, have the expo record each aged or remade ticket on a simple log (ticket#, reason, time, action). Review metrics after each day and adjust timing targets to match your kitchen's real capability.

Tailor to your operation

Menus with many complex composed plates will need longer target windows and possibly a second expeditor. Small fast-casual operations may shorten targets and emphasize immediate pickup. Use the playbook as a starting standard, not a rule carved in stone.

Next steps

1. Adopt the playbook for one week and collect basic KPIs.
2. Run a short training with expo and servers to agree on language and pickup rules.
3. Consider adding a simple incident log form to capture remakes and disputes (see CapabilityEnhancementNotes).