When Every Field in a Cricket Report Reads N/A: The Costly Habit of Reading Empty Data as 'No Risk'

It was eleven at night and a two-page report sat open on my laptop. N/A where the title should be, N/A for the source, 'Unclassified' for the article type. Below it, six risk categories — sporting, personnel, commercial, rules and integrity, public opinion, systemic — each followed by the same three letters. I moved the cursor to 'publish' twice and pulled back, because for two decades my habit has been: if the document arrives empty, send it back before you write. This time the question was not what the report said. The question was how an empty report had travelled the whole length of the system to my desk and nobody stopped it on the way.

Cricket coverage is now a two-storey building. On the ground floor sits extraction, which breaks an article into information points, entities, time-sensitivity and source quality. On the first floor sits analysis, which reads those points through format, player, team, auction, governance and public-narrative lenses. The paper in front of me had an entirely empty ground floor — no title, no publication date, not one information point, not one name. The only populated field was the domain label: 'cricket_world'. That label does not even exist in the taxonomy we work to, where the value is simply 'Cricket'. The one thing that should have been most reliable, the classification, was itself filed under the wrong name.

My habit of reading the clause first dates from a time when you had to walk through the document before touching the drama. In February 2026, thirty-two years old in that Mumbai auction room, one of fewer than ten women among roughly two hundred accredited media, I started logging every sold lot against its base price. Deccan Chargers paid US$1.35 million for Andrew Symonds, the highest bid of the evening. When I added up the sheet, Hyderabad had paid roughly thirty-eight per cent above the median for overseas all-rounders. The editor ran it as a graphic, not a story. That was the first time I understood that the story is not where the paddle goes up; it is in the ledger somebody stubborn is balancing at night.

That ledger had one condition — the numbers had to be real. The report in front of me had no numbers, because nothing had come out of the extraction floor. The people who run these systems call it a null payload. The envelope arrived from the ground floor, sealed and stamped, and nothing fell out of it. The problem is not that the envelope was empty. The problem is that the first floor read the empty envelope and produced a full report in which nearly every field says 'insufficient information' and no field says the article never arrived.

This is the real failure: in cricket analysis, N/A means unknown, not no risk. When six of six risk categories come back blank, the reader's brain files it as 'all clear', when the truth is 'we have no idea'. That gap looks small until you are standing in a newsroom. A sports desk receives dozens of items a day with not one hard fact in them, and the deadline demands they all get a slot. A system that stops and writes 'we don't know' is honest. A system that writes 'no notable risk' and moves on is lying — even if it printed not a single wrong number.

I treat the missing format marker as the most serious gap, because cricket's entire statistical architecture rests on it. Test, ODI, T20 and The Hundred averages cannot be swapped for one another. A batting average of 45 in first-class cricket describes career depth; in a T20 league it describes uncertainty in the batting order. Duckworth-Lewis-Stern is not just rain arithmetic either — it decides which team caught the weather's break, and applying DLS without knowing the format is meaningless. The World Test Championship table carries weight only in Tests, bilateral results feed rankings, and a league fixture measures nothing but franchise strength. Dropping all three worlds into one table is like adding league goals and cup goals into a single football account.

Entity extraction has another failure mode that few on the desk recognise. When not one player, team or board name comes out of an article, two different diseases look identical. The first: the article never had names — it was a caption, a scorecard stub, a half-loaded page behind a paywall. The second: the article had names and the parser dropped them. The remedies differ — drop the item from the analytical queue in the first case, treat the whole batch as suspect and re-run in the second. I have seen newsrooms more than once assume the second disease was the first, because 'there wasn't much in it' is the easiest excuse available.

In May 2026, when S. Sreesanth, Ankeet Chavan and Ajit Chandila were arrested, I was the only woman on the Mumbai briefing calls. In the first weeks everyone chased the crime story and I deliberately left that race. I began reading what nobody was reading — which clause voids a fee, who owed what to which franchise, in which paragraph the contract defines 'misconduct'. With eleven reporters across four cities I built a shared pool of documents on one condition: nobody would trade a source for a scoop. Two years later the Lodha Committee banned Gurunath Meiyappan and Raj Kundra and suspended Chennai Super Kings and Rajasthan Royals for the 2026 and 2026 seasons. What survived that whole affair was not the shouting on television; it was the paper.

I am writing this because the greatest danger of a null payload is not technical but ethical. When a field says 'value unavailable', a skilled writer's instinct is to fill it. Sliding a 14.5 crore figure into an auction story without a source, or describing a player's 'recent form' without a date window, is false precision — and it is the oldest disease in sports journalism, far older than AI. I still keep the 2026 sheet, so I can say with some authority that an auction price and cricketing strength are different things. A system that fuses the two into one sentence does far more damage than an empty payload, because its lie sounds like the truth.

The governance check failed for the same reason. There was no integrity signal at all — no tribunal finding, no abnormal market movement, no approach report. Here one discipline needs recording, which I learned in the 2026 era while watching the Cronje affair from the South African side. Institutional failure and criminal conduct are separate categories. Opacity, conflicts of interest and incompetence deserve coverage, but inflating them into corruption kills the journalism that has to stay credible in every other case. So when the document contains nothing, the right answer is to write nothing — neither defence nor accusation.

One more detail in the report stung most. The risk matrix carried N/A against six categories, and a seventh row had been added: 'Pipeline risk: high'. The only concrete finding of the entire exercise was that the exercise had no fuel. I liked the honesty, because most systems quietly move on at that point. Any analytical chain needs a door that shuts when it sees an empty envelope — no title, stop; zero information points, stop; no format marker, stop. Engineers call it a null-gate; newsrooms call it an editor. Both do the same job: keep unfinished material out of print.

Now the objection my position will attract first. It will be said that this is a software fault, that it will be fixed, and that turning it into a cricket story is an overreaction. I accept part of that. A fetch failure is an engineering problem with an engineering solution, not a cricket one. But I would push past it to an inverted conclusion: the report that said 'unknown' in every field was more truthful than the healthy-looking report that begins every week with 'sources close to the franchise say'. The broken system at least told us it had nothing. A system that looks full and is empty inside deceives the reader — and nobody installs a null-gate on it, because its face is perfectly fine. My worry is less about this empty report than about the full one nobody is stopping.

So next time a piece of cricket analysis lands in front of you, don't ask first what it found. Ask what never arrived. Was there a title, a date, a format marker, at least five information points, and one name — team, player, board, league — that you could pick up a phone and check? The day all five answers are yes, averages, strike rates and auction prices become worth arguing about. Before that they are decoration.

The file does not shout; it waits — the sheets in my desk drawer have been saying so for twenty-five years. The real question is not how much cricket data we have. It is: on the day the data isn't there, will our system print a blank page or a beautiful lie? And if the answer is a beautiful lie, who will vouch for the next story you read?