Rush Management & Line Control Playbook

Welcome — why this playbook matters

Rushes are predictable and unpredictable. When a rush hits, the goal is not simply to move food faster — it's to keep the experience reliably good while protecting your team from burnout. This playbook gives concise, practical actions for pre-rush preparation, surge staffing, rapid line-balancing, ticket triage, front-of-house support options, quick quality checks to avoid remakes, and post-rush recovery and learning.

When to use this

Use these tactics before known peaks (service windows, reservations blocks, events), and as an immediate playbook during unexpected surges (walk-in spikes, delivery windows, kitchen slowdowns). Many items are role-specific; put the right person in charge of execution.

Primary hunger served

Control service during peaks so speed improves without harming quality or staff morale.

Quick roles & responsibilities

• Manager on duty (MOD): authorizes surge staffing, monitors ticket backlog, communicates with guests, and makes ticket-capping decisions.
• Expediter/Expo: leads line balancing, triages straggler tickets, assigns plate checks, and coordinates FOH/BOH communication.
• Line lead / Chef: reassigns stations, simplifies orders when needed, and verifies critical quality checks.
• Servers / Hosts: set guest expectations, manage waitlist/timing, and escalate issues to MOD or expo.

Triggers — quick decision guide

Consider invoking the full rush plan when any of the following occur:

• Ticket backlog exceeds X minutes (set locally, e.g., 8–12 min average ticket time)
• More than Y simultaneous ticket prints (e.g., 6+) in the kitchen
• Multiple remakes or quality complaints within a short window
• Reservation surge or event with > Z covers per 15 minutes

Pre-rush checklist (30–60 minutes before peak)

Quick actions that materially reduce chaos during a rush.

• Confirm staffing levels and call in approved surge staff if needed.
• Stage mise en place: top-up common proteins, pre-portion garnishes, ready sauces, and hot/cold holding stations.
• Run brief 5-minute huddle: clarify roles, expected volume, key menu items that may slow the line, and who is authorized to cap tickets.
• Prep FOH messaging: wait estimates, available substitutions, and whether ticket capping will be used.
• Ensure communication tools are working (POS notes, expeditor headset, pass area visibility).
• Check equipment and critical stations (broilers, fryers, ovens) for readiness and any warning signs.

Surge staffing & short-notice options

• Reassign cross-trained staff from lower-impact areas (e.g., bussing or prep) to line support or expo.
• Use a dedicated runner for expo to free cooks for cooking tasks.
• Implement shortened-service positions: a single person for garnish/top-off rather than full station coverage.
• Limit complex modifiers: temporarily block high-variance modifiers on POS if they disproportionately slow throughput.

Rapid line balancing (in-shift tactics)

Small, immediate changes that smooth flow.

• Simplify the line: temporarily move a station to produce only high-volume items.
• Use batching where safe and reasonable: produce components in small batches to reduce ticket-to-ticket variability.
• Assign a floating support cook to the bottleneck station until backlog reduces.
• Implement a visual board or ticket stack so the expo and line share a single view of priority tickets.

Straggler ticket triage (decision matrix)

Sort late or stalled tickets quickly using three categories:

1. Fast recoverable: minor hold-ups (missing garnish, quick reheat). Action: finish and prioritize for immediate pass.
2. Requires remake: clear quality failure (undercooked, wrong protein). Action: remake with expedited flag and notify server of delay.
3. Compromised but salvageable: close to serviceable (small plating or portion issue). Action: correct at pass with minimal rework and offer FOH mitigation if needed.

Always mark remakes clearly on tickets and track time-to-service for triaged items to avoid repeated delays.

FOH support options — ticket capping & guest communication

Ticket capping is the controlled decision to limit order acceptance to protect existing guests and staff. Use it sparingly and always pair with clear guest communication.

When to cap

• Backlog exceeds safe service window or quality drops are occurring.
• Not enough FOH to reasonably manage new guests without increasing mistakes.

How to cap (script)

Host script: “We’re at peak right now and want to make sure everyone gets the attention they deserve. We’re taking a short break from new orders to get caught up—your wait will be about X minutes. Can I take a drink order while you wait?”

Server mitigation script for a delayed table: “We’re sorry for the delay. Your meals are being prioritized and will be out in about X minutes. May I bring complimentary [bread/drink] while you wait?” (Use your discretion on comps.)

Quick quality checks to avoid remakes

• Assign one person as plate checker during peaks to verify temperature, portion, and garnish before pass.
• Use a 3-second glance rule at pass: is the plate complete and within standard? If no, send back for immediate correction.
• Keep a short checklist at pass: temperature, protein doneness, portion size, sauce placement, allergen alerts.

Post-rush recovery actions

• Call a 10–15 minute cooldown: reassign a couple of staff to deep-clean the pass, re-stock, and check equipment.
• Capture immediate operational notes on what blocked flow (ingredient shortage, equipment, ticket overload, miscommunication).
• Reset mise en place to baseline before accepting normal flow again.

Debrief questions (5–10 minutes, structured)

Use these to turn the rush into improvement opportunities. Keep debriefs short and blame-free.

1. What went well and should be repeated?
2. What caused the biggest delays or quality problems?
3. Were staffing and station assignments effective?
4. Were any menu items consistently problematic?
5. What single change would make the next rush easier?

Key metrics to watch

• Average ticket time (target depends on kitchen style — set a local threshold)
• Number of open tickets (a rolling snapshot)
• Remake rate (%) during the rush
• Guest complaints or comps issued
• Staff reported stress indicators (qualitative)

Common mistakes to avoid

• letting one station stay blocked for too long without relief
• poor communication between expo and servers about delays
• over-relying on comps instead of operational fixes
• not staging enough mise en place for predictable peaks

One-page printable checklist (copy & post)

Pre-rush huddle — roles named; Surge staff confirmed; Menu modifiers limited; Expo assigned; Plate checker assigned; Guest messaging ready; Equipment checked.

Where to go next

Combine this playbook with an interactive pre-rush checklist and a short post-rush debrief form to capture data and trends over time. Revisit the playbook regularly and adapt trigger thresholds and staffing rules to your service style and menu.