The formula
Turns per table = Parties served / Number of tables
Average minutes per turn = Length of service in minutes / Turns per table
Why the formula works this way: the table, not the guest, is the asset being reused, so parties are counted against tables. The minutes-per-turn figure is the one operators underestimate, because it is not the time a party spends eating. It is the full cycle: the meal, the lingering, the payment, the clearing and resetting, and the empty minutes before the next party sits down. A party that dines for 90 minutes in a room averaging 150 minutes per turn is not slow at the table; the missing hour is happening around the meal, in greeting, ordering gaps, the wait for the check and the reset. That is also the good news, because those minutes can be recovered without a single guest feeling rushed.
How to use it, with an example
- Measure one service at a time: a Friday dinner, not a whole week blended together. Lunch and dinner are different sports.
- Count parties from the host stand or the POS, and count the tables you actually opened, not the full floor if a section stayed closed.
- Time the service from first seating to last seating, and be honest about it. Extending the window flatters nobody.
- Read minutes per turn next to turns. Turns tell you the score, minutes tell you where the time went.
- Only chase more turns when there is demand waiting. An extra half turn on a night with a waitlist is revenue; on a quiet night it is just an emptier room, faster.
Worked example: A casual dining room runs 24 tables through a 300-minute Friday dinner and seats 48 parties, at an average party size of 3 and $95 spent per party. Turnover is 48 / 24 = 2.00 turns per table, 144 covers, and $4,560 in sales for the service. The average turn cycle is 150 minutes, which says the room has recoverable time in it: half a turn more per table would seat 12 extra parties and add $1,140 on the same night, from the same room and the same staff roster. The calculator above is prefilled with these same numbers.
Turn data is only useful if it is captured while the service runs, which is a floor-management job. In Odoo for Restaurants, the dining room runs on a floor plan in the Odoo POS module: tables are opened, transferred and closed at the till, so parties per table and table times are recorded by the service itself, and a Friday can be compared with last Friday instead of with a feeling.
Common mistakes
- Measuring the meal instead of the table. Guests remember a 90-minute dinner; the table was gone for over two hours. Table time includes payment, clearing, resetting and the empty gap before reseating, and that surrounding time is usually the larger half of the opportunity.
- Blending lunch and dinner. A room doing 3 turns at lunch and 1.8 at dinner has two different stories. A single daily figure hides both, and hides which service needs the work.
- Turning tables into a guest experience problem. Chasing turns by hovering, rushing courses or presenting the check unasked buys a fraction of a turn and sells repeat visits to get it. The recoverable minutes are operational: faster greeting, orders fired promptly, checks prepared before they are requested, bussing the moment a party leaves.
- Counting closed sections. If a section never opened, its tables were never available to turn. Leaving them in the count makes the room look lazier than it was and sends you fixing the wrong thing. The habits in restaurant table management tips start with exactly this kind of floor discipline.
- Forgetting that a two-top on a six-top is a partial turn. It counts as one turn while leaving half the table unsold. Party-to-table matching at the host stand is turnover work too, especially on nights when large tables sit half empty.
- Optimising turns when there is no wait. Turnover multiplies demand, it does not create it. If the door is quiet, spend the effort on bookings and waitlist, and judge the room by spend per party until the wait returns. Choosing a system that records all of this is part of restaurant POS features worth checking before you buy.
FAQs
What is a good table turnover rate for a restaurant?
It depends on the format, and published ranges reflect that: counter service commonly runs 4 or more turns a service, fast casual with seating around 3 to 4, casual dining lunch 2 to 3 and dinner 1.5 to 2, and fine dining 1 to 1.5, often a single seating by design. Your own trend across comparable nights is a better benchmark than any of these.
Should I measure turns per table or per seat?
Per table is the operating number, because tables are what the host stand manages. Per seat (covers divided by seats) is useful for spotting party-size problems, like two-tops on large tables, but it can make a room look efficient while big tables sit half empty.
How do I increase turnover without rushing guests?
Take minutes out of everything except the meal: greet and take drinks orders fast, fire courses on time, prepare checks before they are asked for, and reset tables immediately. Guests feel rushed by attention to the clock, not by the absence of waiting.
What is the difference between table turnover and RevPASH?
Turnover counts how often the room refills. RevPASH, revenue per available seat hour, combines turnover with spend and time, so it catches the case where faster turns at lower spend actually earn less. Turnover is the simpler daily lever; RevPASH is the monthly cross-check.
Does a reservation-heavy room turn tables slower?
Usually, yes, slightly: reservations arrive in waves and tables are held for late arrivals, which adds empty minutes. It is manageable with seating intervals and honest table-time expectations, and the trade is worth it for the certainty reservations bring.
Can turnover be too high?
Yes. Past your format’s natural band, extra turns come out of the guest experience, kitchen accuracy and staff stamina, and they show up later as reviews and turnover of a different kind. A full-service room doing fine dining numbers at fast casual speed is borrowing from next month.
