Rush Management & Line Control Quick Playbook

Rush Management & Line Control — Quick Playbook

Purpose: Practical, ready-to-use rules and simple tools to keep the pass moving, reduce remakes, and preserve quality during high-volume periods. Use these as defaults your team can adapt and own.

Why this matters

Rushes are predictable events in most kitchens. Without simple, agreed rules and signals, the pass becomes chaotic: plates pile up, orders go cold, remakes increase, and guests (and staff) get frustrated. This playbook turns busy periods into predictable, trainable work instead of crisis management.

Core elements

• Standard timing windows for ticket flow
• Pass control rules and visual signals
• Expedited / temporary menu selections
• Simple temporary role overlays for staffing
• Short communication scripts for common problems
• 5–10 minute training drill teams can run during huddles

Standard timing windows (adapt these to your service model)

Agree on target windows so the whole team has the same expectations. Adjust times after testing.

Pass control rules

1. One owner per ticket at the pass. The expediter owns sequencing and plating decisions for each ticket until the server picks it up.
2. Respect the lane. Each cook is responsible for their station. Do not pull ingredients from someone else’s station without calling it.
3. Stop-the-line triggers. Any crew member can call a soft stop for quality or allergen risk. Soft stops are brief and specific (see scripts below).
4. Hold rules. If a component isn’t ready, hold the whole ticket rather than chasing partial plates unless the guest has already been notified and agreed to partial service.
5. Remake policy. Define a quick acceptance check at the pass: temperature, portion, garnish, and plating. If it fails one of these, it’s remade immediately.

Visual signals & simple aids

• Traffic-light board: Green = normal; Yellow = approaching peak (staff at 80% load); Red = rush mode (activate overlays).
• Pass zones: Put labeled areas (Expo 1, Expo 2) so servers know where to pick up and where to stage TO GO orders.
• Timer/clock at expo: Visible timer to age-check tickets visually (older tickets flagged by color tags or a simple minute sticker).

Expedited & temporary menu selections

When load exceeds capacity, switch to a short "Rush Menu" with these rules:

• Limit build complexity—items that require fewer shared components or long cook times.
• Keep price/margin in mind—avoid items that lose profitability when expedited.
• Mark Rush Menu items clearly on POS for faster routing and correct portioning.
• Rotate items back in after rush; document any adjustments needed.

Temporary role assignments (staffing overlays)

Use short overlays for expected volume. Each overlay should be one line, pinned where staff can see it.

Communication scripts (short & specific)

Teach short, calm phrases so the line doesn’t get noisy and ambiguous calls stop the flow.

• Expedite call: "Expedite — order 237: two burgers, one salad — 3 minutes to pass."
• Stuck ticket: "Hold 237 — missing fries, ETA 90 seconds."
• Quality hold: "Hold 237 — temperature/garnish issue; remake ordered."
• Allergen / safety hold: "Allergy hold — do not plate. Manager needed at pass."

Short training drill (8–12 minutes)

Run this during a pre-shift huddle. Repeat weekly until new staff are comfortable.

1. Objective (1 min): Practice pass ownership, timing, and communication under pressure.
2. Setup (1–2 min): Choose a real menu subset. Assign roles: lead expediter, two cooks, one runner, one server.
3. Simulated rush (4–6 min): Send a rapid stream of 5–7 tickets (shouted or printed). Use a timer. The expediter sequences, cooks produce, expo plates, runner clears, server collects.
4. Debrief (2–3 min): What worked? Where were the bottlenecks? One action to improve next shift.

Quick start checklist (use at the start of a predictable rush)

• Set traffic-light to Yellow/Red as applicable.
• Assign named expediter and confirm overlay.
• Activate Rush Menu items on POS if needed.
• Set visible timer and age-check method for tickets.
• Run 60-second alignment: remind scripts and stop-the-line rule.

Common mistakes & fixes

• Chaotic calling: Fix with short scripts and one owner at pass.
• Partial plating: Either plate complete or agree with server on partial service rules.
• Unknown roles: Use pinned overlays and name the expediter aloud at the start of rush.

How to adapt and measure

Track a simple set of KPIs during a week of rushes: average ticket-to-pass time, remakes per 100 tickets during rush, and customer complaints about speed. Use these numbers to refine timing windows and staffing overlays.

Close: This playbook is intentionally compact so teams can adopt it quickly. Start with the templates, measure results for one week, then iterate. Document any local changes so knowledge doesn’t live only in people’s heads.