The Record Said N/A. The Match Was Still On.

11:40 pm. On the third floor of a Delhi newsroom the content system was open, and one row had eleven of its fourteen fields blank. Title: N/A. Source: N/A. Article type: unclassified. One-sentence summary: empty. Information points: an empty list. The system had taken a cricket match and returned a perfect zero, without a single error message, without a single warning.

That screen took me back to an October 2026 afternoon at the Feroz Shah Kotla, sent to cover a Ranji Trophy group game. Fourteen reporters in the box; I was the only woman, and two of them asked whether I was from the 'feature desk.' On the third afternoon I counted 137 spectators. The groundstaff, the jaggery-seller outside Gate 4, the crack of a bat handle no camera captures — I filed 900 words on all of it. My editor cut it to 320 and said the score was the story. He was half right. The press box has a pulse, and I learned to type to it.

Since that evening I have kept a two-column notebook: scorecard on the left, sensory detail on the right. The rule was hard — one image per hundred words, never more. The poetry had to be load-bearing enough to survive a desk edit. Sixteen years on, that notebook has quietly become the industry's data model. The left column grew; the right column shrank.

An IPL season has 74 matches. Each one gets a live blog, a ball-by-ball feed, a post-match press conference, three camera angles and a dressing-room corridor. A Ranji season has more than a hundred matches. Most of them get one agency copy, if that. That asymmetry is the real origin of the blank row — the problem was never that the data was wrong. The problem was that the data never entered, and nothing in the system mourned it.

8 March 2026. 86,174 people at the Melbourne Cricket Ground, Australia beating India by 85 runs, Alyssa Healy making 75, and I wrote that evening about noise as architecture. Two weeks later the airports shut. On 10 November 2026 the IPL final was played in Dubai — Mumbai Indians against Delhi Capitals, empty stands. I watched from a Delhi bedroom: stump mic, a fielder's shout, no roar at all. I recorded ninety seconds of ambient audio. The loudest thing on the file was a fielder talking. I report from the edge of the roar, where the story learns to breathe — and that night absence could be filed as precisely as presence.

But the row that came back empty had nothing to do with a pandemic. It was an ordinary domestic fixture, and its emptiness did not mean nothing had happened.

An empty record and 'no news' look identical, and that is their most dangerous property. A downstream system reading that row will log 'no risk found.' The truth is 'no data found.' The distance between those two sentences is the whole of professional ethics, and our software has erased it.

Second, the failure travels. If one file in a batch returns empty, the next three probably did too — same parser, same paywall, same JavaScript-rendered page. Systemic failure does not make noise; it harmonises. Several records go blank at once and the dashboard stays green.

Third, and most embarrassing for my trade: an empty record creates pressure toward fiction. A three-line template can be filled with an invented innings that reads perfectly plausible and costs nobody anything. A 900-word feature cannot, because one wrong name will collide in four places. Short formats demand structure in place of fact — and that is exactly where cricket coverage drifts toward invention.

Do the arithmetic. On the night that row went blank, the same system held a full franchise season — ball by ball, batter by batter, down to Impact Player usage. All 74 IPL matches are logged over by over. Nobody has counted how many of the hundred-plus Ranji matches are. The World Cup I covered was a map of who was missing.

The reflex when cricket writing feels flat is to blame artificial intelligence. My reporting says the blame is misdirected. What zeroed that match was not a clever machine; it was a boring, technical, entirely lifeless thing — a parser, a redirect, a page with no body text. We prefer reporting 'no issues found' over 'no data found,' because the first reads like a completed job and the second admits incompetence.

That habit stains the coverage map. A match whose record returns blank is never seen by a scout next season, because the scout scrapes the same database in which the match was never entered. The selection debate then cites the names with dense numbers rather than the names with extant numbers. India's hardest opponent is its own depth chart — but the rung of the ladder where the file returns blank is invisible to everyone.

From that empty Dubai night I carried out one habit: ninety seconds of sound at every venue. It taught me that absence is recorded with the same labour as presence. The fix that matters in that content system is not an algorithm. It is a rule: every blank field must shout. Any file whose title reads N/A should be blocked from every scoring, ranking and alert pipeline until someone writes on it that this is not a clean negative but a failed extraction.

I write for the ones outside the gate, listening for the roar. That night the match was on and the system said nothing was there. Next time a record returns empty, the question should not be what it contains — it should be who returned it empty, and who they told.