Hold back enough tables to serve a realistic share of walk-in demand, but only after accounting for the physical tables needed by confirmed reservations. Start with a small holdback for each arrival period, review what actually happened, and adjust by night and table size.
The right number is not a percentage you can apply to every service. A Saturday with a line at the door needs a different allocation from a quiet Tuesday. The decision also depends on whether your open tables fit the parties who arrive.
Measure demand by arrival period and table size
Start with a service period narrow enough for the host to make useful decisions, such as 6:00 to 7:30 p.m. List the physical tables available in that period and the largest party each can seat comfortably. Note which tables can be combined, and which become unavailable when that happens.
Then separate demand into two groups:
- Confirmed reservations: Count parties, covers, arrival times, and any seating needs. A reservation for six is one party and six covers; it may require two physical tables.
- Walk-in arrivals: Count parties and covers who arrived without a booking, including those who left before being seated. Record their party sizes and arrival times.
Do not count an empty table as available just because the previous party is expected to leave soon. Allow for the time needed to clear and reset it. If a party is still dining when the next reservation arrives, the host needs another suitable table or a plan to manage the delay.
Use past services to find patterns, not a perfect forecast. Separate ordinary weekdays, weekends, holidays, and event nights. A local concert may change both arrival times and party sizes. Record cancellations and no-shows separately from walk-in demand; the guide to reservation no-shows can help you examine that part of the picture.
For a new restaurant with little history, pick a conservative starting holdback and have the manager check it during service. Write down every change. After several comparable services, you can see whether the starting rule protected too many tables or too few.
Compare holdback choices with a capacity worksheet
The following example is hypothetical. A restaurant has six physical four-seat tables available for one seating period. Each party fits at one table, and a table can serve only one party in that period. There are no combined tables, blocked tables, or second seatings. The restaurant limits advance reservations to the tables not held for walk-ins.
On a busy night, assume five parties want to reserve and two walk-in parties arrive. On a quiet night, assume three parties want to reserve and one walk-in party arrives. Reservation requests and walk-ins are separate parties. The worksheet compares a one-table holdback with a two-table holdback:
| Demand | Walk-in holdback | Reservations accepted | Walk-ins seated; tables unused |
|---|---|---|---|
| Busy: 5 reservation requests, 2 walk-in parties | 1 table | 5 parties | 1 seated; 0 unused |
| Busy: 5 reservation requests, 2 walk-in parties | 2 tables | 4 parties | 2 seated; 0 unused |
| Quiet: 3 reservation requests, 1 walk-in party | 1 table | 3 parties | 1 seated; 2 unused |
| Quiet: 3 reservation requests, 1 walk-in party | 2 tables | 3 parties | 1 seated; 2 unused |
On the busy night, both choices seat six parties, but they allocate one table differently. With a one-table holdback, the fifth reservation is accepted and one walk-in party cannot be seated in that period. With two held tables, the fifth reservation request cannot be accepted, while both walk-in parties can be seated. Neither choice breaks a promise to an accepted reservation, provided the tables are ready.
On the quiet night, both choices seat the same four parties and leave two tables unused. A larger holdback offers no extra benefit under those assumptions. If more reservation requests arrived, keeping two tables locked until service could turn away a booking unnecessarily.
For these assumptions, a two-table holdback is reasonable on the busy night if welcoming both expected walk-in parties matters more than accepting the fifth reservation request. On the quiet night, use the smaller holdback and review availability as service approaches. This is an allocation decision, not a revenue calculation: the example excludes sales, fixed costs, variable costs, and exception costs.
Build your own worksheet with actual table types and arrival windows. If a four-top is held but two parties of two arrive, you cannot seat both there at once. Equally, two open two-tops may not work for a party of four unless they can be combined. The number of covers alone will not tell you whether a promise is safe.
Set release times and host override rules
A holdback should have an owner and an expiration point. Otherwise, online inventory can remain closed while suitable tables sit empty, or a host can seat a walk-in at a table needed for an upcoming booking.
Choose a release time for each arrival period. For example, a manager might review the holdback 60 minutes before the period starts. Release a held table for additional reservations only if the remaining walk-in allocation still matches current demand and the table can accommodate a new booking alongside existing commitments. A release time is a review trigger, not an instruction to open every table automatically.
Give the host a short decision order:
- Check confirmed reservations by arrival time, party size, and seating needs.
- Assign suitable tables, allowing time for clearing and reset. Do not allocate the same physical table to overlapping parties.
- Check the held tables against current walk-in demand and any parties already waiting.
- Release, retain, or use a held table for a walk-in; record the reason and tell the manager when the choice changes the plan.
Define who can override the rule. A host might release a table within the agreed window, while a manager approves a change earlier or handles an unusually large party. If a booked party needs an accessible location or another specific arrangement, protect a suitable table rather than treating all four-tops as interchangeable.
Also decide what happens when a reservation is late. Tell staff how long to wait, who can make an exception, and how the guest will be contacted under your restaurant's policy. Do not assume that a late arrival creates a free table until the host has checked the reservation and the rest of the floor plan.
When comparing a restaurant reservation system, ask how staff set availability by time and party size, block or release inventory, and see changes made by another employee. Ask whether it supports your actual table combinations and whether staff can distinguish a holdback from a table already committed to a booking. If it cannot express your rule, decide how the host will maintain the missing information without creating conflicting promises.
Review missed seating, waits, and unused tables
At the end of each comparable service, review more than the number of covers. The useful question is whether the allocation matched the parties who needed seats when they needed them.
- Reservation requests not accepted: Record the requested time and party size, including requests lost because suitable inventory was unavailable.
- Walk-in parties not seated: Note party size, arrival time, quoted wait, and whether they left before seating.
- Reservation waits: Note when booked parties arrived and when they were seated, plus the reason for any delay.
- Unused held tables: Record which tables stayed empty, for how long, and whether a suitable request could have used them.
- Overrides: Note who changed the holdback, when, and why.
Review those notes alongside the floor plan. An unused table is not automatically wasted capacity if it was the only suitable backup for a confirmed party. A walk-in who leaves is not automatically evidence that the holdback was too small; the party may have needed a table size you did not have. Change one rule at a time where practical, then compare similar services.
Software can make the workflow easier to coordinate, but the host still needs a clear operating rule. If you also use restaurant management software, ask how reservation information reaches the people managing the floor and what they must update manually.
Booking source matters as well. OpenTable offers restaurant operations and reservations alongside a diner discovery network. A direct booking path through your own website serves a different purpose. Ask each provider about booking-channel attribution, permissions, exports, and fees; also ask whether Google bookings are available for your location. Compare written quotes for the workflow you expect to use, rather than assuming the channels have the same costs or guest-data terms.
Before changing providers, assign one person to own the cutover. Reconcile booking counts and preserve the booking identity, local date and time, party size, status, and appropriate special requests using authorized access and a supported transfer method. Practice the floor plan and holdback decisions with simulated bookings first; a simulation should not send guest messages or create real payments. Then monitor a live service pilot with staff ready to resolve discrepancies.
Next step: Pick one upcoming arrival period, list its usable physical tables and confirmed bookings, and calculate one- and two-table holdbacks using your own demand. Compare the resulting host workflow against your operating requirements with Fleksa's reservation system.
Frequently asked questions
How many tables should a restaurant hold for walk-ins?
There is no universal number. Start with the walk-in parties you reasonably expect in a specific period, match them to suitable physical tables, and protect the tables needed for confirmed bookings. Review the result after comparable services.
When should held tables return to reservation inventory?
Set a review time before each arrival period. Release a table only after checking current bookings, waiting walk-ins, table suitability, and the time needed to prepare it. Keep an override available for the host or manager.
Should cancellations automatically become walk-in tables?
Not necessarily. First check whether the freed table is needed for another reservation or an existing wait. Then decide whether to offer it to a walk-in or reopen it for bookings under your release rules.
