Expeditor & Pass Management Playbook

Purpose

This playbook makes the expeditor role repeatable and teachable so the pass flows, tickets move reliably, and guests get hot, accurate plates on time. Use it as the standard for shift briefings, training, and continuous improvement. Adapt numbers to your concept and test changes with data.

How to use this playbook

Keep a printed or digital copy at the pass and review it during pre-shift huddles. Track a few KPIs each shift (ticket time, remakes, plate holds) and tune the timing thresholds to match your kitchen's physical layout and service style.

Quick principles

• Clarity beats memory: have one defined owner of each ticket at all times.
• Early inspection: inspect the ticket within 20–30 seconds of it arriving at the pass.
• Act, don’t delay: if a needed item isn’t started within the target time, escalate quickly.
• Make quality visible: plating standards must be obvious to anyone who walks up to the pass.

Opening checklist (pre-service)

1. Confirm expeditor station is clean, heat lamps operational, and all plating stations stocked with garnishes, sauces, and utensils.
2. Have printed or digital menu/recipe cards for any specials or items with known variability.
3. Confirm ticket printer/handheld ordering connectivity and a visible ticket queue.
4. Run a 3-minute simulated ticket to confirm timing and communication patterns with cooks and servers.
5. Agree on timing thresholds for the shift (see Timing Thresholds).

Ticket verification flow (step-by-step)

1. Receive & Confirm (0–30s): read the ticket aloud, confirm modifiers, allergies, and timing notes (e.g., "allergy—no nuts").
2. Assign owner (0–30s): point to the cook/station who owns each item and say the station name out loud ("York, burger; Mai, saute").
3. Verify start status (30–90s): confirm each station has started or will start within the agreed start window. If a station hasn't started, say the expected time to start ("Start in 30s").
4. Plate inspection (when items arrive): check temperature, portion, garnish, and correct modifiers. Use the plating standard checklist below.
5. Sequence & Expo (finalize): assemble the ticket in order, shout or display any cross-plate timing needs (e.g., "two minutes on crab—hold steak 90s").
6. Ready & Call (hand-off): when complete, call out the ticket number and flags ("Ticket 48 up—one medium rare, one well done").

Plating & quality checklist

• Correct dish and components present.
• Portion size within standard range.
• Garnish and sauce applied in the standard location and amount.
• No excessive fingerprints, spills, or burnt pieces.
• Temperature check for hot plates (brief touch or thermometer when required).
• All modifiers and allergy protections present (separate plating if needed).

Timing thresholds (examples — adapt to your kitchen)

Use these as starting targets. Measure real times for a week and adjust.

• Ticket read & owner assigned: <= 30 seconds
• Station start after assignment: <= 90 seconds
• First item arrival to pass after start: varies by dish; measure baseline
• Full-ticket assembly (time from first item arriving to ticket called ready): <= 60–120 seconds
• Server pickup after call: <= 60–90 seconds
• Hold time allowed for hot items: <= defined per item (e.g., 60 seconds for fries, 120 seconds for steak)

Note: Long hold times require reheat or remake rules—document them for each menu item.

Problem escalation steps

When a ticket is at risk (late, missing item, allergy concern), follow this script and sequence:

1. Call it:
2. Confirm ownership: identify who should be working it. If unassigned, assign immediately.
3. Estimate recovery time: tell the server and manager: "Fries in 90 seconds—server please inform guest of delay."
4. Escalate early: if recovery will exceed the ticket threshold, notify the manager to decide remake, comp, or guest communication.
5. Document repeats: log the incident in the shift notes for coaching and trend analysis.

Communication scripts (examples)

• To cook when item missing: "James—ticket 60, fries—start now, ETA 60s."
• To server when delay known: "Ticket 60 will be 2 minutes late—please let guest know and offer a bread or drink on the house if needed."
• For allergies: "Ticket 63 allergy—no nuts. Reconfirm with line: use clean gloves and separate plate."

Coaching checklist for expeditor development

Use this during shift follow-ups or short coaching sessions (2–5 minutes).

• Observed ticket read speed and clarity — praise quick, loud reads.
• Assignment clarity — did the expeditor point and confirm ownership?
• Quality checks — were plating standards enforced consistently?
• Use of timing thresholds — did the expeditor escalate early when items were late?
• Communication with front-of-house — tone, clarity, and accuracy.
• Action plan: 1–2 specific behaviors to practice on next shift (e.g., "read tickets within 20s, escalate by 90s").

KPIs to track

• Average ticket time (order to ready)
• Remakes per 100 tickets
• % of tickets meeting target thresholds
• Number of escalations per shift and outcome

Common mistakes & fixes

• Relying on memory: use printed recipe/modifier cards at the pass.
• Silent ownership: always verbally assign items.
• Too many hold exceptions: tighten hold rules and re-evaluate sequencing.

Adaptation notes

Fast-casual and delivery-forward kitchens will want shorter thresholds and more rapid hand-offs. Fine-dining kitchens may prioritize staging and simultaneous plating—adjust thresholds and hold rules accordingly. Run a two-week experiment whenever you change thresholds.

Next steps

Start by running the opening checklist for one week and collecting simple data on ticket times and remakes. Use the coaching checklist once per shift for two weeks and compare KPIs. Iterate in small, measurable steps.