Expeditor & Pass Management Playbook

Purpose

Make the pass reliable so food leaves the kitchen hot, complete, and accurate. This playbook defines roles, timing windows, plating and visual checks, communication scripts, and escalation steps to prevent remakes, reduce slow tickets, and keep guests happy during peak service.

How to use this playbook

Use these rules as a starting point. Teams should agree on local thresholds, rehearse radio scripts, and run spot-checks during service. Tailor timing windows and station maps to your menu, equipment, and kitchen layout.

Core responsibilities

• Expeditor (Pass Lead): Owns the pass. Reads tickets, sequences plates, performs final quality checks, calls tickets to service, and enforces timing rules.
• Station cooks: Build items complete and to spec, call ready to pass when plating is finished, and communicate problems early.
• Plating/Expo helper (when used): Assembles composed plates, follows plating rules, and notifies Expeditor if components are missing or incorrect.
• Server/Runner: Watches the pass, confirms order details when called, and notifies expeditor of guest-level notes (allergies, timing, VIPs).
• Manager on duty: Supports 'stop the line' calls, resolves conflicts, and approves remakes or exceptions.

Station map & setup

Post a simple pass map with station names, typical items, and responsible cooks. Keep critical tools (thermometers, garnish station, plating templates) at hand. Label hot and cold zones and ensure heat lamps or cold rails are functioning.

Order sequencing & priority rules

1. Group items by ticket and by priority (fire, VIP, allergy, dine-in/TOGO).
2. Fill plates in logical order to minimize handoffs and cross-traffic.
3. Always finish the most complete tickets first when those items meet quality checks.

Plating rules & visual quality checklist (Expeditor checklist)

• Is the plate complete? (All components present and portioned.)
• Is plating consistent with the spec? (Garnish, wipe rims, arrangement.)
• Is there visible damage, overcooking, undercooking, or incorrect ingredient?
• Temperature quick-check: hot items feel hot to the touch or use thermometer spot-checks when in doubt.
• Allergen & modification check: confirm substitutions or allergy notes are honored and visibly flagged.

Suggested timing windows (starting points — adapt locally)

Agree these targets with your team and measure. They should be adjusted by menu and kitchen layout.

• Hot composed items: Pass within 0–3 minutes after plating. 3–5 minutes requires temperature check and possible rework. >5 minutes = consider remake or hot holding protocol.
• Cold items / salads: Pass within 0–5 minutes. >10 minutes = check quality and temperature.
• Sauces/finishers waiting on assembly: No more than 2 minutes of wait once plating begins.

Clarify what 'pass time' means in your kitchen (from ticket completion to call, or from cook finished to server pickup).

Pass call procedures & language

Consistent language reduces confusion. Keep calls short and specific. Train servers to listen and confirm.

• Standard call: "Pass up — 12, 3 top, two apps."
• Hot hold / temp-check call: "Hold — 12, temp check."
• Allergy/Modify flag: Start call with "Allergy" and repeat the item: "Allergy — 14, no nuts."
• Last call / fire: "Fire 8 — drop now." (Use sparingly for urgent tickets.)

Sample radio scripts

• Expeditor to server: "Pass ready — ticket 42, two mains, two sides. Seat 5, table 12."
• Cook to expeditor: "Up — 42 main is up, plating completed."
• Server to expo (if issue): "Expo, please hold table 9 — allergy confirmed, chef to check."
• Expeditor to manager: "Stop the line — ticket 37 missing protein, need decision."

Stop the line triggers & escalation steps

A 'stop the line' is a tool, not a punishment. Use it early to prevent a larger guest issue.

1. Triggers: missing critical component, unsafe temperature, allergy risk, repeated remakes from same station, or equipment failure that affects quality.
2. Immediate actions: expeditor halts outgoing tickets, calls manager, identifies minimally invasive fix (remake, hot-hold, server communication to guest).
3. Manager response: make quick decision—approve remake, divert customer, or offer compensation. Log the incident for shift debrief.

Remake policy

• Remake when safety, allergy risk, or significant quality failure occurs.
• When remake required, mark ticket and record reason on the shift log (station, cause, time).
• Limit remakes that are due to minor presentation issues—prioritize guest experience and speed when acceptable.

KPIs & quick metrics to track

• Remakes per 100 tickets (goal: decrease over time).
• Average pass-to-pickup time and percentage of tickets meeting timing window.
• Number of stop-the-line events per week and root causes.
• Temperature compliance spot checks (percent within acceptable range).

Training & shift checklist

Use this during pre-service and onboarding.

1. Review station map and responsibilities.
2. Run 2–3 radio scripts aloud with servers and cooks.
3. Practice one plating standard with expeditor feedback.
4. Agree timing windows for the night and write them on the expo board.
5. Assign who will log remakes and stop-the-line events.

Shift close: quick debrief

Record 3 things that went well and 3 things to improve about pass performance. Capture at least one specific action for the next shift (e.g., adjust timing window, rehearse a problematic plate).

Adapting this playbook

Customize thresholds, scripts, and station responsibilities to your menu, equipment, and layout. Consider adding a simple interactive pass-check form (timers, temperature entries, remake reasons) to collect data and drive improvement.

Note: These are practical starting points, not prescriptive rules. Measurement, local adaptation, and regular rehearsal will make pass management work for your team.