Table pacing: stopping four tables ordering at once

At 8.02 on a busy Friday, four tables order their mains within a minute of each other. Fourteen covers land on the grill at once. The grill cook was comfortably keeping up a minute ago; now there are fourteen steaks, two fish and a risotto waiting, and the tickets behind them start to queue. Twenty minutes later, every table in the room is waiting a little longer than it should, and the servers are apologising to guests who ordered after the rush and have no idea why their food is slow.

None of those tables did anything wrong. The kitchen did not slow down. The problem was table pacing: four tables were seated within a few minutes of each other, given menus at the same moment, and so ordered at the same moment. The rush was built at the door twenty minutes earlier.

This guide covers what table pacing means, why a cluster of orders hurts the whole room, how to seat and serve so orders arrive steadily, how the kitchen can hold and release courses, and the signals that keep the floor and the kitchen in step. Every figure in it is an example, not a benchmark.

Table pacing is spreading the moments when tables order, and so the moments when the kitchen receives work, across the service. It works at two levels. Pacing covers, at booking, decides how many guests arrive in each part of the evening. Table pacing, on the night, decides when each table is seated, given menus and has its order taken.

Both matter. A diary that sends forty guests at eight cannot be paced at the door. But a diary that spreads arrivals well can still produce a rush at 8.02 if the host seats every arrival the moment they come in and every server takes orders at the same time. Our guide to pacing covers so the kitchen never drowns covers the booking side; this guide covers the floor.

A kitchen can cook a certain amount at once. Each station, the grill, the fryer, the pans, the pastry section, has a limit: so many steaks on the grill, so many pans on the heat. When orders arrive at a steady pace, each station works within its limit and dishes go out on time. When they arrive in a cluster, the busiest station goes over its limit, and everything queues behind it.

The cost is not just the four tables in the cluster. It is every table after them, whose orders wait behind the backlog, and every table before them, whose next course is delayed because the kitchen is catching up. One cluster at 8.02 can slow the whole room until nine.

Kitchen capacity is not one number. It is a number for each station, and the lowest one decides how fast the whole kitchen can go. If the grill can take twelve steaks comfortably and the menu sends most mains to the grill, the grill is the limit, however much room the other stations have.

Ask the head chef which station runs out first on a busy night, and roughly how many covers' worth of mains it can handle in a quarter of an hour. That figure, for that station, is the most useful number for pacing the room. The traditional kitchen brigade divides cooking into stations for this reason: each has its own capacity, and the slowest sets the pace.

Ticket times show whether pacing is working. A ticket time is how long a table's order takes from being sent to the kitchen to being ready at the pass. On a well-paced night, ticket times for each course stay fairly steady through the service. On a badly paced one, they spike: mains that normally take fourteen minutes take twenty-five after a cluster.

Look at ticket times by station and by course after a busy service. The moments when they spike show where clusters happened, and the station where they spike most is the one to pace around.

The best table pacing starts long before service. If the diary lets forty covers arrive between eight and quarter past, the floor can only do so much. Spreading bookings across the evening, by offering fewer times at the busiest moment and more at the edges, gives the floor a chance.

Look at the bookings for tonight before service with pacing in mind: where are the clusters, and which large tables arrive at the same time? A quiet word with a large party about arriving at quarter to eight rather than eight, or offering half past seven to the next caller instead of eight, can prevent a rush before it is built. Our guide to booking capacity covers limits per half hour.

On the night, the host controls the most important variable: when each table is seated. A few rules turn the seating order into a pacing tool.

The aim is not to keep guests waiting; a few minutes at the bar is barely noticed. It is to turn a wave of arrivals into a steady stream of orders. Our guide to table assignment covers the seating rules in more detail.

Large tables are where pacing matters most. A table of twelve orders as much as four fours, all at once, and usually wants its mains at the same moment. Seat it at a quiet moment if you can, and tell the kitchen when it has been seated.

For the largest tables, a pre-order or a set menu, agreed in advance, lets the kitchen prepare and plan the timing. Even without one, the server can help by taking the large table's order at a moment when no other big order has just gone in, and by letting the kitchen know it is coming.

Between seating and ordering, servers control the pace too. A table seated at 7.50 that is given drinks first, then menus, then has its order taken ten minutes later will order at around eight. If the server greets every table at the same moment and takes every order as soon as menus are down, the server's own section becomes a cluster.

Servers should know where the kitchen is in the service, and pace their own tables accordingly: a little longer with drinks when the kitchen is slammed, straight to the order when it is quiet. This is not about rushing or delaying guests unreasonably, but about the natural rhythm of a table, adjusted by a minute or two.

The kitchen has its own pacing tool: holding courses and firing them when the table is ready. With hold and fire, the order for a table's mains is sent to the kitchen with the starters, but held; the server fires the mains when the starters are nearly finished, and the kitchen starts cooking them then.

Hold and fire spreads the kitchen's work across the meal, rather than cooking everything as soon as it is ordered. It also lets the kitchen see what is coming: held mains for six tables show the grill what the next half hour will bring. Our guide to kitchen tickets that never need a shout covers how tickets carry courses and timing.

On busy nights, someone at the pass, often the head chef or an expediter, watches the tickets and balances the work: calling for the grill to push, holding a course a minute so a table's dishes go together, telling the floor when a station is behind. The pass is where pacing problems become visible first.

The expediter should be able to tell the host, quickly and simply, when the kitchen needs a breather. A single word, agreed in advance, is enough to slow seating for a few minutes.

Walk-ins can help pacing or hurt it. Seated in the gaps between bookings, they fill quiet moments in the kitchen. Seated at the peak, they add to the cluster. When a walk-in arrives during a rush, offer the bar for a few minutes, or seat them and let the server take drinks first.

Early arrivals for bookings are similar. Seating them early adds to the current wave; a drink at the bar until their time keeps the plan intact.

Despite good pacing, kitchens sometimes fall behind: a large table orders unexpectedly, a dish needs remaking, a station has a problem. The response should be agreed in advance, not improvised. Usually it is a short pause in seating, drinks first for new tables, and the manager telling the floor what is happening.

Slowing the room is a decision that affects every guest, the servers and the kitchen, so it should be made by the manager with the kitchen, not by the host alone. Our guide to running the door on a full Friday night covers why that decision should never be the host's alone.

Pacing depends on the floor and the kitchen knowing what each other is doing. The host should tell the kitchen when a large table is seated. The kitchen should tell the floor when a station is behind. Servers should tell the kitchen when a table is lingering over starters, so the mains are not fired too soon.

The simplest tools are often the best: a word at the pass, a sign agreed in advance, a screen that shows the tickets. What matters is that the information flows both ways, before a problem becomes a backlog.

After a busy service, spend five minutes on the evidence. Look at ticket times by station and course, and when the spikes came. Look at the seating times for the tables that ordered just before each spike. Look at when covers arrived across the evening.

The pattern usually tells you what to change: seat large tables further apart, offer different booking times, add a runner on the grill at eight, or ask servers to take drinks first during the peak. Change one thing, then read the next busy night the same way.

Pacing is a team skill. The host needs to understand why staggering seatings matters, servers need to understand why the pace of their first minutes with a table matters, and everyone needs to know the signal for when the kitchen needs a breather.

Explain pacing with the kitchen's numbers: the grill can take twelve steaks comfortably, and four tables ordering at once sends it fourteen. Once the floor understands the kitchen's limit, pacing stops feeling like an arbitrary rule and becomes common sense.

Before service, spend five minutes turning tonight's bookings into a pacing plan. List the arrivals by quarter hour, mark the large tables, and look for the quarter hours where too many covers arrive at once. Then decide how the door will handle them: which arrivals can be offered the bar first, which large tables need to be kept apart, and where walk-ins can fit.

Set a simple seating rhythm the host can follow, such as no more than three tables seated in any five minutes, and no two large tables within fifteen minutes. Share the plan with the kitchen, so the head chef knows when the pressure will come and can plan the stations around it.

The menu decides which station takes the strain. If most mains come off the grill, the grill is the bottleneck however well the room is paced. A menu that spreads mains across stations, some from the grill, some from the pans, some from the oven, lets the kitchen take more orders at once without any single station going over its limit.

Specials can help too. A special that uses a quieter station draws orders away from the busiest one. For large tables, a short set menu, agreed in advance, lets the kitchen prepare much of the work before service and send the whole table's dishes together.

The end of the meal clusters too. Tables seated together tend to want dessert together, and then the bill together. A dessert station swamped with eight tables' orders at once slows every table, and a queue for the card machine at the end of the night holds tables that could be turned.

The same tools work at the end as at the start: servers who notice the room, desserts offered as each table is ready rather than to every table at once, and bills brought promptly when asked for. A table that waits twenty minutes for the bill is a table the next booking waits for.

Lunch has its own pacing problem: many guests arrive at the same time, usually just after half past twelve, and most have less time than at dinner. The room fills in a few minutes, and the kitchen takes most of its orders in a quarter of an hour.

A shorter lunch menu, dishes that can be prepared quickly, drinks and orders taken together, and a few tables seated a little earlier by offering earlier times all help. Our guide to arrival flow covers how the door keeps arrivals moving when everyone comes at once.

An invented restaurant with 80 seats has a familiar Friday problem: at around 8.15, ticket times for mains double, and the room is slow until after nine. The bookings show a cluster of arrivals between 7.45 and 8.00, including two tables of eight.

It makes four changes. Booking times are adjusted so fewer tables can arrive at the peak. The host staggers seatings by a few minutes and keeps the two large tables at least fifteen minutes apart. Servers take drinks orders first for tables seated during the peak. And the kitchen uses hold and fire for mains on every table. On the following Fridays, ticket times stay close to normal through the evening, and the slow hour disappears.

servearound gives the floor and the kitchen the tools pacing depends on. Booking rules set which times each shift offers and how long each booking lasts; there is no automatic cap on covers per time slot, so pacing at booking comes from the times you choose to offer. On the till, orders are taken by course and sent to the kitchen, where the kitchen display shows tickets by station and course, with hold and fire, so mains are cooked when the table is ready for them. See point of sale and kitchen.

The tables screen shows the floor in 2D or in 3D, with a responsible server on each table, and staff seat arrived guests on the plan. Afterwards, kitchen analytics show stage timings by station and course, and reservation analytics show covers by day and hour, so you can see where the clusters came from. See Analytics.

Spreading the moments when tables are seated and order across a service, so the kitchen receives work at a steady pace.

Pacing covers spreads arrivals at booking; table pacing spreads seating and ordering on the night. Both are needed.

The busiest station goes over its capacity, and every later order queues behind the backlog.

How long an order takes from being sent to the kitchen to being ready at the pass. Spikes in ticket times show where clusters happened.

Stagger seatings by a few minutes, alternate sections, keep large tables apart in time, and use the bar for early arrivals during a rush.

Sending a later course to the kitchen with the first, but held, and firing it when the table is ready, so the kitchen cooks it at the right moment.

The manager, with the kitchen. The host should never have to make that call alone.

Look at ticket times by station and course, and the seating times of the tables that ordered just before each spike.

Yes. Seat them at quiet moments, keep them apart from other large tables, and consider pre-orders or set menus.

Yes. A menu that spreads mains across stations, and specials that use the quieter ones, let the kitchen take more orders at once without one station becoming the bottleneck.

Table pacing stops four tables ordering at once by spreading when tables are seated and when they order. It starts at booking, by spreading arrivals, and continues at the door, where the host staggers seatings, alternates sections and keeps large tables apart, and at the table, where servers adjust the pace of the first minutes to the kitchen.

Know your kitchen capacity station by station, use hold and fire so courses are cooked when tables are ready, and agree a signal for when the kitchen needs a breather, with the manager deciding when to slow the room. Read ticket times after every busy service, change one thing at a time, and the 8.02 rush becomes a steady evening.