Speed of service without rushing anybody

A table of four spends two hours at dinner and leaves happy. Another table, in the same restaurant on the same night, spends an hour and a half and leaves feeling the service was slow. The difference is not the total time. It is where the waiting happened: the first table never waited for anything it wanted, while the second sat for fifteen minutes before anyone took a drinks order and another fifteen trying to pay.

Speed of service is not about making meals shorter. Guests who want a long evening should have one. It is about removing the waits guests did not choose: the wait to be noticed, the wait for food that should have come, the wait for a course after the plates are cleared, and the wait to pay and leave.

This guide covers the four waits a guest actually notices, how to measure each one, which to shorten first, and how to do it without making anybody feel rushed. Every venue and figure in it is an example.

A fast service removes unwanted waits; a rushed service removes wanted time. A guest who has to wait ten minutes for a menu feels neglected. A guest whose plates are cleared while they are still talking, or who is handed the bill before asking, feels pushed out.

The aim is to give guests control of the pace. They should never wait for something they want, and never be hurried towards something they did not ask for. Most complaints about slow service are about the first; most complaints about pushy service are about the second.

Keep both in mind when you work on speed. Every change should shorten a wait the guest did not choose, and leave the rest of the evening alone.

Guests notice four waits above all. The wait at the start, from sitting down to the first drink. The wait for the food, from ordering to the plates arriving. The wait between courses, from clearing one to the next arriving. And the wait at the end, from asking for the bill to leaving.

Each wait has its own causes and its own fixes. A venue that measures all four knows where its time is lost. One that measures none works on instinct, and often fixes the wrong thing.

The first wait is the one guests feel most sharply, because it comes when they are fresh, hungry and paying attention. A table that waits ten minutes to be greeted and another ten for its first drink starts the meal irritated, however good the rest of the evening is.

The causes are usually on the floor: a server with too many tables, a host who seats several tables at once, a bar that is backed up, or a server who waits to take the drinks and food orders together.

The fixes are simple: greet every table within a minute, take the drinks order straight away, send it at once and make sure the bar can keep up at the busiest moment.

The second wait runs from the order to the food. Part of it is the kitchen's cooking time; part is the time before the order reaches the kitchen; part is the time the plates wait at the pass before a server takes them.

Ticket times measure the kitchen's part: how long each ticket takes from arriving in the kitchen to being ready. Our guide to ticket times: the only kitchen metric that moves covers how to measure them. The time before the kitchen and the time at the pass need watching too, because they often add as much as the cooking.

An order that sits in a server's pad for five minutes, or plates that wait under the lights for three, add to the guest's wait without anyone cooking.

The third wait is between courses, and it is the one most often caused by timing rather than speed. If the mains are fired too late, the table sits with empty plates after the starters. If dessert menus arrive long after the mains are cleared, the evening goes flat.

The fix is course firing: mains held when ordered and fired when the starters are nearly finished, with slow dishes fired earlier. Our guide to course firing: mains away when the starters clear covers how.

Between mains and dessert, a simple standard helps: clear the plates, give the table a minute, then offer desserts.

The fourth wait is at the end, and it is the one guests remember on the way out. A table that asks for the bill and waits ten minutes, then waits again for the card machine, leaves with that wait as its last impression of the evening.

Faster payment is often the easiest speed improvement to make: bring the bill within two minutes of being asked, bring the card terminal with it, and let guests pay without a second wait. Our guide to faster payment, measured in actual seconds covers the end of the meal in detail.

Before any of the four waits begins, some guests wait at the door: a walk-in hoping for a table, a booked table not yet ready. That wait colours everything after it. A guest welcomed at once and offered a drink at the bar waits happily; one left standing unnoticed starts the evening annoyed.

Acknowledge every guest within seconds of their arrival, even if you cannot seat them yet, and tell them honestly how long it will be. Our guide to walk-ins: how many tables to hold back covers the door's side.

Not every wait is a problem. Guests choose some waits: lingering over a drink before ordering, a long conversation between courses, a coffee after dessert. Those are part of a good evening, and hurrying them is the fastest way to make service feel pushy.

Train servers to tell the difference. A table that has closed its menus and is looking around wants to order; one deep in conversation with menus still open does not. Read the table before acting.

Shorten the first and last waits first. They are the ones guests notice most, they are usually caused by the floor rather than the kitchen, and they are often the cheapest to fix: a greeting standard, a drinks-first habit, a quicker bill.

Then look at the food and the gap between courses, which depend on the kitchen and on timing. Those often need more work, such as changes to prep, stations or how courses are fired, but they also make a large difference to how the meal feels.

Measure all four before deciding. Your venue may be the exception, with a fast greeting and a slow kitchen.

Measure each wait on a few busy nights. Some are easy to capture from your systems: ticket times from the kitchen, the time from seating to the first order from the till, the time from the bill being printed to the payment. Others need someone to watch: the greeting and the wait between asking for the bill and receiving it.

Pick a sample of tables, note the times at each stage, and work out the typical wait and the worst wait at each step. The worst waits matter as much as the typical ones, because they are the tables that complain.

Repeat the measurement after every change, on similar nights.

Measuring the waits need not mean standing over tables with a stopwatch. Many systems record the times you need: when the order was taken, when it reached the kitchen, when the ticket was finished and when the bill was paid. Use those where you can.

For the waits the system does not record, such as the greeting or the time between asking for the bill and receiving it, a manager can note a few tables on a busy night. Even ten tables give a clear picture of where the time goes.

Waits rarely happen one at a time. A rush at the door leads to slow greetings, which leads to orders arriving together, which leads to a wave in the kitchen, which leads to slow food, which leads to bills requested together and a queue at the card machine. One bunched arrival can slow every stage of the evening.

That is why spreading the load matters so much. The queueing theory behind it is simple: when work arrives faster than it can be handled, waits grow quickly, and spreading the arrivals shortens them for everyone.

Every venue has rushes. Handling a rush well means absorbing it without passing the pressure to the guests: seating tables as they arrive but staggering when their orders are taken, prioritising drinks so guests are looked after while they wait, and firing mains in a steady sequence rather than all at once.

The host has a large part to play, by spreading seating where possible and telling the kitchen what is coming. Our guide to handling a rush when everyone arrives at eight covers the decisions in detail.

Lunch and dinner need different speeds. Many lunch guests have a fixed amount of time and want to eat and leave within an hour; many dinner guests want a slower evening. A lunch service that feels like dinner is too slow, and a dinner service that feels like lunch is too fast.

Ask lunch guests if they are short of time, and adjust. Offer dishes that cook quickly, bring the bill with the coffee if they ask, and make sure the kitchen knows which tables are in a hurry.

Faster service can raise table turnover rate, the number of times each table is used in a service, because tables are free sooner. That matters in venues where demand exceeds the number of tables, such as busy lunch spots or popular weekend nights.

But turnover should come from removing unwanted waits, not from hurrying guests. A table freed because the bill came quickly is a table turned politely; one freed because the guests felt pushed out is a table that may not come back. Our guide to table turnover rate: how to raise it politely covers the balance.

The kitchen and the floor must work at the same pace. A kitchen that sends food faster than the floor can carry it leaves plates waiting under the lights; a floor that sends orders faster than the kitchen can cook builds a queue at the pass.

The person running the pass keeps the two in step, telling the floor when food is ready and the kitchen when tables are ready. Our guide to ticket times: the only kitchen metric that moves covers the kitchen's side of the measurement.

Many speed problems are staffing problems. A server with too many tables cannot greet each one within a minute; a kitchen one cook short at the busiest hour cannot keep ticket times down. No routine fixes a section that is too large.

Look at the waits against the rota. If the first drink is slow on the nights a server is missing, the fix is staffing, not training. If ticket times rise when one station is short, the fix is on the rota.

The menu affects speed too. A menu with many slow dishes, or with most dishes on one station, will always be slower at peak than one with a balanced mix. Dishes that can be partly prepared in advance cook faster in service than ones made entirely to order.

Look at which dishes appear most often on the slowest tickets, and whether they can be prepared differently, moved to another station or limited at peak.

The layout of the room affects speed. Tables far from the kitchen, a bar at the back, a terrace up a flight of stairs or a single narrow route between the tables all add seconds to every trip, and those seconds add up across an evening.

Small changes help: a side station for water, cutlery and menus near the far tables, a second route through the room, or handheld devices so orders do not need a trip to the till. Watch how servers move on a busy night and look for the longest walks.

Honesty about timing makes waits feel shorter. A guest told that a dish takes twenty-five minutes waits calmly; one left wondering why the food is late grows impatient. A guest told the kitchen is busy tonight, with an honest estimate, is far more forgiving than one who hears nothing.

Train servers to set expectations: mention slow dishes when they are ordered, tell tables when the kitchen is stretched, and check back during a long wait rather than avoiding the table.

The same wait can feel short or long depending on the guest's mood. A table enjoying itself barely notices ten minutes; a table already irritated feels every second. That is why the first wait matters so much: a good start makes every later wait feel shorter.

Keep the mood good early: a warm greeting, a quick drink and a server who checks in. Guests who feel looked after forgive the small waits that every busy service has.

Checking on a table is part of speed: a server who notices an empty glass or a guest looking around for help prevents a wait before it starts. But checking too often feels like hovering.

Check with your eyes more than your voice. A glance at each table every few minutes shows who needs something; a visit is only needed when something is wanted, or at the natural moments, such as just after the food arrives.

Every change to speed of service should be measured again on similar nights. Did the first drink arrive sooner? Did the bill take less time? Did the complaints about slow service fall?

If a change did not help, undo it and try something else. If it did, keep it and move to the next wait. Over a few months, a venue that measures and adjusts can transform how fast its service feels without anyone working harder.

An invented brasserie has reviews complaining about slow service, and the team assumes the kitchen is the problem. The manager measures the four waits on four busy nights. Ticket times are reasonable. The first drink takes over twelve minutes on average, because servers take drinks and food orders together. The bill takes nine minutes from asking to paying, because the card terminals are shared between sections.

The brasserie introduces a drinks-first habit, a greeting standard of one minute, and a terminal for each section. Nothing changes in the kitchen.

A month later, the first drink arrives within five minutes on most tables and the bill within four. The complaints about slow service fade, and the kitchen, which had been blamed, is quietly pleased.

In servearound, kitchen analytics show ticket times day by day and by day and hour, and where the minutes go between the queue, prep and the pass, so the kitchen's part of the food wait can be read apart from the rest. Order analytics show when checks are rung across the week, and table analytics show the median seating, the gap between seatings and when the room fills, by day and hour.

Rounds can be held and fired from the till, so mains are cooked when the table is ready for them. Guests using the menu they open with the table's QR code can ask for the bill once they have ordered, which sends a request to staff, and settling the bill sends the table to cleaning so it is ready for the next guests. See Analytics and Order Fulfillment.

Removing the waits guests did not choose, at the start, for the food, between courses and at the end, without hurrying them.

The first drink and the bill, at the start and end of the meal.

Usually the first and last, which are cheapest to fix. Measure all four to be sure.

From your systems where you can, and by watching a sample of tables on busy nights.

It can, by freeing tables sooner, as long as guests are not hurried.

Seat as tables arrive, stagger when orders are taken, prioritise drinks and fire mains in a steady sequence.

No. Often the slowest waits are on the floor: the greeting, the first drink and the bill.

Check with your eyes, and visit only when something is needed or at the natural moments.

Speed of service means removing the waits guests did not choose, not shortening the meal. Guests notice four: the first drink, the food, the gap between courses and the bill. Measure each on busy nights, shorten the first and last first, then work on the food and the courses with the kitchen.

Spread the load so waits do not pile up, handle rushes without passing the pressure to guests, look at staffing and the menu as well as routines, tell guests what to expect, and check on tables with your eyes rather than hovering.