Service Flow and Rush Management

## Beyond the basic sequence\n\n«Bar Workflow» lays out the general shape of service — take the order, make the drink, hand it off. This article is about what happens when ten orders arrive in ninety seconds and the basic sequence alone isn't enough: how tickets get sequenced, how drinks get batched, how positions on the bar talk to each other, and how to recover gracefully when the queue backs up anyway.\n\n## Ticket sequencing under volume\n\nStrict first-in-first-out feels fair but is often the slowest way to run a rush. Instead, sequence by what actually shortens total wait time across all guests:\n\n- **Group by drink family, not by arrival order.** If three iced lattes and two drip coffees are queued between two hot lattes, pull the iced drinks and drip together — they share cold-side prep and don't compete for the steam wand — then knock out the hot drinks as a pair.\n- **Protect single-shot, fast items from getting stuck behind complex ones.** An espresso or an Americano that takes forty seconds shouldn't sit behind a multi-modification specialty drink that takes three minutes — pull it in the gap.\n- **Call times, not just order names.** The person on the machine should know roughly how long each drink in the queue takes so the next one can be started while the current one finishes steaming or resting, not after.\n\n## Batching similar drinks\n\nBatching is the single biggest lever during a rush because it turns repeated setup cost into a one-time cost:\n\n- Steam one larger pitcher for two or three milk drinks of the same milk type and texture instead of steaming separately for each — split the pour at the end.\n- Pull shots in pairs on a two-group machine when the next two tickets both need espresso, rather than single-shot, walk away, come back.\n- Stage cups for a batch together so the barista isn't restocking mid-batch.\n\nBatching has a limit: don't batch drinks with meaningfully different milk temperatures or textures (a flat white and a milky latte) into the same steam pour — quality loss there costs more time in remakes than the batching saved.\n\n## Communication between bar positions\n\nA multi-person bar fails or succeeds on a few short, consistent verbal habits, not on elaborate ones:\n\n- **Calling movement:** «behind», «corner», «hot» — said every time, not just when convenient.

Silence is how collisions and burns happen during a rush.\n- **Calling handoffs:** the person finishing a drink says what it is and where it's going before setting it down, so the runner or the guest-facing position doesn't have to guess or double-check.\n- **Calling exceptions out loud immediately:** an allergy modification, an oat-milk substitution, a remake — these get repeated back, not just acknowledged with a nod, because a missed allergy call is a safety issue, not just a service one.\n- **One person owns the queue view.** On a busy bar, one position (often the closest to the ticket screen) should be the one calling sequence and priority, so two baristas aren't independently deciding what's next.\n\n## Graceful recovery when the queue backs up\n\nEven a well-run bar backs up sometimes. What separates a bad rush from a recovered one is what gets prioritized and what gets communicated:\n\n- **Prioritize drinks closest to completion first.** Finishing five drinks that are one step away clears more tickets, faster, than starting five new ones — this shortens the visible queue and gives waiting guests something to see move.\n- **Protect quality on the drinks already in progress over starting new ones perfectly.** A slightly delayed but correct drink beats a fast, wrong one that generates a remake and a second wait.\n- **Communicate proactively, not only when asked.** A short, honest update — «you're next, about two minutes» — reduces perceived wait time even when actual wait time doesn't change. Silence is what makes a queue feel out of control, not the queue length itself.\n- **Reset visibly once it clears.** After a backup, briefly reset the pour order, wipe down, and confirm ticket count matches drinks made — a rush that ends with a mismatched ticket count turns into a second rush of confusion.\n\nThe goal of rush management isn't to prevent every backup — it's to make backups short, predictable, and calmly communicated, so both the team and the guests experience it as a busy bar doing its job rather than a bar that has lost control.