Restaurant Operations

Customer Wait Time: When the Table Before Runs Long

Picture a couple with a 7:30 reservation who end up standing at the bar until 7:50 because the four-top they were promised is still on dessert. They may love the food when it arrives. In my experience, the story they tell a friend the next day starts with the twenty minutes. A restaurant wait time on a booked table feels different from a wait at a walk-in spot: the guest did their part by booking, and the restaurant did not keep its side.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, and 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, the hospitality operating system, inside that restaurant, one service at a time. This article covers how to measure how often back-to-back parties wait past their booked time, what usually causes it, and how to coach it without hurrying the table in front.

The Wait Guests Remember

Most managers I talk to know their average table turn time. Far fewer know how often a guest with a reservation stood at the host stand while their table was still occupied. Those are different questions. A dining room can hit its turn targets on average and still leave the 8:00 party waiting three Saturdays in a row, because averages hide the specific tables that ran long right before a tight booking.

The wait is also lopsided in how it lands. The party that lingered had a lovely evening. The party behind them paid for it. They arrive on time, often hungry, sometimes with a babysitter on the clock, and the first thing the restaurant communicates is that their time mattered less than the table before.

I think of this as a promise problem rather than a speed problem. A reservation is a promise of a time. When the room breaks it, the guest experience starts in debt, and the server inherits a table that is already a little annoyed before anyone has said hello. That is why I treat back-to-back waits as their own number, separate from pace, and look at them every week.

Measuring Waits You Can Check

The measure I use is simple: of all the back-to-back reservations on a table, what share waited past their reservation time because the party before them was still seated. Three pieces of data make it work, and most restaurants already have them in their reservation system and point of sale:

  • The reservation time of the second party.
  • When the first party actually left, from the check close or the host marking the table clear.
  • When the second party was actually seated.

If the first party left after the second party's booked time, and the second party was seated late, that is a wait caused by the table before. If the second party arrived late themselves, it is not.

The detail that matters most is that every wait can be opened and checked. In software customer success I learned that people trust numbers they can verify and argue with numbers they cannot. A server shown a percentage will push back. A server shown the 6:15 table that closed at 8:20 and the 8:00 party seated at 8:25 will usually nod. That is how Customer Wait Time works inside Server Performance in Regular: the share of back-to-back parties who waited, with each wait listed so a manager can look at it.

Why the Table Before Ran Long

Once you can see the individual waits, the causes tend to sort into a few groups. In my experience they look like this.

The first table started late. If the 6:00 party was seated at 6:20 because their own table ran long, the delay cascades down the night. Fix the earliest wait and several later ones disappear.

A slow stage in the middle. Splitting each table into stages, from seated to order, food, check and departure, shows where the time went. A long gap between seated and first order points at the greeting. A long gap between dessert and check points at the close. I wrote more about this in pacing service without rushing guests.

The book was too tight. Some waits are not the floor's fault. If a six-top is booked into a two-hour slot that your room realistically needs two and a half hours for, the wait was planned at the moment the reservation was taken.

A guest who simply stayed. Some tables linger after the check is paid. That is part of hospitality, and the answer is a better plan for the next party, not pressure on the one enjoying themselves.

Coaching Without Rushing Anyone

The worst response to a wait problem is telling servers to turn tables faster. Guests feel it immediately, and the server ends up hovering with the check. The better approach is to coach the stages a server actually controls and leave the guest's pace alone.

Picture a server whose tables keep causing waits. Looking at the stages, the pattern is usually narrow: maybe the check arrives eight or ten minutes after the guests decline dessert, or the first drink order takes too long on a busy section. Those are teachable. Offering the check with the dessert decline, or greeting within a couple of minutes even when slammed, does not rush anyone. It removes dead time the guests did not ask for.

I look at a few weeks of data before I say anything, because one bad night says little. Then I bring two or three specific waits to a short conversation and ask the server what they saw. Often they know exactly what happened. The approach in coaching the stages of a table applies here too.

Technology should find the pattern and hand the manager specific examples. It should not put a countdown in front of the server at the table or turn waits into a public leaderboard. Coaching is a conversation, not a scoreboard.

What to Do While a Guest Waits

Measurement and coaching reduce waits over weeks. Tonight, some guests will still wait, and how the first few minutes go decides most of what they remember. This is the routine I would hand a host before service:

  1. At lineup, check which tables have a tight booking behind them and tell those servers by name.
  2. Around 15 minutes before the next reservation, the host checks on that table: are they on dessert, has the check gone down?
  3. When the party arrives and the table is not ready, the host says so plainly, gives an honest time and does not guess low.
  4. The manager, not just the host, greets the waiting party within a few minutes.
  5. Offer something real at the bar or a standing spot: a drink, a small bite, a place to put coats. Decide in advance what the host is allowed to offer.
  6. Seat them, then have the manager stop by the table once more.
  7. After service, note the wait and the cause in the shift log so the weekly review has context.

None of this needs a screen in front of the guest. The system's job is to tell the host earlier which tables are at risk, so the people at the door have time to be people. If you want to see how Regular handles this, you can book a demo.

You can find me on Instagram.

Frequently Asked Questions

What is a reasonable wait time for a restaurant reservation?

Many guests will accept a few minutes past their booked time, especially if the host is honest and offers somewhere comfortable to wait. Past ten or fifteen minutes, in my experience, the wait starts to shape how they remember the meal. The better goal is not a target number of minutes but fewer back-to-back parties waiting at all, which comes from realistic booking intervals and steady pacing.

How do you measure reservation wait time in a restaurant?

Compare three times for back-to-back reservations on the same table: the second party's reservation time, when the first party left and when the second party was seated. If the first party left after the booked time and the second party was seated late, count it as a wait. Divide those waits by all back-to-back reservations to get a share you can track weekly.

Why do restaurant tables run long?

Common causes include the earlier party being seated late, slow stages such as a delayed greeting or a long gap between dessert and the check, bookings placed in slots too short for the party size, and guests who simply linger. Splitting each table into stages shows which cause applies, so the fix targets the booking, the service or the plan for the next party.

How can servers turn tables faster without rushing guests?

Focus on the time servers control rather than the guest's pace. Greet promptly, take the first drink order quickly, fire courses on time and offer the check as soon as guests decline dessert. Removing these gaps shortens table turn time without hovering or pressuring anyone. Coach from specific examples across several weeks rather than reacting to a single busy night.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.