The Lie of the Empty Cell: Where Cricket's Data Chain Breaks Silently

Last month a risk sheet was placed in front of me. The columns were all there — format, venue, workload, injury history, rotation policy. Under every heading was space, and under every space, nothing. The person who sent it had one line: "There's nothing here." Four days later the same sheet travelled onward, and at the next desk its title had changed to "No risk found."

I have logged 340 matches. They were logged during that empty stretch of 2026, when the Fatorda final was played to no crowd and my freelance income fell from ₹38,000 to ₹14,000. An old habit took hold then and has stayed: write beside every blank space why it is blank — "no footage available", "over-wise profile broken", "camera did not follow". Of those 340, 61 matches have no ball-by-ball record in my file at all. I did not delete them. That is my most expensive data, because it shows where observation stopped.

Cricket's information arrives through two streams: what the camera sees, and what nobody watches at all. The first stream runs on money. In July 2026, in Durban, the ICC Board approved a revenue model that fixed India's share at roughly 38.5% of an annual pool of about $600 million. The largest money in the system returns to the market with the most cameras. Where cameras stand, there is a ball-by-ball data partner, a pitch map, a field-placement log, a release point. Where no camera stands — the November Ranji group stage, women's domestic one-dayers, Under-19 afternoon innings — there is a scorecard and then silence.

For me this is not a technical fault but architecture. The data skeleton bends the way advertising bends, and the scouting decision sits inside that skeleton.

Missing cricket data is not random. It is missing precisely where the camera does not go, and the camera does not go where advertising does not sell. That is a directional bias, not noise. Directional bias is the more dangerous kind, because it vanishes into an average while leaning the same way every time.

The effect lands directly on the development pipeline. Franchise scouting has replaced zonal selectors, but a scout reads the same scorecard everyone else reads, because for November Ranji matches nothing more exists. A player whose pitch map nobody has recorded is selected in the same darkness in which his performance was recorded. India's hardest team to pick is its second XI — and that is a problem of non-recording, not of talent.

A second issue gets caught here, more linguistic than technical. A spreadsheet renders two entirely different things identically: "the event did not occur" and "no observation was made". Both come out blank. In risk language the first can be scored zero; the second never can, because it means we did not look, so we do not know. What the sender wrote was not a statement about data — it was a statement about the absence of observation. Downstream, that sentence became a risk certificate.

The Spain–Russia night at the 2026 World Cup still returns to me for this reason. I counted the passes myself in a hostel room — Spain 1,029, Russia 202, nearly 80% of the ball, and the match went to penalties. My piece argued that this was passing volume, not penetration: the ball circled the box and never went through it. Data reporting now shows the same shape — reports orbit the hole and never cross it. I do not chase narratives; I count the overs that make narratives possible — and in overs 12 to 25 of bilateral one-day cricket, that count is still outstanding.

The reflex demand is for more data. That demand points the wrong way. The problem is not quantity but provenance: recording where a number came from, and why there is no number where there isn't one. A wrong number gets caught, because someone who watched the match remembers what actually happened. A blank number is never caught, because nothing exists to challenge it.

There is also an incentive layered into this. When an institution prints a clean number it creates a liability — anyone can later pick that number up and use it against them. Ambiguity or an empty cell creates no such liability. Ambiguity is therefore sometimes not a mistake; it is the safe option. I should declare my own conflict: I hold no BCCI accreditation and work from broadcast footage and public scorecards. My 340-match log inherits every blind corner of the broadcast. It is not neutral; it is only honest about where it came from.

Making the commentary box a punchline is the easiest work available, and a trap I keep sidestepping. It is a design problem: that room rewards noise, not silence. Something must be said within thirty seconds, and "I don't have this over's data" costs more courage than effort. Where the incentive rewards noise, you will not find analysis, however many screens are mounted on the desk.

The next time a report says no risk was found, the question is not "what was the risk". The question is: "was anything observed there?" My suggestion is a public test — take the next bilateral one-day series and count how many overs have a published pitch map and how many do not. If the hole sits between overs 12 and 25 again, it is not coincidence, it is design. And a design with a hole cannot be audited without the hole in the ledger.