A restaurant should quote a wait from the next compatible table, not from the number of chairs it can see. Match the party to a table type, look at how that table has actually turned during this service, add a small buffer, and tell the guest when you will update them. That is more useful than promising every walk-in the same neat number.
This is deliberately narrower than our guide on reducing restaurant wait times. That guide fixes the whole flow: the line, the handoff and the empty-table gap. This one gives the host a repeatable way to answer the question at the door without guessing.
Do not quote the room; quote a compatible table
Start with the party in front of you. A two-top may fit at a bar, a deuce or a four-top you can split. A six-top may need one specific large table, or two tables that can genuinely be joined and served together. Empty seats elsewhere in the room do not shorten that party’s wait.
Before giving a number, make four quick checks:
- Classify the party. Record the party size and any practical requirement, such as a high chair, accessibility space or a table that can be joined.
- List compatible tables. Do not count a table as available merely because its total number of seats looks close.
- Look at the queue ahead. A three-top may be ahead of a two-top but unable to take the same next table. Queue order and table fit work together.
- Find the next real release. Use tables that are open, being reset or likely to clear based on what has actually happened in this service—not a hopeful glance at a check presenter.
That method prevents the common failure where a host sees four empty chairs across the room and tells a group of four to expect ten minutes, even though the only usable four-top is still on entrees.
Build a baseline from your own turns
You do not need an industry average to start. For two ordinary weeks, keep a simple record for each seated party: party size, table type, time seated, time the table was ready for the next party and service period. A dinner two-top, a Saturday four-top and a late-lunch six-top are different patterns.
Turn those timestamps into a small reference sheet for the host stand. It can be as simple as:
| Party and table | Service period | Observed turn range | Starting quote |
|---|---|---|---|
| Two at a deuce | Weekday dinner | Your recent range | Range plus buffer |
| Four at a four-top | Friday dinner | Your recent range | Range plus buffer |
| Six at a joinable table | Peak service | Your recent range | Range plus buffer |
The point is not to manufacture a universal “average turn.” It is to give the team a common starting point that becomes more accurate as it is compared with actual seating times. If the record is thin, quote more conservatively and say when you will check back.
Give a short range and a check-in promise
Guests can handle uncertainty better when you name it clearly. “For four, I would plan for 30 to 40 minutes. We will update you if that table opens earlier” gives the guest a usable choice. “About 20” does not.
Use a range only as wide as the room requires. The upper end should include the small tasks that make a table truly usable: payment, clearing, resetting, finding the next party and seating them. It should not hide an hour of uncertainty.
The language matters as much as the arithmetic. Train hosts to say what the number refers to and what happens next:
“For a table for four, the current estimate is 30 to 40 minutes. We will message you if we can seat you sooner, and we will update you before the top of that range if the floor changes.”
The guest now knows they are waiting for a compatible table, not a mysterious place in line. That clarity makes it easier to retain the party and easier for the host to revise the estimate honestly.
Recalculate before the guest has to ask
A quote becomes unreliable when the next likely table changes: a large party lingers, a server needs more time to close a check, a busser is pulled away or a compatible table is taken by the party ahead. The right response is not to protect the first number. It is to recalculate the affected groups and communicate early.
Work through the queue from the most constrained party first. A party of six with one possible table can be affected by a delay that has no impact on a two-top. For each affected party, decide whether the range still holds, has improved or needs a new estimate. A small early update preserves more trust than silence after the promised window.
Make the handoff part of the quote
The quote is not finished when a table clears. The next party still needs to know it is ready and get back to the host stand. A virtual restaurant waitlist lets guests join from a phone and receive a table-ready update by SMS, WhatsApp or email, so they can wait nearby instead of clustering at the door.
For the host, that means the same workflow carries the quote through to seating: add the party, give the range, send an update if the range moves and send the ready message when the table is available. The broader restaurant waitlist management guide explains how to keep that sequence consistent during a rush.
Our restaurant guest messaging guide helps teams define the message for an earlier table, a revised range or an unanswered table-ready notice without losing the original promise.
Review quoted versus actual after the rush
At close, compare five fields: party size, compatible table type, quoted range, actual seated time and service period. Mark why large misses happened: a longer meal, a reset delay, a queue-fit error or an estimate that began too optimistically.
Do not judge the team by one late table. Look for repeated patterns. If four-tops routinely exceed their upper range during Friday dinner, change that starting range. If two-tops are consistently seated early, tighten it carefully. Pair the operational review with the waitlist ROI calculator when you want to put a value on recovered seats and less idle table time.
StoveOps is designed for restaurants operating an owned live waitlist alongside their current POS: guests join from a phone and receive table-ready updates by SMS, WhatsApp or email. Start with one busy service, use the quotes your team can stand behind, then compare the result with your current workflow and pricing. The public plans include a 7-day trial; use it to test a real rush rather than a scripted demo.