Key takeaways
- Configure the room before the calendar: tables, combinations and sections first, then turn times and pacing.
- Write policies once and use them everywhere: late hold, cancellations, card guarantees for large parties.
- Put the booking button on your home page and map listings; many bookings are made when you are closed.
- Run a soft launch with staff bookings before opening the book to the public.
Why setup decides how your nights feel
A reservation system is a model of your restaurant. If the model is wrong, the system will happily book tables you cannot seat, stack arrivals your kitchen cannot cook for, and leave gaps you could have sold. Most of the frustration owners feel with booking software traces back to setup decisions made in a rush on the day it was installed.
Getting it right matters because dining room business matters. In the National Restaurant Association's 2025 research, 90% of fine dining operators and 87% of casual dining operators said growing on-premises business is important to their success[1]. The reservation book is where that growth is won or lost, one Friday at a time.
Source: National Restaurant Association, 2025[1]
Show the data
| Item | Value |
|---|---|
| Fine dining | 90% |
| Casual dining | 87% |
The setup sequence
Build the table inventory
Enter every table with its number, minimum and maximum party size, and features such as booth, patio, high-top, accessible or window.
Define combinations and sections
Record which tables can be pushed together and the party sizes each combination seats. Group tables into server sections.
Set turn times
Give each party size a dining duration for each daypart, based on your own data where possible.
Set pacing
Limit how many covers or parties can arrive in each 15-minute window, based on kitchen and floor capacity.
Create shifts and booking windows
Define services, first and last seating times, how far ahead guests can book and the same-day cutoff.
Write policies
Late hold time, cancellation window, large-party rules and any card guarantee, with the exact wording guests will see.
Connect channels
Website, map listings, booking networks, phone and walk-in waitlist, all writing to the same book.
Set confirmations and reminders
Choose what guests receive, when, and how they change or cancel.
Soft-launch
Book staff and friends for a few services, fix what breaks, then open the book to the public.
Table inventory and combinations
Walk the room with a floor plan and a tape measure rather than copying an old seating chart. Note which tables really seat four comfortably and which only seat four when the guests are friends. Record minimum party sizes too: if a four-top should not go to a single diner on Friday night, the system needs to know.
- Name tables the way staff say them, so hosts and servers use the same numbers.
- Mark accessible tables and any with step-free routes from the door.
- Enter combinations as explicit pairs or groups, with the party size each one seats.
- Block tables that are held for walk-ins, the bar or regulars, rather than leaving them bookable and hoping.
For a detailed walkthrough of this step, including sections and combinable tops, see how to map your floor plan in a reservation system.
Turn times and pacing
Turn times tell the system how long a table will be occupied; pacing tells it how many guests can arrive at once. Set both before taking a single booking. Start with realistic estimates, then replace them with your own point-of-sale data after a few weeks.
| Party size | Lunch | Weekday dinner | Weekend dinner |
|---|---|---|---|
| 2 | 60 min | 90 min | 105 min |
| 3–4 | 75 min | 105 min | 120 min |
| 5–6 | 90 min | 120 min | 135 min |
| 7+ | Manual | Manual | Manual |
For pacing, a common approach is to cap covers per 15-minute window at a level the kitchen can fire without the line falling behind. See reservation pacing for the method and table turn times by party size for using POS data.
Shifts and booking windows
- First and last seating for each service. Last seating should leave the kitchen enough time to serve a full meal before close.
- Booking horizon: how many days ahead guests can book. Longer horizons suit destination restaurants; neighborhood spots often use a few weeks.
- Same-day cutoff: whether guests can book online up to the last minute or only until a set time.
- Special dates: holidays and events with their own shifts, menus and policies, set up weeks in advance.
- Blackouts: private events and buyouts entered as blocks, so nothing is double-sold.
Policies guests accept
Policies protect your tables, but they only work if guests see them as fair. Cornell research found diners view holding a table for a stated period, typically 15 minutes, as fair and acceptable[2]. US diners also consider table-holding policies and credit card guarantees the most acceptable reservation policies, while penalties for parties that arrive smaller than booked were seen as the least acceptable[3].
- Late hold: state the hold time on the booking page, in the confirmation and in the reminder.
- Cancellation: a clear window, such as by noon the day before, and how to cancel.
- Card guarantees: consider them for large parties, holidays and set menus, and explain them before the booking is final.
- Party size changes: ask guests to tell you, and make it easy by text.
Write each policy once, in plain language, and paste the same text into the booking page, phone script, confirmation and reminder. Mismatched wording causes most policy disputes.
Booking channels
Every channel should write into the same book. Guests also book at odd hours: Cornell research cited an estimate that 25% of online reservations were made between 10:00 p.m. and 10:00 a.m., and 59% of restaurants using online reservations saw sales increase as a result[4]. Yet in a later Cornell study only 9% of restaurants that took online reservations offered reservation access on their home page[5].
- Website: booking button at the top of the home page and on the menu page, working well on a phone.
- Map listings: connect a supported booking partner so guests can book from your listing; see how to get reservations through Google Maps.
- Booking networks: decide which, if any, to list on, and check how their fees and guest data terms work.
- Phone: hosts enter bookings live in the same system.
- Walk-ins and waitlist: managed in the same tool so the floor view is complete.
Train the team before the first guest books
A well-configured system still fails if hosts work around it. Give every host and manager a short session on the screens they will use most: the floor view, the booking form, the waitlist and the guest profile. Then practise the moments that go wrong: a party that arrives early, a booking that needs moving to a different table, a walk-in squeezed into a gap, a no-show released after the hold time.
- Agree who may override pacing limits and when, and make overrides visible in the system.
- Decide what goes into guest notes and what does not; keep notes factual and polite, because guests can sometimes see them.
- Practise entering a phone booking while talking, with the readback, until it takes well under a minute.
- Show servers how to mark tables as seated, on dessert and paid, so the floor view stays accurate.
Review after 30 days
- Compare planned turn times with actual table durations from the POS and adjust.
- Check which 15-minute windows ran over the pacing limit and how the kitchen coped.
- Review no-shows and late cancellations by channel and day.
- Read guest feedback that mentions booking, confirmation or waiting.
- Confirm every channel still writes to the book and every link still works.
Confirmations, reminders and soft launch
Send a confirmation immediately and one reminder the day before, both with the policies and a one-tap way to change or cancel. Ask for a mobile number and consent to text at booking. Keep marketing out of these messages.
Example: a fictional bistro runs three soft-launch services with staff and friends making real bookings through every channel. The team finds that the patio tables were bookable on rainy days and that the confirmation linked to an old menu. Both are fixed before the public launch, along with a turn time for parties of six that proved too short.
Frequently asked questions
What should I set up first in a new reservation system?
The room: every table, its capacity and features, combinations and server sections. Turn times, pacing and channels depend on getting the room right.
How long should a restaurant hold a table for late guests?
Cornell research found diners see a stated hold of about 15 minutes as fair. Whatever you choose, state it at booking and in reminders.
Should we require a credit card for reservations?
Card guarantees are among the reservation policies diners find most acceptable, especially for large parties and holidays. Explain the terms before the booking is final.
How do we avoid double-booking across channels?
Connect every channel to one book of record and have hosts enter phone bookings live, so availability updates everywhere at once.
References
National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry press release) (opens in a new tab) ↑
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) ↑
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑
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) ↑
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) ↑