An Empty File, a Loaded Roar: The Case of the Cricket Report That Contained No Facts

Two forty-seven in the morning. On the desk in a Hyderabad flat lay two objects: a spiral notebook whose corner is still faintly yellow with the dust of Sharjah, April 2026, and a laptop with a file open on it called cricket_asia. The file listed N/A where the title should have been. N/A where the source should have been. Article type: Unclassified. And the list of information points — where a match, a player, a score, a date could have lived — was empty. I looked at that screen for a long time. In forty-five years I have seen half-finished stories, wrong numbers, headlines that quarrelled with their own copy. A report containing no report arrived for the first time. Let me say this plainly: what follows is not a cricket analysis. Where the match, the player, the team and the date are all absent, any tactical conclusion built on top is a guess — and a guess in good prose starts to look like analysis. This piece is about that costume, not about wearing it. What is in front of me is simply this: an empty record. An empty record is also a story, if you have the nerve to read it. Most cricket coverage no longer gets made the way it was made in 2026. We used to sit in the ground, fill the notebook, go back and write. Now the first step is usually a program — it reads a feed, scrapes a page, breaks facts into small boxes, and every floor above is built from those boxes. If the first box arrives empty, the whole building stays empty. The trouble is that emptiness on paper starts to look like 'no risk identified'. Empty files arrive for three common reasons, and all three have less to do with cricket than with plumbing: pages locked behind a paywall; pages assembled by JavaScript that an older scraper cannot read; and bad encoding, which throws out a Hindi or Urdu story believing it to be garbage. In all three cases what survives is not the story but the space where the story should be. Space always gets filled with something. I have watched that space being filled, by human hands. In April 2026 my editor sent me to Sharjah with a paper notebook and no laptop. On 22 April, Sachin Tendulkar made 143 off 131 balls against Australia inside a stadium swallowed by dust; two nights later he made 134 in the final. I filed 2,400 words and did not once mention the required rate. That was not an error, it was a habit: I believed facts were for the paper and atmosphere was for the reader. It took years to understand that atmosphere without facts is only a mood, and moods do not last thirty years. In December 2026 the BCCI handed Mohammad Azharuddin a life ban and my desk ordered five parts on fallen idols. I wrote two and stalled; the language sounded like a courtroom. What rescued the week was a groundskeeper at the Hyderabad Gymkhana who had been rolling practice pitches since Azharuddin was a boy. I filed nine hundred words about him instead. The groundskeeper knew the pitch better than the heroes knew the script. Now the part that is actually analysis. Judge an empty file by cricket's own standards and four conditions appear. It fails all four. The source condition. Every claim needs a name behind it — an outlet, a byline, a board or ICC release. The empty file carries N/A, which means the story has no owner. An unowned story travels fastest in cricket and corrects slowest. The missing source is not merely a question of trust; it tells you whose interest the story serves. The format condition. A Test average, an ODI strike rate, a T20 economy rate are three different currencies. Printing a number without a format tag is like signing a cheque without a date. Which is why, in a file where the format was never fixed, every sentence containing a statistic is compromised, however correct it looks. The date condition. You need the date of publication and the date of the event. A file with no publication date cannot tell yesterday's story from last year's. When old news starts to read as new, it is not the reader who needs fixing. The witness condition — the heaviest of the four. 2 April 2026, Wankhede. Mahendra Singh Dhoni 91 not out, the six off Kulasekara, twenty-eight years closed. I was there on a broadcaster's commission for a three-part documentary, and I filled 41 minutes of a borrowed recorder with crowd noise before writing a single line of narration. The scorecard told me what happened; the tape told me what the story was. But the tape existed because someone was in the room. The witness is the protocol — my oldest and cheapest technique, and the one thing no bot will ever own. Then the batch disease. When the title, the source, the type and the information points are all empty at once, the fault usually sits not with the story but with the system that read it. System faults rarely travel alone; the sibling files in the same batch carry the same fingerprint. The day a desk understands this, it audits the batch, not the record. And the temptation to fill. An empty space frightens an editor, so the instruction comes down: put something in. This is where most invented numbers are born, because in cricket the easiest filler is a statistic — a strike rate, an average, a 'record'. My rule for years has been simple: if I cannot remember the source and the format of a number, the number does not reach the page. A risk matrix full of N/A never means 'no risk'; it means 'risk unknown'. Anti-corruption reporting taught me the same lesson — an agency's silence does not acquit anyone. The easiest way to fill space is always the auction, and it is the most dangerous. Turning a large bid for a twenty-one-year-old into immediate 'international strength' is the magic sentence that returns every season and reads well every season. For a player with fewer than fifty top-flight games, the price measures market appetite, not the cricket. An auction number is a record of bidding, not of performance. The habit of welding the two into one sentence has done more damage to cricket coverage than any single wrong scoreline. The second easy route is inflating a small sample. Four innings and a rapid fifty in a T20 league becomes a 'shift in attitude', which is exactly the disease that flourishes in copy written without going to the ground. Someone who has not felt the heat, seen the colour of the pitch or watched a batsman's feet will turn four innings into four years. I trust the quiet groundskeeper more than the loud highlight reel, because the reel is made to sell and the pitch is made to last. Now the uncomfortable turn. The pipeline sent an empty file, and we are comforting ourselves that the machine erred and the human is fine. I think it is the other way round. The empty file is not a new illness; it is the final stage of an old habit — writing the story with nobody at the ground. Press-box seats thinned, the Ranji Trophy went quietly invisible, scorecards began arriving from websites, and 'match report' came to mean 'translation of the score'. The day no witness was left between the writer and the cricket, the empty file became inevitable. The machine only accelerated what we were already doing by hand. So here is a claim you can check, and I will be glad to be wrong. Take the last twenty-five Ranji reports from any major Indian outlet. I say at least eighteen of them will not contain a single sentence written that day by a person sitting in the stadium. The claim is about witness, not arithmetic, which is why only witness can overturn it. The IPL did not kill Test cricket. It made the Ranji Trophy invisible, because it changed the economics of coverage — camera and money go to the four-hour show, and the six-day match finishes with nobody in the seats. The empty file is the technical document of that invisibility, and it should be filed as evidence rather than hidden as embarrassment. What sits in front of us is a plain demand. Before any cricket report is called analysable, it needs a named source, a fixed format, five dated information points, and one sentence a witness could prove false. These are not bureaucratic conditions; they are the things that separate one story from another. In the notebook that night I wrote two lines. Above: 'There was no match today. The report was still commissioned.' Below: 'An empty file is also a scene — the players simply never walk in.' By morning I understood something else: the next time a file arrives blank, the question will not be what was written in it. The question will be whom we are sending to the ground to fill it.