A no-show feels like a small thing in the moment — a table sits empty for twenty minutes, someone shrugs, service moves on. Multiplied across a month, it's rarely small.
The direct loss is the easiest part to see: an empty table during peak hours that could have turned twice. The harder part to see is what it costs in staffing — a restaurant schedules servers assuming a certain covers count, and a run of no-shows on a Friday night means someone's standing around getting paid for a shift that isn't producing revenue.
Most restaurants treat no-shows as random bad luck. In practice, they cluster: a specific reservation source (a particular platform, a particular time slot, a particular day of week) is almost always responsible for a disproportionate share. That's a fixable pattern, not a fact of life — but it only shows up once someone actually looks at when and where the no-shows are coming from, not just that they're happening.
The other quiet cost is what a no-show does to the rest of the night: a kitchen that fired a table's food that never got eaten, a server who now has a lopsided section, a host managing a waitlist against tables that were never actually going to open up.
Find out what this is actually costing your business — free, 60 seconds, no signup.
Start My Free Assessment