When should a restaurant open its waitlist? A sober workflow for capacity and contact
A practical walkthrough of four steps in the waitlist decision: which capacity signals should trigger it, how expectations are kept realistic both internally and externally, which contact order is easiest to defend, and why a fixed expiry time makes every enquiry predictable to handle.
Capacity figures that actually trigger the waitlist
Many restaurants open the waitlist because the evening 'feels' full, not because the numbers show it. A firmer rule is to look at the share of tables booked for the coming hours, weighed against average seating time. How high this share should be before the waitlist opens is something each restaurant must decide for itself, based on its own experience with traffic and table turnover.
The threshold should also take table types into account. A fully booked two-seater does not mean a party of four can be seated, even if the overall capacity overview shows free space. The restaurant should therefore assess the threshold per table size, so the waitlist opens for the right guest group rather than for capacity that does not match the need anyway.
Managing expectations internally and externally
Internally, staff should know what the waitlist means on a given evening: an estimate in minutes, not a promise. Whether this estimate is built on previous seating times, kitchen pace, or a combination of both is something the restaurant must clarify itself. If the estimate changes because a table stays seated longer than expected, the update should happen immediately, not at the next lull in service.
Externally, managing expectations means giving the guest the same estimate that staff themselves believe in. An approximate time span is often more honest than a precise time the restaurant cannot guarantee. The guest should also be told what happens if the estimate changes, so that a delay feels like an update the restaurant had prepared for, not a broken promise.
The contact order that is easiest to defend
The simplest order to explain, both internally and to guests who ask, is registration time combined with a party size that actually fits an available table. The first registered party that matches the table becoming free is contacted first. Deviations from this - for instance seating a smaller party before a larger one because it fits better - should be explainable with one clear reason.
The restaurant should also decide in advance who gets contacted if two parties match the same table at the same time. A fixed rule, such as the earliest registered going first regardless of a small difference in size, removes the need to assess each situation from scratch. This makes the order easier to explain to a guest wondering why another party was seated ahead of them.
An expiry time that makes every enquiry predictable
Without a fixed expiry time, every contact with a waitlisted guest becomes a fresh judgment call: should we wait a little longer, or move on now? How long this period should be is a question the restaurant must decide for itself, based on how busy it usually is and how quickly tables actually become free. A fixed limit removes the need to reassess this anew every evening.
The expiry time should be the same for everyone, but clearly communicated to the guest at first contact, so it does not come as a surprise. When the time runs out without a response, the restaurant moves on to the next person on the list without having to weigh exceptions. In TableBooking, the dashboard shows bookings, guests and the table map together, so staff can keep track of which tables are in use.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free