N/A Is Also a Finding: Auditing Asian Cricket's Data Ledger

Methodology Box - Sample: IPL 2026 (60 matches, 14,216 deliveries), IPL 2026 in the UAE (60 matches), the 2026 FIFA World Cup overnight desk (64 matches), the public Ranji Trophy scorecard set, and women's cricket records from 2026 to 2026. - Date range: 5 April–21 May 2026; 19 September–10 November 2026; 14 June–15 July 2026; domestic seasons 2026-24 to 2026-26. - Source: my hand-coded spreadsheet ledger, official scorecards, broadcast-feed readings and public archives. - Known gaps: ball-by-ball data for domestic and women's fixtures is incomplete; soft variables — injury, workload, travel — have no column in any ledger.

---

Last week a file landed on the desk. Blank title, blank source, blank author stance, blank summary. Only one field was filled — domain: Asian cricket. Two roads opened. Fill the blanks from memory, since nobody at deadline asks where a number came from. Or write that the file is empty.

I took the second road, then spent three hours looking at how much information that emptiness contains. Invert the Asian cricket ledger and it is not an anomaly. It is the rule. Men's international T20 and ODI data sits second by second; in the same subcontinent there are domestic matches whose scorecards are not even complete. The sport we argue about for four hours a day is, in places, not recorded at all.

Three screens, one timezone, and a column that cannot be filed until the field is filled.

Context: Asian cricket's data geography has three layers

Layer one — men's international cricket. Coverage is dense. ACC tournaments, BCCI series, PCB fixtures, SLC and BCB series — scorecards exist, ball-by-ball logs exist in many places, and the data provider behind the television graphics logs speed, line, length and revolutions on every delivery. My complaint here is not scarcity but surplus, and surplus is where everyone forgets to ask what the baseline is.

Layer two — domestic first-class cricket. The Ranji Trophy has run since 2026. Every season: 30-plus teams, 100-plus matches, 1,200 to 1,500 deliveries per match. The scorecard exists. Phase splits do not. The mode of dismissal exists; the speed of that delivery does not. Runs exist; the pitch, the ball and the temperature they were made in do not.

Layer three — women's cricket and associate nations. WPL began in 2026; India won the home World Cup in 2026. Yet ball-by-ball archives of women's domestic matches remain fragmentary, and in Nepal, the UAE or Oman a match's only record is sometimes a tweet or a newspaper cutting.

Across the three layers, one pattern holds: more money, more data; more data, more argument. Where there is no data there is no argument — only opinion. Asian cricket's deepest information inequality is not about who owns cameras. It is about who owns records.

A transfer assumption belongs here, because I was raised in Australia and work in India. My instincts were formed on Kookaburra bounce and day-night seam. That model runs as confidently here as it did there, and the output looks equally clean. The bigger risk in Asian conditions is not missing data but mis-transferred data. The boundary line must be written every time: this analysis does not travel to red-ball cricket.

Core: five ledgers that refused to fill the blanks

1. The 2026 hand-coded ledger

In 2026 I wanted dot balls split by phase. Nothing free did that. So from 5 April to 21 May I hand-coded all 60 IPL matches — 14,216 deliveries — into one spreadsheet. Batter, bowler, over, runs, wicket, fielding intervention. The number that got published: Mumbai Indians conceded 7.42 an over between overs 17 and 20, the tightest death-bowling figure of the season. The desk ran it as "The Death Overs Nobody Noticed." I was 27, and my name sat above a methodology note for the first time.

One date completes the number: 21 May 2026, Hyderabad, Mumbai Indians beat Rising Pune Supergiant by one run — Rohit Sharma's side against Steve Smith's.

What I did not understand then: 7.42 means nothing on its own. It needs the league's average death run rate, the venues' scoring baseline, and the dew those 240 deliveries were bowled in. The first two were available. The third never was, because an IPL scorecard has no dew column.

That is where my rule came from: I do not trust a metric I have not verified myself. And its corollary: a blank field should be printed as blank, not filled with an average.

2. The 2026 dew curve

Behind closed doors in the UAE, a mid-table franchise paid me to build a dew curve from second-innings run rates in Abu Dhabi, Dubai and Sharjah. Chasing sides won 65% of those 60 matches, against 52% in 2026 — thirteen percentage points, in a season with no crowds. The curve had a hinge: at Sharjah the effect inverted after the 15th over.

My memo argued for batting first there after winning the toss. The team ignored it twice, lost both, then adopted it for the final four games.

Process and outcome are separate things. A good decision that lost is a good decision that lost; a bad one that won is a bad decision that won. Assigning praise from the scoreboard is the easiest and most dishonest work on the desk.

One thing nobody wrote afterwards: empty stadiums changed the baseline itself. Dew forms the same, but a bowler's pressure, a batter's hearing and a fielder's reaction all shift. Comparing that season's numbers directly with 2026 or 2026 is a methodology error. I did not make it, because every table carried the line: this sample is an empty stadium.

3. The 2026 overnight desk

June 2026, all 64 World Cup matches, overnight desk, licensed data arriving eight hours late. I logged xG and PPDA off broadcast feeds. In Kazan, Germany lost 0-2 to South Korea with 74% of the ball and an xG that never crossed 1.0. The explainer that travelled: possession without penetration is just passing. By August I had ported the idea into cricket as a "pressure index" — dot balls plus fielding interventions per over — and tested it on 2026 IPL footage. I stopped publishing raw averages. Every figure now carries an opponent adjustment and a comparison baseline.

4. The Ranji dataset nobody watches

Hundreds of performances a season with no video, no graphics, no highlights. Sarfaraz Khan is the recent proof: he scored season after season in the Ranji Trophy before national selection arrived, and only then did people open his domestic record. The record was there. Nobody read it.

The real casualty of the IPL boom was not Test cricket but the domestic competition's visibility. Test cricket has history, prestige and an audience. Ranji has only a record, in a format nobody wants to read. When comparable data is absent, the fastest available information wins — and the fastest available information is always reputation.

5. Women's cricket: a record of wins, not a structure of records

After WPL 2026 and the 2026 home World Cup, the celebrations are justified. My interest is accounting. A sport whose record is not maintained cannot be argued about. How many matches of the 2026 women's domestic season have ball-by-ball data? Where is a clean series of WPL phase splits a researcher can open in three years? Mostly the answer is "incomplete." Men's cricket spent 150 years building, breaking and rebuilding its record. Women's cricket can build the right structure at the start instead of spending decades repairing an old one. That window does not reopen.

Contrarian: "insufficient sample" is the most honest and most ignored finding

Earlier this year I held a column because the sample was 11 innings and no phase verdict could survive it. The desk asked whether we could run it anyway. I said we could — the conclusion would simply be "insufficient sample."

People make a face at that. A column concluding "we do not know yet" sells nothing. It is also a publishable finding, and infinitely better than a false one. Respect for sample size, learned the hard way, makes "not enough data" feel honest — and safe. That is exactly where columns stall.

The fix is procedural: file on the evidence that exists at the cutoff, timestamped. Then "insufficient sample" becomes a finding rather than a defeat, and the reader learns what eleven innings cannot say.

Two more traps sit close. Dataset transfer: Australian priors produce equally confident output in Indian conditions, and clean output is not proof of truth. Statistical attractiveness: 65% of chases were won in 2026 — that does not mean dew won them. Correlation is not causation, least of all with dew, which arrives from temperature, humidity and grass density, not from a coin. And access: in India, data, accreditation, auction access and press-box facilities flow from the same institution I am meant to audit. Every privileged dataset's source and my accreditation status belong in a standing line; where access was conditional, the condition gets written into the piece.

And the subtlest trap — writing a player as a set of phase splits. Numbers are cleaner than testimony, but injury, workload, family and selection fear have no column in a methodology box. Before any verdict, insert one conditions note built from reported facts; if none exist, say so explicitly rather than implying none matter.

Takeaway: the next-round signal sits in four unglamorous jobs

Standardise domestic scorecards so phase splits exist for Ranji and women's fixtures. Add a permanent conditions column — toss, dew, temperature, humidity, attendance — so that "180 is safe" can be tested rather than asserted. Build a culture of cutoffs and timestamps, so a piece read six months later still knows what it was built on. And accept that some fields will stay blank, then print them.

In 2026 I thought the methodology note would weaken the copy. Readers quoted it back in the comments. The next time a scorecard lands in front of you with empty fields, pause. That emptiness is not a defect. It is a question the scorecard is asking — and the best Asian cricket argument of the next few years will begin with the answer: "we do not have that data yet."