Reservations and table management

How to set table turn times that work

Set booking durations by party size and day part from your own EPOS and booking data, with a worked example, reset buffers and weekly checks.

Ava research teamPublished 7 min read

On this page
  1. Why one duration does not fit every table
  2. Why it matters more this year
  3. Step one: get the data
  4. Step two: work out the durations
  5. Example: durations by party size and day part
  6. Step three: adjust for menus and occasions
  7. Set the reset buffer honestly
  8. Mistakes that undo good durations
  9. Tell guests, kindly
  10. Check it weekly for the first month
  11. Example: what the change did
  12. Frequently asked questions
  13. References

Key takeaways

  • One booking duration for every table either wastes seats or rushes guests; set durations by party size and day part instead.
  • Use eight weeks of seated and bill-closed times from your EPOS and booking system, and set durations near the slower end of what guests actually take.
  • Add a short reset buffer between bookings, and adjust for menus and occasions such as Sunday lunch or tasting menus.
  • Check weekly for late seatings, overruns and empty gaps, and adjust in small steps.

Why one duration does not fit every table

Many booking systems ship with a single default duration, often two hours, and many venues never change it. The result is predictable. Couples at weekday lunch leave after an hour and their table sits empty for the second hour. A party of eight on a Saturday night needs longer than two hours, runs over and the next booking waits at the bar.

A turn time, or booking duration, is the time your booking system reserves a table for a party. Getting it right is one of the cheapest ways to add covers without adding seats, and one of the easiest ways to improve how guests feel about their evening.

Why it matters more this year

Revenue per seat is under pressure from both sides. Costs keep rising: the National Living Wage for workers aged 21 and over rose to £12.71 an hour from April 2026[1], and median hourly pay for waiting staff was £12.81[2]. Meanwhile demand is uneven. In September 2026, 30.7% of trading UK accommodation and food businesses said domestic demand had fallen compared with August, while only 4.4% said it had risen[3].

Change in domestic demand reported by UK accommodation and food businesses, September against August 2026
Change in domestic demand reported by UK accommodation and food businesses, September against August 2026Bar chart. Demand stayed the same: 35.4%; Demand fell: 30.7%; Demand rose: 4.4%.Demand stayed the sameDemand stayed the same: 35.4%35.4%Demand fellDemand fell: 30.7%30.7%Demand roseDemand rose: 4.4%4.4%Change in domestic demand reported by UK accommodation and food businesses, September against August 2026Bar chart. Demand stayed the same: 35.4%; Demand fell: 30.7%; Demand rose: 4.4%.Demand stayed the sameDemand stayed the same: 35.4%35.4%Demand fellDemand fell: 30.7%30.7%Demand roseDemand rose: 4.4%4.4%

Source: Office for National Statistics, 2026[3]

Show the data
ItemValue
Demand stayed the same35.4%
Demand fell30.7%
Demand rose4.4%

Most operators are cautious about raising prices further: 72.9% of accommodation and food businesses kept prices the same in September 2026, and 12% raised them[4]. The managed restaurant groups that are growing are doing so slowly, with like-for-like sales up 2.6% year on year in September[5]. When prices are hard to push and demand is patchy, using the seats you already have well becomes one of the main levers left.

Step one: get the data

  1. Choose a period

    Take at least eight recent weeks of trading. Avoid December and any weeks with unusual events, or analyse them separately.

  2. Export seated and closed times

    From your EPOS, export each table's open time and the time the bill was closed, with the number of covers. If your booking system records seated and left times, use those too.

  3. Match to party size and day part

    Group each table by party size (one or two, three or four, five or six, seven or more) and by day part (weekday lunch, weekday dinner, Friday and Saturday dinner, Sunday lunch).

  4. Remove the odd ones out

    Drop tables that were left open by mistake, staff meals and private hires. A table open for five hours is usually an error, not a slow guest.

  5. Add the reset time

    Ask hosts to time how long it takes to clear, reset and seat a table at each size for a few services. This becomes your buffer.

Step two: work out the durations

For each group, sort the dining times from shortest to longest. Do not use the average: a few long tables drag it up, a few quick ones drag it down, and it describes almost nobody. Instead, look at two points.

  • The middle value, or median: half of parties take less than this, half take more.
  • The slower end, roughly the time by which eight in ten parties have paid. This protects the next booking.

A good starting duration is the slower-end figure, rounded up to the nearest 15 minutes, plus your reset buffer. That way most parties finish comfortably, and the few who linger rarely collide with the next booking because the buffer absorbs it.

Example: durations by party size and day part

Example booking durations for a fictional 70-cover restaurant, including a 15-minute reset buffer
Party sizeWeekday lunchWeekday dinnerFriday and Saturday dinnerSunday lunch
1 to 21h 15m1h 45m2h1h 45m
3 to 41h 30m2h2h 15m2h
5 to 61h 45m2h 15m2h 30m2h 15m
7 or more2h2h 30m2h 45m2h 30m

Example: these figures come from a fictional restaurant, not a benchmark. Your numbers will differ by menu, format and guest. A small-plates bar may find large groups take longer than the table suggests; a café may find lunch is much faster.

Step three: adjust for menus and occasions

  • Tasting or set menus: time them separately. Courses set the pace, so durations are more predictable but usually longer.
  • Sunday lunch: families, roasts and second rounds of drinks make it slower than a weekday lunch of the same size.
  • Pre-theatre: guests leave on time; set a shorter duration and a firm finish, and say so when they book.
  • Celebrations: birthdays and anniversaries often run long. If your booking system records the occasion, add time for them.
  • Children: families with young children often eat faster at lunch and slower at weekend dinner. Check your own data.
  • Seasonal menus: re-time durations after a menu change, especially if you add courses or sharing dishes.

Set the reset buffer honestly

The buffer is the gap between one party leaving and the next sitting down. It covers clearing, wiping, relaying and getting the next party to the table. Too short and new guests stand by a dirty table; too long and you lose a turn across the evening.

Most venues find a buffer of 10 to 20 minutes realistic, longer for big tables that must be split or pushed together. Measure it rather than guessing, and measure it on a busy night, because that is when it matters.

Mistakes that undo good durations

  • Setting durations from memory. Managers tend to remember the slow tables and the rushed ones, not the typical evening. Use the data.
  • Changing every duration at once. If covers fall or complaints rise, you will not know which change caused it.
  • Ignoring the kitchen. Shorter durations mean more covers arriving close together; check the pass can cope before you open extra slots.
  • Letting the floor ignore the system. If hosts seat walk-ins on tables the system has held, durations stop meaning anything. Agree a rule and stick to it.
  • Forgetting combined tables. Pushing two fours together for an eight takes longer to set and clear; give large parties a longer buffer.
  • Treating the duration as a deadline for guests. It is a planning tool for you. Staff should manage the end of a meal gently, not present a bill at the two-hour mark.

Most of these come down to the same principle: durations work when the booking system, the floor team and the kitchen all plan from the same numbers.

Tell guests, kindly

Shorter durations only work if guests know about them before they arrive. Say it on the booking page and in the confirmation, in friendly words, and train staff to manage the end of the meal without rushing anyone. Our guide to limiting table times and telling guests politely has wording you can adapt. If you are deciding between fixed sittings and flexible durations, read two sittings or open booking first.

Check it weekly for the first month

  1. Late seatings: how many booked parties waited more than ten minutes for their table, and why.
  2. Overruns: how many tables stayed past their booked end and delayed the next booking.
  3. Empty gaps: how often a table sat unused for more than 30 minutes between bookings at peak.
  4. Guest comments: any mention of feeling rushed, in person, in reviews or by email.
  5. Covers: total covers per service compared with the same weeks last year.

Change one thing at a time, in 15-minute steps. If larger tables keep overrunning on Saturdays, add 15 minutes to that cell only, rather than to every duration.

Example: what the change did

Example: a fictional 70-cover neighbourhood restaurant had used a single two-hour duration for every booking. After timing eight weeks of tables, it set the durations in the table above. Weekday lunch twos now book at 1 hour 15 minutes, which opened an extra 12.30 and 1.45 slot on most tables. Saturday eights now book at 2 hours 45 minutes, which ended the regular 9pm queue at the bar.

Example: over the following month, weekday lunch covers rose, Saturday covers were flat but late seatings dropped sharply, and no guest commented on feeling rushed. The restaurant reviews its durations every quarter and after every menu change. It also uses the data to plan the floor; see table mix and revenue per available seat hour.

Frequently asked questions

What is a typical table turn time?

There is no reliable UK benchmark, because it depends on menu, format and party size. Use your own EPOS data: time eight weeks of tables by party size and day part, and set durations near the slower end of what guests actually take.

Should we use the average dining time?

No. Averages are pulled about by a few very fast or very slow tables. Use the middle value to understand typical parties and the slower end, where most parties have finished, to set durations.

How long should the reset buffer be?

Measure it. Most venues find 10 to 20 minutes realistic, longer for large or combined tables. Time it on a busy night rather than a quiet one.

How often should we review turn times?

Weekly for the first month after a change, then every quarter and after any menu change.

References

  1. GOV.UK (2026). National Minimum Wage and National Living Wage rates (opens in a new tab) ↑

  2. Office for National Statistics (2026). ASHE 2026 provisional, Table 14.6a: hourly pay excluding overtime by occupation (opens in a new tab) ↑

  3. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (domestic demand) (opens in a new tab) ↑

  4. Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (prices) (opens in a new tab) ↑

  5. NIQ (CGA by NIQ) with RSM (2026). Bright September gives hospitality groups their best growth of 2026 (restaurant groups) (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