Zero Information Points: When a Cricket Data Report Came Back Empty

Bengaluru, 2026. A report sat open on my screen — Stage-2 Deep Analysis, Cricket Domain. Eight sections, all present. Under each heading, a table. Every row straight, every column counted, every confidence level tagged. And everywhere a number, a name, or an event should have been, the same phrase kept returning: N/A — insufficient information.

One thing in the entire document had survived. At the top, in the classification line, a single tag: cricket_asia. No article title. No source. No format. No author stance. No team, no player, no date. Zero information points. A warehouse with a label stuck to the door and nothing behind it.

In eleven years I have read many reports that were wrong. This was the first I read that simply was not — and its honesty stopped me harder than any sharp number ever has.

Start with what the document is. In the data desk I work from, analysis runs in two layers. The first — deconstruction — pulls “information points” out of a source article. An information point is one checkable unit of fact: a score, an over, a date, a name, a fee. The second layer — analysis — assembles those points across eight dimensions, under one hard rule: every conclusion must carry a line saying which information point produced it.

On this file, the first layer came back empty. Zero points. And when the first layer is empty, the second has nothing left to do except declare the emptiness. All eight dimensions — format and match, player technique, team landscape, league economics, rules and governance, risk, public narrative, industry transmission — were structurally complete and substantively vacant.

Three explanations existed. The source article was genuinely empty: a live-score stub, a photo caption, something with no news in it. Or the article existed and never reached the pipeline. Or it arrived, was read, and the field-mapping broke during extraction.

The third is the strongest, and the evidence sits inside the file. A tag survived — cricket_asia — while everything else died. A tag is applied by the classification layer, which runs after content has been read. If content had never arrived, the tag would not exist either. A living tag beside a dead title and a dead source is the signature of truncation. This is not a story about data. It is a story about the pipe that carries the data.

Which raises the question my work is built around. If a cleanly formatted, professionally structured report can stand on zero evidence, why do we trust cricket's own archive, which always looks full?

In 2026, building the first public xG ladder for Indian football, I had 1,842 shots from 90 ISL matches, hand-logged by freeze-framing broadcast replays. I built the ladder by hand, then let the numbers argue. It put Bengaluru FC top on a 14.2 xG differential while flagging them as eleven goals above expectation. I published the regression warning two days before the final. Chennaiyin won it 3–2. The lesson has travelled with me: the thing that looks most complete is usually the least audited.

In 2026, locked down in Bangalore, I cleaned eleven IPL seasons (2026–2026, roughly 1.1 million deliveries) and four ISL seasons, then used the Bundesliga's 81 behind-closed-doors matches to test home advantage. Home win rate fell from 43.2% to 33.3%. That 6,000-word piece was the first time I had a sample big enough to be wrong in public. A large sample does not make you right. It makes your errors legible.

So when a file arrived with eight named dimensions and zero facts, my first instinct was not to fill the space with a good story. My first instinct was that the emptiness is itself a record, and records get read, not overwritten.

The real danger is not that the report contains nothing. It is that it looks like it contains something. Eight sections, straight tables, confidence tags, a risk matrix — together they make an envelope that opens empty but persuades any manager that the work was done.

The report flagged this itself. It rated overall risk “High”, and said plainly that the risk is epistemic, not sporting. That is the honesty I rarely meet in cricket coverage, where the reflex runs the other way: when evidence thins, language thickens.

Which brings back an old rule of mine — what looks like a trend is often a missing column in disguise. Indian cricket's clearest example sits below the IPL.

The densest ball-by-ball record in the country sits at the top of the pyramid, because every IPL match has a camera and every camera has a logging system behind it. Go down a tier — Ranji Trophy, Vijay Hazare, Syed Mushtaq Ali — and the light drops. Some matches are fully logged, some exist only as scorecards, some only as news reports, and some as a single line: match drawn.

Incomplete data is not the scandal. Incomplete data is cricket's permanent condition. The scandal is how the incompleteness is presented. When someone quotes a Ranji average, I ask: across how many innings, on which grounds, and how often was he on television? Before I trust a table, I ask who assembled it and why.

India's bench-strength debate is not a selection argument. It is a data-collection problem wearing a selection argument's clothes. When a selector chooses between two players and one has forty logged domestic innings while the other has two televised ones, the decision is being made on visibility, not on capacity. Whoever the camera found becomes the player who was “seen”.

That is why I hold myself to a quota — for every IPL piece, one from the Ranji or the women's game, even when the record is half-dark, and I make the half-darkness the subject. Where a number is absent, the absence is the story.

The same disease shows up at the auction. The most-quoted number in Indian cricket is a price; the least audited number is the same price. Price is a claim, not a valuation. When I set value-per-crore against phase-split output — powerplay, middle, death — the same mismatch returns every cycle. Franchises repeat the error because they keep a record of what they paid and not of what they bought.

It shows up again in the matches that never finished. No-results, DLS-adjusted targets, net run rate, rain-ruined games: these become footnotes in the table when in fact they decide qualification. An abandoned match is not a scheduling inconvenience to me. It is evidence, and the paper trail is where the story sits.

And it shows up, most dimly of all, in governance. ACC hosting politics, revenue-share disputes, NOC and central-contract discipline — the public record is thin there, and thin records attract speculation fastest. The 2026 Cronje case, the 2026 spot-fixing case, the 2026 IPL case survive in memory because their paperwork survived. The cases whose paperwork did not are simply gone.

One thing needs saying plainly, because my whole method rests on it. A model is a story with its seams showing, and I map the seams. When there is no cloth at all, I do not pick up the scissors. I say: the cloth did not arrive.

That is what this file did. It recorded the absence, and it recorded the method of recording. It wrote: this is a null result, and it belongs back at the data pipeline, not patched by inference. That is the sentence I see least in cricket media today.

Consider the alternative. Pick a fast bowler. Assemble a workload argument. Attach an Asian tournament. Write three thousand words. It would read far better than the empty file. It would be entirely worthless, because the reader would believe it and I would never be able to check it again.

A filled-in empty report is more dangerous than an empty one, because an empty report stops you and a filled-in one sends you forward.

Now the part where I have to fight my own habit. Over the last few years, the counter-intuitive angle has become part of my name. When a clean story arrives, something in me starts planning the reversal. That habit is dangerous, because reversal can arrive before evidence does. This file stopped me. There was nothing to reverse. There was only: nothing here.

That is the most useful thing the document produced. A pipeline that returned zero did better work than a pipeline that quietly filled in a guess. It also bounded its own confidence — “low” almost everywhere, except for the single tag, which supports only so much: the subject was Asia-related cricket, plausibly an Asian national side, an ACC event, or an Asian-market league. Beyond that, nothing.

Years of watching domestic streams, where the camera sits on one angle and the commentary takes long breaks, taught me that a scorecard is always a map, never a record. The map shows what someone chose to log. The ball that lifted an inch short of the rope and was left alone is not on it. The dropped catch that became a wicket next over is not on it. The match rained off, leaving one point in the table, is not on it.

When someone tells me the numbers do not lie, I say: the numbers do not speak. The person who assembled them speaks.

One lesson covers the file and covers cricket too: looking complete and being complete are different conditions. The IPL scorecard looks complete because every ball had a camera. The Ranji scorecard also looks complete, and the question there is who watched the rest.

So here is what I will watch on the re-run. If the content returns and cricket_asia survives alongside it, the system is sound. If the tag flips to something else, the fault sat in classification, not extraction. And if the tag survives while the content comes back empty again, the source article was hollow all along. Three different stories, and I want all three.

I will take no decision on this file — not editorial, not commercial, nothing adjacent to a betting market. I will keep it the way an unfinished scorecard is kept: unerased, and with its blanks unfilled.

In cricket we usually ask who won. The next question may be better: who wrote that match down, who left it out, and who decided to fill the gap.