Reservations and Waitlists

Table Turn Times by Party Size and Daypart

Use POS data to set realistic table turn times for twos, fours and large parties at lunch, dinner and brunch, then shorten them without rushing guests.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. What a turn time really measures
  2. Why every minute counts on busy nights
  3. Pull turn times from your POS
  4. Example turn-time results
  5. What makes turns run long
  6. Why dayparts differ
  7. Share the numbers with the floor team
  8. Set turn times in your system
  9. Shorten turns without rushing anyone
  10. Example: finding a second seating
  11. Frequently asked questions
  12. References
Reservations and Waitlists: Table Turn Times by Party Size and DaypartArticle coverRESERVATIONS AND WAITLISTSTable Turn Times byParty Size and DaypartAva for RestaurantsInsightsReservations and Waitlists: Table Turn Times by Party Size and DaypartArticle coverRESERVATIONS AND WAITLISTSTable Turn Times byParty Size andDaypartAva for Restaurants

Key takeaways

  • Turn time is seat-to-reset, not just how long guests eat; measure it from POS check times plus a reset buffer.
  • Set separate turn times by party size and daypart, using the median for planning and a higher percentile for peak nights.
  • The biggest delays are usually at the start and end of the meal, not in the middle.
  • Paying at the table and timely check drops can shorten turns without making guests feel rushed.

What a turn time really measures

A table's turn time is how long it is unavailable for the next party: from the moment guests sit down to the moment the table is reset and ready. It includes the meal, but also the wait for menus, the wait for the check, the time to pay and the time to clear and reset. Reservation systems use it to decide when the next booking can go on that table, so a wrong number either leaves tables empty or stacks guests at the door.

Most restaurants set turn times once, by feel, and never revisit them. Your point-of-sale system already holds better data. Every check has an open time, a close time, a table and usually a guest count. With a few hours of work you can turn that into turn times you can defend.

Why every minute counts on busy nights

Turn times matter most when demand is high. A University of California, Berkeley study found that moving from 3 to 3.5 Yelp stars raised a restaurant's chance of selling out at prime times from 13% to 34%[1]. When you are selling out, the only way to serve more guests in the same room is to plan turns accurately and protect them.

Chance of selling out at prime dining times, by Yelp rating (San Francisco study)
Chance of selling out at prime dining times, by Yelp rating (San Francisco study)Comparison. 3 stars: 13%; 3.5 stars: 34%.13%3 stars3 stars: 13%34%3.5 stars3.5 stars: 34%Chance of selling out at prime dining times, by Yelp rating (San Francisco study)Comparison. 3 stars: 13%; 3.5 stars: 34%.13%3 stars3 stars: 13%34%3.5 stars3.5 stars: 34%

Source: University of California, Berkeley, 2012[1]

Show the data
ItemValue
3 stars13%
3.5 stars34%

Cost pressure makes it more pressing. Food and labor each take roughly 33 cents of every sales dollar[2]. The labor in the room is the same whether a table turns once or twice in a night, so a realistic turn plan that adds a second seating on a few tables changes the economics of the shift.

Pull turn times from your POS

  1. Export check data

    Download eight to twelve weeks of checks with table number, guest count, open time, close time and day. Exclude takeout, delivery and bar tabs.

  2. Clean the data

    Remove checks opened long before guests sat, checks left open by mistake, and transfers between tables. Note which checks were split.

  3. Add a reset buffer

    Check close is not table ready. Time a few resets on a busy night and add that buffer, often a few minutes, to every check.

  4. Group by party size and daypart

    Twos, threes and fours, fives and sixes, and seven or more, for lunch, weekday dinner, weekend dinner and brunch.

  5. Calculate the median and a high percentile

    The median shows a typical table. A higher percentile, such as the 80th, shows the slow tables you must still plan for.

  6. Compare with your system settings

    Put the results next to the turn times in your reservation system and note the gaps.

If the POS cannot tell you when guests sat, use the time the first item was ordered and add a few minutes for greeting. The goal is consistency, not perfection: the same method every time lets you see change.

Example turn-time results

Example median seat-to-reset times for a fictional casual full-service restaurant, including a reset buffer
Party sizeLunchWeekday dinnerWeekend dinnerWeekend brunch
252 min84 min96 min68 min
3–461 min98 min112 min79 min
5–674 min118 min131 min95 min
7+88 min139 min152 min112 min

Example: this restaurant's system was set to 90 minutes for every party at dinner. The data shows twos turning faster on weekdays and every larger party running longer, especially on weekends. Booking a six at 90 minutes on Saturday guarantees that the next party waits.

What makes turns run long

  • Slow first contact: menus and drinks arriving late push the whole meal back.
  • Kitchen surges: when pacing is too loose, entrées slow down for every table at once.
  • Celebrations: birthdays, anniversaries and business dinners linger; mark them on the booking so the turn time can be longer.
  • Booths and corner tables: guests often settle in for longer than at tables in the middle of the room.
  • The check: waiting for the check, then waiting again to pay, can add more time than dessert.
  • Late arrivals: a party 15 minutes late eats into the next booking's buffer.

Late arrivals deserve a clear policy. Cornell research found that holding a table for a stated period, typically 15 minutes, is seen by diners as fair and acceptable[3]. State it at booking so a late party does not quietly destroy the next table's timing.

Why dayparts differ

Lunch guests often have a meeting or a job to get back to, so meals are shorter and guests welcome speed. Weekday dinners are more relaxed but still end at a sensible hour. Weekend dinners stretch, with more courses, more drinks and more celebrations. Brunch is its own pattern: meals can be quick, but groups arrive staggered, wait for the last friend and linger over coffee.

Season matters too. Patio nights in summer often run longer than winter dinners indoors, and holiday weeks bring larger family tables. Run the export separately for your busiest season if your turns change noticeably through the year.

Share the numbers with the floor team

Servers and hosts see the room every night, but they rarely see the data. Show them the turn-time table in a pre-shift meeting and ask what they think drives the slowest tables. They will often point to things the data cannot show: a section far from the kitchen, a printer that jams, a dessert that takes too long to plate. Fixing those helps every table, and it makes the team part of the plan rather than the target of it.

Set turn times in your system

Use the median plus a small cushion for normal nights, and something closer to the high percentile for your busiest nights or for tables that tend to run long. Set them by party size and daypart, not one number for everything. If your system allows, set longer turns for booths and celebration bookings.

  • Weekday dinner: median plus a few minutes of cushion.
  • Weekend dinner: closer to the high percentile, because a late turn on Saturday hurts more.
  • Brunch: often shorter meals but longer waits for tables; check door waits too.
  • Large parties: always manual review, with a set time slot if possible.
  • Holidays: separate turn times for set menus, which often move faster.

Shorten turns without rushing anyone

Guests should never feel hurried out. The time to recover is at the edges of the meal, where nothing is happening from the guest's point of view.

  • Greet and take drink orders within a couple of minutes of seating.
  • Fire the first course promptly; ask about appetizers with the drink order.
  • Pre-bus as courses finish, so the reset starts before guests leave.
  • Drop the check when guests signal they are done, not after a long wait.
  • Let guests pay at the table: 65% of adults would be comfortable paying their check at a full-service restaurant with a tablet at the table[4].
  • Reset with a ready kit at each section so tables are turned in minutes.

Never use turn times as a reason to tell a guest their time is up, unless you told them about a time limit at booking. Use them to plan the book, not to police the table.

Example: finding a second seating

Example: a fictional 100-seat bistro measures weekend turns and finds its two-tops average well under its 105-minute setting, while sixes run long. The manager lowers the two-top setting, raises the six-top setting, and adds pay-at-table devices for the patio. On Saturdays the book now fits a second seating on several two-tops that used to sit empty after 9 p.m., and parties of six stop waiting for their table.

Example: the manager reruns the export every quarter and after menu changes, since a new tasting menu or a slower dessert course changes turns overnight. Pacing and turns work together, so revisit reservation pacing at the same time, and use walk-ins vs reservations to decide how many of the freed-up tables to hold for the door.

Frequently asked questions

What is a good table turn time?

There is no single number. Measure seat-to-reset times from your POS by party size and daypart, then set your reservation system from your own medians plus a cushion.

How do I calculate table turn time?

Export checks with open and close times, table and guest count, remove errors, add a reset buffer, and calculate the median for each party size and daypart.

Should turn times be different at lunch and dinner?

Yes. Lunch, weekday dinner, weekend dinner and brunch usually differ, and so do party sizes. One setting for everything leaves tables empty or guests waiting.

How can we shorten turn times politely?

Speed up the parts guests do not enjoy: the wait for menus, the wait for the check and the wait to pay. Pay-at-table and pre-bussing help most.

References

  1. University of California, Berkeley (2012). Yelp reviews boost restaurant business (Anderson and Magruder, Economic Journal) (opens in a new tab) ↑

  2. National Restaurant Association (2026). Restaurants remain resilient despite challenging business conditions (opens in a new tab) ↑

  3. Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑

  4. National Restaurant Association (2024). Serving Up Technology: New Data Shows How Tech Integration is Transforming the Restaurant Experience (Restaurant Technology Landscape Report 2024) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo