Empty Feed, Green Tick: Why Cricket Newsrooms Keep Mistaking 'No Data' for 'No Risk'

6:10 a.m., Mumbai. A green tick glowed on the laptop screen — Processed. Below it were twelve rows, and every row said the same thing: N/A. Title N/A. Source N/A. Facts N/A. The system called it completeness, not failure. The monitor glowed small, but the silence filled the stadium.

I have watched matches for twelve years and sat behind a microphone for several of them. What unsettled me that morning was not the absence of information — it was that the absence presented itself as an all-clear. The most dangerous scoreboard in cricket is not the one that shows a wrong number. It is the one that forgets to mention it saw nothing at all.

Modern cricket coverage runs on four pipes. First, the ball-by-ball scoring feed. Second, Hawk-Eye ball-tracking, on which DRS's "umpire's call" depends. Third, the broadcast graphics engine. Fourth — and the least visible — the pre-match data desk assembling pitch reports, head-to-heads and retention lists. When any of them returns empty, a newsroom has only two readings available: the pipe is broken, or nothing happened. Telling those apart is a cricket reporter's first duty.

On 19 December 2026 at Adelaide Oval, India were bowled out for 36 in 21.2 overs — Hazlewood 5/8, Cummins 4/21. I ran live text from home that night. The feed never went quiet; every falling wicket pushed a fresh number. That coverage's problem was emotional, not informational. The dangerous case is the inverse — when the numbers stop arriving and nobody declares the outage.

I have seen this up close at Ranji knockout matches. Two hundred people, one camera, one operator updating the score on a laptop. If that feed drops for an hour, the scoresheet gets filled from memory. This is where a blank first becomes a wrong number — and nobody corrects it, because the space for a correction never appears.

The problem is not technical but taxonomic. Every cricket metric is bound to a format. A T20 strike rate of 150 and a Test strike rate of 50 measure different competencies; placing them on one scale is not carelessness but dishonesty. When the input does not record a format, every "benchmark comparison" becomes fiction.

The moment format is undefined, every statistic stops being evidence and becomes decoration. And decoration's signature is that it disproves no sentence. My desk has one rule: with every statistic, write the sentence it is meant to break. If the sentence cannot be written, cut the number. That morning, not one of the twelve rows produced a sentence.

In October 2026, Prithvi Shaw scored 134 on Test debut at Rajkot aged 18 years 329 days — the youngest Indian to a debut Test hundred. I barely watched the innings. I was at the Dadar maidan where he learned to bat, talking to coaches who had bowled at him at fourteen. That day I had less data and more information. The difference is simple — data is what the feed sends, information is what you go and fetch.

Now the reversal. The industry's common belief is that Indian cricket coverage improved over the past decade because data grew richer — ball-by-ball granularity, DRS transparency, WPL broadcast budgets, public retention lists. The strongest version of that claim holds: the floor of the craft has risen, and a 2026 report is not the same profession as a 2026 one.

What overturns it is not the volume of data but the honesty of absence. That morning's failure was in labelling, not extraction. In a system where every field reads N/A and still calls itself Processed, the pipe did not break — the pipe lied. A system that cannot say "I failed" will always be read as "nothing happened."

The press box sits inside precisely this trap. It repeats what the feed says — and when the feed goes quiet, the press box prints "no news." Injury reports, auction outcomes, board rulings, corruption charges: all time-sensitive. A null payload that hides them costs more than a wrong number, because a wrong number gets corrected. A blank does not.

The question ahead belongs to those who will sit down for the next broadcast and data contracts. Every deal will promise granularity — every ball, every angle, every millisecond. Ask one question in any such meeting: when your feed dies, what does your dashboard show? If the answer is a green tick, then the number you are paying for is not a statistic — it is a rumour with a decimal point.