Playbooks

How to cut table-turn time without rushing guests

Faster turns mean more covers, but rush guests and you lose them. The bottlenecks that quietly cost you tables, and how to clear them gracefully.

By The Crubby TeamPublished on 17 May 20266 min read

Every empty table on a busy night is revenue you can never get back. But the fix isn't speed for its own sake, it's removing the dead time guests never asked for in the first place.

The short version

  • Turn time is the gap between seatings, not how fast people eat, most of the waste lives in greet, fire, and payment, not at the table.
  • Shaving even five to ten minutes off a turn can add a full extra seating on a peak service.
  • The check is the single biggest source of avoidable dead time; pay-at-table closes it.
  • Measure your actual turn times before you change anything, gut feel is usually wrong.

The math: why a few minutes matter so much

Table turn time is the elapsed time from when one party is seated to when the next party can be seated at that table. It is not the same as how long guests linger, it includes the slack before they're greeted, the lag between courses, the wait for the check, and the time the table sits dirty before it's reset.

Do the arithmetic on a single table. If your average dinner turn runs roughly 90 minutes and a peak service window is about three hours, that table delivers two seatings. Trim the turn to 75 minutes, without anyone feeling hurried, and on many nights you unlock a third. Across a 20-table room, that is a meaningful lift in covers from the same kitchen, the same staff, and the same rent.

A turn you can't refill is worthless

Faster turns only help if you can fill them. The lever is most powerful when you regularly turn guests away or run a waitlist; in a half-full room, hospitality beats speed every time.

Find the bottlenecks (they're rarely where you think)

A turn is a chain of handoffs, and the slow links tend to be invisible because they happen between the obvious moments. The usual suspects:

  • The greet. Parties seated but not acknowledged for several minutes. Drinks order delayed, kitchen ticket delayed, everything downstream slips.
  • The order. Servers taking orders sequentially across a section instead of in a planned sweep; indecision unaided by a clear, scannable menu.
  • Fire timing. Appetizers and mains landing too close or too far apart. Bad coursing either rushes guests or strands them between plates.
  • The payment. The long, quiet wait after the last bite, flag the server, wait, get the check, wait, pay, wait for the card back. This is the classic dead zone.
  • The bus and reset. A table cleared but not wiped, reset, and re-marked as available, the host can't seat it even though it's empty.

Most operators overestimate how long guests spend eating and underestimate the bookends, the slow greet at the start and the slow checkout at the end.

Clear the bottlenecks gracefully

Pace the courses, don't compress them

Good coursing is the difference between a meal that feels attentive and one that feels rushed. The goal is to eliminate gaps where guests sit with empty plates and nothing happening, not to fire everything faster. Expediting that keeps the next course moving the moment plates clear does more for your turn than any single trick, and guests read it as good service, not haste.

Kill the checkout dead time

The end of the meal is where minutes vanish silently. Industry observers have long pointed at the check-out sequence as the most fixable chunk of a turn. Pay-at-table devices and QR-based payment let guests settle the moment they're ready, on their own phone, without hunting for a server. Adoption of self- and contactless payment in hospitality has climbed steadily since the pandemic era, and the payoff is less about novelty than about reclaiming the five-to-ten minutes a table sits idle waiting on a piece of paper.

Nobody ever felt rushed because they could pay the instant they decided to leave. They feel rushed when the food shows up before they've finished talking.

A common refrain among floor managers

Staff the floor for the handoffs

Turn time is a labor story as much as a process one. A dedicated busser or a runner system keeps tables resetting while servers stay with guests; a host who actively manages the seating chart fills openings the instant they appear. Understaff the floor on a peak night to save on labor and you pay it back in lost turns, often at a worse rate than the wages you saved.

Smooth the front door

Acknowledge every party within a minute or two, get drinks and water moving immediately, and make the menu easy to decide from. A cluttered or confusing menu adds quiet minutes at the start of every turn; a clear one moves the order along and, not coincidentally, tends to nudge the average check upward too.

Measure before you optimize

You cannot improve a number you don't track. Before changing anything, capture your real turn times, by daypart, by section, by table size, and find your true distribution, not your average.

  1. 1.Time a sample of turns end to end: seated, greeted, ordered, fired, paid, reset.
  2. 2.Break each turn into its segments so you can see which stage is bleeding minutes.
  3. 3.Look at the worst tables and the worst hours, not the averages, that's where the recoverable time hides.
  4. 4.Change one thing, then re-measure. Pacing, payment, and staffing each move the needle differently.

Make it a number someone owns

Set a turn-time target per table size and daypart, and treat it like a kitchen ticket time, visible, owned, and reviewed. What gets watched gets managed.

The hospitality line you don't cross

There's a hard limit to this game: the moment a guest senses they're being processed, you've lost more than a turn, you've lost the relationship and the word of mouth. Cleared plates before everyone's finished, a check dropped unprompted, a hovering server: these are the tells diners hate. The art is removing your friction without adding theirs. Every change above either is invisible to the guest or actively improves their experience. That's the test for whether you're cutting turn time or just rushing people.

What's a normal table turn time?
It varies wildly by format. Quick-casual rooms may turn in well under an hour, casual dining often sits somewhere around an hour to ninety minutes for dinner, and fine dining can run two hours or more by design. There's no universal target, benchmark against your own format and your own peak demand.
Does pay-at-table really speed things up?
It mainly removes the dead time at the end of the meal, the wait to flag a server, get the check, and settle up. That stretch is often several idle minutes per table, and on a busy night that's exactly the slack that adds up to an extra seating. It also tends to be the change guests welcome rather than resent.
Won't faster turns hurt my reviews?
Only if guests feel it. Speeding up your internal handoffs, greet, fire timing, payment, bussing, is invisible to diners. Compressing the meal itself, clearing plates early, or hustling people out is what shows up in reviews. Cut the former, never the latter.
Where should I start if I can only fix one thing?
Usually the checkout. It's the largest pocket of avoidable dead time, it's the same on every table, and fixing it doesn't touch the guest's actual meal. After that, look at your reset process so empty tables don't sit unseatable.

The bottom line

Cutting table-turn time isn't about making guests eat faster, it's about deleting the minutes they never wanted in the first place: the slow greet, the misfired courses, the long wait for a check, the table that sits dirty too long. Measure where your turns actually leak, attack the bookends before the meal itself, and hold the hospitality line without exception. Done right, more covers and better service aren't a trade-off. They're the same project.

Keep reading