Zero Information Points

Zero is a number. It took me eleven years to accept that.

Last week a deconstruction report landed on my desk. Eight dimensions — format and match, player technique, team landscape, league economics, governance, risk matrix, public narrative, industry transmission. Three or four tables per dimension. Every table populated. Over a hundred cells in total. In all but one of them the same sentence was typed: N/A, insufficient information. No title. No source. The one-line summary empty. The core viewpoints empty. And the list of information points — the thing the entire building was supposed to stand on — completely empty. One unit of data survived that document: a tag, cricket_asia.

That is the moment when you have to decide what you are reporting on — the match, or the information about the match. That week there was no match in either column. There was a pipeline, and it was broken.

The scorecard that came back blank

A blank scorecard is an impossible object in cricket. Every ball is recorded — runs, bowler, fielder, annotation. That is the sport's oldest inheritance: the first game to keep accounts of every major fixture since 1877. So when a document turns up with no match, no player, no format, the first question is not "what happened." The first question is where the accounting machine stopped.

The report's internal inconsistency was its own best clue. A document whose type could not be identified and whose source could not be traced, yet which had been assigned the domain tag "Asian cricket" — that is not a content failure. It is an extraction failure. The metadata survived; the payload died. That sentence is the summary of everything I have written about Asian cricket coverage in the last few years.

Where the data lives, and where it doesn't

One honest thing first. The map of the data I work with is not the map of cricket. It is the map of broadcast contracts.

Where there is a camera and a per-ball commentary bill, there is data — the IPL, India's televised bilateral series, ICC events. Where there is only a score, there is only a score. The 2026 Asia Cup is the clean illustration: under the hybrid model, four matches were played in Pakistan and nine in Sri Lanka, and the final on 17 September 2026 in Colombo saw Mohammed Siraj take 6/21 as Sri Lanka were bowled out for 50 and India won by ten wickets. That result is recorded everywhere. But the eighth-over field placement in that final, or a powerplay-by-powerplay wicket-probability curve for any match in the tournament, does not exist publicly at the depth at which a single IPL league match exists.

The boundary of coverage is not a cricket boundary. It is a commercial boundary. Which is why a tag — cricket_asia — is both the most surviving piece of information we have and the least trustworthy. A tag tells you which box the document was filed in. It does not tell you what was in the box. I have to write that limit at the top of every piece, because where the data structure is richest, its absence also hides most easily. Ranji knockout cricket and WPL depth sit in exactly that ditch, and every season I try to build at least one angle out of them — because presenting the unmeasured as measured is the oldest sin in this trade.

What I counted existed

In 2026, when I built the Pressure Index for IPL death overs, I had data. Dot-ball percentage, boundary-conceded rate, wicket-economy across overs 17 to 20. Jasprit Bumrah's index came out best — economy 6.2, dot-ball 45 percent. But my first model was inverted. I built the Pressure Index backwards, and the failure is why it holds. When the data exists and the answer still comes out wrong, you learn how much room the model has. When the data does not exist, there is no way left to find the error.

In 2026, working with Star Sports, I tested the same frame on the Russia World Cup. Germany went out in the group stage with 72 percent possession and only 1.2 xG per game. I called it false dominance and wrote that it was exactly like a cricket side making 180 and losing by twenty because of a slow middle. But I had also written, first, that the cross-sport translation is inexact: football is continuous, cricket is discrete; in football both teams can attack at once, in cricket bowler and batter stand opposed; and football's scoring density over 90 minutes does not exist in cricket's 120 balls. The lower the event count, the more dangerous the data gap becomes.

In 2026, when CSK furloughed me, the stadium went quiet for eleven weeks and I started counting. I built a Player Valuation Engine on IPL data from 2026 to 2026 and found that all-rounders who bowl in the powerplay and bat above a 140 strike rate in the middle overs are systematically underpriced. The recommendation was Moeen Ali. CSK bought him for 70 lakh; he made 357 runs at a strike rate of 138 and took six wickets, and the 2026 title followed. At the 2026 mega auction my model got eight of the top ten buys right, including Ishan Kishan's 15.25 crore move to Mumbai Indians.

All four share one thing, and it is not that I was right. It is that all four ran on a clean, bounded, ball-by-ball dataset. The document in front of me today has no such dataset. So the most honest output available is not a forecast and not a verdict on what happened. It is a null report with a recovery instruction attached.

Narrative fills the empty cell

Here is the inverted point, and it is the actual argument of this piece.

A null result is worth more than a thin result, because a thin result gets published. Had that report come back with sixty of a hundred cells filled, nobody would have sent it back. Someone would have written a confident paragraph off those sixty cells, it would have run, and the forty empty ones would never have been seen by anyone. With one cell out of a hundred filled, the only option is to write the truth. That is the most useful thing I have learned in this job, and it runs straight into a habit I repeat constantly — the eye test is data too, it has simply never been written down. True. But an unwritten eye test, once it starts getting written down, usually turns into an eye bias.

The second thing, repeated most often and checked least: where there is no data, narrative fills the vacuum. "Momentum shifted" is the sentence you speak when you do not have the denominator. And in Asian cricket that sentence is spoken more than anywhere else, because that is where the data is thinnest — ACC competitions, associate nations, women's domestic cricket, Ranji knockouts. The India-Pakistan bilateral door has been shut since December 2026; when the match is not being played, no metric of that match is being built. What sits most in the conversation is measured least.

The third thing I have to remind myself of repeatedly. A tag is not evidence. cricket_asia is a retrieval hint, not analytical ground. Inferring from it that the article concerned the Asia Cup, or an India-Pakistan hosting dispute, or WPL broadcast rights — all three are possible, all three could be correct, and none of them is analysis until the source text comes back. This is the same mistake I catch in others: importing a scale and calling it translation. Before bringing football's xG into cricket I published four structural disclaimers. How many disclaimers does it take to convert a domain tag into a finding? All of them.

So the correct professional output of that report is not ten estimates with a "low confidence" label stuck to them. It is a statement of which questions cannot be asked of that document at all. With the format undetermined, weighing a Test economy rate against a T20 economy rate on the same scale is the most common error in the field — and it happens not from ignorance but from haste.

What gets counted next time

In February 2026 I wrote three figures into my desk log before publication, so that later there would be no excuse. One: of all ACC-governed fixtures this year, how many will have ball-by-ball data in the public domain — I will declare that number in December, as a count, not an estimate. Two: for every match of the third WPL season, how many phase-wise splits are available, and how many of those I built myself. Three: in how many Ranji knockout matches I extracted one original finding from ball-by-ball data rather than restating the scorecard.

What I cannot measure, I will not call measured — that should be the whole rule of this trade. And still the question stays open: a sport that spent a century and a half writing down every ball — why can it not keep accounts of every match on its most populated continent? Until that has an answer, what we call cricket analysis is really the analysis of the matches somebody's camera happened to watch.