Reservations and Waitlists

How Far in Advance to Open Reservations

Set your reservation booking window from real demand, choose rolling or batch release, and decide which tables to hold back for later.

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

On this page
  1. What the booking window controls
  2. Measure your lead time before you choose
  3. Choosing a window by demand level
  4. Rolling windows versus batch releases
  5. Holding tables back and releasing them later
  6. Seasons and holidays need their own window
  7. Large parties and private bookings
  8. Telling guests when the book opens
  9. Review the window every quarter
  10. Frequently asked questions
  11. References
Reservations and Waitlists: How Far in Advance to Open ReservationsArticle coverRESERVATIONS AND WAITLISTSHow Far in Advance toOpen ReservationsAva for RestaurantsInsightsReservations and Waitlists: How Far in Advance to Open ReservationsArticle coverRESERVATIONS AND WAITLISTSHow Far in Advance toOpen ReservationsAva for Restaurants

Key takeaways

  • Match the booking window to how far ahead your prime slots actually fill, measured from your own lead-time data.
  • Rolling windows suit most rooms; batch releases suit rooms where demand far outstrips seats.
  • Hold back a share of tables to release later so regulars and walk-ins still have a way in.
  • Open holiday books earlier than the normal window, with their own policy.

What the booking window controls

Your booking window is how far ahead guests can reserve: seven days, thirty days, ninety days. It decides who gets your best tables. A long window rewards planners and visitors; a short one keeps tables free for locals and regulars who decide later. It also changes your workload, because every extra week of open inventory adds confirmations, changes and cancellations to manage.

Bookings do not only arrive during opening hours. An early Cornell analysis cited an estimate that 25% of online restaurant reservations are made between 10 pm and 10 am[1], when most dining rooms are closed. That is one reason a window matters even for small rooms: if the book is open, guests will fill it at midnight, so set it on purpose.

Measure your lead time before you choose

Lead time is the gap between when a booking is made and when the guest dines. Most reservation systems can export booking date and dining date; if yours cannot, log it for a month. Then answer three questions for your busiest slot, usually Friday or Saturday at 7:00 pm.

  1. How many days before the date is that slot four-fifths booked?
  2. What share of those bookings were made more than 14 days ahead?
  3. How many of the long-lead bookings later cancelled or did not show?

If prime slots fill five days ahead, a 60-day window adds risk without adding covers. If they fill three weeks out and you still have a waiting list for them, a longer window or a batch release may serve you better.

Example: a 110-seat bistro finds Saturday 7:00 pm is four-fifths booked nine days out, while Tuesday never gets past about 60%. It sets a 21-day rolling window, enough to cover the Saturday fill with a margin, and leaves weeknights open for walk-ins.

Choosing a window by demand level

Starting points for booking windows by demand pattern; adjust with your own lead-time data
Demand patternSuggested windowRelease styleHold-back
Weeknights rarely full14 to 30 daysRollingBar and counter only
Weekends fill a week ahead21 to 30 daysRollingAbout 10% to 20% of tables
Weekends fill three weeks ahead30 to 45 daysRolling, released at a fixed hourAbout 20% of tables, released 48 hours before
Every night sells out on release14 to 30 daysBatch on a set day and timeBar, counter and a same-day release
Tourist or event-driven60 to 90 daysRollingSmaller hold-back, larger walk-in bar

These are starting points, not rules. Two things push the window longer: guests who travel in and must plan, and groups that need to coordinate several people. Two things push it shorter: a loyal local base and high no-show rates on long-lead bookings.

Rolling windows versus batch releases

A rolling window opens one new day at a time, for example each morning at 10:00 am the date 30 days out becomes bookable. It spreads demand and is easy for guests to understand. A batch release opens a block, such as the whole of next month on the first of this month. Batch releases create a rush, which suits restaurants where demand is so high that the rush is going to happen anyway, and the goal is to make it fair and predictable.

  • Rolling: lower stress on systems and staff, fewer complaints about tables vanishing in seconds.
  • Rolling: prime slots for any date fill gradually, so lead-time reports stay meaningful.
  • Batch: one predictable moment for regulars to book; easy to announce on social media.
  • Batch: invites bots and resellers if you do not limit bookings per guest and verify phone numbers.

Whichever you choose, release at a fixed time of day that your team is awake for. If something breaks, someone should be able to fix it within the hour.

Holding tables back and releasing them later

Holding back means keeping some tables out of the online book at first and releasing them closer to the date, often 24 to 72 hours ahead, or keeping them for walk-ins altogether. It protects the guests who do not plan, such as regulars, neighbors and hotel guests, and gives the manager room to place large parties or accessibility needs well.

  1. Choose which tables to hold

    Pick tables that are easy to fill late: two-tops, the bar, the counter. Holding back large tables is risky because they are hard to fill at short notice.

  2. Set the release time

    Release held tables at a set time, such as 48 hours before service, so regulars learn when to look.

  3. Decide where they go

    Release some to your own website and phone first, then to booking networks. About 60% of diners who booked online in a Cornell study used a multi-restaurant site rather than the restaurant's own website[2], so a direct-first release favors guests who come to you.

  4. Track the result

    Check whether held tables were filled and how. If they routinely sit empty, hold fewer.

Seasons and holidays need their own window

Demand is not flat across the year. In 2025, US food services and drinking places sales ran from about $75.8 billion in February to about $92.8 billion in May, not seasonally adjusted[3]. Your booking window can move with that curve: a little longer in your peak months, shorter in slow months when same-day bookings carry the night.

US restaurant and bar sales by month, early 2025 (US dollars)Monthly sales, not seasonally adjusted, billions of dollars
US restaurant and bar sales by month, early 2025 (US dollars)Line chart. Jan: 76.8 billion; Feb: 75.8 billion; Mar: 89 billion; Apr: 86.5 billion; May: 92.8 billion.70 billion75 billion80 billion85 billion90 billion95 billionJanFebMarAprMayJan: 76.8 billionFeb: 75.8 billionMar: 89 billionApr: 86.5 billionMay: 92.8 billion92.8 billion76.8 billionUS restaurant and bar sales by month, early 2025 (US dollars)Line chart. Jan: 76.8 billion; Feb: 75.8 billion; Mar: 89 billion; Apr: 86.5 billion; May: 92.8 billion.70 billion75 billion80 billion85 billion90 billion95 billionJanMarMayJan: 76.8 billionFeb: 75.8 billionMar: 89 billionApr: 86.5 billionMay: 92.8 billion92.8 billion76.8 billion

Source: US Census Bureau, 2025[3]

Show the data
PeriodValue
Jan76.8 billion
Feb75.8 billion
Mar89 billion
Apr86.5 billion
May92.8 billion

Peak dates deserve their own policy. The National Retail Federation reported that 39% of Valentine's Day 2026 shoppers planned an evening out[4], and 40% of adults planned to use a restaurant for a Mother's Day meal in 2023[5]. Open these books earlier than your normal window, often 45 to 60 days, announce the release date in advance, and attach the holiday policy (set menu, seating times, deposits if you use them) to the booking itself. Our guide to reservation policies for holidays and peak nights goes further.

Large parties and private bookings

Groups need a longer horizon than two-tops. A party of ten needs time to agree a date and you need time to plan staffing and menus. Many restaurants allow large-party requests further out than standard bookings, by phone or form, with the manager confirming. Keep these outside the normal online window so they do not consume prime tables before you have agreed terms. See large party reservation policy examples for sample terms.

Telling guests when the book opens

A window only works if guests know it. When the release rule is unclear, the phone fills with people asking whether next month is open yet, and regulars feel shut out when tables vanish before they knew to look. State the rule in the same words everywhere: on the booking page, in the website footer, on your social profiles and in what the host says on the phone.

  • Website line: "Reservations open 30 days ahead at 10:00 am. A few tables are released 48 hours before each night, and the bar is always walk-in."
  • Phone script: "We open bookings 30 days ahead, every morning at ten. That date is not open yet, but I can tell you exactly when it will be. Would you like the bar as a back-up?"
  • Social post for a batch release: "Tables for December open this Monday at noon. Up to two bookings per guest. Bar and counter stay walk-in all month."

Keep the time zone in mind if you attract visitors, and keep a fair-use rule for batch releases: a limit on bookings per phone number or account, and a check for duplicate names on the same night. When a booking platform allows it, require a verified phone number for prime slots so that tables are held by people who intend to come.

Review the window every quarter

  • Lead time for prime slots: has the fill date moved earlier or later?
  • Cancellation and no-show rates by lead time: are long-lead bookings less reliable?
  • Walk-away and turned-away counts: are locals losing access?
  • Phone calls asking for tables "when do you open bookings?": a sign your release time is not clear.

Change one thing at a time and give it a month. Before you shorten or lengthen the window, honor every booking already made under the old rules and update your website, confirmation messages and phone answers on the same day. Then compare against our guide on whether to take reservations at all if the numbers suggest a bigger change.

Frequently asked questions

What is a typical restaurant booking window?

Many full-service restaurants use 14 to 30 days. Destination and tourist-driven rooms often go longer. The right window is the one that covers how far ahead your prime slots fill, measured from your own data.

Should I release all tables online at once?

Not usually. Holding back part of the room for later release or walk-ins protects regulars and gives you flexibility for large parties and accessibility needs.

When should holiday reservations open?

Earlier than your normal window, often 45 to 60 days out, with the release date announced and the holiday policy attached to each booking.

Does a longer window increase no-shows?

It can. Check cancellation and no-show rates by lead time in your own reports before lengthening the window.

References

  1. Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑

  2. Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑

  3. US Census Bureau (2025). Monthly Retail Trade: Estimates of Monthly Retail and Food Services Sales by Kind of Business (1992-present) (opens in a new tab) ↑

  4. National Retail Federation (2026). Valentine’s Day Spending Expected to Reach New Records (2026 survey with Prosper Insights & Analytics) (opens in a new tab) ↑

  5. National Restaurant Association (2023). Get ready for the mother of all restaurant holidays (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