Ask most operators which booking is most likely to vanish and they will say the party of twelve. The recorded data says the opposite: 10+ parties had the lowest no-show rate of any party size, and the two-top had the highest. The risk in a large party is real, but it is not the probability. It is the number of covers exposed when one does go missing.
The Restaurant No-Show Index 2026 reports recorded no-shows across 3,768,761 reservations from 2,417 restaurants between August 1, 2025 and July 31, 2026. It is a descriptive source for planning. It does not establish why a booking was missed or whether a deposit, reminder, or policy caused a particular outcome.
Worth being clear about why the belief is so durable, because it is not stupid. A missed party of twelve is memorable in a way that four missed two-tops across the same week is not: it leaves one conspicuous empty stretch of dining room, it usually involves prep that was already done, and it is the story the team retells. Frequency and salience are different things, and the assumption survives because nobody normally counts. When you do count, the pattern that emerges is that the largest bookings are the ones guests treat as an occasion, with someone in the group personally accountable for it happening.
This page is the data and the reasoning. For the operational workflow, the confirmation cadence, and the service-day mechanics, see how to manage large party bookings.
The data in brief
The party-size cut shows a lower recorded no-show rate as the reservation gets larger:
| Party size | Reservations | Restaurants | Recorded no-show rate |
|---|---|---|---|
| 1-2 guests | 1,860,642 | 2,399 | 2.63% |
| 3-4 guests | 1,150,708 | 2,379 | 2.13% |
| 5-6 guests | 414,338 | 2,331 | 2.28% |
| 7-9 guests | 187,425 | 2,231 | 1.73% |
| 10+ guests | 155,583 | 2,122 | 1.15% |
These are recorded rates, not a universal forecast for your restaurant. Your own history should decide where your policy changes. Keep the party-size bands visible in reporting so you can see whether your experience follows or differs from the index.
Why rate and capacity risk are different
No-show rate answers: “How often does a reservation not arrive?” It does not answer: “How many covers were unavailable when it happened?”
A 10-top represents five times the seats of a 2-top. If the 10-top does not arrive, the restaurant has also prepared a larger table configuration and may have turned away more demand. The index describes this as roughly three times as many expected covers at stake for a 10+ reservation compared with a table for two. The exact impact depends on your floor plan, turns, and ability to refill the space.
That is why large-party reporting should include both:
- Booking rate: recorded no-shows divided by eligible large-party reservations.
- Covers affected: the booked headcount attached to no-shows and late cancellations.
Do not turn the second measure into a claimed revenue loss unless you build a separate, clearly labelled model from your own average check, table turns, and recovered capacity.
Define your large-party threshold
There is no universal definition. Start with the operational change, then map it to a guest count.
Treat a reservation as a large party when one or more of these apply:
- tables must be joined or a special area must be held;
- the reservation blocks a meaningful part of a service period;
- the kitchen needs advance menu or dietary information;
- the booking needs a named owner, extra confirmation, or payment terms;
- a late change would be difficult to replace from the waitlist.
For one restaurant, that may begin at six guests. For another, it may begin at ten or when a booking requires a private room. Write the threshold into the booking flow and staff playbook so guests receive the same answer across channels.
Choose a proportionate policy
Use the lightest control that protects the capacity at risk. A useful policy can have several levels:
| Booking profile | Suggested control |
|---|---|
| Above your large-party threshold | Capture a phone number, occasion, dietary needs, and a specific headcount |
| Large party in a high-demand service | Add a confirmation deadline and a card guarantee or deposit if appropriate |
| Large party needing joined tables or a private area | Confirm final headcount, menu requirements, and payment terms before the deadline |
| Buyout or event-style booking | Use a separate written agreement reviewed for local legal and payment requirements |
The no-show index does not show that deposits cause lower no-show rates. If you use a deposit, card guarantee, minimum spend, or cancellation fee, describe it as a policy choice and check that it fits your local rules and payment provider terms.
A copy-paste large-party policy
Adapt the placeholders to your operation and have the final terms reviewed where required:
Large-party reservations
We classify bookings of [X] or more guests as large parties because they require a specific table plan and service preparation.
Please confirm your final headcount by [deadline]. Changes after this time may affect the table configuration and the terms shown at booking.
Your reservation is held until [time]. If you are delayed, call [phone number]. We will do our best to seat the party as guests arrive, subject to the room and service plan.
[A deposit of [amount] per guest / a card guarantee / no payment guarantee] applies. The terms are: [refund, cancellation, and no-show terms]. Any deposit will [be applied to the final bill / be handled as described here].
If your plans change, please use [cancellation link or phone number] so we can release the space and offer it to other guests.
Keep the policy short enough to read at checkout. Link to the full terms, but do not hide the deadline, payment requirement, or cancellation consequence in a separate document.
Build the workflow around the booking
At booking
Capture the information that changes the service plan:
- exact or provisional headcount;
- contact name, mobile number, and preferred contact method;
- occasion and timing constraints;
- allergies, dietary requirements, and accessibility needs;
- table configuration and any menu or payment expectations;
- the policy version shown to the guest.
If the guest gives a range, record both the expected number and the maximum. Ask for a specific final number before the confirmation deadline.
Before the deadline
Send one written confirmation that repeats the important terms. For a high-value or difficult-to-replace booking, assign a staff owner to check the response. The goal is to surface changes early, not to create unnecessary contact for every group.
When the final headcount changes, update the table plan and kitchen notes immediately. If the smaller party can be reseated without losing capacity, do that. If it cannot, explain the policy the guest saw at booking and offer the available alternatives.
On the day
Give the host and service team the same information:
- booked and confirmed headcount;
- table location and seating plan;
- arrival grace period and partial-arrival rule;
- payment or minimum-spend terms;
- contact person and escalation path.
If a group is late, record the contact attempt and release or reconfigure the space according to the policy. Avoid improvising a different rule at the door unless a manager documents the exception.
If the booking does not arrive
Use a short recovery checklist:
- confirm the reservation time and contact details;
- make one reasonable contact attempt through the agreed channel;
- note the status and any cancellation reason;
- release or reconfigure the tables when the policy allows;
- offer the space to the waitlist if there is still service capacity;
- record the covers affected, not only the booking count.
The index records no-shows and cancellations as separate outcomes. Keep those labels separate in your own data too, especially when a cancellation arrives shortly before service.
Measure whether the policy is working
Review large parties by the same bands used in your system. A simple monthly view can include:
| Metric | Calculation |
|---|---|
| Recorded no-show rate | Large-party no-shows / eligible large-party reservations |
| Late cancellation rate | Late cancellations / eligible large-party reservations |
| Covers affected | Booked covers on no-shows and late cancellations |
| Headcount accuracy | Actual covers / confirmed covers |
| Waitlist recovery | Refilled covers after a release / covers released |
| Policy exceptions | Bookings handled outside the written rule |
Compare like with like. Separate dinner from lunch, peak from off-peak, and deposit or guarantee cohorts from bookings without one. Treat the result as an operational comparison, not proof of causation.
The bottom line
Large parties are not automatically a higher no-show segment. In the current index, reservations of 10 or more had a 1.15% recorded no-show rate compared with 2.63% for reservations of 1-2. They still deserve a dedicated workflow because each booking can hold many covers and require more preparation.
Set your threshold from the floor plan, publish simple terms, confirm the final headcount, and track covers affected. Use deposits or card guarantees where they fit your operation and local requirements, but do not present an association in the data as proof that a payment policy caused the outcome.
Related guides: How to manage large party bookings | Restaurant cancellation policy | Restaurant no-show statistics (2026) | Do SMS reminders reduce no-shows? | Waitlist management