Variance Is a Question, Not an Accusation

After 20 years operating 10 QSR locations, I learned that treating variance like blame is the fastest way to destroy inventory accuracy. When variance becomes an accusation, managers learn to hide bad numbers. The fix is to treat variance as a question, not a verdict. Three questions before assuming anything: Was it received correctly? Was it prepped or portioned correctly? Was it counted correctly?

Why Variance Culture Kills Accuracy

I've seen this happen repeatedly. A location shows a $300 variance on a high-value item. The operator calls the manager. The manager feels accused. Next week, the manager adjusts their count to make the variance look smaller. Not by counting better, but by counting to match. The variance disappears from the report, but the actual problem, whether it's waste, theft, or a receiving error, continues.

This is how bad variance culture creates worse data than no variance tracking at all. When managers count to make the numbers look good instead of counting to make the numbers accurate, your inventory data becomes fiction. And you make ordering decisions based on fiction.

I fixed this in my own stores by changing how I talked about variance. I stopped asking "why is your variance so high?" and started asking "what do you think happened here?" The first question puts the manager on defense. The second invites them to investigate with you.

The Three Questions That Replace Blame

When a variance shows up, I don't assume the manager miscounted or someone stole product. I ask three questions in this order:

Question	What It Investigates	Common Finding
Was it received correctly?	Did the delivery actually contain what the invoice says? Shorted deliveries are a top cause of false variance.	Supplier shorted 2 cases but invoice showed full delivery. Manager signed without counting the delivery.
Was it prepped or portioned correctly?	Did the kitchen use the right recipe amounts? Over-portioning is invisible waste that looks like inventory loss.	Line cook using 2 oz of sauce instead of the 1.5 oz spec. Adds up across 500 servings.
Was it counted correctly?	Was the count accurate? This comes last because counting errors are usually the smallest source of variance, not the largest.	Manager estimated an open case instead of counting individual units. Off by 8-10 units.

Notice that counting errors are last. In my experience, they're the least common cause of real variance. Receiving errors and portioning errors are far more frequent. But most operators assume counting is the problem because that's the only variable they can control directly.

What Variance Actually Tells You

Variance is a signal, not a conclusion. Here's what different variance patterns mean:

• One-time spike on a single item: Likely a receiving error, a prep mistake, or a one-off waste event. Investigate that item.
• Gradual drift on one item over several weeks: Likely a portioning issue or a slow leak. The trend matters more than any single week.
• Variance across multiple items in the same category: Likely a counting methodology issue or a supplier problem affecting that category.
• Consistent small variance everywhere: This is normal. A 1-2% variance across all items is just the noise of running a kitchen. Don't chase it.
• Variance that matches seasonal patterns: Expected. Higher volume weeks create more variance in absolute dollars even if the percentage stays the same.

How to Build a Healthy Variance Culture

1. Treat variance as investigation, not interrogation. Never call a manager about variance without also calling to praise good counts. If the only time you discuss counts is when they're bad, managers learn to dread variance reports.
2. Review variance weekly, not monthly. A weekly review catches problems while they're small. A monthly review lets problems compound for 4 weeks before anyone notices.
3. Share variance data with the manager, not just the operator. If the manager doesn't see the variance report, they can't fix the problem. Transparency builds trust.
4. Celebrate good investigation, not just good numbers. If a manager finds a supplier shorting deliveries, that's a win even though it created variance. Reward the discovery, not just the absence of problems.
5. Accept a realistic variance threshold. I aim for under 3% on high-value items and under 5% overall. Zero variance is not a goal. Zero variance usually means someone is adjusting counts to match.

Why I Built This Into the App

TrackItWeekly shows variance per item, not just a total. You can see which items contributed to the variance instead of just seeing a dollar amount. The app also categorizes variance so you can tag it: waste, theft, receiving error, counting error. Over time, the pattern of tags tells you where your real problems are.

The app's stock dot system also makes variance visible before it becomes a number. If an item shows red (below par) consistently before the next delivery, that's a signal. If it shows green (above par) consistently after ordering, the par is too high. The dots are an early warning system that runs continuously, not just at count time.

I didn't build a variance tracker. I built a system that makes variance a conversation instead of a confrontation.

Common Questions About Inventory Variance

What is an acceptable inventory variance?

Aim for under 3% on high-value items and under 5% overall. Zero variance is not realistic and often indicates manipulated counts. The goal isn't eliminating variance, it's understanding what each variance means.

How often should I review inventory variance?

Weekly. A weekly review catches problems while they're small and lets you investigate before the evidence goes cold. Monthly variance reviews are too late to identify receiving errors or portioning issues.

What causes the most inventory variance in restaurants?

In my experience, receiving errors (shorted deliveries, wrong pack sizes) and portioning errors (over-portioning, recipe drift) cause more variance than theft or counting errors. Counting errors are usually the smallest source but the most commonly blamed.

Should I confront my manager about high variance?

Not confront. Investigate with them. Ask what they think happened. Review the delivery logs, the prep sheets, and the count together. If you treat variance as a shared problem to solve, managers will help you find the cause. If you treat it as their fault, they'll hide it.