What is a no-show in restaurants? Definition and tracking guide
A guest with a reservation who does not arrive and does not cancel.
A no-show is a guest who makes a reservation but does not arrive and does not cancel. It is a recorded booking outcome, not a guess based on an empty table. Track it separately from cancellations so your team can see both attendance and how much notice guests give when plans change.
Key facts
- Definition: A reservation marked no-show after the guest does not arrive or cancel.
- Formula: Recorded no-show rate = recorded no-shows / eligible reservations x 100.
- Benchmark: The Resos No-Show Index 2026 recorded 2.33% across 3,768,761 eligible reservations at 2,417 restaurants.
- Important caveat: Only 72.9% of eligible venues recorded at least one no-show, so the underlying rate may be higher than the recorded rate.
How to calculate a no-show rate
Use a stable definition:
Recorded no-show rate = (Recorded no-shows / Eligible reservations) x 100
For example, if your team records 4 no-shows across 200 eligible reservations, your recorded no-show rate is 2%.
Document what counts as an eligible reservation. The index excludes cancellations, unresolved bookings, test and duplicate reservations, and walk-ins. Your system may have different fields, but the same rule should be used every week.
Why the denominator matters
Different sources can report different no-show figures without disagreeing. A survey may ask diners whether they have ever missed a reservation. A platform may combine late cancellations with no-shows. A recorded per-reservation rate counts the booking outcomes a restaurant marks in its system.
The 2.33% index figure is a useful comparison because it has a defined denominator. It is not a target or a prediction for every restaurant. Booking channel, service, party size, local market, and staff recording practices all affect a restaurant’s own rate.
What to track with no-shows
Track the rate and the operational context together:
| Measure | Calculation | Why it helps |
|---|---|---|
| Recorded no-show rate | No-shows / eligible reservations | Shows booking outcomes consistently |
| Late cancellation rate | Late cancellations / eligible reservations | Shows how much time you have to recover a table |
| Covers affected | Booked covers on missed reservations | Shows capacity exposed, not just booking count |
| Waitlist recovery | Refilled covers / released covers | Shows whether released capacity was recovered |
Break the data down by service, party size, lead-time band, and booking source when you have enough observations. Do not draw conclusions from a very small segment or treat an association as proof of cause.
How to respond operationally
Start with accurate recording, a clear cancellation path, and a recovery plan for released tables. For a high-demand service, the team may also use confirmation, card guarantee, or deposit workflows that fit the restaurant’s policy and local requirements.
Measure one change at a time. Reservations with a delivered SMS reminder had a 16% lower recorded rate than comparable reservations at the same restaurants in the index, but the comparison was observational. Use it as a prompt to test your own workflow, not as a promised reduction.
Keep cancellations and no-shows separate. The same index found that 56.1% of recorded cancellations were within 24 hours of service or after the booking started. Earlier cancellation can make a table easier to recover, even when it does not change the no-show count.
Related terms
- Cover for the guest count attached to a reservation
- Walk-in for a guest who may fill released capacity
- Booking lead time for the time between booking and service
- Cover fee for a per-guest platform charge
Frequently Asked Questions
What is a typical no-show rate for restaurants?
Can restaurants charge for no-shows?
How do no-shows affect restaurant revenue?
Do SMS reminders actually reduce no-shows?
How do I track repeat no-shows?
Related: How to reduce no-shows | Restaurant no-show statistics (2026) | Restaurant cancellation policy guide | Waitlist management