Table Turnover Rate Calculator
Enter one service to see how many times you turned each seat, how close you came to capacity, and what five fewer minutes per table would be worth over a year.
What table turnover rate actually measures
Table turnover rate is the number of times you sell the same seat during a single service. It is the only lever in a restaurant that increases revenue without increasing prices, adding seats, or finding new guests. You already have the demand and you already have the room — turnover decides how much of that demand the room can physically absorb before the doors close.
Most operators track covers and average spend and stop there. Covers tell you how many people came; they do not tell you how many more could have come. A 90-seat dining room running a four-hour dinner service with an average table time of 82 minutes has a theoretical ceiling of just under three turns. If you served 152 covers, you achieved 1.69 turns per seat — roughly 58% of what the room was capable of. That gap is not a marketing problem. It is a timing problem.
The second half of the calculation is the ceiling. Divide the length of the service by your average table time and you get the maximum number of turns the room could deliver if every seat were refilled the instant it emptied. Nobody hits that number, because parties do not arrive in perfectly spaced waves and a 90-seat room does not fill with 90 solo diners. But the distance between your actual turns and that ceiling is the most honest measure of how much capacity you are leaving unsold.
Dining time is not the same as table time
The single most common error in this calculation is measuring the meal instead of the table. A guest sits for 74 minutes; the table is unavailable for 91. The difference is the turnaround — the interval between the guest standing up and the next party sitting down, during which the table is cleared, wiped, reset, and reassigned by whoever is running the door.
That turnaround is dead time you are paying rent and wages for, and in most rooms it is longer than anyone believes. Time it yourself on a busy Saturday with a phone stopwatch. Ten to fourteen minutes is normal in a room where nobody has been given responsibility for resets. Three to five minutes is achievable with nothing more than a stocked side station and a runner who knows the table is theirs.
Enter table time, not dining time, into the calculator above. If you only have POS data on seated-to-paid duration, add your observed turnaround to it before entering. Understating table time inflates your theoretical ceiling and makes your utilisation look worse than it is, which sends you chasing a problem you do not have.
The four stages worth timing separately
- Seated to first order — usually the largest recoverable block, and entirely within your control.
- Order to first course — a kitchen throughput question, not a service one.
- Last course to bill request — where guests decide whether to stay, and where you should not push.
- Bill request to table reset — payment friction plus turnaround, and the easiest minutes in the building to win.
Time twenty tables across two services and you will find your minutes concentrated in one or two of these stages. Attacking the wrong stage is why turnover initiatives usually produce a rushed dining room and no additional covers.
What a normal turn rate looks like
| Format | Turns per seat per service operators typically see |
|---|---|
| Counter service | 4 or more — there is no table service stage to compress |
| Fast casual with seating | 3–4 — ordering happens before the guest sits down |
| Casual dining, lunch | 2–3 — time-pressed guests and a shorter menu |
| Casual dining, dinner | 1.5–2 — more courses, longer stays, drinks |
| Fine dining | 1–1.5 — a single seating is often the intended design |
Treat this as orientation, not as a target. A tasting-menu restaurant turning tables twice a night has broken its own concept, and a lunch counter turning 1.8 has a queue out the door and no idea why it is losing money. The comparison that matters is your own room this month against your own room last month, at the same service, on the same days of the week.
It is also worth separating peak from shoulder. A dinner service that averages 1.7 turns may be running 2.4 between 7pm and 9pm and 0.6 either side. Averaging the two hides the fact that your problem is demand at 6pm, not speed at 8pm — and those need opposite responses. Comparing the same service period across periods, the way a like-for-like comparison does, keeps you honest about what actually changed.
What five minutes is actually worth
This is the arithmetic that makes turnover worth the effort. Because the relationship between table time and capacity is a ratio rather than a subtraction, small reductions compound across every table, every service, every week of the year.
Take the 90-seat room again: 152 covers, 82-minute table time, $38 average spend. Cut table time to 77 minutes and the same service supports about 9.9 extra covers — roughly $375. Run that service twelve times a week and it is around $4,500 a week, or $234,000 a year, from five minutes.
The reason that number is so large is that almost all of it drops through to profit. You are not adding rent, you are not adding fixed labour, and the only incremental cost is food and the variable portion of wages. Ninety extra covers a week against a fixed cost base moves your break-even point more than a price increase of the same headline value, because a price increase risks the demand while a faster turn does not.
One caveat the calculator cannot apply for you: extra capacity only converts to revenue when there is unmet demand at that moment. Turning tables faster on a quiet Tuesday produces nothing except an emptier room. Fix speed where you have a wait list, and fix demand everywhere else.
Where the minutes actually go
In most rooms the recoverable time is not in the meal at all. Guests eat at roughly the pace they always have. The delays sit around the edges of the meal, in the parts of the experience nobody is watching.
- The greeting gap. Parties seated but not acknowledged for six or seven minutes because the section is buried. Costs the table time and costs you a drinks order at the front of the meal.
- Kitchen bottlenecks on two or three dishes. A single slow ticket item holds the whole table. Your menu engineering should account for ticket time, not just margin — a high-margin dish that adds nine minutes to every table it appears on is not the winner it looks like.
- Payment friction. Bill printed, bill delivered, card machine located, receipt signed. Four separate waits, often twelve minutes in total, and the most solvable problem on this list.
- The reset. Table clear, wipe, relay, reassign. Unowned resets are why turnaround stretches to fourteen minutes on the exact nights it matters most.
- Door management. A table sitting empty for eight minutes because nobody told the host it was ready. No amount of kitchen speed recovers that.
Add those up and a typical casual dining room is carrying twenty to thirty minutes of non-dining time per table. That is where the five minutes comes from — and you can take it without a single guest noticing anything except better service.
Faster turns without a rushed room
The distinction that matters is between removing waiting and removing time. Guests resent being hurried; they resent waiting considerably more. Almost every minute worth recovering is a minute the guest was waiting for you.
- Own the reset. Assign specific tables to specific people and stock side stations so nobody walks the length of the room for cutlery. This alone is often five minutes.
- Bring the payment to the table. Handheld terminals or a QR pay option remove the single longest avoidable wait in the meal, and guests read it as good service rather than as a nudge.
- Acknowledge within sixty seconds. Even if the order comes later. The clock starts when the guest feels seen, not when they sit.
- Fix the two slowest tickets on the menu. Re-engineer the prep so the long pole becomes a mise en place task rather than an order-time one.
- Give the door live table status. A table that is clear but unknown to the host is worth nothing.
- Stagger reservations against your actual table time. Booking every 90 minutes when your true table time is 82 builds idle time into the plan by design.
- Match your section sizes to peak, not to average. Servers running too many tables at 8pm are the reason greetings slip, and slipped greetings extend every table in the section.
Watch the labour side as you do this. Faster turns raise revenue per labour hour, which usually improves your labour cost percentage — but only if you resist the temptation to add a runner for every minute saved. Recalculate after the change rather than assuming it.
Frequently asked questions
What is a good table turnover rate?
It depends entirely on format. Counter service commonly runs four turns or more per service, casual dinner sits around 1.5 to 2, and fine dining is often designed around a single seating. The useful benchmark is your own room over time, not another restaurant's number.
Should I measure turns per table or turns per seat?
Turns per seat, which is what this calculator returns. Turns per table looks tidier but is distorted by party size — a two-top seated with two guests and a six-top seated with three both count as one turn, while the second one is leaving half a table unsold.
Does faster turnover always mean more revenue?
Only where demand exceeds capacity. Extra turns on a night you were half full produce nothing. Measure your turn rate during your busiest two hours, and put the effort there rather than across the whole week.
How do I measure average table time without POS reports?
Write the seated time on the docket and note the reset time on a clipboard at the pass. Twenty tables across two services gives you a workable average. Remember to run the clock until the table is reset and reassigned, not until the guest pays.
Why is my seat utilisation above 100%?
Your entered table time is shorter than reality, or the service window is longer than the hours you entered. Utilisation above 100% means the room served more covers than your stated table time allows, which is arithmetically impossible — recheck the turnaround you included.
Will faster turns lower my average spend per cover?
It can, if the speed comes from cutting the dessert and second-drink window. It does not if the speed comes from resets, greetings, and payment. This is the practical reason to compress the stages either side of the meal rather than the meal itself.
Does table turnover affect labour cost percentage?
Yes, usually favourably. The same staffed hours produce more covers and more revenue, so revenue per labour hour rises and labour percentage falls. The exception is when you add headcount to achieve the speed, which can cancel the gain entirely.