Handling a rush when everyone arrives at eight

At five to eight, the restaurant is calm: a few tables eating, a couple arriving. By ten past, eleven tables have walked through the door, most of them booked for eight, two of them walk-ins. Every table wants menus, water and a drink. Every server has three new tables at once. In twenty minutes, all eleven will order, and the kitchen will receive more tickets than it can cook in the next half hour.

Every restaurant has its rush, and many have it at the same time every night, because that is when guests like to eat. Handling a rush well is not about working faster. It is about making a handful of decisions, before and during the rush, that spread the work so nobody, guest or team, feels the full weight of it at once.

This guide covers why rushes happen, the seating, ordering, firing and payment decisions that absorb them, and the one decision worth making at a quarter to eight, before the door fills. Every venue and figure in it is an example.

Rushes happen because guests share habits. Eight o'clock is a popular time for dinner in many places; half past twelve for lunch. Booking pages offer the most popular times, guests choose them, and the room fills in a wave.

Walk-ins add to it. People who did not book often arrive at the same popular times, hoping for a table. A room that is calm at a quarter to eight can be full ten minutes later.

The first defence is at the booking stage: spreading the times you offer, so the wave is smaller to begin with. But some rush will remain, and the floor has to absorb it.

A rush hurts service in a chain. The greeting is late because servers are busy. The drinks are late because the bar has a queue. The orders arrive together, so the kitchen faces a wave. The food is late, so tables wait. The bills are asked for together, so there is a queue at the card terminal.

Each link is a wait the guest did not choose. Handling a rush well means breaking the chain early, so the pressure at one stage does not pass to the next.

Our guide to speed of service without rushing anybody covers the four waits guests notice.

Not every venue's rush comes at eight. Some peak at half past seven, some at nine, some twice in an evening. Look at your own bookings and sales by hour over several weeks to see exactly when the room fills and when the kitchen is busiest.

The shape matters as much as the time. A rush that builds over an hour is easier to absorb than one that arrives in ten minutes. Knowing your own shape lets you plan for it rather than react to it.

The rush can be reduced before the night begins. Pacing covers means spreading arrivals across the evening: offering fewer tables at the most popular times, more at the edges, and making sure large tables do not all arrive at once.

Look at your bookings for the busiest nights. If most arrive within a fifteen-minute window, offer fewer slots in that window next time, and more at quarter past seven and quarter to nine. Our guide to pacing covers so the kitchen never drowns covers how.

Some guests will still want eight o'clock. The aim is not to refuse them, but to make sure the room does not depend on everyone arriving at once.

The one decision worth making at a quarter to eight is the order of the next half hour. Look at the bookings due between eight and half past, the walk-ins likely at the door and the tables that will free up. Decide which tables will be seated when, and in what order the floor will take their orders.

That decision turns the rush from a wave into a sequence. The host knows which tables to seat first; the servers know which tables to greet first; the kitchen knows roughly what is coming and when.

It takes two minutes, with the manager, the host and the chef looking at the same list. It saves the next hour.

The host sees the rush first and can do most to soften it. A host who can see the bookings due in the next half hour, the tables that will free up and the walk-ins at the door can seat in a sequence rather than all at once.

Give the host the authority to pace the room: to ask a walk-in to wait at the bar for ten minutes, to seat a booked table in a quieter section or to hold a table for a few minutes while a section catches up. A host who is trusted to manage the door protects the whole evening.

Large tables arriving in the middle of a rush can tip the kitchen over. A party of twelve that orders at a quarter past eight adds a dozen mains to an already full kitchen.

Plan large tables in advance: a set menu or a pre-order where possible, a staggered fire agreed with the kitchen, and a warning at the briefing. If a large table arrives early or unexpectedly, tell the kitchen at once, so it can prepare.

Guests who arrive together do not all need to be seated in the same minute, and they certainly do not need to order in the same minute. Seat tables as they arrive, but spread them across sections, so no server takes three new tables at once.

If a section is already full of new tables, seat the next guests in a different section, or offer them a drink at the bar for a few minutes while a table is prepared. A guest seated two minutes later, with a drink in hand, rarely minds.

Our guide to table pacing: stopping four tables ordering at once covers the floor's side in detail.

In a rush, get a drink to every table as quickly as possible. A guest with a drink is a guest who is comfortable waiting; one without is watching the clock.

Take the drinks order first, send it straight away, and make sure the bar is staffed for the wave. If the bar is the bottleneck, simplify: offer water at once, suggest a few quick drinks, and leave complicated cocktails until the pressure eases.

Drinks also buy time for the kitchen. Tables that are enjoying their drinks are less likely to order the moment they sit down.

The kitchen's biggest problem in a rush is that every order arrives at once. The floor can soften that by staggering when food orders are taken: greeting each table, taking drinks, then returning for the food order in sequence, a few minutes apart.

That is not delay for its own sake. Guests who have just sat down often want a few minutes with the menu anyway. A server who spaces the orders naturally, by the order the tables were seated, turns a wave of tickets into a steady stream.

The same applies to mains. If every table's mains are fired at the same moment, the kitchen faces a second wave. Fire mains as each table becomes ready, in a sequence, and tell the kitchen when a large table's fire is coming.

Holding mains when they are ordered and firing them when the starters are nearly finished keeps the kitchen's work flowing. Our guide to course firing: mains away when the starters clear covers the routine.

During a rush, one station usually falls behind first: the grill, the fryer or the pass. Kitchen bottlenecks show up as tickets waiting at one station while others keep up. The person running the pass should watch for it and act early: move a cook, simplify plating or tell the floor which dishes are slow tonight.

Our guide to kitchen bottlenecks: finding the station that stalls covers how to find the real constraint, so the fix goes where it is needed.

The bar often feels the rush before the kitchen, because every table orders drinks first. A bar that falls behind makes every table wait for its first drink, which is the wait guests notice most.

Staff the bar for the rush, keep the most ordered drinks quick to make, and prepare garnishes, ice and glasses in advance. If the bar falls behind, offer water and simple drinks first, and let the more complicated orders follow.

A long menu makes a rush harder, because the kitchen faces a wider range of dishes at once. Some venues offer a shorter menu on their busiest nights, or remove the slowest dishes at the peak.

Even without changing the menu, the floor can help by recommending the dishes the kitchen can deliver quickly when it is stretched, and by telling guests honestly when a dish will take longer.

When the kitchen is stretched, tell guests. "We're very busy for the next half hour, so the mains may take a little longer than usual." Guests who are told wait patiently; guests who are not grow impatient and start asking.

Offer something while they wait if the wait is long: bread, a small snack or a drink. Small gestures in a rush are remembered far longer than the wait itself.

Walk-ins at the height of a rush need care. Seating every walk-in at once adds to the wave; turning them all away loses trade. Quote an honest wait, take their name, offer the bar, and seat them when a table frees and the floor can manage it.

Our guide to walk-ins: how many tables to hold back covers how to plan for them, and our guide to waitlist management on a night with no tables covers the waiting list itself.

A rush at eight often becomes a payment rush at half past nine, as the tables that arrived together finish together. Bills are asked for at the same time, and a single card terminal becomes a queue.

Plan for it: enough terminals for each section, bills prepared promptly when asked for, and a server or manager free to help with payments at the peak. A table that waits ten minutes to pay leaves with that wait as its last memory.

In a venue with a second sitting, the payment rush is followed by a turnover rush: tables to clear, reset and prepare for the next guests. A table that sits dirty for fifteen minutes is a table the host cannot use.

Assign someone to clear and reset during the peak, and let the host know as soon as each table is ready. A steady turnover keeps the second sitting from becoming a second rush.

Lunch rushes are often shorter and sharper than dinner ones: a crowd that arrives at half past twelve and must leave by half past one. Speed matters more, and guests have less patience for long waits.

Prepare for the lunch rush with quick dishes, a fast greeting and the bill brought promptly. Ask tables if they are in a hurry, and prioritise those who are. A lunch rush handled well brings the same guests back the next week.

The rush is when staffing matters most. Look at when your rush starts and ends, and make sure the team is at full strength for it: servers, bar, kitchen and someone free to help wherever the pressure is greatest.

A manager who stays on the floor during the rush, helping where needed, is worth more than one in the office. Our guide to staff scheduling against the trading curve covers matching the rota to the rush.

Prepare the team for the rush at the pre-shift briefing. Tell them how many covers are expected, when the peak is and which large tables are coming. Name the slow dishes, the shortages and the plan for walk-ins.

A team that knows the rush is coming, and what the plan is, stays calm when it arrives. Our guide to the pre-shift briefing, in five minutes covers what belongs in it.

After a busy night, take a few minutes to look back. When did the rush start and end? Which stage struggled most: the door, the bar, the kitchen or the payments? Which tables waited longest, and why?

Use the answers to change the next rush: fewer booking slots at eight, an extra person on the bar, a second card terminal, a quicker dish on the menu. Rushes repeat, so lessons from one improve the next. Treat it like any rush hour: predictable, and therefore something you can plan around.

A rush is stressful, and stress spreads. A manager who stays calm, speaks quietly and helps where needed keeps the team calm too. One who shouts and rushes around spreads the panic.

Before the rush, remind the team that it is coming and that the plan will handle it. During it, keep messages short and clear. Afterwards, thank the team. A team that has come through a rush together, with the plan working, faces the next one with more confidence.

Write the rush plan down, on one page: when the rush is expected, how seating will be sequenced, who covers which section, who watches the pass, how walk-ins are handled and who helps with payments at the peak. Pin it by the pass.

A written plan means the team follows the same plan even when the manager is busy at the door, and it can be improved each week as the venue learns what works.

An invented brasserie fills between five to eight and ten past most Fridays. Servers take three new tables at once, the bar has a queue, the kitchen receives fifteen tickets in ten minutes and the card terminals queue at half past nine.

The brasserie makes changes at every stage. It offers fewer booking slots at eight and more at quarter past seven and quarter to nine. At a quarter to eight, the manager, host and chef agree the seating order for the next half hour. Servers take drinks first and stagger food orders. Mains are fired in sequence. A second card terminal is added to each section.

A month later, the Friday rush still comes, but it feels like a busy evening rather than a crisis. Ticket times at the peak fall, and the reviews stop mentioning the wait for the bill.

In servearound, the booking rules set which times each shift offers and how long each booking lasts. There is no automatic cap on covers per slot, so pacing at the booking stage comes from the times you choose to offer, and reservation analytics show covers by day and hour, so you can see when your rush really falls. On the night, the host adds walk-ins to the waitlist with a quoted wait, and each party's card shows how long it has waited against the quote.

The tables screen shows each table's status, from reserved and occupied to needing cleaning. The till holds and fires rounds, so mains go to the kitchen in sequence, and each station's screen shows its tickets oldest first, each with its age counting. Table analytics show when the room fills, by day and hour. See the reservations module and Order Fulfillment.

Guests share habits, and booking pages often offer the most slots at the most popular times.

Pace covers at the booking stage: fewer slots at the peak, more at the edges, and large tables spread out.

The order of the next half hour: which tables are seated when, and in what order their orders are taken.

As they arrive, but spread across sections, with a drink at the bar if a table needs a few minutes.

Yes, naturally, by the order tables were seated, so the kitchen receives a stream rather than a wave.

Quote an honest wait, offer the bar and seat them when a table frees and the floor can manage it.

Enough terminals for each section, bills prepared promptly and someone free to help at the peak.

Look at which stage struggled most, and change one thing before the next rush.

Handling a rush means turning a wave into a sequence. Pace covers at the booking stage, and at a quarter to eight decide the order of the next half hour. Seat tables as they arrive but across sections, get a drink to everyone first, stagger the food orders and fire mains in a sequence.

Watch for the kitchen's bottleneck, tell guests honestly when the kitchen is stretched, handle walk-ins with an honest wait, prepare for the payment rush and the turnover, staff for the peak, brief the team beforehand and learn from every busy night.