N/A: The Most Dangerous Word in Cricket Reporting

Last week a document arrived on my screen. Eight sections — format and match, player technique, team landscape, league economics, rules and governance, risk matrix, public narrative, industry transmission. Every section had a table, every table had an assessment column, and every column carried the same entry: N/A – insufficient information. Title N/A. Source N/A. Article type: unclassified. Information points: empty. In the slot where a team name should have sat, the template's own instruction was printed — 'identify from the information points above' — and above there were no information points at all.

By the last page one thing had become clear. This was not an analysis of cricket. It was the post-mortem of the pipeline that produces cricket analysis. And the post-mortem, with some irony, applied to itself.

I went back to the tape expecting a verdict; I found a question.

Cricket's information economy has never been richer. Every ball is logged, every bowler's seam position is available frame by frame, every batter's scoring arc is sold as a heatmap, and the NRR arithmetic runs on broadcast in three decimal places. Against that pile, the industry's governing belief is simple: more data, more clarity. The template is that belief turned into discipline — no section skipped, no comparison made without a basis, every claim sitting above a column that can be checked.

The chain has four steps: retrieval, extraction, analysis, publication. The document in front of me had died at step two. Its corpse, however, was arranged so tidily that step three assumed it was alive. The rule says: where information is missing, invent nothing. The rule also says: fill all eight dimensions. Both were obeyed. The result was a document one hundred per cent compliant in form and zero per cent informative in content. That is the shape the modern cricket content machine produces whenever the story is absent — full skeleton, no flesh.

The most important line in that document was the one stating that 'unknown' and 'low risk' are different statements. This is the spine of reporting and it is broken most often. When a player's injury record cannot be found, the finished report says there is no serious injury. When a franchise's wage bill is not public, the report says there is no financial pressure. In both cases the truth is that we do not know. Mistaking absence for equilibrium is the oldest and most expensive error in cricket journalism.

I have three receipts of that error from my own work. June 2026, The Oval. Pakistan beat India by 180 runs — Fakhar Zaman's 114, and Mohammad Amir removing Rohit Sharma and Virat Kohli inside the first five overs. The first-hour verdict was ready: choke. That night, from a rented flat in Kothrud, I wrote a fourteen-tweet thread and went looking for a number nobody had in a column — how many balls India's top three had faced against left-arm seam across the whole tournament. The answer was roughly sixty, and the contingency plan was zero. That information was not recorded in any document; it was sitting in the document's empty slot. An empty slot is a finding in itself, provided someone has the nerve to call it one.

December 2026, Adelaide. India were bowled out for 36 — their lowest Test total — with Josh Hazlewood taking 5/8 and Pat Cummins 4/21. My editor wanted rage that night. I filed a calm 1,800-word piece about scheduling instead: a pink-ball Test, zero warm-up matches, and a batting order that had walked off a T20 tournament in three empty UAE venues eleven days earlier. Readers said I had gone soft. Five weeks later at the Gabba, an injury-ravaged India chased 328 on Rishabh Pant's 89* and took the series 2–1. The piece that looked useless that night read like prophecy five weeks on, because the fault it identified lay in a calendar, not in a batter.

The third receipt taught me that the empty slot is not only a cricket phenomenon; it exists in the attention market too. On 7 August 2026, Neeraj Chopra's 87.58m won India's first Olympic athletics gold in Tokyo, part of a seven-medal haul. Ten weeks later, on 24 October 2026 in Dubai, Pakistan beat India by ten wickets — Babar Azam 68, Mohammad Rizwan 79, India's first World Cup defeat to Pakistan. I pulled my own numbers. The Pakistan post carried roughly eleven times the reach of the Neeraj post. That was not a cricket result; it was cricket's attention monopoly producing a result.

All three receipts say the same thing. An empty space is never empty — either a number is hidden in it, or a decision. And when reporting leaves that slot marked N/A, it does not tell the reader that information was unavailable. It tells the reader that information was not required.

What looks like a collapse is often a system showing its seams. The risk matrix in that document carried one row heavier than all the others: information/meta risk — analysis produced on hollow input, level high, likelihood high, already realised. A system built to adjudicate player injuries, team batting depth and broadcast rights had printed the fastest diagnosis of its own failure on page one. That was not a breakdown; it was honesty, the scarcest commodity in the trade.

There is a second kind of gatekeeping here, and it does not live in software. Every major cricket report answers a quiet question first: which story got a beat? The Ranji Trophy is played every year, the Tests sell out, and still it disappears from the conversation with the same silence with which an unclassified article dies at Stage One. The WPL's broadcast promises after the 2026 home World Cup are recorded in auction paperwork, not in living rooms. Regional-language commentary is doing the democratising that grassroots programmes claim credit for. The Style File was never about style; it was about permission — who gets the frame, and who gets a place in the column that will read N/A tomorrow.

So my recommendation is not a technical patch. It is an editorial policy: fail closed. When the input is empty, the system returns no default conclusion. The report still goes out, but its first line names it as non-analytical, a pipeline failure, not to be cited as an assessment of any player, team, league or match. Readers deserve to know what is not known.

Here is where I have to argue against myself. Perhaps I am inflating a software bug into a story. Newsroom desks run on deadline pressure, and a template full of N/A is a working file, not a publishable piece. Perhaps the underlying article genuinely contained nothing — no match, no player, no claim — and the document is an accurate mirror of that emptiness. Perhaps my objection is aesthetic rather than principled.

I accept most of that. Writing N/A into an internal file is entirely legitimate. The problem begins with the file's travel. The moment that document leaves its origin and lands inside a summary, an index, a dashboard or an outlet, nobody reads the alert banner; they read the box marked comprehensive assessment. And if eight sections appear populated inside that box, the emptiness becomes invisible. That is my real objection, and it is larger than any single cricket story.

Accountability, stated plainly. Who made the call? The pipeline's designers, who built a rule that produces all eight dimensions as output even on empty input. What did they have available? An explicit recommendation — re-run Stage One, block publication. What does a competent version of that decision look like? An output that states the cause instead of dressing the template: extraction failed, zero information points, article returned for re-extraction. Not a document that hides the empty slot, but one that names it.

My prediction comes with its conditions printed beside it, so it can be checked rather than claimed. If, over the next quarter, cricket data desks begin declaring in their output headers which articles have returned from re-extraction, their analytical quality should show a measurable improvement — because every empty slot will get caught. If they do not, the story that never got a beat will stay uncatchable, and we will keep writing its post-mortem the way we wrote the first-night post-mortem of 36 all out.

The post-mortem starts where the hot take stops.