Prime cost and food cost percentage get most of the attention because they sit right there on a P&L, waiting to be calculated. Three other leaks almost never do: no-shows, comps and discounts, and slow table turnover. Each one quietly reduces revenue without ever being named as a line item, which is exactly why they're so easy to underestimate.
None of the three requires new software or a POS overhaul to measure. This guide walks through what each leak actually costs, how to total it up with numbers you already have, and how the three add up across a single month for one worked example.
Why these leaks never show up on a standard P&L
A P&L reports what happened — total sales, total food cost, total labor cost — not what should have happened if every table had been filled, every reservation had shown up, and every discount had been deliberate. No-shows show up only as slightly lower-than-forecast revenue, with no line explaining why. Comps and discounts get buried inside a single "promotions" or "other" line, if they're tracked separately at all. Slow table turns don't show up anywhere, since a P&L has no concept of how many additional covers a faster turn could have served. All three require pulling the number out deliberately — they won't surface on their own.
Leak #1: No-shows
Industry sources put average restaurant no-show rates somewhere in the 5%–20% range depending on the type of reservation system and deposit policy in place, with some markets reporting rates as high as one in four reserved tables going unfilled on a busy night. The real cost isn't just the empty seats — it's the prep, staffing, and turned-away walk-ins that went with holding that table in the first place.
A useful way to think about the net cost: no-shows lose revenue, but walk-ins seated at tables that would otherwise have sat empty partially offset that loss. The number that actually matters is the difference between the two, not the raw no-show count on its own.
Worked example
A 60-seat restaurant runs 45 reservations on a Saturday night with a $34 average check and a 14% no-show rate — roughly 6 reservations, or 13 covers accounting for average party size. If 5 of those seats get backfilled by walk-ins over the course of the night, the net loss is 8 covers × $34 = $272 for that single service. Run consistently across four Saturdays a month, that's roughly $1,100 a month from one shift alone — before counting Friday nights or any other high-reservation period.
The no-show revenue loss calculatorruns this net-of-walk-ins math automatically for any period, which turns a vague sense of "we get a lot of no-shows" into an actual dollar figure worth deciding whether a deposit policy or reservation confirmation system would pay for itself.
Leak #2: Comps and discounts
A comped appetizer here, a manager discount there, a percentage-off promotion that ran two weeks longer than planned — individually, each one looks negligible. Restaurant accounting guidance consistently notes that total comps and discounts can run well in excess of 10% of gross sales at venues that track the dollar amount but never total up the margin impact, and that gap between "tracked" and "totaled up as a percentage" is exactly where this leak hides.
Worked example
A restaurant doing $150,000 in monthly gross sales runs a mix of server comps, a 15% off promotion, and manager discretion discounts totaling $6,000 for the month — 4% of gross. That 4% sounds modest against the total, but measured against net margin rather than gross revenue, it can represent a much larger share of what actually would have hit the bottom line, since a comp or discount comes straight off the top with no offsetting reduction in food or labor cost for that ticket.
The comp & discount cost trackertotals comps, discounts, and coupons as a single percentage of gross revenue, which makes it possible to see the number in one place instead of reconstructing it from scattered POS discount codes at month's end — and to judge whether a given promotion is actually paying for itself in the extra traffic it drives, rather than just assuming it is.
Leak #3: Slow table turnover
The dead time between one party leaving and the next party being seated — sometimes called idle gap — typically runs somewhere between 14 and 22 minutes per turn once bussing, resetting, and greeting delays are counted. That gap doesn't show up as a cost anywhere; it shows up as fewer total covers served during a service period that had the demand to fill more of them.
The industry-standard way to measure this is revenue per available seat hour (RevPASH) — total revenue divided by seat-hours available — which captures both how full the room ran and how quickly tables turned, in a single figure that's easier to track over time than turnover rate alone.
Worked example
A 50-seat dining room running a 3-hour dinner service averages 1.8 turns instead of a realistic 2.2 turns for that concept and seating count, with a $38 average check. The difference — 0.4 turns × 50 seats × $38 — works out to roughly $760 in unrealized revenue for that single service. Repeated across a typical 20 dinner services a month, that gap alone represents well over $15,000 in monthly revenue the room had the demand to serve but the turn speed didn't capture.
The table turnover & revenue per seat calculatorturns turns-per-service and average check into a revenue-per-seat figure for any period, which surfaces this gap as a dollar number rather than a turnover-rate percentage that's harder to act on directly.
Putting all three leaks side by side
None of these numbers are large enough on their own to trigger alarm on a monthly P&L review. Added up, they tell a different story. Using the worked examples above for a single restaurant in one month:
| Leak | Monthly estimate | % of a $150,000 month |
|---|---|---|
| No-shows (net of walk-ins) | ~$1,100 | 0.7% |
| Comps & discounts | ~$6,000 | 4.0% |
| Slow table turnover | ~$15,000 | 10.0% |
| Combined | ~$22,100 | ~14.7% |
A combined figure in that range — a real, if wide, possibility once slow table turnover is included — is large enough to change how a menu repricing decision or a staffing investment gets evaluated. It's also why measuring each leak individually, rather than eyeballing the P&L for anything that looks off, is worth the twenty minutes a month it actually takes once the habit is in place.
Common mistakes when tracking these leaks
- Tracking no-shows as a raw count instead of net of walk-ins. A restaurant that backfills most no-shows with walk-ins has a much smaller real revenue problem than the raw no-show count suggests — the net figure is what matters for deciding whether a deposit policy is worth the friction it adds at booking.
- Measuring comps against net margin only, never against gross revenue.A single consistent percentage-of-gross figure, tracked monthly, is easier to compare over time and against other restaurants' benchmarks than a dollar figure alone.
- Treating a slow Tuesday the same as a slow Saturday.Turnover speed only represents lost revenue during periods with enough demand to fill the seats faster — a slow turn on an already-quiet Tuesday isn't costing anything, while the same slow turn on a fully-booked Saturday is a direct revenue loss.
- Reacting to one bad week instead of a trend.All three leaks are noisy at the weekly level. A single rough Saturday doesn't mean turnover has a structural problem; a pattern across several weeks does.
- Assuming a discount promotion is working without checking the number against it.A promotion that drives enough extra traffic can be worth running even at a real cost — but that's a decision that needs the actual percentage-of-gross figure in front of it, not a guess about how busy the room felt.
Building a monthly leak-audit routine
These three numbers don't need to be checked weekly the way prime cost does — a monthly pass is usually enough to catch a real trend without adding another task to an already full week. A workable routine: run the no-show and comp/discount numbers at month's end alongside the regular P&L review, and check table turnover quarterly or after any change to seating layout, service pacing, or staffing. See reading your restaurant's numbers without a CFO for how these three fit alongside prime cost and break-even in a full weekly-and-monthly routine.
The goal isn't to drive any of the three to zero — some no-shows, some comps, and some turnover slack are normal in any service business. The goal is knowing the actual number instead of a feeling, so a fix (a deposit policy, a tighter comp approval process, a faster bussing rotation) can be judged against what it would actually save.