"About Half a Case" Is Not a Count: Why Guesses Look Like Data on Paper

After 20 years running 10 QSR locations, I learned that the most dangerous inventory number is the one that looks precise but is actually a guess. "About half a case" written on a count sheet looks identical to a real count once it enters your spreadsheet. Confident guesses are indistinguishable from actual counts, and they quietly corrupt every decision you make from that data.

How a Guess Becomes a Number

Here's how it happens. A manager is counting the walk-in. They get to the sauce shelf. There's a case that's been opened. Some bottles used, some left. They look at it, think "that's about half," and write "12" on the count sheet because half a case of 24 is 12.

That number goes into the spreadsheet. It becomes part of the food cost calculation. It flows into the variance report. It affects the next order. And every person who looks at that spreadsheet sees a clean number with no indication that it was a guess.

I caught this in my own stores when I started doing independent recounts. I'd send a second manager to count the same walk-in on the same day. The items with exact counts matched perfectly. The items with estimated counts were off by 20-30%. Not because anyone was stealing. Because "about half" is not 12. Sometimes it's 8. Sometimes it's 15. The guesser doesn't know, and neither does the spreadsheet.

What a Guess Looks Like on Paper

The problem with estimated counts is that they're invisible once they're written down. Here's what I've seen on real count sheets across my stores:

What Was Written	What Actually Happened	Real Count	Variance Created
12 (half case)	Manager glanced at open case, estimated half	8	50% overcounted
6 (looks low)	Manager saw few items on shelf, guessed low	9	33% undercounted
24 (full case)	Manager assumed unopened case was full	19	26% overcounted
15 (about 2/3)	Manager estimated two-thirds of a case	11	36% overcounted

Every one of those numbers looked like a real count on the spreadsheet. Every one was a guess. And every one corrupted the food cost percentage for that week.

Why Smart Managers Guess

Managers don't guess because they're lazy. They guess because counting individual items takes time, and they're usually counting at the end of a long shift. I've been that manager. When you've been on your feet for 10 hours and you're looking at 400 items, the temptation to estimate the obvious-looking ones is strong.

Here's the thing: a guess on a clipboard and a guess in an app are equally bad. The app doesn't magically make the number accurate if the person entering it is estimating. What the app does is make guessing slower than counting, which reverses the incentive.

On a clipboard, estimating is faster than counting. Write "12" and move on. On the app, you still have to type a number, but the app shows you the last 4 weeks of counts for that item. If you write 12 and last week was 22, the app flags it. The clipboard doesn't.

The Two-Person Test: How to Find Your Hidden Guesses

If you want to know how many of your counts are actually guesses, do what I did: send two people to count the same inventory independently on the same day. Don't tell them they're being checked. Just compare the sheets afterward.

Items with exact counts will match within 1-2 units. Items with estimated counts will be off by 5-15 units. The gap between the two sheets is your real count accuracy rate, not the clean-looking spreadsheet you've been trusting.

I ran this test at 3 of my locations. Results:

• Location A: 22% of items had count differences greater than 10% between two independent counters
• Location B: 31% of items showed significant variance
• Location C: 15% (this location had a dedicated counter who counted individual items)

Location C's counter was the most accurate because he counted every item individually. No estimates. No shortcuts. It took him 5 minutes longer per count, but his variance reports were actually trustworthy.

How to Stop Guesses From Entering Your Data

1. Count individual units, not fractions of cases. If a case has 24 bottles and you see an open one, count the bottles. All of them. Every time.
2. Don't count by weight unless you have a scale. "Feels like 5 pounds" is a guess. 5.2 on a scale is a count.
3. Use the last 4 weeks as a sanity check. If a count is dramatically different from recent history, either something real happened (delivery error, waste event) or the count is wrong. Investigate before accepting it.
4. Train managers to flag estimates, not hide them. If a manager writes "est. 12" instead of "12," you can review those items separately. A culture that punishes honesty about estimates creates invisible data corruption.
5. Audit 10 random items per week. Pick 10 items from the count sheet and recount them yourself. If more than 2 are off by more than 10%, the whole count is suspect.

Why I Built This Into the App

TrackItWeekly shows the last 4 weeks of counts next to the current entry field. If a manager enters a number that's dramatically different from recent history, the row turns red. Not as a punishment, but as a prompt: "Are you sure?" The manager can confirm it's correct (maybe there was a waste event) or correct the count.

I also built barcode scanning because scanning forces an exact count. You can't estimate a barcode scan. You either scanned the item or you didn't. The scanning itself becomes the accuracy mechanism.

The app didn't fix the guessing. It made guessing visible.

Common Questions About Count Accuracy

How accurate should my inventory counts be?

Your counts should be within 2-5% of actual. Below 2% is excellent. Above 5% means your variance reports are unreliable and you're likely ordering based on bad data. The target isn't perfection, it's consistency within a tight enough range that trend analysis works.

What items are most commonly estimated?

Items that come in cases with many individual units: sauce bottles, packets, small supplies. Items that are hard to count visually: items in deep freezers, items stacked in the back of walk-ins. And items where the manager thinks they know the number from memory without actually looking.

Should I fire a manager who estimates counts?

No. The problem is usually systemic, not personal. If estimates are common, the manager is likely overworked, counting at the wrong time, or counting too many items. Fix the system first: better count timing, fewer items, barcode scanning for high-volume products. If estimates continue after system fixes, then address the individual.

How do barcode scanners prevent guessing?

A barcode scan forces an exact count. You can't estimate a scan. You either scanned the item or you didn't. For high-volume items like cases and multi-packs, scanning each unit eliminates the "about half a case" problem entirely.