The Empty File: A Cricket Story With No Cricket In It

Eleven forty-four at night. A document is open on the laptop and the letters N/A appear in it fifteen times. N/A where the title should be. N/A for the source. Team, player, coach, venue, date — all N/A. The list of information points is empty. The cricket report I had been assigned to work on contained not a single cricket fact.

One word survived the entire file — cricket_asia. That is a domain label, not information. It says only that the story probably concerns Asian cricket: an Asia Cup, a bilateral series, or a league like the IPL, PSL, BPL or ILT20. It does not say what the format was, what the state of the innings was, who was playing, or when it was played. A label does not make a story. The attempt to make one from that single label is the actual subject here.

A cricket story now passes through three floors. On the first sits the stringer, paid by the word, who often does not know where the copy will land. On the second sits the extraction stage — software or a tired sub-editor pulling out 'information points': score, overs, economy rate, contract value, an injury reference. On the third sits the analysis, which breaks those points apart. If the second floor returns empty, the third has nowhere to sit.

That is exactly what happened. Title N/A, source N/A, format unresolved, no entity, no number. One thing remained — the label. In technical terms, a half-populated extraction points to a parser fault, not to a genuinely hollow article. The failure was not in the story. It was in the machine that read it.

From fifteen years of watching matches I have learned one thing: when material is missing, the most dangerous work is filling it in. In 2026, when the IPL moved to the UAE, I was working as a local fixer. The broadcast truck idled outside Sharjah with its engine running, and inside, the stands sat empty. Any report from those weeks could safely say the sky was clear. None could honestly say what the crowd was like, because there was no crowd. The stadium was still there; only the crowd had become a rumor.

On the night of 27 September 2026 I stood inside that empty ground. Rajasthan's Rahul Tewatia, 8 off 19, was struggling; Sheldon Cottrell bowled one over and conceded five sixes to him. Kings XI had made 223 for 2. Rajasthan chased 226 down for the loss of six wickets. Zero spectators. That night I recorded four minutes of stump-mic silence — the sound of a ball resting on grass, a fielder's breathing, paper shifting in the commentary box. That tape later became the spine of a film.

The lesson carries directly to tonight's blank file: recorded absence is also evidence — provided you wrote down, at the moment of recording, what was not there. Since then I have kept a margin column in every treatment headed 'what is not being said'. It earned its keep in 2026, when Pakistan beat India by ten wickets in Dubai on 24 October; Shaheen Afridi took 3/31 and Babar Azam finished 68 not out. The largest fact of that match was not on the scoreboard but in the number of people in the stands, and I had noted it.

Back to the empty file. Its risk table reads N/A in every row, and immediately beside it sits the most basic discipline of a working newsroom: risk unreported is not risk absent. A document with no data does not prove there is no danger. It proves only that nobody asked. That distinction is almost never explained in sports media, and it is where most of the damage happens. I learned the night shift by listening to what the building refused to say — and I learned that 'refused to answer', 'was never asked' and 'no access granted' are three separate documents. Merging them is dishonesty.

Here the real conflict shows. The industry instinct is to patch the blank at the output end — drop in a neutral sentence, add a familiar line, give the reader something. In cricket media that instinct is older than anywhere else, because here something must be said every week. The correct move is the opposite: mark the file plainly as a failed extraction and block it from any downstream summary or briefing. A report that cannot tell you what the pitch was like cannot tell you what the batsman was like either. The pitch remembers footsteps longer than it remembers names — and in this case the footsteps were never recorded.

One more thing I have to state every time I write from Dubai. I was not in the room where this article was written, nor at the desk where it was processed. My work here was to read one empty file, and I am saying plainly that I read nothing else. The absence I am documenting is partly my own distance.

Another scene comes back — the 2026 Asia Cup final in Dubai, when Liton Das made 121 off 117 and Bangladesh still lost by three wickets. The data for that innings was complete. My six-minute segment did not open on the score. It opened on the forty minutes I spent outside a losing dressing room asking nothing. Those forty minutes have now returned in the form of having no question left to ask.

So the forward question is this: when machines file the copy, who signs off on a file that comes back empty? A report that cannot say who played — can it say why it did not? And the reader who opens a screen the next morning wanting only to know who won: will he be told that this time there was nothing to report, or will he be quietly served a story that sounds right?