The Testimony of Zero Data: Why 'N/A' Is the Most Honest Answer in Cricket Analytics

The file arrived at my desk a little after ten in the morning. Eight sections. More than forty table cells. Every one of them read the same: N/A. No date, no team, no format, no competition, not even a single player's name. The only address it carried was a tag: cricket_asia.

A continent and a sport, glued together, do not make a dataset. That is the address of an assumption, not of evidence.

But at the bottom of the document sat a line I rarely see in my trade. It said that with insufficient information, the analysis could not proceed. In twenty years I have watched bad models, surplus confidence, and blind faith in scorelines. A data desk admitting its own empty hands is a rarer sight than any of them.

The numbers were never the story; they were the trail. And when the trail has not started, describing the destination is not my job.

I joined the Mumbai City FC data desk in 2026, forty-nine years old at the time. After a 2-1 win over FC Pune City in the ISL, the dressing room was celebrating and I was on a laptop rebuilding the match. xG came out at 1.9 against 1.1, PPDA at 8.3. The numbers said the win was happier than the result deserved. I filed a column that night arguing the pressing structure was not sustainable, that every lost ball opened a corridor. I called the column Expected Notes. Fifty thousand people read it. A national broadcaster wrote back.

The next year, Russia. On 30 June 2026, at the Kazan Arena, France beat Argentina 4-3. I built the Kylian Mbappe file the same night: seven dribbles, two goals, one penalty won, top speed 36.6 km/h. France's xG was 2.1, Argentina's 1.4. Two hundred thousand readers came through that dispatch. The mantra settled there — data does not lie, but you must interrogate it.

In 2026, working with Bengaluru FC inside Goa's bio-bubble, I measured empty stadiums. Home win percentage fell from 46 percent to 38 percent. Pressing intensity dropped twelve percent. That was the year I moved from match reports to systemic trends.

The method itself runs in two stages. Stage one is deconstruction: pulling information points, named entities, sources, and viewpoints out of the original document. Stage two is the eight-dimension analysis: format, player technique and data, team landscape and ranking, league and commercial ecosystem, rules and governance, risk, public narrative, and industry transmission. The file that reached me was empty at stage one. There was no door into stage two.

I opened the Expected Notes, and the match would not confess. Silence, I learned that morning, is also a result — provided you do not misread it.

Without a format, no number means anything. On 18 June 2026 at The Oval, Pakistan made 338 for 4 in the Champions Trophy final, Fakhar Zaman scoring 114. India were bowled out for 158, beaten by 180 runs. In that match, eight runs an over was a measure of dominance; the same eight an over in the middle overs of a T20 is ordinary. ODI and T20 baselines differ. Test baselines differ from both. Without the format, you do not know whether the run rate is low or high.

Format is the calibration line against which every performance is judged. The same strike rate is elite in one format and a burden in another. That is why I keep the Mbappe file so carefully — speed, dribbles, penalties won, goals, all measured inside a single format context. When somebody tells me a batter is going at nine an over, my first question is: in which format, in which phase, off how many balls.

Player analysis needs three things — identity, role, sample size. Without a name, all three vanish. Without a role, you cannot tell whether a 130 strike rate is valuable for a number five or wasteful for an opener. With a small sample, every conclusion is noise. In my experience a T20 batter's strike rate stabilises around two hundred balls; anything shorter measures form, not skill. Bowler economy is equally empty without phase and matchup — an economy of seven with the new ball in the powerplay and an economy of seven in the middle overs are two different professions.

Sample size is the line below which talent and luck cannot be separated. A twenty-year-old left-arm spinner's sudden 4 for 22 may mean something, and may mean nothing. What separates the two is home-away splits and the quality of the opposition.

The team picture is emptier still. The ICC ranking is a rolling formula; weights shift with every series and points bleed with every defeat. Without a team name it is a null set. Squad depth, bench strength, and age structure have to be read together. My desk keeps one rule: when a side's batting averages from number three to number six swing by more than five runs, that side has nobody in the middle overs. That is a reading of structure, not a personal opinion.

The commercial layer is blank in the same way. Without an identified league, broadcast valuation is impossible. In the 2026 auction, the IPL's media rights for the 2026-27 cycle sold for roughly 48,390 crore rupees in total, with the television and digital packages going to two separate buyers. The question is not the per-match price; it is whether that price tracks audience growth or the fear of a rival platform. A platform that buys rights without growing subscribers is repeating old television's mistake in new colours. I hold the same objection to fat signing-on fees for free agents — the transfer fee sits in plain sight, the signing fee hides, and the core test of financial transparency gets skipped.

Governance needs a controversy to enter. On 14 July 2026 at Lord's, the World Cup final ended with England 241 and New Zealand 241 for 8, the Super Over tied, and the trophy decided on boundary count, 26 against 17. The result was not settled by cricket; it was settled by a regulation. That is what governance analysis is — watching how rules manufacture outcomes from outside the game. DRS decisions, revenue-distribution formulas, eligibility clauses all belong to the same family. Without an identified subject, not one member of that family can be judged.

The risk section says the most in this document. The list read: mixing conclusions across formats, over-extrapolating from thin information, ignoring home-ground bias, failing to account for luck, DRS controversies affecting fairness. Notice what these are. They are not findings about a match. They are a catalogue of the places where an analyst can lie.

A risk register is the analyst's own checklist of weaknesses, not a scouting report on the opposition. A desk that applies that list to itself writes less and writes correctly.

The narrative layer is subtler. A young batter's six-hitting clip goes viral while his strike rate against spin in the middle overs sits in the mud. That gap between expectation and fundamental is the most profitable analytical territory — if the player is identified. Without identification you are measuring the temperature of hype, not cricket.

Industry transmission is a simple chain: youth development and talent supply, then national teams and leagues, then broadcast, sponsorship, and derivatives. With nothing at the front of the chain, impact at the back cannot be computed. That is the cruelty of method. You can fill the chain with assumptions, but that is a story, not a model.

Here the contrarian turn arrives, and it turns against my own trade.

The industry's real failure is not missing information. It is confidently manufactured information. Show an analyst a label like cricket_asia and the mind supplies a scene — a thrilling Asian series, an emerging star, a boardroom quarrel. What gets written then comes from the label, not from data. And the relationship between a label and an outcome is correlation, never causation.

The distance between correlation and causation is the only real boundary line in this profession. An analyst who does not draw it can publish fast, but the work will not survive as inheritance.

There is one more subtle lesson in the document. Confidence ratings were attached to certain claims — high in some places, low in others. Those words are instructions, not verdicts. High confidence means high confidence about the document, not about the dataset. A reader who misses that distinction will believe cricket has been judged. It has not. It has merely stopped for want of data.

I have watched this kind of stopping from the stands many times. When rain arrives and a Duckworth-Lewis-Stern recalculation shifts the target, the scoreboard number and the match's truth stop being the same thing. The experienced commentator goes quiet; the weak one guesses. The same law governs a cricket desk.

So where does the gaze go next? The document set out five tracking signals, each with a trigger condition. If the original source is published, reliability can be assessed. If players or teams are named, targeted data analysis can begin. If the format is established — Test, ODI, T20, or something else — tactical reading becomes possible. If verifiable statistics appear from the ICC or a reputable statistical archive, claims acquire a floor. And if the publication date is confirmed, we will know whether this is history or a live event.

A null result is never a permanent verdict; it is a pending trigger list. The desk that holds the list speaks first in the next round. The desk that invents a story now will have to correct it later, and correction always costs more than silence.

I have no illusions about my legacy. Readers will not remember my tables, nor even the rows inside them. They will remember a habit — put the source next to the claim, and if there is no source, delete the claim. If the next generation of analysts learns that one thing, the work was worth it.

As for the report that arrived this morning, every N/A in it reads to me as testimony: this desk at least did not cheat itself. The question now is a single one. When the next match file lands, will you build a story out of the number, or go looking for the trail behind it?