The Empty Cell: Zone Occupation and the Credibility of Cricket Data

Last night, sitting at home in Melbourne, I was digging through the freeze-frames of an old IPL match. The screen carried ball-tracking, a wagon wheel, a field map, an expected-runs curve. But when I pulled the zone-occupation data for one particular over, the dashboard handed back a row of empty cells — N/A, N/A, N/A. The most frightening number in cricket is never a low strike rate. It is an empty cell, which looks harmlessly like a zero but is actually shouting, "I don't know." And if we mistake that "I don't know" for "neutral," the entire reading of the match flips over.

I came to cricket from football, and my first lesson was this — a field is really a grid, and every over is an account of who holds how much of that grid. Since the Indian Premier League (IPL) began in 2026, the Board of Control for Cricket in India (BCCI) and the ICC have both turned post-match analysis into a separate industry. Hawk-Eye, ball-tracking, edge detection, expected-runs models — these are no longer luxuries but the daily language of coaching staffs. In 2026 the IPL's media rights were sold for roughly 48,390 crore rupees (about 6.2 billion US dollars at the time) — proof that cricket is now not just a game but a data-driven market.

But here is the question. We split a T20 innings into three phases — the powerplay (overs 1–6, with fielding restrictions), the middle (7–15), and the death (16–20, where scoring rates peak). In ODIs the powerplay is 1–10 and the death is 41–50. That phasing is not merely convenience; each phase is a different game with a different risk calculus. In the powerplay you can play the true shot; at the death every ball is a gamble, where arithmetic matters more than raw skill.

Now to the real subject — zone occupation. I read a cricket field as a set of geographic regions: the half-space behind point, the corridor outside off, the arc between deep midwicket and long-on. The half-space is not a place; it is a question — will the bowler dare to bowl into it, or force the batter to do so? Just as an inverted winger in football occupies that half-space and breaks the midfield, in cricket a sweep-prone batter or a fielder guarding the cover region runs the same politics of geometry.

This is where data enters. But numbers are proof, never a premise. If I do not first ask — "who is holding which region in this match?" — then a wall of averages and strike rates tells me nothing. From years of watching matches, my experience says analysts make their biggest mistake exactly here: they collect the numbers first, then hunt for a question to fit them.

Think of Russia 2026, where I wrote a phase-based notebook every day, watching France shift from a 4-2-3-1 to a 4-4-2 without the ball. I carried that method into cricket: build-up, progression, creation, rest-defence. The session-by-session split of a Test match and the over-by-over split of a T20 innings are pages of the same notebook. A launch is just a hypothesis that survived the first ten minutes of contact. In cricket, those "ten minutes" are the first six overs.

Yet the problem is that our modern data systems cannot recognise these empty cells. An empty cell and a zero are vastly different things. A zero means "nothing happened" — a batter out for nought, a bowler with no wickets. An empty cell means "we did not record it." A piece of information, a silence. And our dashboards, our models, our expected-runs algorithms — all of them erase the difference between the two.

Here I want to bring in the idea of blockchain — not literally, but as an analogy. Blockchain's core strength is not decentralisation alone; its real strength is immutability — once a transaction is written, it cannot be quietly deleted. Cricket's data architecture lacks exactly this quality. A scorecard logs a ball as a "dot," but whether that ball was outside off or hit the pad — that fine detail is lost. We preserve outcomes, not processes. Yet the process is the match itself.

Think of the 2026 World Cup final — England against New Zealand, the Super Over tied, England eventually champions on boundary count. That night the loudest argument was about a rule, not a number. Some said the rule was unfair. But the real question was different: at the moment the match tied, what information did we actually hold? Boundary count is a number, but the true story of the match was New Zealand's bowling discipline and England's final-over arithmetic — where was that recorded?

Now to the biggest trap of all. The conventional view says: data makes cricket objective. That is a half-truth. Data does not make cricket objective; data makes cricket objective only when its pipeline is honest. And a pipeline is not honest unless we ask — where did the information come from, who collected it, and which information was lost?

My greatest caution in cricket analysis is not the quality of the information but its absence. I do not trust formations; I trust the triggers that let a formation breathe. In cricket those triggers are the press ball, a change of line and length, a fielder suddenly moving in the ring. Those triggers do not appear on a scorecard. They do not appear in an expected-runs table. They exist only in the stream, where we are actually watching the match.

There is a reaction here, and I know this ENTP wiring is dangerous. Chasing the novel angle, we sometimes neglect a proven truth. The honest line is this: the data revolution is real, and it is good. Bowling plans, field placements, death-over match-ups — all of it is now far more planned, far less emotion-driven. So I am not against this revolution. I am only warning: by treating an empty cell as "neutral," we may drift into wrong decisions without noticing.

And here a deeper truth about cricket hides. We are used to measuring outcomes, not processes. When a team wins, we assume its strategy was right. But sometimes a team wins with a wrong strategy — because the opponent made even more mistakes. Data cannot catch that fine distinction unless we ask the question first. A number is only valuable when we know which question it answers.

My conclusion is not that data should be discarded. Quite the opposite. My conclusion is that cricket's data system should work like a blockchain — every piece of information chained, who gave it, when they gave it, and which data went missing, all recorded. The empty cells cannot be hidden; they must be flagged. Because the system that cannot recognise its own ignorance is the most dangerous system of all.

Next time you watch a match, do not look only at the scorecard. Watch — who is holding which region. Listen — what the coach is saying on the stump mic, how the crowd is falling silent. Then ask what information you do not have. Because a map is honest only when it admits it too has blank spaces.