When the Rush Hits, Orders Shouldn't Fall Apart

Illustrative scenario: it's 8:40 on a Thursday evening. A table of six orders at once. One guest wants the burger without onions, another wants the sauce on the side. The waiter repeats it back, walks to the counter and keys the order in between two takeaway customers. The onion note makes it in. The sauce request doesn't. The kitchen ticket simply reads “Burger × 2”. Twenty minutes later a plate comes back, and the next table is still waiting for drinks that nobody started.

None of that needs a bad employee. It needs a rush, a handover, and a detail that lived in someone's head for thirty seconds too long.

Where orders actually break

Look closely at returned dishes and late tables, and most problems trace back to one of four handovers.

• From guest to order taker: a request is said out loud but never written down.
• From order taker to system: the order is written on a pad and entered later, sometimes in a batch with others.
• From system to kitchen: notes print in small text at the bottom of the ticket, or an item reaches the wrong station.
• From kitchen to service: an order sits ready, or stuck, and nobody feels it's theirs to chase.

Each handover is a chance to lose something. You won't remove all of them, but you can remove the unnecessary ones and make the rest harder to get wrong.

Fix the capture first

Every time an order is copied from one place to another, it can change. Taking it once, where the guest is, and sending it on without retyping removes a whole category of mistakes.

• Turn your most common requests into options on the item: no onions, sauce on the side, extra cheese, well done. Options are hard to skip; free text is easy to miss.
• Keep free-text notes for genuinely unusual requests, so they stand out when they appear.
• Read the order back to the guest, item by item, including the options.
• Enter the order as soon as it's taken, not when the counter is free.

Allergy requests deserve their own path. The UK Food Standards Agency's allergen checklist for food businesses, for example, asks how staff record a customer's allergen-free order and clearly communicate it to the kitchen, and suggests a responsible member of staff on every shift to manage allergy requests. Whatever rules apply where you operate, the principle travels well: an allergy should never depend on somebody remembering it.

Make the kitchen ticket hard to misread

A ticket is read in two seconds by someone holding a pan. Design it for that moment.

• One item per line, with its options directly underneath, not gathered at the bottom.
• Each station gets only the items it cooks, so the grill doesn't scan past desserts.
• Use the same short item names on the menu, the screen and the ticket.
• Show when the order was sent, so the oldest ticket is obvious.
• Test it: read a real ticket at arm's length during service. If you hesitate, the cook will too.

Give every order an owner

The question that matters at peak time isn't “who made the mistake?” but “who notices when an order has been waiting too long?”. If the answer is “whoever happens to look”, the answer is nobody.

• Name one person at the pass during the rush. Their job is to move food out and chase anything that stalls.
• Agree on a small set of statuses, such as received, cooking, ready and served, and use them the same way every shift.
• Set a simple rule for stuck orders. As an illustration: if a ticket is older than your usual cooking time plus five minutes, the person at the pass asks the station about it.
• Give takeaway and delivery orders a fixed shelf and a check before they leave: items, options, sauces, cutlery.

Review the misses, not the people

For two weeks, keep a short log of every returned dish and late table: what went wrong and at which handover. Patterns appear quickly: the same item, the same station, the same hour. Fixing an item's options or a ticket layout does more than reminding everyone to be careful, and it keeps the conversation about the process rather than about individuals.

Where Zad. fits

Zad. Plus brings dine-in, takeaway and delivery orders from the counter, tablets and self-service kiosks into one order list, and sends confirmed orders to the kitchen display or to each kitchen's own printer. Tables are organised by area, with their seats and status. The Waiter App is designed to let your floor team take the order at the table, with notes and add-ons recorded on the item, and send it to the kitchen in one step.

Software won't make a full dining room calm, and it won't prevent every mistake. What it can do is remove the copying steps and make the order look the same to everyone who handles it. The habits above still decide how the night goes.