Running service
The rush-hour playbook: when 20 tables order at once
What to do on the board when every table orders in the same ten minutes: who confirms, kitchen pacing, sold-out dishes, waiter calls, checks and closing.
WaiterPilot Operations
Updated , 8 min read
The short answer
Give every screen one owner before the doors open, mark sold-out dishes early, and work the board by colour. First orders wait for a person to confirm, so the confirmer sets the pace; later rounds go straight to the kitchen. Answer waiter calls with Ack, bring the card machine when the check request says card, and close each table as the party leaves.
Key points
- When guests order from their phones, order-taking stops being the bottleneck; the person confirming first orders and the kitchen become it.
- On the WaiterPilot board, waiting orders and calls change colour at 1, 5 and 10 minutes, which tells you where to send help.
- Holding first orders to pace the kitchen has a cost: guests see Awaiting staff and can cancel while they wait.
- Close every table when the party leaves; until you do, new orders from that table skip the staff check.
- The tool doesn't add kitchen capacity, take payment or print tickets, so plan those parts of the rush yourself.
On this page
When 20 tables order at once, give every screen one owner, mark sold-out dishes before they run out, and work the board by colour. Guests ordering from their phones means nobody waits for a server to reach them. The bottleneck moves to the person confirming first orders and to the kitchen, and that’s where your plan should go. Answer waiter calls with Ack, bring the card machine when the check request says card, and close each table as the party leaves.
This playbook follows the WaiterPilot board. The roles, the pacing questions and the checklist work with any guest-phone ordering tool.
What actually breaks when every table orders at once?
Short answer: the queue moves. Guests stop waiting for a server and start waiting for a confirmer, the kitchen or the card machine.
| Step | Bottleneck with server-taken orders | Bottleneck with guest-phone ordering | What to plan |
|---|---|---|---|
| Ordering | Servers walking table to table | Gone: each table orders when ready | Nothing |
| First-order check | None | One person reading and confirming new tables | A named confirmer and a backup |
| Kitchen | Orders arrive spaced by the servers’ walking | Orders can arrive in a wave | Pacing and honest wait quotes |
| Second rounds | Guests flag someone down | Gone: they go straight to the kitchen | The kitchen and bar see more tickets sooner |
| Requests and calls | Guests wave | Calls on the floor screen, with minutes waiting | Someone watching the floor screen |
| Paying | Fetching the check, then the card machine | Check request arrives saying cash or card; payment still with staff | Card machines charged and at hand |
| Till | Orders entered as taken | No POS or printer connection: someone re-keys | Who enters sales, and when |
The second and third rows are where rushes go wrong. Servers used to pace the kitchen without meaning to, because they could only take one table’s order at a time. Remove that and the kitchen sees the true demand all at once.
A Cornell report hints at the size of the shift: in one restaurant, server time per table fell 65% when guests ordered and paid on a tabletop device, from 10 minutes 16 seconds to 3 minutes 30 seconds, with only 7 tables observed in that group (Susskind and Curry, Cornell, 2016, p. 6). The time doesn’t vanish. It moves to the kitchen and the floor.
Before the rush: what should you set up?
Short answer: ten minutes of decisions before doors open saves an hour of confusion at 8 pm.
- Name a person for each screen. Main board (confirmer), kitchen screen (the pass or head cook), floor screen (servers). Write the names on the pass. The stations are tabs on the same staff board, running on phones or tablets you already have.
- Name a backup confirmer. The one who steps in when first orders wait more than 5 minutes.
- Mark sold-out dishes now. From an owner’s or manager’s phone, and WaiterPilot stops offering them right away. Include anything that will run out by 8 pm.
- Check staff phones. Charged, logged in, alerts on. On an iPhone, lock-screen alerts need the board added to the Home Screen.
- Agree the till rule. WaiterPilot has no POS connection, so orders are entered in the till by hand, either as they’re confirmed or when the table asks for the check. Pick one for the night.
- Say the allergy rule out loud. Any allergy mention means a person goes to the table, and staff have the final say.
- Put printed menus at hand. For guests who prefer them, and as the fallback if the connection drops.
During the rush: how do you read the board?
Short answer: by colour and by column. Waiting orders and calls change colour at 1, 5 and 10 minutes, so the board tells you where the room is falling behind.
| You see | It means | Do this | Who |
|---|---|---|---|
| A ticket in Awaiting staff | A table’s first order, waiting for a person | Read the notes, tap Confirm; it moves to In kitchen | Confirmer |
| Awaiting tickets that have changed colour at 5 or 10 minutes | The confirmer is behind | Backup confirmer takes the oldest ones | Backup |
| An order that looks wrong (wrong table, duplicate, a prank) | Something a person should catch | Tap Reject, then speak to the table | Confirmer |
| An allergy note | A stop | Walk to the table before confirming; see food allergies and QR ordering | Allergy lead |
| A note in a language nobody reads | Notes are not translated | Go to the table, or use a translation app | Confirmer |
| A dish in In kitchen that just ran out | The kitchen can’t make it | Tap Out of stock: it comes off the bill and the guest sees a note; a server offers an alternative | Kitchen, then server |
| A dish that will run out for the night | More guests will try to order it | Mark it sold out from an owner’s or manager’s phone | Manager |
| “Wants a waiter” on the floor screen, with minutes waiting | A guest called from their phone | Go to the table, tap Ack | Floor |
| A check request marked card | The table wants to pay | Bring the check and the card machine together | Floor |
| A party asking to move | Different table needed | Move the party to the new table on the board | Floor or confirmer |
| A party leaving | The table is done | Close the table | Floor |
Two rules hold the rest together. Mark Served when food reaches the table, so the guest’s phone and the board agree. And close every table when the party leaves: until staff close it, new orders from that table go straight to the kitchen without a staff check, so the next party at that table would skip the first-order check.
Should you use Confirm to pace the kitchen?
Short answer: only lightly. It’s a brake with side effects.
Holding a first order for a minute or two can space out a wave of new tables. But the guest sees “Sent. Waiting for staff to confirm” on their phone, with a Cancel order button, and a guest can cancel an order while it’s still awaiting staff. Hold it for long and some will. And it only works on first orders: second rounds from seated tables go straight to the kitchen whatever the confirmer does.
Better tools for a slammed kitchen:
- Quote a time at the table. A server who says “the kitchen’s busy, mains are about 25 minutes” loses fewer guests than a ticket that sits.
- Mark slow or scarce dishes sold out for the peak, and back on after.
- Let the bar run. Drinks go out fast and keep a waiting table happy.
- Watch the In kitchen column. If it keeps growing, tell the floor before guests start calling.
A worked rush: Casa Olivo, 8:00 to 8:30 pm
Casa Olivo is a fictional restaurant (an example, not a customer). The times are illustrations, not measurements.
Casa Olivo has 20 tables. At 7:55 pm a large party leaves and the host seats a wave of walk-ins. Ana confirms first orders on a tablet at the host stand; Luis is her backup; Marta and Sami work the floor; Rui runs the pass.
| Time | What happens | Who acts |
|---|---|---|
| 8:00 | Six new tables scan and start chatting. Two tables already seated order a second round, which goes straight to the kitchen. | Nobody yet |
| 8:04 | Five first orders arrive in Awaiting staff. One has a note in French. | Ana confirms four, walks to the French note |
| 8:06 | Two Awaiting tickets pass the 5-minute colour change while Ana is at the table. | Luis confirms them |
| 8:09 | Table 4 asks for the check, marked card. | Marta brings the check and the card machine |
| 8:12 | The kitchen runs out of the lamb. Two lamb dishes are already on In kitchen tickets. | Rui marks both Out of stock; Sami tells the tables and offers the fish; Ana marks the lamb sold out from her phone |
| 8:15 | A guest at table 11 calls a waiter from their phone. The floor screen shows “Wants a waiter”. | Sami goes, taps Ack |
| 8:20 | Table 4 leaves. | Marta closes table 4 |
| 8:22 | A new party sits at table 4 and orders. Because the table was closed, their first order waits in Awaiting staff. | Ana confirms |
| 8:30 | The board is mostly In kitchen and Served. The In kitchen column is long: mains are running late. | Marta and Sami quote times at their tables |
Notice what nobody did: nobody walked to a table just to take an order, and nobody walked to the till just to print a check.
How fast do orders reach the board?
Short answer: within seconds. In our test on 15 Oct 2026, four confirmed orders reached the staff board in 0.8 to 2.7 seconds, from one table at BroadNet.AI’s quiet demo restaurant, with the guest in a phone-sized browser window and the board in a desktop browser. That’s four samples, not a full Saturday, and the time a person takes to tap Confirm comes on top. How it works shows the real screens.
The one-page board guide
Print this and pin it by the pass:
- Awaiting staff: read the notes, tap Confirm. Allergy or foreign-language note: go to the table first.
- Colour changes at 1, 5 and 10 minutes. An Awaiting ticket past 5 minutes: the backup confirmer steps in.
- Looks wrong: Reject, then talk to the table.
- Ran out after ordering: Out of stock on the dish. It comes off the bill. Offer an alternative in person.
- Will run out tonight: manager marks it sold out from their phone.
- “Wants a waiter”: go, tap Ack.
- Check request: cash or card is on it. Bring the machine with the check. Payment is with us, not the app.
- Served: tap it when food lands.
- Party left: close the table. Always.
- Connection down or guest prefers paper: printed menu, take the order by hand.
After the rush: what should you check?
- Every table is closed.
- The till matches. Compare what was rung in with the live bills for the night’s tables.
- The owner’s analytics. Time to staff confirm, kitchen time and call-answer time show which part of the rush was slowest.
- Questions the chat couldn’t answer. Add the answers to the menu before the next service.
- Sold-out dishes back on for tomorrow, if the kitchen is restocked.
What to do next
Run the setup list before your next busy night, and try the board yourself: try a sample order and watch it move from Awaiting staff to Served. For the full flow, read what QR table ordering is, and for nights when you’re also a server down, 9 jobs you can take off your servers’ plate.
Questions readers ask
How do you speed up restaurant service during a rush?
Remove the waits that don't need a person: let guests order and ask for the check from the table, and bring the card machine with the check. Then put one named person on each job, so nobody wonders whose turn it is.
Who should confirm first orders on a busy night?
One named person who can see the room, usually a host, manager or lead server, with a backup ready when waiting tickets pass 5 minutes. The first order at each table waits for them, so a slow confirmer slows every new table.
Can I hold orders to stop the kitchen getting slammed?
You can hold a first order for a minute or two, but guests see Awaiting staff and can cancel while it waits, and later orders from seated tables go straight to the kitchen anyway. It's usually better to tell guests the kitchen is busy and quote a time.
What happens when a dish runs out mid-service?
Mark it sold out from an owner's or manager's phone so WaiterPilot stops offering it. If it's already on a ticket in the kitchen, staff mark that dish Out of stock: it comes off the bill and the guest sees a note, and a server offers an alternative.
How fast do orders reach the staff board?
Within seconds. In our test on 15 Oct 2026, four orders reached the board in 0.8 to 2.7 seconds at a quiet demo restaurant. The time a person takes to tap Confirm comes on top.
Sources
- The Influence of Table Top Technology in Full-service Restaurants (Cornell Hospitality Report 16(22)), Susskind and Curry, Cornell Center for Hospitality Research, 2016-10 (checked 2026-10-15)
