An Empty Cell Is Not a Clean Bill of Health — The Silent Failure of Cricket Analytics

It was nearly two in the morning in the Camden flat. On the laptop, a spreadsheet with eight rows, five columns, and the same entry in almost every cell: N/A. The producer leaned over and asked, "So there's no risk, right?" I could not answer. Not one of those empty cells meant "nothing there." They meant "we did not look." In cricket right now, that is the largest risk we have. In data tables, ranking charts, fitness bulletins, I keep watching the same error repeat. We read the absence of information as information. An empty cell feels like safety, and once that reflex settles into your head it never leaves.

A blank in a school maths book is not a zero. It is a question. But put rows of blanks on a screen and the mind quietly rounds them down to zero. That was the first arrow I drew, and it was wrong.

Cricket carries a problem football does not. Goals, assists, expected goals all mean the same thing across formats. Cricket numbers do not. A batting average of 45 is outstanding in T20, solid in ODI, respectable in Test. An economy rate of 8 is acceptable in ODI and expensive in T20. Without a format tag, no cricket statistic is analytically valid, however tidy the number looks. In nine years of watching matches, the most useful lesson I have learned is to ask two questions before anything else: which format, and how big is the sample?

That takes me back to 17 October 2026, Al Amerat in Oman, where Scotland beat Bangladesh by six runs in the first round of the T20 World Cup. That match still reads to me as a silent text. The preview sheets circulating beforehand had Bangladesh's experience, Asia's pedigree, the size of the senior core. What they did not have was powerplay scoring rate, dot-ball ratio, or middle-over strike rotation — or they had those numbers contaminated by the wrong format. The six-run defeat was not a surprise to the numbers. It was a surprise only to the story.

In that Camden bedroom, every formation was a door I hadn't opened yet. At sixteen I started the Half-Space Diary with Chelsea's 3-4-3, because drawing the pitch made football legible. After the 3-1 win over Arsenal on 4 February 2026, fourteen screenshots showed how Marcos Alonso and Victor Moses pinned Arsenal's full-backs. A talkSPORT pundit called me a schoolgirl with a whiteboard. I answered with a twelve-part breakdown of Chelsea's thirteen-match winning run. The habit survives: draw the pitch before typing a word. That night I learned the harder skill — drawing the pitch when the pitch is missing.

My first wrong arrow was the team sheet. I assumed a team's name told me its strengths and weaknesses. It does not. A name tells you which questions are available. The questions that remain unavailable are where the real analysis lives.

Three layers separate out here. The first is the format gate. Test economy, ODI average and T20 strike rate can be arranged in one table; they cannot be argued with in one table. A true number feeding a false conclusion is the most common error in cricket writing, and an untagged table should be assumed wrong — politely, but completely.

The second is sample size. Four good weeks in a franchise league get presented as international readiness. We rarely ask who the opposition bowlers were, how many of those runs came in the death, how many catches went down. A hot streak and a capacity are different objects, and the distance between them is measured in six extra months of column. Without that column, four matches become a five-year judgement.

The third layer is the heaviest. A name on a squad list is a selection document, not a medical clearance. A fast bowler plays four matches in fourteen days and nobody tracks the workload, because the cell is never filled in — the question is never asked. Schedule congestion is the real driver here; no medical staff on earth can offset two matches a week. We do not write that in the empty cell. We write "fit."

Luzhniki, forty minutes. 11 July 2026, Croatia 2-1 England. At half-time I watched Croatia rotate — Modric dropping left of the pivot, Brozovic shadowing Kane's link with Alli, England's wing-backs pinned. Nine hundred words in forty minutes, my first national byline. Deadline taught me speed of decision. It never taught me to make up a number quickly.

Then 14 August 2026, Estadio da Luz, empty seats, Bayern Munich 8-2 Barcelona. I could hear Manuel Neuer's defensive calls and counted nine Bayern counter-press recoveries in the first fifteen minutes. That became "The Silent Press." An empty stadium lets you hear the press; an empty spreadsheet lets you hear your own assumptions. Crowds bury them. Blank cells shout them.

Now flip it. A risk table that says "low" is a claim. A risk table that says "cannot be assessed" is an admission. Reading the two as one is how we mistake the absence of a signal for the absence of risk. Cricket punishes that slowly: a bowler breaks down, we hunt for a reason, and the workload cell had been blank for three months.

My suspicion is that the industry is auditing the wrong object. We check whether the number is correct. Almost nobody checks whether the number exists at all. When a data pipeline fails, the output is not wrong data. It is missing data, and missing data looks alarmingly clean. No red flag, no alert, just a tidy white box.

So I keep a personal rule that makes people uncomfortable. If more than three cells in a sheet are missing, I do not draw conclusions from that sheet. I throw it out and start again with three questions: which format, what sample, under what conditions. It slows the writing down. It sometimes reads as less confident. Analysis that does not know its own limits is the most confident and the most damaging.

One concrete anchor. 17 June 2026, Taunton. Shakib Al Hasan made 124 not out and took two wickets as Bangladesh beat West Indies by seven wickets in the ODI World Cup. The line looks like a freak day. The real story of that tournament was rhythm — repeated batting and bowling contributions across a single event, rare in that format. One innings and one rhythm are different claims, and only a blank column teaches you to tell them apart.

Two weeks later, when a fast bowler breaks down, nobody remembers the sentence that said there were no injury concerns. They assume the timing was unlucky. It usually was not. The timing was in the schedule all along; the cell was just empty.

So here is the check for the next match. Does the data carry a format tag? No tag, discard it. Is the sample size stated? Four matches is not a verdict. Does a claim open with "obviously" or "surely"? There is a blank cell behind it. And then the one that actually matters: watch the first six overs and count the dot balls. That count never appears in a spreadsheet, and it tells you whether the powerplay plan was real.

Next time a table shows rows of empty cells, remember the producer's question. "So there's no risk?" The answer is that risk is there, and we have not yet learned its name. Unnamed risk grows fastest, because nobody is looking at it. In the next match you will probably notice something small — a fielder half a step slow between slip and gully. That is the empty cell nobody filled in.