The Empty Dataset and the Full Scorecard: The Cricket Analysis Lesson We Keep Forgetting

I have kept one file open on my laptop for the past few days. It is called stage2_analysis_final.md. Inside it, there are eight sections — format analysis, player technique, team landscape, league ecosystem, governance, risk matrix, narrative analysis, and industry transmission. Every section has a table, every table has rows, and every row repeats the same sentence: N/A — insufficient information, cannot assess.

This is not a cricket report. This is a report refusing to be a cricket report. And in my trade, over the past few years, I have rarely seen anything this honest.

The case is simple. In the first stage of an analysis pipeline, the source material came in empty. Title N/A, source N/A, core viewpoints blank placeholders, information points lists with zero entries. The stage-two analyst had two choices. One: fill the blank spaces with guesswork, with feeling, with a narrative that reads well. Two: write clearly in every cell that there is no information here.

The second path was chosen. In that file, the phrase insufficient information, cannot assess appears more than forty times. I know how hard that is to admit. When you have been tagging data for ten years, when you have logged sixty-four matches in thirty-two days, the hand itches when it sees an empty cell. It wants to fill it.

This is exactly where the biggest problem in cricket analysis sits.

Consider the context. Over the last decade, the cricket data industry has picked up a dangerous habit — the habit of filling empty space with inference. A heat map area that is not clear gets colored in anyway. A player with a sample of twenty balls gets a verdict written on his technique. A match with four wickets produces a trend about the whole series. I learned this myself, hand-tagging 380 Championship matches — a model stays clean only when you accept that some things lie outside it.

In 2026, building the shot-quality model for Chris Wood at Leeds United, I priced 27 goals at 19.4 xG — a 39% overperformance. That was a warning, not a highlight reel. Burnley still signed him for £15m that August. I had not filled the empty part of the model — I had only shown which part was empty. The model was clean, but the player kept arriving late for the press.

Now apply that thinking to cricket.

The most dangerous sentence in cricket analysis is: "the data says." This sentence is often written when the data has said nothing at all. A strike rate is available and the context is not — so the analyst fills the context with feeling. An economy rate is there and the pitch is not — so the analyst assumes it was flat. Is it really so hard to write that the pitch report for this match is unavailable, and therefore the bowling numbers are limited in interpretation?

In the same way, when a player's last five innings arrive, the depth beyond six games is often not shown. But the verdict is written on five innings. This is the technique that ignores the age curve, bypasses injury history, explains why a team is changing, but gives no context.

And this problem is not limited to player analysis. When any league (IPL, BBL, The Hundred, PSL, SA20, CPL, MLC) comes into discussion, broadcast rights, franchise valuations and player salaries come up. But if the number for any one of these three is unavailable, is it necessary to add an estimate? In my experience, the biggest error in league valuation is erasing the gap between salary and sporting value. An auction or trade price is a rumour until the minutes show who was missed. And if the minutes data itself is unavailable, the right thing to do is to write that the minutes data is unavailable.

Now the contrarian angle. There is a misunderstanding that could form around this empty report — that it is a failure of analysis. My view is that it is the greatest win of analysis. This is the report that refuses to accept that the reader must be given a story under all circumstances. In both cricket journalism and analysis, we have built a strange equation — that unavailability of material is inadequacy, and that inadequacy should never be printed. So we fill that space with cricketer stats, data indices, live blogs and talking heads, when actually the truth is that we do not know.

I remember an old editor from twenty years ago who used to say — if there is even one sentence in a paragraph you cannot prove, cut it. Today, the same advice applies to data. Stop calling analysis any line that did not come straight from a source.

This empty report shows a discipline that is not common in cricket — in the risk matrix, every cell clearly states that assessment is not possible. Sample size could not be checked, home-ground bias could not be assessed, nothing can be said about the fairness of DRS controversies. This is the method that actually builds trust. If an analyst tells me their model applies to every match, I do not trust them. I like the analyst who says — this model works here, not there, and they do not know why.

What to look for next. This empty file is a signal in the cricket data world. In the next few months, when the next big tournament arrives — a World Cup, an Asia Cup, a Hundred season — there will be a flood of highlight clips, commentary boxes and infographics. Everywhere there will be the claim that the data says this. Whenever you read that claim, ask one question — how many matches is behind this claim, how many players' data is there, and what is empty in that data. If the answer contains only words like 'trend' or 'momentum', understand that the honest path of the empty file has been buried somewhere.

What I learned in sixty-odd matches is this — the table breathes only when it contains only what was seen. What was not seen is not a story, it is an inference. And calling an inference a story is the habit this empty report cleanly refused.

Numbers are not the opposite of stories; they are stories with their shoes tied. But a shoe without data is best left empty, and that is respect.