Most voids are training gaps. The 10% that aren't, are the ones that matter.
A 12-minute playbook for independent owners. The categorization, the velocity test, and the server-distribution heatmap that separates the noise from the signal in your void log.
Owners running this routine cut their void rate by half in 60 days.
Read This First
Voids aren't a single problem. They're three problems that look identical in the report. Roughly 60% are training gaps: wrong item rung, modifier missed, ticket misfired. About 30% are process failures: POS workflow, menu engineering, wrong-printer routing. The last 10% is the signal nobody wants to see.
The benchmark moves with concept. Fine dining lives at 0.4%, full service at 0.5%, fast casual at 0.8%, QSR at 1.2%. Without the concept anchor you're reading noise.
This playbook gives you the categorization, the velocity test, and the heatmap.
I take days to figure this stuff out. This is game-changer type stuff. I don't even see my numbers until end of month right now.
Andrew Foster
Owner, Caplingers Fresh Catch
What you will have by the end of this page
01A void variance number specific to your concept and revenue, with a defendable benchmark.
03The Velocity Test that separates a normal Saturday from an investigation-worthy one.
04The Server Distribution Heatmap that surfaces patterns the report can't.
05A Weekly Void Review you can run in 12 minutes every Monday.
Quick Win, 60 Seconds
The Void Variance Calculator
Concept-aware. Five inputs. Three buckets you can route on.
$
%
Your estimated annual loss:
$18,000
Training gap (60%)biggest
Wrong item rung, fixed by retraining and menu placement
$10,800
Process failure (30%)
POS workflow issues, missing menu items, modifier errors
$5,400
Theft signal (10%)
Pattern voids: same server, same item, same time of week
$1,800
Your routing
Most of your void variance reads as a training gap. Start with Chapter 2 (Categorize Every Void) and Chapter 4 (Server Distribution Heatmap). Cheap to fix, fast to verify.
For reference: total void dollars at this volume = $40,500/yr
Server / terminal count is manageable; investigation can be quarterly rather than monthly.
Benchmarks: fine dining 0.4%, full service 0.5%, fast casual 0.8%, QSR 1.2%. The split (60% training / 30% process / 10% theft) is from independent-owner audits.
Bring your questions to a free working session. No system access needed for the call.
Heads up: this playbook gives you the routine. It does not run the routine for you every morning. Marty does. Keep reading if you want the routine. Skip to the bottom if you want it run for you.
The Playbook
Six chapters. Twelve minutes. One system.
Each chapter ends with something you've actually done.
CHAPTER 01
Anchor the benchmark to your concept
A 1% void rate is normal for QSR and a five-alarm fire for fine dining. The benchmark is the line between "expected friction" and "investigate now." Without it, every conversation about voids is opinion.
Within a concept, the benchmark also moves with menu complexity. A fine-dining concept with a tasting menu and frequent off-menu requests will run higher than a concept with a tight printed menu. Adjust the benchmark by 0.1 to 0.2 points if you're an outlier in menu complexity.
Concept benchmarks (% of sales)
Concept
Benchmark
Healthy range
Fine dining
0.4%
0.3% to 0.6%
Full service
0.5%
0.4% to 0.7%
Fast casual
0.8%
0.6% to 1.0%
QSR
1.2%
0.9% to 1.5%
Your turn
Pull your trailing 90 days of voids as % of sales. Compare to your concept benchmark. The gap is the recovery target. Anything inside the healthy range is a "tune." Anything above is a "fix."
Takeaway
The benchmark is the line between expected friction and investigation.
CHAPTER 02
Categorize every void into four buckets
Training gap, process failure, theft signal, legitimate void (re-fire of a kitchen mistake, swap of a 86'd item). Every void belongs in exactly one bucket. The ratio of buckets in your data is your diagnosis.
Most owners run 60% training / 30% process / 5-10% legitimate / 1-3% theft. If your mix doesn't look like that, the deviation is the story. Heavy on legitimate? Your menu availability or kitchen workflow is breaking. Heavy on process? Your POS is fighting your team.
The 4-category void taxonomy
Category
Looks like
Fix lives in
Training gap
Wrong item rung, modifier missed
Re-training, POS layout
Process failure
Item 86'd, wrong-printer fire
Workflow / menu engineering
Legitimate
Kitchen recook, customer swap
Document, monitor velocity
Theft signal
Pattern voids, post-payment voids
Manager Override Audit
Your turn
Pull last 30 days of voids. Tag each into a bucket. If your training:process:legitimate ratio doesn't roughly match the benchmark, that's the diagnosis.
Takeaway
The mix of categories is your diagnosis. Ignore total. Read the ratio.
CHAPTER 03
The Velocity Test
A void rate of 0.7% on a 240-cover Saturday is different from 0.7% on a 60-cover Tuesday. The Saturday is normal noise. The Tuesday is a signal. The velocity test is the ratio of voids per cover, not voids per dollar, which controls for ticket size and party complexity.
Compute voids-per-cover by daypart. Anything more than 2 standard deviations above your trailing 8-week average is investigation-worthy. Anything below 1 SD is normal.
Velocity test, filled example
Shift
Covers
Voids
V/C
Read
Sat dinner
238
11
0.046
Normal
Tue dinner
62
7
0.113
Investigate
Sun brunch
144
5
0.035
Normal
Your turn
Compute V/C for the last 8 weeks by daypart. Set a threshold at 2 SD above the rolling mean. Any single shift past the threshold is on this week's investigation list.
Takeaway
Voids per cover is the test. Voids per dollar lies because ticket sizes vary.
CHAPTER 04
The Server Distribution Heatmap
Pull voids by server for 60 days. Plot them. Most servers cluster around the same voids-per-cover. Two or three servers will sit visibly above the cluster. Those are your investigation candidates, not because they're stealing, but because something specific about their workflow or training is producing more voids.
The heatmap is also a coaching tool. Most "outlier" servers get pulled into the cluster with a single 30-minute coaching session on POS layout and modifier flow. The remaining outliers after coaching are the signal that warrants the deeper audit.
Server distribution example, 60 days
Server
Covers
Voids
V/C
Action
Tara M.
1,820
62
0.034
Cluster
Malik R.
1,640
58
0.035
Cluster
Sasha K.
1,210
94
0.078
Coach (POS layout)
Jamal F.
1,540
128
0.083
Coach + audit
Your turn
Build the heatmap for last 60 days. Identify the top 2-3 outliers. Coach the first outlier this week, the second next week. Re-pull in 30 days to see if coaching closed the gap.
Takeaway
Outliers above the cluster are coaching candidates first, audit candidates second.
CHAPTER 05
The Manager Override Audit
When a void requires a manager swipe, the override log is the data. Pull it monthly. Sort by manager. Inside each manager, sort by server. The same pair appearing repeatedly is the pattern.
Specifically watch for post-payment voids, meaning a check closed, paid, then voided. That's almost always either a process failure (kitchen miscook discovered after pickup) or the theft signal. Either way, it warrants a conversation.
Override audit, monthly
Pull last month's override log.
Group by manager. Identify any manager with override volume > 25% of total.
Within that manager, group by server. Flag any pair > 30% of that manager's volume.
Filter for post-payment voids. Pull them all. Read the timestamps.
Categorize each into training / process / theft. Have the conversation.
Your turn
Run steps 1-4 this week. Most owners find one pair worth investigating and one or two post-payment voids that surface a process gap.
Takeaway
Post-payment voids are the rarest data point and the loudest signal.
CHAPTER 06
The Weekly Void Review
Twelve minutes every Monday. Pull last week's voids. Three views: void % vs. concept benchmark, V/C by daypart, top three servers by V/C. Anything off-trend gets a one-line investigation note. That's it.
The point of the cadence is normalization. After 8 weeks of running this, you know what normal looks like in your restaurant. After that, the abnormal week jumps off the page without effort.
Weekly void review template
View
This wk
8-wk avg
Note
Void %
0.62%
0.55%
Within tolerance
Tue dinner V/C
0.113
0.048
Investigate
Top server (Jamal F.)
0.091
0.083
Continue coaching
Your turn
Run last week's review tomorrow. Flag any line that drifted 30%+ from the trailing 8-week average. That's the work item for the week.
Takeaway
Run the review for 8 weeks. After that, the abnormal jumps off the page.
Print this cheat sheet
The Cheat Sheet
One page. Print it. Pin it.
Everything in this playbook, condensed.
Concept Benchmarks
Fine 0.4% / Full 0.5% / Fast casual 0.8% / QSR 1.2%. Adjust ±0.2 for menu complexity.
4-Category Taxonomy
Training (60%) / Process (30%) / Legitimate (5-10%) / Theft signal (1-3%). The mix is your diagnosis.
Velocity Test
Voids per cover, not per dollar. Daypart-level. 2 SD above 8-week mean = investigate.
Server Heatmap
60-day V/C by server. Outliers above the cluster = coach first (POS layout), audit second.
Override Audit
Monthly. Manager → server pairs over 30% of volume = pattern. Post-payment voids = loudest signal.
Weekly Review
12 min Mondays. Void % / V/C by daypart / top servers. 30% drift = work item.
What this playbook can't do
You now have the system. Marty runs it for you.
A playbook can't:
Tag every void into the 4-category taxonomy automatically
Compute V/C by daypart and surface 2-SD outliers in real time
Refresh the server-distribution heatmap every week
Flag post-payment voids the moment they happen
Marty does all of it.
Marty is the analyst sitting next to your GM. We plug into your POS, run this routine every morning before you open, alert the moment a number breaks, and review the rest of your operation in the background. It starts with a 2–3 store Cash Recovery Plan pilot. If the Cash Recovery Plan doesn't surface anything worth fixing, we refund the plan fees in full. You keep the work.