Most restaurants have no idea what their table turn time actually is. They have a feeling. They know Friday is slammed and Tuesday is slow. But ask for the average minutes from seated to reset, and you get a shrug.
That is a shame, because turn time is the single most leveraged number on your floor. Shave eight minutes off a 55-minute average in a 20-table room and you have effectively added tables to your restaurant without signing a new lease.
What you will get from this guide
- How to measure turn time properly, including the reset gap most POS systems miss
- The five stages where minutes actually leak, ranked by how much they cost you
- Fixes you can apply this week, without hiring or rushing guests
- How to tell the difference between a faster turn and a rushed guest
Why turn time beats almost every other metric
Average order value gets all the attention because it is easy to influence with an upsell script. But turn time is multiplicative. Every minute you save applies to every table, every service, every day, forever. It compounds in a way a one-time menu price change does not.
Consider a restaurant doing 180 covers a day at a $32 average ticket. That is roughly $2.1M a year. Now cut turn time by 12%, and assume you fill even two thirds of the newly available capacity. You have added six figures of revenue using the same kitchen, the same staff, and the same rent.
We were not trying to be faster. We were trying to stop losing eight minutes between when a guest wanted to pay and when they actually could.
How to measure it properly
Here is where nearly everyone gets it wrong. Most systems report seat to close, meaning the moment a guest sits to the moment the bill is settled. That is not turn time. Turn time ends when the table is bussed, wiped, reset, and marked available again.
That gap between payment and availability is where the hidden minutes live. In the restaurants we have measured, it averages between four and nine minutes, and almost nobody tracks it.
- Log the seat timestamp the moment a guest is seated, not when the first order is entered.
- Log the settle timestamp when payment clears.
- Log the reset timestamp when a staff member marks the table available. This is the one you are probably missing.
- Segment by day part. A Saturday dinner turn and a Tuesday lunch turn are different animals. Averaging them together hides both.
qrtable tracks every one of these timestamps automatically
Seat, order, fire, settle and reset, per table, per day part. No clipboard, no manual logging, no guessing.
Free to start · No card required · Live in minutes
The five places minutes actually leak
Once you are measuring properly, the leaks become obvious. In our experience they show up in the same five places, in roughly this order of cost.
1. The gap before the first order
A guest sits down, reads the menu, decides in four minutes, then waits another six for someone to come take the order. That waiting is pure loss. It does not make the meal better and it does not make the guest happier.
This is the single biggest reason QR ordering moves the number. The guest orders the second they decide. We routinely see this stage drop from ten minutes to under four.
2. The gap between courses
Usually a kitchen pacing problem, not a service problem. If mains land while the table is still working through starters, you get a pile-up. If they land twelve minutes after the plates are cleared, you get dead air. Station-level ticket routing and fire timing fix most of this.
3. The gap before the bill arrives
The guest is done, coat on, ready to leave. Now they have to catch someone's eye, wait for the bill, wait for the card machine, wait for the receipt. This stage alone commonly runs eight to twelve minutes, and every second of it is a table earning nothing.
4. The reset gap
The invisible one. Table is paid and empty, but nobody has bussed it, and the host does not know it is free. Two things fix this: a floor view that flags tables needing reset, and a habit of marking availability the moment the wipe-down is done.
5. The seating gap
Table is clean and available, but the waiting party is outside and nobody has told them. A waitlist that texts automatically closes this in seconds instead of minutes.
Fixes you can apply this week
None of these require hiring, and none of them involve rushing a guest.
- Let guests order without waiting. QR ordering on the table removes the biggest single gap. Keep servers for hospitality, not order-taking.
- Let guests pay without asking. Pay-at-table via QR removes the second biggest gap. This one change alone often accounts for half the improvement.
- Route tickets by station. Mains to the line, drinks to the bar, desserts held until fired. Pacing improves immediately.
- Add a reset flag on your floor view. Bussed tables should be visibly distinct from occupied and available ones.
- Text your waitlist automatically. Do not send a host outside to shout names.
- Review your slowest day part weekly. Fifteen minutes with the numbers beats a quarterly consultant.
How to know you are faster, not just rushing
This matters more than the speed itself. A rushed guest does not come back, and no efficiency gain survives that.
Watch three numbers alongside turn time. If turn time drops while these hold steady or improve, you are genuinely more efficient. If they slide, you have crossed the line.
- Average order value. Rushed guests skip dessert and the second drink. If AOV falls as turn time falls, you are pushing.
- Review sentiment. Watch for the words rushed, hurried, or pushed out in new reviews.
- Repeat visit rate. The slowest signal, and the most honest one.
The short version
- Measure seat to reset, not seat to close. The reset gap is where minutes hide.
- The two biggest leaks are waiting to order and waiting to pay. Both are solvable without staff changes.
- Route kitchen tickets by station to fix course pacing.
- Track AOV, review sentiment and repeat rate to confirm you are efficient rather than rushing.
Frequently asked questions
What is a good table turn time for a restaurant?
It depends on format. Quick service aims for 20 to 30 minutes, casual dining 45 to 60, fine dining 90 or more. The number that matters is your own baseline and whether it is trending down while complaints stay flat.
Does QR ordering actually speed up table turns?
Yes, and mostly by removing waiting rather than rushing eating. Guests order when they decide and pay when they are ready, which typically removes six to ten minutes per cover.
How do I measure table turn time accurately?
Seated to reset-and-available, not seated to paid. Most POS systems track seat-to-close and miss the reset gap entirely.
Frequently asked questions
What is a good table turn time for a restaurant?
It depends on your format. Quick service aims for 20 to 30 minutes, casual dining 45 to 60 minutes, and fine dining 90 minutes or more. The number that matters is your own baseline and whether it is trending down without complaints rising.
Does QR ordering actually speed up table turns?
Yes, mostly by removing wait time rather than rushing guests. Guests order the moment they decide instead of waiting to catch a server, and they can pay without flagging anyone down, which typically removes 6 to 10 minutes per cover.
How do I measure table turn time accurately?
Measure from the moment a guest is seated to the moment the table is reset and available again, not to the moment they pay. Most POS systems track seat-to-close but miss the reset gap, which is where a surprising amount of time hides.
