The Empty Spreadsheet, the Unfinished Ledger: An Audit of Asian Cricket's Data Provenance

Last week I opened a file. The spreadsheet cells were white, roughly twenty rows. No title at the top, no source below, no date to the side. In one cell, in small type: cricket_asia. Every other cell was empty. Beside every field sat an N/A. No team, no player, no match, no score, no date, no summary. A deep-analysis document had arrived on my desk, and inside it the raw material of analysis was zero.

My first reaction was not irritation, and not curiosity. It was relief. Because at forty-seven I have learned at least one thing: when you see an empty cell, stop the pen. You can fill a cell with imagination, but then it is no longer analysis — it becomes a story. And cricket does not lack stories. It lacks truth.

But the stopping is not the whole event. The file that came back empty carried a tag: cricket_asia. Asian cricket. The tag names no team, no format, no time. It is only a geographic boundary. Yet for an analyst the tag teaches more than the empty file. It hints that in our pipeline, Asian cricket's data cannot even enter — or enters and gets lost. Today's piece is about that lost data. And one disclaimer up front: I am not predicting any team's win or loss. I am auditing an infrastructure.

Context: My Own Cells, Next to the Empty One

On my desk I keep one habit — before any piece I draw a small box called Method & Sample. In it I write three things: the competition, the match count, the definition of the metric. The habit began in 2026, at Brentford. I was thirty-eight, just finishing an MA in Sociology, and the club hired me as a part-time data consultant. The task was plain: forty-six Championship matches of 2026-17, logging second-ball recoveries after set pieces. Using xG, I found Brentford were generating 0.18 xG per game from those sequences — but only when the first contact was won within twelve yards of goal. I refused to generalise until the sample passed forty matches. The club adopted the trigger. I was silent in the meetings; my spreadsheet changed the training drill.

I audited Brentford. That box still opens every piece I write.

Then came 2026, the Russia World Cup. The Brentford work put me in a BBC Sport data consultancy chair. Across sixty-four matches I tracked PPDA and set-piece xG. Against England's six set-piece goals, xG stood at 4.2 — I warned that regression was coming. I also logged Croatia's slow starts: zero first-half goals in three knockout matches. Some wanted to call it momentum; I refused. Russia 2026 taught me that every group-stage miracle needs a sample-size warning. After the final I filed a twenty-two-page report; the BBC used three of my charts on air.

At the Russia data desk, I learned that vibes do not survive a second pass.

In 2026, during the pandemic hiatus, Brighton hired me to model the empty-stadium effect. I examined ninety-two Premier League matches before and after lockdown. Home advantage fell from 0.41 goals per match to 0.19. But I did not say fans were irrelevant, because the post-lockdown sample was only forty-six matches. I wrote a cautious twelve-page report with confidence intervals, checking every match for red cards and weather as controls. Empty stadiums did not erase home advantage; they revealed where it lived.

One thing is common to all three jobs: the data existed. Someone logged every ball, kept every timestamp, saved every file. My job was only interpretation. In Asia my problem is the exact reverse. There, before interpreting, I often have to ask: where is the data at all? Before the narrative arrives, I check the baseline and the control group. In Asian cricket that baseline is frequently absent. And without a baseline, counter-intuition is just arrogance.

Core: The Unfinished Ledger

A blockchain's value is not in its coin but in its ledger — in the ability to hold provenance and the record of change. So long as a block holds the hash of the previous block, it cannot easily lie. Cricket's problem is exactly here: Asian cricket has no intact ledger. How many balls a player has bowled, how much spin a pitch has taken, how much workload a body has absorbed — there is no verifiable, preserved account. That is why the file came back to me empty. But it is not a failure; it is a symptom. Below are five cells that are often blank in Asian cricket.

(1) The Limits of Ball-by-Ball Logging. In international matches, almost every ball is now logged; there is no denying that. The problem is not internationals but domestic cricket. England's County Championship, Australia's Sheffield Shield — their ball-by-ball data is relatively accessible; age curves, strike rates, bowling loads can all be extracted. Yet Asia's first-class cricket — Bangladesh's National Cricket League, Pakistan's Quaid-e-Azam Trophy, Sri Lanka's Major Clubs — often has either unpublished or incomplete deep data. So the domestic workload of a Shakib Al Hasan, or how many overs a spinner has carried in club cricket, cannot be calculated. Arriving at the international stage, one can only guess; the rest is inference.

This is not a small matter. Suppose a side keeps bowling a young left-arm spinner in domestic cricket. With a time-series of his strike rate, economy, wickets per over, you could see he is good on flat pitches but weak on turning ones. Without the data, the same player plays three straight Tests, damages the side, then disappears — and no one knows why. Not analysis but guesswork is at work here. And guesswork has no confidence interval.

(2) Pitch, Dew and Humidity. xG-style models were born mainly in English and European football conditions — green grass, cool air, light evening dew. Transplant that to Asia and you get what I have seen. Mirpur's spinning top, Colombo's evening dew, Chennai's bitter turner — these are not captured by any world-class model, because the model was never built here. In the second innings the ball loses grip, the spinner's line shifts, run-rate arithmetic flips. If these variables are not preserved quantitatively, the sentence 'batting is hard under dew' stays a proverb and never becomes a metric.

Here is my second concern. We think of Asian cricket as weak because its data is scarce. But the real problem is not volume, it is relevance. The dataset that let me find Brentford's set-piece trigger is useless in Mirpur's forty-five-degree heat. Different environment, different ball, different physical limits. The Asian analyst must therefore do two jobs at once: seek data, and identify the irrelevance of foreign models.

(3) Selection and Workload. Asian boards' selection processes are frequently opaque. Who was dropped, why, who was rested — there is often no auditable document. So workload management runs on proverb and pressure rather than plan. An all-format player like Shakib Al Hasan plays on and on, because 'the side is incomplete without him'. Yet if overs, sprints, innings and travel were held in one ledger, one could see on which travel schedule his injury risk leaps. In the late career of a Mushfiqur Rahim, or with a whip-fast modern batsman like Babar Azam, that account is worth gold.

I am not saying Asia's selectors are incompetent. I am saying their hands lack the instruments of decision. In Europe a club drops a thirty-three-year-old striker after seeing his sprint-decline and recovery curve. In Asia that data either does not exist or is locked in a manager's private notebook. The decision may be right, but it is not repeatable. And without repetition no process is durable.

(4) Satellite Assets. Now I come to the place that worries me most. In Asian cricket the absence of domestic data does not only weaken analysis; it distorts market power. Because when there is no auditable record of the local domestic competition, the only things left to price a player are a few franchise-league highlights, an agent's push, and a television moment. Look at Rashid Khan's rise. The story of a player from Afghanistan becoming a top T20 asset is a story of talent, no doubt; but how much of it was systematic scouting and how much was a few memorable evenings, no one has measured. Without a data ledger, a young Asian talent becomes a 'satellite asset' — a distant, low-cost mine for a big club or big league, whose price is set not by the player but by his noise.

From I audited Brentford I learned one thing: Brentford succeeded because it built data before it bought data, and verified the sample. Asia's small boards do not have that luxury. So the talent logged every week at home does not rise in price, while the talent that appeared twice in highlights flies. That is a market, but not an efficient one.

(5) Agent Noise and the Distance Illusion. Two beliefs have irritated me for years, and both circulate in Asian cricket like untested truths. The first — the player's agent. Agents are football's biggest hidden cost, and in cricket that tendency is now strong. A young Asian cricketer's name suddenly rises in a big league, and it turns out the pricing process contained more relationships and news than record. A data ledger would filter that noise. The second — distance covered and high-intensity sprints. These are sold as effort metrics, yet pointless running also produces pretty numbers. If a fielder runs to the wrong position and covers twelve kilometres, the data calls him 'hard-working'; standing in the right place, he covers less than one. In Asian cricket these metrics are only now arriving, and arriving without design.

Contrarian: Emptiness Is Not Absence of Evidence

Now I come to the point where my audit places me against the consensus. On Asian cricket almost everyone's proposal is the same — more data, more tracking, more analytics. I disagree with that diagnosis. My audit says the problem is not volume but provenance. Asia's deficit is not more data, but reliable and preserved data. And confusing the two produces what I have seen myself: a foreign model is imported, then mispredicts in Asian conditions, then everyone concludes data 'does not work'.

The truth is that one honest empty cell is worth far more than a fabricated number. If the file that came back empty had been filled with imagination — a fictional score, a fictional trend — it would have looked like analysis, but it would have been a story. Russia 2026 taught me that every group-stage miracle needs a sample-size warning. Likewise, every Asian data project needs a provenance warning. Emptiness does not mean absence of evidence; emptiness means emptiness. And the analyst's first duty is to admit that, not to fill it.

This is not, of course, an argument for leaving Asian cricket in the dark. The reverse. Asia's traditional 'eye test' sometimes catches what Western models miss — how much the ball stops in Mirpur, how early Colombo's dew arrives, what changes in a spinner's shoulder angle. My claim is this: that eye test must be seated in the ledger alongside data, not erased by data. Model and human observation are not opposites; the opposites are an unexamined model and an unacknowledged observation.

Takeaway: The Next Round's Signal

So what do I watch next? Three signals. First, watch who is the first in Asia to release domestic ball-by-ball data publicly — a board or a franchise league. Whoever releases first will set the language of player valuation for the next decade. Second, watch who first separates agent noise from the distance metric — who says 'this number is running, not effort'. Third, and most important — watch who admits their data does not exist.

I audited Brentford, and there I learned that the most valuable moment is not when the number arrives, but when you honestly say the sample is insufficient. Asian cricket's next big leap will come not from data volume but from data honesty. The board that first publicly admits its empty cells will be the first to write a trustworthy ledger. So the question is not 'how much data does Asia have' — the question is, 'how true is Asia's data?'