The Short-Order Line at 6:40 PM
You run a 120-seat bistro. Saturday service peaks between 6:30 and 8:30 PM. At 6:40 PM the expo window backs up: ticket times hit 28 minutes against a 16-minute target. The sauté station is also finishing all garnishes and plating desserts because the pantry cook called out and no replacement was scheduled. The grill cook is competent but has been on station 11 hours. Two servers are comping drinks to manage a four-top that has waited 35 minutes. Walk-in inventory is fine; the bottleneck is purely labor and flow. Your sous chef is off tonight. You have one cross-trained prep cook who knows pantry but has never worked a Saturday peak.
1. What is the first corrective action, and why is it prioritized over adding a cook to the sauté station?
Read the worked answer
The first move is to relieve the sauté station of its non-sauté work, not to add bodies to it. Sauté is the constraint: it is simultaneously producing entrées, garnishes, and desserts, so every dessert ticket steals capacity from the highest-value, longest-lead items.
Reasoning:
- Identify the true bottleneck. Ticket times rose when one station absorbed three task streams. Adding a cook to a station that is already at capacity on its core work doesn't fix the mixed-workload problem.
- Pull the prep cook into pantry for cold garnishes and desserts only - a narrow, well-defined scope they can execute under supervision, which limits the risk of using an untested person at peak.
- Sequence the relief: clear the current expo backlog before new tickets are released, then reassess.
- Protect the grill cook - 11 hours on station at peak is a safety and quality risk; plan a relief break within the next 30 minutes even if it costs a few minutes of throughput.
Adding a warm body to sauté without separating the task streams would leave the constraint unchanged while adding coordination cost on a crowded line.
2. The four-top has now waited 40 minutes. How do you handle the table, and what do you change so this does not recur next Saturday?
Read the worked answer
At the table: the manager (not the server) visits, owns the delay without blaming staff, states a realistic time for the next course, and offers a specific remedy - e.g., a comped appetizer or dessert and a drink - rather than open-ended comping. The servers have already been comping drinks reactively; the manager should consolidate that into one deliberate gesture so cost stays controlled and the guest feels attended to.
Structural fix for next Saturday:
- Schedule pantry coverage explicitly - a call-out with no backup is a scheduling design flaw, not bad luck. Build a named on-call or cross-trained backup into the Saturday roster.
- Cross-train the prep cook on pantry during a slow service first, so peak deployment isn't their first exposure.
- Separate dessert plating from sauté, or pre-plate components so desserts don't compete with entrées.
- Set a ticket-time trigger (e.g., 20 minutes) that automatically escalates to the manager and authorizes a defined recovery gesture, so recovery is consistent and costed rather than improvised.