The Zero That Meant Something Else
A zero on a report can mean nothing happened, or it can mean nobody recorded anything. Those are opposite situations and most systems show them identically. Here is how to tell them apart before you act on the wrong one.
The report says zero.
Zero bookings from that listing. Zero returns from that promotion. Zero complaints last month.
⚠️ Every one of those has two possible meanings, and the report will not tell you which. Either the thing genuinely did not happen, or nobody wrote it down, or the thing that counts it was not running.
The short version
- A zero means "nothing happened" or "nothing was recorded" — the display is identical
- Acting on the wrong one is how a working channel gets cut
- The test is whether anything else in the same place is non-zero
- A number that has been zero for a long time deserves suspicion, not acceptance
- The dangerous zero is the one that used to be a number
Three kinds of zero
| What you see | What it could be |
|---|---|
| 0 | It genuinely did not happen |
| 0 | It happened and nobody recorded it |
| 0 | The counter stopped working |
⚠️ Only the first is information. The other two are silence wearing a number.
One: the one that costs money
The expensive version is a channel that appears to produce nothing.
A listing shows zero bookings
⇒ decision: stop paying for the listing
⇒ reality: bookings came in by phone and nobody asked how they heard
⚠️ The listing was working. The attribution was not. Cancelling it removes the bookings along with the cost, and the drop appears a month later with no obvious cause.
How to check before cutting
Ask three guests this week where they found you.
If any of them say the listing, the zero is a recording problem.
⇒ Three conversations, no system required. Never cancel a channel on a zero you have not tested by asking a human.
⇒ Related: what a listing is worth to one room.
Two: the zero that used to be a number
This is the highest-value pattern to watch for.
March 14
April 11
May 9
June 0
July 0
⚠️ A gradual decline to zero is a trend. A sudden drop to exactly zero is a mechanism. Something stopped — a form, an integration, a person who used to type them in.
The date is the clue
Find the exact day it became zero.
Ask what changed that day.
⇒ Usually somebody knows: a website change, a staff departure, a new phone system. The date does most of the investigating for you.
⇒ On the specific case of a check that quietly stopped running: the check that quietly stopped.
Three: the code version of the same mistake
There is a version of this that lives inside software, and it is worth knowing because it explains a whole class of wrong reports.
Some systems treat "no value" and "zero" as different things
Others treat them as the same
⇒ a total that skips the first kind quietly undercounts
⚠️ We hit exactly this while building a billing summary. Our unpaid total came out as zero yen across every account. The amounts were there; the field we read held a genuine zero for unpaid items rather than nothing at all, so the fallback we had written never fired. A real thirty thousand showed as nothing.
⇒ The lesson for a non-technical reader is narrow and useful: when a total reads exactly zero, ask whether the figure is being read from the right column before concluding the money is not there.
Four: zeros that should alarm you
Some zeros are normal. These are not.
Zero complaints - somebody is absorbing them
Zero cancellations - they are not being recorded
Zero returns from a new channel - attribution, not performance
Zero overtime - it is happening off the record
Zero breakages - genuinely unlikely
⚠️ Zero complaints is the one to take most seriously. Complaints exist in every venue. A zero means they are being handled and not logged, which is fine right up until the person handling them leaves.
What to do with an alarming zero
One Do not celebrate it.
Two Ask one person who would know.
Three If they say "oh, loads", you have found a recording gap.
Five: the difference between zero and blank
A blank and a zero look similar on a page and mean different things.
0 we looked, and the answer was none
blank we did not look, or nothing was entered
⚠️ Most spreadsheets and reports blur these, and once blurred they cannot be separated again.
The habit that preserves the difference
Write 0 when you checked.
Leave blank when you did not.
Never fill blanks with 0 to make a sheet look complete.
⇒ Tidying a sheet by replacing blanks with zeros destroys the only record of what was actually checked. A tidy sheet is worth less than an honest one.
Six: the total that hides a zero
The reverse case: a healthy-looking total that contains a broken component.
Total bookings this month: 312
⇒ of which, from the website: 0
⚠️ The total looked fine, so nobody looked inside it. The website form had been broken for three weeks and the shortfall was masked by a good month elsewhere.
The check
Once a month: read the breakdown, not just the total.
Any component that is exactly zero gets one question.
⇒ It takes two minutes and it is the only way a component failure surfaces before the total finally drops.
Seven: asking for the denominator
A zero without a denominator is unreadable.
"Zero conversions" - out of how many?
Zero from 4 visits - meaningless
Zero from 900 visits - a real problem
⚠️ Always ask what the zero is out of. Small denominators produce zeros constantly and they carry no information at all.
The rough rule
Under about 30 attempts - a zero tells you nothing
Over a few hundred - a zero is a finding
⇒ That is a rule of thumb for reading reports, not a statistical claim. The useful habit is refusing to act on a zero until you know its denominator.
⇒ On measuring a funnel one step at a time rather than in totals: the guest who stopped halfway.
Numbers worth keeping
One Which of your reported figures are currently zero
Two For each: when did it last have a value?
Three For each: what is the denominator?
Four Which of them would you act on if you trusted them?
⚠️ Four is the filter. A zero you would never act on does not need investigating. A zero that would make you cancel something needs checking first.
The card for the office
────────────────────────
When a report says zero
1. Did it used to be a number? When did it change?
2. Is anything else in the same place non-zero?
3. Zero out of how many?
4. Ask one human who would know.
Never cancel anything on an untested zero.
────────────────────────
Common objections
"Zero is zero"
⚠️ Zero recorded is zero recorded. Whether zero happened is a separate question and the report cannot answer it.
"The system would flag it"
⇒ Systems flag errors, not absences. Nothing failing is exactly what a broken counter looks like from the inside.
"We'd notice if a channel stopped"
⚠️ You notice when the total drops. If another channel is up that month, the total does not drop and the zero sits there quietly.
"It's been zero for months, so it clearly doesn't work"
⇒ Or it clearly has not been recorded for months. Duration makes a zero more suspicious, not more reliable.
"We don't have time to check every zero"
⇒ Check the ones you would act on. That is usually two or three, not twenty.
What to do this week
One List every figure on your reports that currently reads zero.
Two For each, find the last date it was not zero.
Three Ask three guests this week where they found you.
Four Read one monthly total's breakdown, not just the total.
Five Stop filling blank cells with zeros.
Summary
- A zero means nothing happened or nothing was recorded
- The expensive mistake is cancelling a channel on a recording gap
- A sudden drop to exactly zero is a mechanism, not a trend
- Zero complaints is the most suspicious zero in any venue
- Blank and zero mean different things — keep them different
- A zero without a denominator cannot be read at all
Nothing is the hardest thing to measure, because a system that has stopped counting and a world in which nothing happened produce exactly the same report.
Related articles
Who Did It Is Not What They Did
Your records show who made a change and when. They almost never show what the change actually was, or what it replaced. Here is the difference between a log and an audit trail, and the three lines that turn one into the other.
Two Clocks In One System
A scheduled message goes out a day late. A shift lands on the wrong date. A report counts yesterday as today. Usually there is nothing wrong with the schedule — the system is running on two different clocks and only one of them is yours.
The Second Record Nobody Meant To Create
The same guest exists twice. The same booking is in the system twice. Duplicates are not a data problem — they are a symptom of two people acting on the same thing without seeing each other. Here is how they form and what actually stops them.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days