When the Headline Reads N/A: The Silence Inside Cricket's Information Chain

One column in the audit sheet was not blank. It said N/A. Blank and N/A are different things. Blank means nobody filled it in. N/A means the machine asked, got nothing back, and recorded the nothing. Title: N/A. Source: N/A. Article type: unclassified. Information points: an empty list. Author's stance: N/A.

In twenty-nine years I have seen a great many incomplete scorecards. At the Sector 16 ground in Chandigarh, after rain, the scorer's book for the day carried a date, a wind direction and the words "no result". That blankness was honest. It recorded the absence of a match, not the absence of a reporter. This blankness is different. The match existed. The hand meant to lift it went cold, and nobody made a sound.

In 2026, writing a six-part series on the 2026 T20 World Cup win, I set myself a rule — keep the camera low so the boys look tall. The reverse holds too. When there is no camera at all, nobody looks tall and nobody looks small. Everyone disappears at the same size.

Cricket news in India does not travel in a straight line. It comes down a staircase. From the scorer's book to the state association office, from there to the BCCI match centre, from there to a wire-agency stringer, from there to a website sub-editor, and finally to the screen in your hand. Every step has a door, and every door has one man standing at it who also has two other matches that day and one more phone call.

The detail that stung in that sheet was not the empty list of information points. It was the N/A in the title field. Title and source are boxes filled mechanically, before any language model reaches the page. Page opens, headline lifts, source logged. When both come back empty, the conclusion is plain: the page never opened. The failure was in delivery, not in understanding.

In cricket's language: a scorecard with the wrong toss time printed on it can be corrected. A scorecard with no venue, no innings and no overs is not a wrong scorecard. It is a scorecard that never arrived.

And here the domestic structure enters. IPL scorecards never return N/A, because there are twelve broadcast trucks, four data operators and a dedicated feed. A Ranji scorecard runs off one stringer's phone, and that morning his notebook is already wet. The day his phone dies, you have no news of the match — and you will not be told that there is no news.

The audit listed three candidate causes and graded confidence on each. First, a retrieval-layer failure: the article's raw text never reached the machine. Confidence: high. Second, a domain-routing mismatch — the label carried cricket_asia while the required label was Cricket. Confidence: medium. Third, the source was never prose at all: a photo caption, a live-score widget, a video page. Confidence: low.

Why is the first cause held at high confidence? Because the shape of the emptiness shows the failure was in transport, not in thought. A model that fails to understand usually misreads — it writes a headline, it calls the piece a match report by mistake. When it goes quiet and puts N/A in every box, it means there was nothing to read.

The second cause is the more dangerous one for cricket, because it happens in silence. A regional label such as cricket_asia passed downstream without being mapped to the canonical Cricket domain means the extractor underneath never starts. The router fires, the engine does not turn, and from the outside everything looks fine. That label touches precisely the territory where the domestic game lives. The cricket that already had the least airtime now has one more loose joint in the pipe that carries its news.

The third cause is the least likely, but it cannot be dismissed. If the source was never prose, then this is a boundary, not a failure — and logging it as a failure would corrupt your own quality metrics.

Now the part nobody looks at. When an empty payload reaches a writer, two roads open. The first is to say: I have nothing. The second — and this is the real hazard — is to fill the hole with memory.

Twenty-nine years of experience is a strange advantage here. I can write nine hundred words about any team that will read as though nobody should doubt a line of it. The bowler's economy rate will come out of memory, to two decimal places. The injury reference will read as if the physio told me himself. A selector's sentence will be composed that sounds exactly like a selector's sentence. And through all of it I will not have told a single direct lie — because I will have written "likely", "probably", "it is being said".

The audit did not say the information was thin. It said the information was zero, and it said that no cricket-specific claim should be issued on the back of it. It rated the risk high, and then made a necessary distinction: the risk is to the analytical process, not to the sport.

The damage is asymmetric. A missed report can be re-fetched in minutes. A fabricated economy rate travels through media, fantasy-league arguments and betting-adjacent channels, and pulling it back costs many times more. Filling a hole with a guess is the most expensive trade available. Stopping is the cheapest.

One thing here is specific to cricket — the shelf life of news. A match report is stale within forty-eight hours. An auction item runs for a few days. A governance or board-politics story stays alive for weeks and months. The cost of delay is not the same for every item.

And that is where the real question sits. You cannot price a delay until you know what it is that was delayed. In this record the article type was unclassified. Not a match report, not a preview, not a profile, not an auction item, not an opinion column. I cannot even say whether what I did not receive was a forty-eight-hour thing or a six-month thing.

The same applies to something people treat lightly: the label. cricket_asia is not an event. It is a geography. Geography does not make news. If all I know is that the story came from South Asia, I cannot establish whether it was a Test or a T20. And when the format is undetermined, you cannot even choose among the ICC's three separate rankings tables — Test, ODI and T20 run on different tables, and quoting any figure without a date is a mistake on its own.

The audit proposed a fix that is structural more than technical. Require entity output on the next extraction: teams, players, coaches, competitions, venues, dates. The reason is simple. If every payload must carry those boxes, then "empty but well-formed" can no longer be mistaken for "analysed". Emptiness needs a signature of its own, or it gets read as analysis.

It reminds me of that night in Kazan. 30 June 2026, France and Argentina, 4-3, and I had thirty-two people in front of me who had come from Malappuram and Kochi, who had sold gold and taken loans. I recorded nineteen hours of sound and cut a twenty-two-minute film with not one tactical graphic in it. The lesson from that film: a voice never recorded is simply not in the story. And an incomplete archive tells its biggest lie when it implies it is complete.

Cricket commits that error every week. A match nobody covered does not vanish from the calendar. It stays on the calendar with no record attached. And when someone adds up that era's numbers ten years later, they will have no way of knowing where the sum began.

Now the thing least likely to be said. Reading everything above, the easy conclusion is that this is a technology story — a scraper, a router, an empty payload, and an engineer who will fix it. That conclusion is convenient, because it blames nobody.

The truth is less comfortable. Cricket's information economy has always tolerated the blank, because the blank is cheap and the correction is expensive. The Ranji scorecard did not come? Nobody rings. The press box is a sponsor's box? Nobody writes it. The agency copy ran without a second call? Everyone forgets by morning.

The machine did not create this hole. It put the hole in a table, with a percentage, where everyone can see it. The blank used to be scattered — in someone's notebook, in someone's memory. Now it stands in a column and says N/A. And this is the first time we can count how much we do not know.

The audit rated its own overall risk high, with one essential qualifier: the risk belongs to the analytical process, not to the sport. Cricket was not harmed. The harm lands on the reader who is handed a piece that covers an empty space with borrowed authority. And that reader will not trust the same desk next time.

What to watch next, the audit has already written down, and the list is useful to any cricket desk. Count N/A headlines per batch — more than one means a system fault, not a single story. Log raw body length — under two hundred characters means the page never opened. Track the share of records with a captured publication timestamp. And three consecutive failures on the same record turns the question from the story to the source.

I am left with one question, and it comes from the same sheet that started all this. If we cannot say what format a story was, which team it concerned and what date it carried, then when we report that cricket generated this much news this week — what exactly are we counting?