Table turnover rate: how to raise it politely

Table turnover rate is a simple idea with an awkward reputation. It measures how many times each table is used during a service. On a busy night, a higher turnover rate means more guests served from the same room, which is often the difference between a good night and a great one. But say the words "turn the tables" to a team and many of them hear "rush the guests", which is the opposite of hospitality and, in the long run, the opposite of good business.

The reassuring truth is that most of the time that can be recovered in a sitting has nothing to do with rushing guests. It sits in the gaps: the wait for a first drink, the pause before the order is taken, the time a ticket waits in the kitchen, the minutes between finishing and getting the bill, and the time a cleared table sits waiting to be reset. Guests rarely notice these minutes being removed, because they never wanted to spend them in the first place.

This guide explains how to measure table turnover rate, how turn times and dwell time relate to it, where the minutes hide in a typical sitting, and four changes that recover time without anyone feeling hurried. It also covers when not to push turnover at all, because on some services and in some venues, a slow table is exactly what the guest came for.

Table turnover rate is the number of times a table is used during a service. If a table seats one party at seven and another at nine, it has turned twice. Across the whole room, the rate is the number of parties seated divided by the number of tables:

If a room with 20 tables seats 34 parties on a Saturday dinner, its turnover rate is 1.7. Some tables turned twice, some only once.

The rate is useful because it connects the floor plan, the booking diary and the kitchen. It is limited, though, because it ignores party size: a table that turns twice with couples has served fewer guests than one that turns once with a family of six. That is why turnover is best read alongside covers per table, which shows how many guests each table actually seated.

Two related measures sit underneath the turnover rate.

Dwell time is how long a party stays at the table, from being seated to leaving. It varies with party size, service and occasion. A couple at weekday lunch may stay under an hour; a group celebrating on a Saturday may stay for two and a half.

Turn time is the time a table is unavailable for the next party: dwell time plus the time it takes to clear and reset the table. It is the number your booking slots should be built around. If a table for four needs about two hours on a Saturday before it can be offered again, booking a party into it every ninety minutes will cause delays all evening.

The relationship between these is the same one that governs any system with arrivals and waiting, captured neatly by Little's law: the number of parties in the room equals the rate at which they arrive multiplied by how long each one stays. If you want to serve more parties in the same room, you either need more tables or shorter stays. Since more tables is rarely an option, the question becomes how to shorten the stay without anyone minding.

Break a typical dinner sitting into stages and the hidden minutes become visible. Here is an illustrative two hour sitting for a party of four on a busy night:

That adds up to well over two hours, and only the eating stages are time guests actively want to spend. The rest is waiting: for a server, for the order, for the food, for the bill, and for the table to be reset. Those waiting stages are where turnover can be improved without anyone feeling hurried.

The first fifteen minutes of a sitting are often the slowest and least enjoyable. Guests sit waiting to be greeted, waiting for menus, waiting for a drink. A server who greets the table within a minute or two, offers water and takes a drinks order straight away removes several minutes before the meal has started, and guests experience it as attentive service, not speed.

Have menus on the table or offered immediately. If guests can order from their phones, make the menu easy to open as soon as they sit. The aim is not to hurry the decision but to remove the dead time before it.

The gap between courses is the next largest source of lost minutes, and it usually comes from the kitchen and the floor not being in step. A main that is fired too late leaves a table waiting; a main that is fired too early arrives while starters are still being eaten. Both lengthen the meal, the second by forcing the table to slow down or by sending food back.

Course firing fixes this. Mains are held until the server sends them, once starters are nearly finished, and the kitchen knows how long each dish takes to prepare. Pacing covers across the evening helps too: if four large tables order at the same minute, every one of them waits longer. Our guide to pacing covers covers how to spread orders across a service.

The end of the meal is where guests most often feel stuck. They have finished, they are ready to go, and they cannot catch anyone's eye. Ten minutes later they are still waiting for the bill, and the next party is waiting at the bar for their table.

Bring the bill when the table is ready, not when it has asked three times. Train servers to watch for the signs, such as closed menus, finished coffees and coats being reached for, and to offer the bill rather than make guests ask. Where guests can call for the bill or a server from their table, the request reaches the floor immediately instead of waiting for someone to notice a raised hand.

Once guests leave, the table is useless until it is cleared and reset. On a busy night, a table that waits ten minutes for a reset is a table that could have been seating the next party. Assign a clear owner for resets in each section, keep reset supplies close to the tables, and make it visible on the floor which tables are waiting to be cleaned.

A table status that the whole floor can see, such as occupied, needs cleaning or available, lets hosts and servers act without asking each other. The host knows which table is about to be free; the server knows which table to reset next.

Turn times are not the same for every table. A couple at lunch, a family at Sunday lunch and a group celebrating on Saturday night all stay for different lengths of time. Setting one turn time for every booking leads either to tables sitting empty or to parties waiting for tables that are not ready.

Measure dwell time by party size and service from a few weeks of your own data, then set turn times to match. Many venues find that couples need noticeably less time than groups of four or more, and that weekend dinners need more time than weekday ones. Build those differences into your booking slots, so the diary offers times the room can actually deliver.

On a night with two sittings, the second sitting depends entirely on the first one leaving on time. A first party seated twenty minutes late, because they arrived late or because the table was slow to reset, finishes twenty minutes late, and the second party waits at the bar. One late start at six o'clock can ripple through the whole evening and reach tables that had nothing to do with it.

That is why the start of the evening matters more than the end. Seat the first sitting promptly, greet tables quickly, fire the first courses on time and watch for any table that falls behind. A host who knows which first-sitting tables are running late can warn the second party, offer them a drink at the bar, or move them to a table that is already free.

Booking slots should also leave a small buffer between sittings, rather than booking the second party the minute the first is due to leave. A buffer of ten or fifteen minutes, set from your own reset times, absorbs most small delays without leaving the table empty for long. It is cheaper to lose a few minutes of table time than to keep a booked party standing.

Not every recovered minute needs a booking to fill it. A table that comes free forty minutes before its next booking can seat a walk-in couple for a quick drink and a light meal, or a party from the waitlist who are happy to eat quickly. Those short sittings add covers without moving a single booking.

To use them well, the host needs to see at a glance which tables are free, how long each one has until its next booking and who is waiting. A waitlist that shows each party's size and how long they have waited lets the host match a short gap to the right party. Our guide to waitlist management covers how to run one on a busy night.

Be honest with walk-ins about the time available. "We have this table for an hour, until the next booking" is a fair offer that most guests appreciate, and it keeps the next booking safe. Guests who know the limit at the start rarely mind it at the end.

Large parties turn slowly and often earn well. A table for eight that sits for two and a half hours may still earn more than two tables for four that each turn twice, especially if the group orders generously. The question is not whether large parties turn slowly, because they do, but whether the time they take has been planned for.

Seat large parties in the first sitting or the last, rather than in the middle of the evening, where their long stay blocks a combined table that could have turned twice. Take their order early, agree the menu in advance for very large groups so the kitchen can plan, and fire each course so the whole table eats together.

Turnover and covers per table answer different questions. Turnover asks how often each table was used; covers per table asks how many guests each use served. Together they tell you how hard each table worked.

If turnover is high but covers per table is low, couples may be sitting at tables for four, and the table mix may need changing. If covers per table is high but turnover is low, tables may be held too long between sittings, or the booking slots may be too far apart. Our guide to designing a restaurant floor plan that sells covers how the table mix affects both.

Here is an illustrative Saturday for a 20-table room, to show how small changes add up. The figures show the method, not typical results.

No course was shortened and no guest was asked to leave. The time came from waiting that guests did not want: the gap before the first drink, the pause between courses, the wait for the bill and the slow reset.

Turnover matters most on busy nights, when there are guests waiting for tables. On quiet nights, raising it achieves nothing, because there is nobody to seat at the table once it is free. Pushing a table along on a half-empty Tuesday only makes the guests feel hurried, for no gain.

Some formats should not chase turnover at all. A tasting menu, a celebration dinner and a fine dining room are places where guests expect to linger, and the price reflects the time. Even in these venues, though, the waiting stages can still be shortened: nobody wants to wait twenty minutes for the bill after a tasting menu.

Measure turnover by service, alongside dwell time by party size, the gap between sittings and covers per table. Look at the gap between sittings particularly closely, because it shows how quickly a table is reset and reseated after a party leaves, which is the easiest time to recover.

Compare busy services with each other over several weeks, and look for the tables that turn least. A table that consistently turns once while its neighbours turn twice may be in an awkward position, may be too large for most parties, or may be held for late bookings that leave it empty early in the evening.

Turnover lands badly with a team when it is described as moving people on. It lands well when it is described as removing the waiting guests hate. Frame it that way in the pre-shift briefing: greet tables quickly, keep the kitchen in step with the table, offer the bill when guests are ready and reset fast. Every one of those is better service as well as better turnover.

It also helps to share the numbers. When the team sees that the gap between sittings fell from twelve minutes to seven, or that two more tables reached a second sitting on Saturday, they can see the effect of what they did. Celebrate the waits that disappeared, not the guests who left sooner.

In servearound, booking rules set how long a sitting lasts and which times are offered within each service, so the diary only offers slots the room can deliver. Tables show their status to the whole floor, including when they need cleaning, so resets happen faster. Dishes can be held on the check and fired when the table is ready, so the kitchen stays in step with each table, and guests can call for the bill or a server from their table, so the request reaches the floor at once.

The table report in Analytics shows seatings, covers and revenue for every table, the median seating time, revenue per seated hour, the minutes each table went unsold and the gap between seatings, which shows how quickly the room is reset. See the reservations module for how booking rules and the floor plan work together.

It depends entirely on the format, the service and the size of the room. The useful comparison is your own busy services over time, and between tables in the same room.

Not when the time comes from waiting. Guests rarely want to wait for a drink, the order, the next course or the bill. Removing those waits is usually experienced as better service.

On very busy nights with two sittings, many venues mention the time when the booking is made. It is better said at booking than at the table.

Gently, and only when guests are waiting. Offering coffee or a drink at the bar is more hospitable than presenting the bill unasked.

Usually, yes. Measure dwell time by party size and set longer turn times for larger groups.

Yes, especially for busy weekday lunches where guests have limited time and the room fills quickly. A faster lunch can be exactly what guests want.

It can remove the wait for a server to take the order, especially for drinks and second rounds. Guests order when they are ready rather than when a server reaches them. It works best alongside attentive service, not instead of it.

As long as it takes to do properly, and no longer. Time a few resets on a quiet service to set a realistic target for each table size, then watch the gap between sittings to see whether resets are holding up the room.

Table turnover rate is how many times each table is used in a service. To raise it politely, leave the eating alone and remove the waiting. Greet and take drinks quickly, keep the kitchen in step with the table through course firing and pacing covers, make the bill effortless and reset tables fast.

Set turn times by party size and service, read turnover alongside covers per table and dwell time, push only on the nights when guests are waiting, and leave the slow tables alone where slow is the point. Most of the minutes you recover are minutes your guests never wanted to spend.