Most conversations about table turn time start with revenue: more turns, more covers, more money. I think that gets it backwards. A table that turns too slowly is often a table where the guest sat waiting for a check they asked for ten minutes ago. A table that turns too fast is a table that felt hurried. Both are hospitality failures before they are financial ones. The goal is pacing the guest wants, and you can only manage that if you can see where the minutes actually go.
I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success, and today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco. I built Regular inside it, one service at a time. Here is how I break a turn into stages, where I look for lost time, and how I coach servers on pacing without anyone feeling rushed.
Turn Time Is a Hospitality Question
A turn time on its own tells you almost nothing. Ninety minutes could be a relaxed couple who lingered over a second bottle, or a four-top who spent twenty of those minutes trying to flag someone down for the check. The number is the same. The experience is opposite.
That is why I treat turn time as a service standard first. The question I ask is not "how do we get tables out faster" but "did this table move at the speed the guests wanted, and when it didn't, whose minutes were those?" Some minutes belong to the guest: the conversation between courses, the decision about dessert. Others belong to us: the wait for a greeting, the empty plates that sit, the card that takes a long time to run.
Picture a guest who is ready to leave and cannot get the check. Those last ten minutes often colour how they remember the whole meal. Removing our minutes improves the visit and frees the table. Squeezing the guest's minutes does neither for long, because rushed guests tend not to come back.
The Stages of a Table Turn
You cannot coach a single number. You can coach stages. When I look at a turn, I split it from the moment the party sits to the moment the table is reset:
- Seated to greeted: how long before someone acknowledges the table.
- Greeted to first order: drinks, and sometimes food in the same visit.
- Order to first course landed: mostly kitchen, partly the server firing on time.
- Courses and clears: the guest's time, with our clearing and refiring in between.
- Last plate to check requested: dessert, coffee, lingering.
- Check requested to paid: almost entirely ours.
- Paid to departed to reset: the guest leaving and the table being ready again.
Once a turn is in stages, patterns appear quickly. A server whose total turns look average may be fast at greeting and slow at closing. Another may be the opposite. In Regular, the Server Performance app splits each table turn into stages from seated to departed, which is the view I wanted when I was trying to work this out from receipts and memory.
Where the Minutes Usually Go
In my experience, most lost time sits at the edges of the meal, not the middle. The middle belongs to the guest and the kitchen. The edges belong to the floor.
The first edge is the greeting. A table that waits several minutes for water and a hello starts the meal behind, and often orders later and slower because the momentum is gone. The second is the gap after the last plate. Plates sit, nobody offers dessert, and the guest decides on their own that they are done, then waits again to tell someone.
The third, and often the biggest, is payment. The check is requested, the server is in the weeds, the check arrives, the card sits in the folder, the card is run, the slip comes back. Each of those handoffs can add minutes, and none of them make the guest happier.
Reset is the last one. A table that is empty but not set is a table the host cannot seat, which pushes into the next reservation. When I review a slow night, I look at these four edges before I ever ask the kitchen to speed up.
Coaching Servers on Pacing
Pacing is a skill, and it can be taught. The mistake I see most is coaching to the total: "your turns are too long." That gives a server nothing to do differently. Coaching to a stage does. In customer success I spent years breaking onboarding into steps so we could see exactly where customers stalled; restaurant tables respond to the same approach.
Here is the routine I use before a service:
- Pick one stage to focus on tonight, usually the one where the team lost the most time last week.
- Name the standard out loud at pre-shift, for example: greet within a couple of minutes of seating, or drop the check as soon as it is asked for.
- Pair a server who is strong at that stage with one who is still learning it.
- Read each table for cues: menus closed, plates pushed aside, a guest looking around the room.
- After service, look at that one stage per server and give one specific note, not a ranking speech.
On technology: it should show the manager the stages after service and highlight patterns worth coaching. It should not buzz a server mid-conversation or put a timer between them and the guest. I cover where this fits in the manager's week that works.
When a Guest Waits Past Their Reservation
Reservation wait time is where pacing problems become visible to guests who have not even sat down. A slow close at one table becomes a party standing at the host stand fifteen minutes past their booking.
The first fix is upstream: protect the reset and the check stages above, because they create most of the overlap. But on a busy night it will still happen, and how the host handles it matters more than the delay itself.
What I ask hosts to do: acknowledge the party by name the moment they arrive, give an honest estimate rather than "just a few minutes", and offer them somewhere to be, like a seat at the bar with a drink, rather than leaving them by the door. Then check back before the estimate runs out, not after. If the wait runs long, the manager goes over in person.
Picture a guest who waited twenty minutes but was looked after the whole time. They often remember the care, not the clock. A first-time guest who was ignored for the same twenty minutes rarely books again. I wrote more about that second visit in how to turn first-time guests into restaurant regulars.
Setting Targets by Party Size
A single turn target for the whole room is unfair to most of your tables. A two-top and an eight-top are different meals. Larger parties order more slowly, share more, and linger longer, and they should.
I set targets by party size from our own history, not from a number someone quoted at a conference. Pull several weeks of closed checks from your point of sale, group them by party size, and look at the middle of the range for each. That is your starting target. Then adjust for format: a tasting menu night or a weekend brunch may need its own targets.
Review them weekly. If a party size keeps running long, go back to the stages and find which one is stretching. If a party size keeps running short, ask whether guests felt hurried before you celebrate. In Regular, the Reports app shows table turns against party-size targets, which is how I keep this review to a few minutes on a Monday. You can see every app in Regular or book a demo if that is useful.
If you measure turns differently, I'd like to hear how. You can find me on Instagram.
Frequently Asked Questions
What is table turn time in a restaurant?
Table turn time is how long a table is occupied by one party, from the moment they are seated to the moment the table is ready for the next guests. Many restaurants measure it from seated to paid, but including departure and reset gives a truer picture, because a table that is empty but not set still cannot be used for the next reservation.
How can a restaurant improve table turn time without rushing guests?
Focus on the minutes that belong to the restaurant rather than the guest. Greet tables quickly, clear plates promptly, offer dessert at the right moment, drop the check as soon as it is requested, run payment fast and reset tables right away. Leave the time between courses and the conversation to the guest. That shortens turns while making the visit feel smoother.
Should table turn targets be the same for every table?
In my experience, no. Larger parties usually order more slowly, share dishes and stay longer, so one target for the whole room is unfair to them. Set separate targets by party size using your own point-of-sale history, adjust for formats like brunch or tasting menus, and review the targets weekly against how guests actually experienced the meal.
What should a host do when guests wait past their reservation time?
Greet the party by name right away, give an honest estimate rather than a vague promise, and offer them somewhere comfortable to wait, such as a seat at the bar. Check back before the estimate runs out. If the wait gets long, a manager should go over in person. Guests often forgive a delay when they feel looked after throughout it.