When the Scoreboard Returns N/A: The Part of Cricket Coverage Nobody Audits

Eleven-twenty at night. In a Bengaluru digital newsroom a file lies open on a screen and it has thirteen lines. Beside every line hang the same three characters — N/A. Title N/A. Source N/A. Article type: unclassified. The list of information points is empty. In seventeen years I have heard several kinds of emptiness in a commentary box — a ground after rain, the three-second delay when ball met pad and the speakers pushed out canned applause, and the silence that settles across forty lakh living rooms at once. This is none of those. There is no sound here because there is no ground.

The half of sports journalism a reader sees is the smaller half. The other half sits between the field and the page — the scorer's terminal, the broadcaster's data pipe, the agency feed, and now the automated systems that pull facts out of a link. Between September and November 2026, sixty IPL matches were played in Abu Dhabi, Dubai and Sharjah with nobody in the stands. That season taught us, for the first time, that feed and ground can speak differently. The speakers were applauding, I was silent on mic, and the score on screen was correct. The lesson went past the scoreline: a story exists where the score and the ground agree with each other.

This case is the same equation inverted. When an article reaches an analysis desk it passes through two stages. The first breaks it open — information points, claims, source, author stance, time sensitivity. The second does the cricket work on those points: format, player, team, rankings, league, governance, public expectation. Everything in the second stage stands on the first stage's floor. The file I am writing beside came back from stage one structurally complete and substantively empty. No title, no source, no information points.

N/A and zero are different things. Zero carries context in cricket. A maiden over is an achievement; a batsman's duck is a fact you can argue about, rewind, trace back to a ball. Nothing sits behind N/A. It is the absence of information, not a value of it. The framework that handled this file did what a good scorer does — it left the blank blank. In eight analytical dimensions it wrote, plainly, that nothing could be assessed. That is not a small thing. The easy move was to read the cricket_asia label and guess: an Asia Cup piece, an auction piece, an India–Pakistan piece. One guess might even have landed — and if it had, nobody would ever have seen it as a guess. It would have gone out as analysis.

A blank title and a firing domain label are two different pieces of news. The label firing means the machine started. The title failing means it never finished. Something broke in the fetch. Four causes account for most of it: a paywall or a JavaScript-rendered page, an image- or video-only source, an encoding failure in a non-Latin script, a truncated payload. All four share one property: the fault is in the pipe, not in the article. And pipe faults are never one-off. Same domain, same crawler, same error, next time too. One more signal belongs in the log — the label reads cricket_asia where the parent taxonomy says Cricket. Two schemas colliding will misroute every filter and benchmark downstream.

A risk that was not rated is not a low risk; it is an unknown one. Cricket people have understood this for decades — silence about an injury is not proof of fitness. Media people forget it inside the pipeline. An empty cell is not a safe cell. It is a cell nobody has filled yet, and anyone can fill.

Compare it with a night when everything was full. 24 October 2026, Dubai: India 151/7, Pakistan 152/0 in 17.5 overs, Shaheen Afridi 3/31, Babar Azam 68 not out. Every number existed that night and none of it was enough. What was enough was forty seconds of nothing across forty million living rooms, and reading that took a human ear. The file in front of me does not even have the number you could carry to an ear.

For three years the argument in cricket media has centred on whether a machine can write the story. I want the reverse question. The real question is what happened to the story the machine could not read. The industry audits the player, never the pipe. We have a review system to decide whether a ball pitched outside leg; there is no review for a feed that came back empty. And the danger is not where people look for it. The danger is not that a machine writes the cricket report. The danger is that a machine fills the blank, and the sentence then reads like sourced analysis. This is not a cricket crisis; it is a cricket-journalism crisis, and it happens in the exact moment when someone fills instead of reads.

In 2026 I learned something that applies directly here: a broadcast is never one person's work. The scorer, the cameraman, the sound engineer — the names that never reach the credits are the ones deciding whether what you hear is true. A cricket report in 2026 is not written alone either. A crawler writes it, a parser writes it, and a sub-editor writes it by letting N/A stay N/A. That sub-editor gets no byline, because the work is invisible. All it does is stop the wrong story from printing.

How many of the cricket stories you read today were written from a file that came back empty and was quietly filled in? No scoreboard will answer that. The answer lives in a habit we learned in 2026 and then forgot — the habit of hearing the score and the ground separately. Next time a number looks very clean, pause and ask whether it came from the field, or from a blank cell somebody filled.