Expeditor & Pass Management Playbook (timing, roles, and escalation standards)

Why this playbook matters

The pass is where kitchen craft meets guest expectation. A clear expeditor and pass system reduces remakes, shortens ticket times, protects food quality, and prevents the scrambling that makes both guests and staff unhappy. This playbook gives commonsense, operational standards your team can run tonight and improve over time.

Quick orientation

Keep this short, visible, and practiced. The pass system should answer three daily questions: Who owns the pass right now? Which dishes are on short/medium/long timers? What do we do when something slips? Use the roles, timing rules, language, checklists, and escalation flow below as your standard work.

Roles & responsibilities

• Expeditor (Expediter) — Owns the pass, inspects plate quality, sequences plating, coordinates timing between stations, calls tickets to the floor, and communicates delays. The expeditor also records basic pass issues for the shift report (remakes, temp issues, major delays).
• Lead Cook / Station Leads — Deliver completed items on time, state any expected delays to the expeditor, and confirm plate temp/portion before sending.
• Runner / Food Expo — Picks up plated orders promptly, confirms order accuracy at the pass, and communicates guest-facing status to servers.
• Shift Leader / Manager on Duty — Owns escalation beyond the pass (e.g., side dish shortages, equipment failure, or staffing gaps) and reviews pass audit checklist during service.

Timing rules by dish complexity

Use simple timer bands so everyone has the same expectations. Time windows begin when the last element that affects quality is plated or finished.

• Short (ideal 0–2 minutes) — Simple plates, fries, salads, or composed items that are best served immediately. Hold window: 0–2 minutes.
  • Examples: fries, dressed salads, single-pan desserts.
• Medium (ideal 2–6 minutes) — Plates that tolerate brief holding with minor finish work (saucing, garnish). Hold window: 2–6 minutes.
  • Examples: pan-seared proteins with sides, composed entrees.
• Long (ideal 6–12 minutes) — Complex builds, late-stage finish items, or multi-component plates that need staging. Hold window: 6–12 minutes; consider rework if exceed window.

When a plate exceeds its hold window, treat it as a potential remake — inspect, reheat/refinish if safe, or escalate according to the flow below.

Ticket batching & sequencing guidance

• Batch tickets by table and arrival time — keep builds for the same table together to reduce hot/cold mismatches.
• Sequence by last-element timing: finish simple items first if they match the ticket's send window, but never send a partial table unless the server is ready and it meets the hold rules.
• Use a visible ticket board or digital indicator to show readiness and send priority (e.g., green = ready, amber = watch, red = delayed).

Acceptable hold windows and temperature checks

• Define and post safe internal temperature targets for hot items and maximum hold times for cold/hot items (e.g., hot plated items should be at or above X°F/C at the time of pickup; cold items at or below Y°F/C). Align these targets with your food safety program.
• Perform a quick temperature-and-finish check before sending: visible quality, portion, garnish, sauce levels, and plate temp.
• If plate temperature is below the acceptable threshold but still within safe hold time, either reheat/refinish or note the issue and escalate; do not send a plate that will leave a guest unsatisfied.

Pass language and callouts (standard phrases)

Use short, consistent phrases so noise and misunderstandings drop. Train on these and enforce kindly but firmly.

• On the pass — "Ticket 42 on the pass" (simple readiness), "Ticket 42 holding 3 mins" (watch), "Ticket 42 delayed by steak" (specific cause).
• If an item is remade — "Remake: ticket 42, [dish name], reason: [burn/undercook/missing]. ETA [minutes]."
• Guest-facing script for servers — Short, polite lines to communicate delays without overpromising: "We're just finishing your dish to make sure it's perfect. It will be out in about X minutes — would you like a complimentary side while you wait?" (Modify per policy.)

Visual pass layout checklist

Arrange the pass to support consistent inspection and flow. Post this checklist above the pass and use a quick walkthrough at shift start.

1. Clear pickup area with visible ticket queue.
2. Designated staging spots for short, medium, long items labeled and separated.
3. Thermometer, finishing tools (sauce spoon, heat lamp), napkin/towel, and garnish station nearby.
4. Visible communication board (whiteboard or digital) showing delays and responsible station.
5. Tray or bin for remakes with time-of-remake noted.

Escalation flow for delayed items

Make escalation fast and predictable. Use time-based triggers tied to your complexity bands.

1. 0–hold window: Expeditor manages sequencing and communicates with stations. Quick fixes happen at the pass (finish, sauce, garnish).
2. Hold window + 1–2 minutes: Expeditor marks the ticket as delayed, informs runner/server, and sets a new ETA. If issue is station-related, expeditor asks for priority rework.
3. Hold window + 3–5 minutes: Shift leader is notified. Consider temporary guest compensation options (free appetizer, expedited replacement) per policy, and assign a staffer to clear the backlog.
4. Repeated or systemic delays: Log the event in the end-of-shift report and initiate a short root-cause check (equipment, recipe clarity, miscounting, staffing) next non-service period.

Sample guest communication scripts

• Server to guest when dish is delayed: "I'm sorry — your [dish] is taking a touch longer. The kitchen is finishing it to make sure it's right; it will be out in about X minutes. Can I bring you a small salad while you wait?"
• Server to guest when offering a remake/comp: "We want you to enjoy this. We can remake your [dish] right away or offer [comp option]. Which would you prefer?"

Pass audit checklist for shift leader

Use this short audit during service or at periodic checks. Score each item Yes/No and capture corrective notes.

• Is an expeditor clearly identified and actively managing the pass?
• Are tickets batched and sequenced for tables consistently?
• Are short/medium/long staging areas labeled and used correctly?
• Are plate temps and portion sizes checked before send?
• Are callouts clear and standard language used by staff?
• Are remakes staged with timestamps and recorded?
• Was any delayed item escalated properly and recorded in the shift log?
• Remake count this check (number): ______; any repeated causes noted?

Metrics to watch

• Remake rate (remakes / total tickets) — target: as low as practicable; track trends.
• Average pass hold time by complexity band — know your baseline and reduce it incrementally.
• Ticket-to-table time distribution — identify bottlenecks and peak pressure points.
• Guest complaints tied to timing/quality — capture and act on root causes.

Training & continuous improvement

Practice pass language and an emergency escalation drill in pre-service huddles. Run short, focused retros after service: what delayed, who fixed it, and one improvement to try next shift. Track improvements in your shift log and review weekly.

How to start using this playbook tonight

1. Post the timing bands and pass layout checklist where everyone can see them.
2. Assign an expeditor and run one two-minute walk-through of callouts during pre-service.
3. Use the audit checklist once in the first hour and again mid-service; capture two improvement ideas.
4. Log remakes and delays in the shift report so you can track trends and fix common causes.

Keep the language simple, measure what matters, and iterate. Small, consistent improvements at the pass yield big wins for quality, speed, and morale.