Where the News Was, There Were Only Blanks

At two in the morning in Delhi, a file opened. Eight headings, all of them in place, in order, in bold. Under every heading the same sentence — “insufficient information”. No team, no player, no format, no venue, no score, no date. The most complete-looking cricket report of the year, and inside it nothing at all.

Nine years ago, on an evening at Lord’s, the same lesson reached me from the opposite direction. The scoreboard said nine runs; the story was hiding not in the margin but in the twenty-seven balls in which India slid from 191/3. England 228/7, India 219 all out, Anya Shrubsole 6/46, Punam Raut’s 86 — those figures sit in my recorder, and I opened them across three thousand words in that feature. Since then my habit is fixed: I go looking for the margin and find a dressing room instead. This time the margin was zero, and the dressing room stood empty.

Cricket reporting now passes through a pipeline before it passes through a pen. Facts are pulled from a source, tagged, dropped into a dashboard, turned into alerts, and only then does an editor decide what gets space. The auction-night purse, the net-run-rate graphic, the DRS overlay, the injury update — all of it stands on that layer. Beneath the commentary box there is now a second room, where scripts run instead of microphones. What happened in that room this week is a technical event, but its consequences land on cricket journalism.

The file asked eight questions. What was the format? Who was the player? How deep was the squad? Which way was the league’s money flowing? What was moving in governance? Where was the risk? What did the market expect? And by what route would this story travel through the industry? Against all eight, the same answer — “insufficient information”. Eight boxes, eight empty.

The point is that the file did not arrive broken. It arrived complete. All eight sections present, the risk list present, the star-rated table present — and everywhere “not applicable”. In technical language this is a schema-valid empty payload: the structure correct, the content zero. The most dangerous failure is not the one you can see; it is the one that passes every check and is hollow inside. An unfinished report warns the reader. A finished-looking empty one reassures him.

One thing survived in that file — the category. The language label said cricket; everything else had died. That gap says a great deal. It means the classifier ran and the extraction did not. The source document existed; the machine that reads it stopped silently. Such faults are not one-off — they repeat on the same source. And if this ran inside a batch, the stories beside it may be hollow in exactly the same way, with nobody the wiser.

The second loss is more expensive than the prose: provenance. Publisher, link, byline, timestamp — all “not applicable”. Text can be re-fetched; identity may not be. Without a date no story remains time-sensitive, and without a publisher no claim stands on any scale of credibility. A story with no address is not a story, it is rumour — however clean its structure.

There was one small thing that is actually large: the label. The file recorded the category as “cricket_world” while the system expects “Cricket”. It reads like pedantry. But in the world of routing, that single character decides whether a story reaches its desk or reaches no desk at all. Cricket content can slip quietly out of the cricket queue and nobody notices — because the error is not in the story, it is in the naming.

Now the part that is the real lesson for me. What that report did was this: it wrote not one sentence about any player, any team, any league. It did not borrow a figure from memory. This is not a small thing. In a world where everyone carries every batsman’s strike rate on the tongue, writing “I do not know” is the hardest work available. And the most valuable.

To see why, look at the grip format has on the argument. In cricket, format is not decorative information; it is the door to analysis. Without settling format you cannot say whether a strike rate of 140 is good; in T20 it is adequate, in Test cricket it belongs to another sport. An economy of eight is acceptable in a T20 death over and ruinous in a first-innings Test spell. So until format is settled, the phrase “good performance” carries no meaning at all. That report treated format as the first door, found it shut, and said nothing further.

The order of recovery follows the same logic, and the order is the useful part. First entities — which team, which player. Then format — Test, ODI, T20. Then figures. And only last, narrative. Narrative sits at the top, but it rests on three bricks laid beneath it; pull the bricks out and the story becomes an elegant guess. Auction coverage gets this wrong more than anywhere else — the price arrives first, the player second, and the plan never arrives.

Now the counter-question. For several years we have all been frightened by one thing: invented statistics. A flood of false numbers off the machines. That fear is justified, but it is half a fear. The real risk does not come from the story that lies — that one gets caught. It comes from the story that says nothing and is published anyway, because its structure was complete. The reader reads it, assumes analysis occurred, and moves on. False numbers start arguments; empty structures produce silence. And nobody fact-checks silence.

I understood this in 2026, when the IPL was played in Abu Dhabi, Dubai and Sharjah — sixty matches, fifty-seven days, empty stands. In that film I set the noise of a 2026 Wankhede against a 2026 stump mic, and held seventeen seconds of silence after a wicket. The loudest thing in the empty stadium was what used to be there. The same happened with that file. There was no cricket in it, but the shape of cricket’s absence was plainly visible.

So I do not call that report a failure. It is a negative test case, and a good one — it showed which parts of the pipeline die quietly and which survive. The crowd does not cheer in data; it cheers in memory. Machines do not remember, they only fill boxes. The day a box looks full and holds nothing, the question belongs not to the reader but to the editor.

The question ahead is this, and it is squarely a cricket question: who audits the layer beneath the commentary box? The next time a win-probability bar shifts on screen, or an auction-night bid flashes beside a player’s name, pause and ask — who fed this number? If the answer is “a pipeline”, the next question is whether that pipeline last read a whole story or merely picked up its frame. The loudest thing in an empty stadium is what used to be there — and the loudest thing in an empty report is what we never heard, because it was never written.