Empty File, Full Template: The Cricket Report That Had Not a Single Fact Filed

A report in eight parts landed on the desk. Every section had its frame — format, match nature, player age curve, team batting depth, broadcast-rights value, DRS precedent, DLS calculation, public expectation gap. The tables were drawn, the rows numbered, the columns dressed. And in every cell sat the same sentence: N/A – insufficient information.

In fifty years I have not seen a document like it. A match report can be incomplete, a scorecard can be smudged, a page can fall out of a referee's file. But a report that is present on every page and empty on every page is not a document of journalism. It is an accident report from a pipeline.

The file contained no player, no team, no venue, no score, no date. Where a name should have stood, an instruction had printed itself: "identify from the information points above." And above there were no information points. It is as if an umpire stood in the middle with a card in his pocket carrying nothing at all, and the scorebook recorded only that the scorer was absent.

Context: two layers, and the first one collapsing

Every cricket decision is built in two layers. The first gathers fact — who is playing, in which format, at which ground, in which innings, at which over. The second reads those facts, which is to say it interprets. A match referee's report is the first layer; a disciplinary hearing is the second. If the first layer arrives empty, the hearing is adjourned. It is not called a clean chit.

That is what happened here. The first layer — called the deconstruction stage in the report's own language — returned a title of N/A, a source of N/A, a type of "Unclassified", and zero information points. The second layer had one road open: either invent names and numbers to fill the blanks, or state plainly that nothing was there. The report took the second road. The technical term is fail-closed — refusal to open.

In cricket analysis that refusal is not courtesy, it is necessity. The reason is simple: format is the door without which no number is comparable to any other number. A Test average, an ODI strike rate and a T20 economy rate are three different languages. An analyst who weighs all three on one scale is not analysing; he is mistranslating. If the file cannot say whether this was a Test or The Hundred, then anything said on the strength of that file is a translation error.

The blockage does not stop at format. Without a venue, home advantage cannot be measured — and cricket's largest structural variable is not how strong a team is but whose soil it is standing on. Without weather and dew, the DLS calculation is unfinished. Without the toss, luck cannot be separated from performance. None of these entries existed in the file.

The core: four fingerprints of emptiness

The first fingerprint is the template itself. Where the machine should have entered a value, an instruction sentence got printed instead. "Identify from the information points above" and "judge from the source fields" are not values; they are the markings left on cards nobody filled. The distinction matters: retrieval did not fail, extraction did. The article presumably arrived, the external data presumably arrived, but the part that walks inside and seizes names and figures quietly shut down.

The second fingerprint is the word "Unclassified". A match report, an auction story, a governance item, a profile — each demands a different analytical frame. Unclassified means the pipeline never even decided which beat this story belonged to. When the first stair was never climbed, talking about the tenth is dishonesty.

The third fingerprint is the most instructive, and it hides inside the risk matrix. In several places the report writes "N/A", and nowhere does it write "low risk". Unknown and low-risk are not the same thing, and collapsing the two into one cell is the most common habit of automated research. If injury status is unavailable, you cannot say the player is fit. If no disciplinary matter surfaced, you cannot say the record is clean. "Integrity status unknown" and "integrity status clear" — an entire journalism sits in the distance between those two sentences.

The fourth fingerprint belongs to the industry rather than the sport, and it concerns reading behaviour. Selectors, broadcasters, the buyer at the auction table, the fantasy player — how many of them read an eight-part report in full? Very few. Most read the closing comprehensive assessment. If that section travels without the warning banner above it, a document containing zero information circulates as "analysis". It is the man who tears out the last page of the scorebook and claims to have the match's essence.

One thing the report does record honestly, and that is that the largest risk here is not a cricketing risk but an information-integrity risk: hollow analysis being consumed as substantive analysis. That risk is not theoretical. The condition already exists. And the impact is large precisely because selection, valuation and contract decisions in cricket rest on paper of this kind.

The contrarian angle: the fabrication pressure sits on the desk, not the machine

The easiest reaction to all this is that the machine let us down, that the AI did nothing. My card index testifies the other way.

What this file did is what an honest umpire does when he sees the ball skim the grass and cannot be certain the fingers had closed — he gives it not out, because what was not seen cannot be given out. That is not courage. That is discipline. The real danger lies elsewhere: the pressure to fill a blank falls far more on the desk than on the machine. A sub-editor with a deadline in front of him puts "according to sources" and "it is learnt" into the empty cell. The machine refused. The human frequently does not.

Sydney taught the same lesson. The 2026 World Cup semi-final, rain, and a target of 22 from 13 balls becoming 22 from one inside ten minutes. Forty thousand people were making noise that evening and nobody was asking what the rule said. I rebuilt that calculation on three scorecards with a pocket calculator because the certainty rolling across the screen did not satisfy me. In Sydney the rain rule was rebuilt on three scorecards — and the paper buried the piece on page nineteen. Filing at two in the morning was not wasted; it was the day the Clause Index became a real thing.

And in 2026, on day two of that Ranji final at the M. Chinnaswamy Stadium, I was watching the umpire rather than the batsman. A catch dying at short leg, given not out, and no one in the press box could name the clause. I went home, read the 2026 Code end to end, found the wording useless, and wrote 900 words. The desk ran 200. The card index began there — one card per clause, filed by situation rather than number, a system that made sense to me and to no editor.

The card index begins at short leg, and the rulebook follows. There is now a blank card in that index, set apart from the rest. The card is small; the precedent it holds is not.

Takeaway

Whatever report is placed before you, ask about format first, date second, source third. If any one of the three reads N/A, the rest is worth as much as a scorebook without a spine. And the empty file that started this argument should not be thrown away. It has become the gauge. The day that pipeline runs again and fills in one player's name, we will learn whether the machine had stopped inventing — or had simply forgotten how to read.