Rush Management Quick Play (1–page tactical guide)

Rush Management Quick Play — 1‑page Tactical Guide

When the dining room fills fast, small choices make the difference between a controlled rush and chaos. Use this compact routine as your team’s shared playbook: clear triggers to start, quick pre-rush checks, priority rules to follow while it’s busy, a short recovery checklist, and a short debrief script to capture fixes before you forget them.

When to pull the rush play

• Trigger examples (adapt to your service): line of 6+ parties waiting, average ticket time rising above target, or reservations pushing capacity in the next 20 minutes.
• Call it out loud: any manager or lead can declare “Rush Play” and the team immediately follows the steps below.

Pre-rush (last 15 minutes) — quick checklist

• Confirm mise en place at every critical station: proteins, sides, garnishes, sauces.
• Start expedite pre-cook items where safe (rice, roasted veg, holding units) but avoid overcooking.
• Assign roles: Runner (clears/plating support), Backup Cook (covers critical station), Expediter (manages pass), Support Server (buses/takes payments), Manager (floats, handles seating/issues).
• Confirm POS modifiers and prep-cook flags (allergens, temp holds, special requests).
• Set a visible communication signal (e.g., “Rush flag up” or colored ticket) so front and back know plan’s active.

During the rush — operating rules

• Suspend non-essential tasks: deep cleaning, long prep for tomorrow, and training drills. Protect core work.
• Batching rules: group identical or similar tickets to reduce repeated station setup. Example: cook two identical proteins at once, plate when both ready.
• Prioritize hot‑hold items and time‑sensitive plates (fry items, delicate proteins). Use a two‑person plating rule for complex dishes: one cooks, one plates/inspects.
• Keep the pass clear — only plated items and outgoing tickets on the pass. Runner removes empty plates and sends drinks/condiments as soon as ready.
• Limit new request variety temporarily (e.g., freeze extensive modifications) and politely offer the next-best standard option when safe to do so.
• Use short, exact communication: call items by name and ticket number. Avoid long explanations on the line.
• Manager or lead monitors ticket backlog and decides when to open/close seating or pause online orders if necessary.

Roles — what each person focuses on

• Expediter: Runs the pass, prioritizes tickets, calls for plating, does final quality check.
• Runner/Support server: Clears, restocks small items, assists plating, delivers food to tables when needed.
• Backup cook: Rotates in to support the busiest station, handles simple assemblies, and keeps tickets moving.
• Manager/Lead: Controls seating flow, handles any guest issues, communicates with front-of-house, authorizes temp menu limits if required.

Post-rush — rapid recovery checklist (first 10–20 minutes)

• Restock critical stations (proteins, sides, garnishes, sauces) — note what ran low.
• Reset the pass: clear debris, wipe, reorganize plating tools.
• Run temperature checks and log any holding equipment out of range.
• Quick clean sweep of service items and trash to restore workspace flow.
• Record remakes and reasons (short note) for immediate fixes and later analysis.

Short debrief script — capture fixes in 3 questions (2–4 minutes)

1. What worked? (One quick item to keep doing.)
2. What created the biggest delay or quality risk? (One cause.)
3. One small fix we can try next time. (Assign an owner to try it.)

Quick decision rules (examples to adopt)

• If ticket queue > X (your team’s safe backlog), stop seating new guests for 10 minutes and clear backlog first.
• If remake rate > 5% of covers during a rush, pause complex mods until staff recovers.
• If any critical station is down (equipment or person), manager deploys backup cook immediately and prioritizes simpler menu items.

KPIs & things to watch in the moment

• Tickets in system / oldest ticket age
• Average ticket time vs target
• Number of remakes and out‑of‑stock items
• Guest wait time for seating or pickup

Adaptation notes

Treat this playbook as a baseline. Each kitchen should set its own numeric triggers (e.g., backlog count, ticket time targets) and test one small process change at a time. Keep the language simple so any team member can trigger the plan.

Keep it visible: Post the 3 debrief questions and current role assignments on a small whiteboard near the pass. After a few shifts, update the playbook with the fixes that actually worked.