The Warning of an Empty Spreadsheet: Data-Integrity Crisis and Method Discipline in Asian Cricket Analysis

A night last month. Asia Cup preparation was underway. I was preparing for live analysis from Mirpur, a ball-by-ball dashboard open in front of me. Numbers were supposed to float across the screen; empty cells floated instead. One blank cell after another. No error message, no warning, just silent emptiness. In that moment it became clear: I was not watching a crisis of cricket, I was watching a crisis of data. And in cricket, a data crisis is almost always a truth crisis.

That is the centre of today's discussion. When I saw the output of an automated analysis pipeline in which every single field read 'insufficient information, cannot assess', my first instinct was to call it a failure. Later I understood it was a warning. When a spreadsheet is empty, it does not lie. And in the world of Asian cricket analysis today, the greatest danger is not lying; the greatest danger is filling the blank cell with our own imagination.

The spreadsheet remembers what the stadium forgets.

Context: The impossible speed of analysis in Asia

Since Bangladesh gained Test status in 2026, subcontinental cricket has moved through continuous change. Beating India at Port of Spain in 2026, beating Australia at Cardiff in 2026 — these were not just results, they were moments when the region's audience first began to understand that nothing miraculous happens without information and preparation. Then came the Indian Premier League, the BPL, the frequent editions of the Asia Cup, the subcontinental hosting of T20 World Cups. Behind each of these stages grew an enormous data economy.

I used to score cricket in Rajshahi. Back then records were kept by hand, in a notebook, sometimes on a scrap of paper. In 2026, when I started a football analytics newsletter called Expected Truth, I had no big studio, no live dashboard. I had only one habit — writing down the source of every number. That habit is now the rarest thing in Asian cricket analysis.

I moved from a Rajshahi newsletter to live World Cup analysis, and the discipline never changed. The question never changed: where did this number come from, who recorded it, and in what context does it mean anything?

Today Asian cricket analysis lives inside two contradictory realities. On one side, ball-by-ball data, delivery tracking, multi-angle camera capture — a flood of information that was unimaginable twenty years ago. On the other, a large portion of that information is unverified, incomplete, sometimes filled in purely by guesswork. A pipeline that is supposed to deliver over-by-over data during a live match returns empty one night — and no one notices, because we find it easier to cover the absence of numbers with the presence of numbers.

This piece is written against that habit of covering up. I hold no specific scorecard today, no player name, no venue pitch report. So I will not invent a team, a player, or a result. Instead I will look at the question the empty spreadsheet leaves in front of us: in Asian cricket analysis, what are we actually measuring, and where do we go wrong in trying to measure it?

The core: Cricket's 'expected' problem

In football, expected goals is a simple idea. Shot location, angle, distance, pressure — combined into a probability. My whole career is built around that idea. In cricket it does not transfer directly, because cricket has no 'shot'; cricket has a ball, a batter's decision, a bowler's plan, and a situation that changes with every delivery.

What we might call 'expected runs' in cricket can never be as simple as xG. The expected runs from a delivery depend on the bowler's type, line and length, the age of the ball, the state of the pitch, the field setting, the batter's handedness, and even the phase of the match. Each variable can be measured separately, but their interaction is so complex that the model and the human eye frequently disagree.

I have seen many times a model claiming a batter performed far above expectation, while someone watching from the ground knows that half the runs came from two or three slog-sweeps made easy by the wind that day. Expected goals are confessions, not predictions. That line is true in football; it is even truer in cricket. A model never says 'this batter will score 50 next match'; it only says 'balls like this usually yield this many runs'. The difference is enormous, and failing to grasp it is why Asian cricket analysis produces so many wrong forecasts.

Subcontinental pitches complicate this further. Mirpur, Chattogram, Dhaka, Colombo, Lahore — each venue has its own character, and the same venue behaves differently by season. A winter-morning Dhaka pitch rewards spin; a monsoon match makes the same pitch nearly inert. A model that treats a venue as a fixed variable tells half the story and calls it the whole.

This is where data integrity enters. If I do not have — which venue, which day, what humidity, what ball age — I can manufacture any 'expected' number I like. And a manufactured number is more dangerous than a measurement, because it looks confident. An empty cell is at least honest; a filled cell with unknown provenance is a lie.

Bowling pressure: Cricket's low block

In football I spent years working on one idea — defensive structure. At the 2026 Qatar World Cup I built a model around Morocco's defence: across five matches before the semi-final they conceded only one goal, an own goal, with an xGA of just 1.2 and a PPDA of 13.5. — Root: 2026 Qatar World Cup and Morocco. I called that model Low Block as High Art, because I believe organised defence is not cowardice, it is architecture.

In cricket, the name of that architecture is dot-ball pressure. When a bowling unit strings together dot balls, it does to the opposition what a low block does in football — it shrinks the time available to make decisions. This craft matters especially in subcontinental cricket, because pitches here are usually slow, and on slow pitches the value of a dot ball rises sharply.

There is a trap here too. Dot-ball percentage alone says little. Forty per cent dots in the powerplay means something different from forty per cent in the death overs. The same number reverses its meaning when the context changes. An analyst who concludes from dot-ball percentage alone is like a map-reader who knows only north.

My own habit is to split bowling pressure into three separate skills: powerplay pressure, middle-over control, and death-over effectiveness. Each demands its own metric. Bangladesh's spinners have historically been superb in the middle overs, because the pitch is on their side. But when the same spinner bowls at the death, the metric changes, because the batter is forced to take risk. Miss that distinction and analysis sounds like advocacy rather than audit.

I always follow one rule: a number only means something when it has a companion context. The companion of dot-ball percentage should be the over phase, the field setting, and the opposition's required rate. Without those companions, the number is decoration.

Empty stadiums: A controlled experiment

In 2026, when world sport shut down, I analysed 55 Bundesliga matches played in empty stadiums. Home win rate fell from 43.3 per cent to 33.3 per cent, linked to higher pressing and greater distance covered by away teams. I titled that piece The Ghost Advantage. Empty stadiums did not silence football; they exposed its skeleton.

That experience taught me a large lesson, one that applies to cricket: environment is never neutral. Crowd, noise, pressure, even the announcer's voice — these are part of the game, and measuring without them means measuring an artificial version of the game.

In cricket the question becomes urgent when we try to explain 'home advantage'. In the subcontinent, home advantage is not only about pitch or weather; it is about crowd pressure, familiar surroundings, even umpiring bias. But each of these variables is nearly impossible to isolate, because we never get a controlled cricket match in which only one variable has changed.

Here lies my caution. After Covid, some analysts wanted to transplant the empty-stadium football data directly into cricket. But football pressing and cricket bowling pressure are not the same thing. In football, crowd noise translates directly into pressing intensity; in cricket, crowd noise translates mainly into a batter's mental pressure. Same change, two different channels. Ignore that and we reach a wrong conclusion — and that conclusion then becomes the basis of wrong decisions.

So I treat the empty stadium in cricket as an open question, not a source of certain answers. The question is: does home advantage shrink in a crowdless environment? I do not know, and an analyst who claims to know is probably over-trusting their own model. An honest 'I do not know' is always worth more than an unknowingly wrong 'I know'.

The cross-format trap and the small-sample delusion

One of the most common errors in Asian cricket analysis is mixing formats. A Test century and a T20 century are not the same thing, even though the number is identical — 100. A Test innings runs eight hours; there, patience is the measure. A T20 innings runs seventy minutes; there, risk is the measure. Judging one player on the same index across two formats is like marking two different exam papers together.

The error turns dangerous with small samples. In T20, a player is declared 'in form' or 'out of form' after three or four innings. But statistically, three or four observations are not a trend; they are noise. Mistake that noise for a signal and we reach conclusions that collapse within a month.

I have fallen into this trap myself, so I now keep a personal rule: before judging any player I check how many ball-events their recent performance rests on, who the opposition was, where the venue was, and what the match situation was. Without answers to those four questions I reach no conclusion. An empty cell is worth more to me than four filled cells whose provenance is unknown.

This discipline matters especially in subcontinental cricket, because the depth of talent here is enormous, and depth of talent means depth of competition. A young pacer can sparkle in one tournament and instantly acquire a legend. Behind that legend there is often no load-management data, no workload analysis. Yet it is at this age that pacers carry the greatest risk, because their bodies are not yet mature and the dense T20 calendar puts near-cruel strain on them.

Let me be clear about one thing. Load management is romanticised, but in practice it is often a polite name for accommodating commercial tours and warm-up matches. If the decision to rest a young pacer comes not before a preparatory series but in the middle of a meaningful competition, that decision serves the calendar, not the player. Analysts should catch that distinction, because if data tells the truth, it also carries the duty to tell it.

The auction ledger: A liquidity event for hope

Every year the BPL and IPL auctions arrive, and every year the same scene. The January transfer window is a liquidity event for hope, and I audit the books. I wrote that line for football, but it is even clearer in cricket auctions.

An auction is essentially a valuation process. The price a team pays for a player is a blend of cricketing value and commercial value. But the two are not always aligned. A big name may fetch more because of marketability, even when recent form says otherwise. An effective all-rounder may go cheap because the name is not big, even when the numbers make him indispensable.

That mismatch is the most interesting analytical object. In January 2026, when I wrote about Sofyan Amrabat — 89 per cent pass completion, 8.7 progressive passes per 90, 2.3 tackles per 90 — I was really hunting for value inefficiency in the football market. The same work can be done in cricket; only the metrics change.

The simplest route to finding value inefficiency in cricket is to compare two kinds of players: the one who draws crowds, and the one who wins matches. The gap between them is measurable, if we choose the right metric. But caution is needed. An auction price is set by demand and supply, not merit alone. So a low price is not always 'undervaluation'; sometimes it is just normal market behaviour.

Here I always remind myself that a model never controls the market, it only explains it. And when explanation puts on the costume of prediction, danger begins.

The contrarian angle: Correlation is never causation

Now to the part I care about most. In Asian cricket analysis we routinely make a dangerous leap — from correlation to causation. We see that a team wins more when it bowls more dot balls. We immediately conclude that dot balls cause victory. That is a faulty inference. Perhaps those teams simply have better bowlers, and better bowlers bowl more dots. Here dot balls are the effect, not the cause.

Understanding that distinction matters, because the entire value of analysis depends on whether we are asking the right question. A flawless answer to a wrong question never leads to a right decision.

And here the empty spreadsheet teaches us. A pipeline that returns empty at least does not lie. The danger comes when we fill the blank cell with our own assumptions and pass it off as information. In Asian cricket analysis, this habit is the disease of the age. We cover the absence of numbers with an abundance of numbers, then base decisions on the covering.

I identify three causes. First, the pressure of live broadcast — something must be said every over, so gaps are quickly filled. Second, audience demand — they want certain answers, not nuance. Third, analyst ego — saying 'I do not know' is hard, especially when the platform demands certainty.

These three pressures combine to create an environment where a wrong number is rewarded more than a right question. And Asian cricket, where the data infrastructure is still uneven, is where this environment turns most dangerous.

I follow one rule in my own work and recommend it to everyone: write the confidence level next to every number. Mark verified fact, probable fact, and assumption separately. That small habit turns analysis into an audit, and an audit never lies.

Reconciling spreadsheet and stadium

My whole career rests on one simple belief: the spreadsheet and the stadium are not in conflict. When the two diverge, either the spreadsheet is wrong or the eye is wrong. That reconciliation is the true duty of a data analyst.

Whenever I see a number, I check it against the memory of the ground. If a model says a spinner was effective while I watched from the ground as batters played him comfortably, I question the model, not the memory. If the memory says a batter was extraordinary while the number says he underperformed, I again question the model — because the model probably failed to account for venue or situation.

This two-way check is especially necessary in Asian cricket, because the game here is often unorthodox. Batters slog-sweep against spin, pacers use cutters to kill pace, keepers stand up to the stumps to help spinners. These are behaviours a Western-centric model struggles to capture.

So Asian cricket needs its own models, its own metrics, its own definitions. Transplanting an outside model wholesale means telling a wrong story — one with plenty of numbers and little truth.

The expectation gap: Public opinion and ground truth

Another duty of analysis is to identify the gap between public opinion and reality. In Asian cricket, the audience's expectation of a big name often runs ahead of that player's current performance. That gap is the most interesting analytical territory.

I have often seen a whole region build a story around one name before a tournament, and that story collapse before the tournament ends. Behind the collapse there is no secret; only the limits of the sample and the change in environment. But because the story was built early, damage is done before the truth arrives.

Let me be clear. I am not against hero stories; I am against hero stories that erase the system. When a spinner wins a match, only his name is spoken; no one mentions which academy, which coach, which pitch, which domestic competition made him. The system disappears and we tell only the story of the individual.

In subcontinental cricket, this erasure is harmful in the long run. It teaches us not how talent is produced, only how talent is celebrated. And an analysis stuck in celebration cannot show the path of development.

Industry transmission: From data to decision

Cricket analysis is never isolated work. It is part of a supply chain that begins with a domestic scorecard, moves to national selection, then broadcast, then sponsorship, then fan expectation. At every layer of this chain information is transformed, and at every transformation some information is lost.

My own work sits at the chain's most delicate point — where raw data becomes interpretation. At that point a small error returns amplified across the whole chain. A wrong dot-ball percentage can push a selector toward a wrong decision; a wrong venue reading can create wrong expectations in broadcast; and that expectation later becomes fan disappointment.

For Asian cricket this transmission chain is still incomplete. In some places data is collected but not stored; in others stored but not verified; in others verified but not published. This uneven chain is what produces the empty cell I saw last month.

Morocco's lesson: Comparative modelling

I return to Morocco again and again, because Morocco is a recurring model for me. — Root: 2026 Qatar World Cup and Morocco. Limited resources, limited stars, extraordinary organisation. Seeking the cricket analogue, we find teams that fight bigger opponents with limited resources — sometimes on slow pitches, sometimes through clever field settings, sometimes through a game of patience.

Morocco's model teaches that weakness is never only a lack of resources; weakness is a lack of organisation. A team with fewer resources but better organisation often outperforms a richer, less organised side. In cricket this principle applies directly, especially in short tournaments, where a precise plan can beat a star-dependent one.

I want to see this model in Asian cricket, but cautiously. Cricket differs from football in one big way — in cricket every ball is a separate decision, so organisation matters even more. A good plan pays off every ball in cricket; in football, mainly every attack.

The contrarian corner: The forecasting trap

Now the trap that is my own greatest risk. Because I love developmental forecasting, I can easily slide into the role of prophet. This risk is widespread in Asian cricket analysis, because star-making is an industry, and that industry rests on prophecy.

To avoid the trap I use a simple method. Whenever I make a forecast I write it down, then check it later. If my forecast is wrong, I admit it, publicly. This habit is uncomfortable, because it makes me look weak. But that discomfort keeps me honest.

Here is my core argument. An analysis is valuable only when it knows its own limits. An analyst who does not know their limits is not a prophet, only a confident liar. An empty spreadsheet admits that limit — and that is why I am writing today in defence of the empty spreadsheet.

Final word: The next-round signal

The empty cell I saw last month left me with a question that I believe is the most urgent facing Asian cricket analysis: can we build a data infrastructure that keeps the provenance of every number, records every context, and marks every assumption clearly as an assumption?

I know this is not easy. It demands discipline, time, and that uncomfortable honesty which resists the temptation to call a blank cell a filled one. But I believe this work is what will distinguish Asian cricket on the world stage over the next decade — not by talent alone, but by method.

The spreadsheet remembers what the stadium forgets. The only question is this — will we learn to read that memory, or will we fill the blank page with our own story?