The Empty File: When Cricket’s Record Stops Speaking

2:40 in the morning. The rain over Kolkata had stopped, and on the laptop screen a document was open with every heading exactly where it should be. There was a title, a slot for the source, a slot for article type, a slot for the one-sentence summary, and a list for information points. Every slot was empty. In more than three decades on this beat I have seen half-filled scorecards, scorers’ registers smeared by rain, and cassettes on which only the wind survived. This was the first document I had met that was fully built and contained nothing. That file did not lie. It said nothing at all. By the end of that night one thing was clear — the most expensive error in cricket coverage is not a wrong number; it is the empty slot that everyone assumes has been filled.

Cricket’s record never begins with the scoreboard. It begins in the room at Eden Gardens where the scorer’s chair sits, where there is a pencil, an eraser, and a register whose ink bleeds in the humidity. I have sat there and watched what happens when an over is missed: the card does not say that information is unavailable. It prints a number. And the number is wrong. That is the anxiety underneath this whole business.

When my first byline appeared in December 2026, cricket’s memory lived in two places — the scorer’s register and the notebook of the man in the press box we all called the stats uncle. Later it all moved into ball-by-ball databases, and today it moves through a pipeline: a scraper reads the page, an extractor pulls the facts, a summariser trims them and passes them on. Every stage is a filter. A filter is meant to remove noise. Sometimes a filter removes the signal along with the noise and leaves only the shape behind.

What lay open on my screen that night was such a shape. The interesting question is not why the file was empty. It is why nobody stopped when they saw that it was.

In a pipeline, emptiness has three testable causes, and all three resemble the ordinary problems of cricket reporting. One, the material exists as thermal paper, an image or a PDF — the text is there but it is not readable text. Two, the page sits behind a paywall or behind JavaScript — the door is visible, the room is not. Three, the body-parsing step drops something. All three share one property: failure makes no noise. No error message, no red light, and the dashboard says analysis complete. That is the most dangerous kind of failure, the kind that looks like success.

I was there when the silence broke, but I have spent far longer in the silences nobody heard. In February 2026, outside the green room at the mega auction in Bengaluru, I had the list of unsold players in my hand. Most of them had full records in the database — Ranji overs, domestic seasons, all of it. The problem was never a shortage of information. The problem was that nobody chose to read it. What I watched across those 48 hours was not very different from an empty file: each player had a slot, each slot had a name, and after each name there was nothing.

That is why my notebook still carries five items before any assignment. One: at least three to five hard facts that can stand on their own without interpretation. Two: format, because a Test average and a T20 strike rate do not belong on the same sheet and reading them together is the oldest error in cricket analysis. Three: a name — at least one team, player, board or event; analysis without a name is weather talk. Four: source and date, because a fact without a date becomes rumour. Five: the author’s stance, because you cannot test a claim without knowing which way the source leans.

That list is not a software requirement. It is a reporter’s spine. The day it turns up empty in a document, that document should not be published, however elegant its skeleton.

One more thing in that file made me stop. The entity field carried an instruction — identify from the information points above. There were no information points above. This is the same loop cricket runs everywhere: someone is asked to justify themselves on the basis of something they were never given. A young Ranji cricketer asks why he was not picked and is told to look at his record — the same record nobody logged that season, because nobody covered that match. I have heard that silence. That circular instruction is not a broken file; it is our system’s habit.

There was another small thing in the same document, easy to overlook. The domain label read cricket_world, while the specification asked plainly for Cricket. It sounds like a technicality, but it looked to me like a miniature of our profession’s largest categorical mistake. Domestic cricket spent decades filed under other because it had no clean label. Women’s cricket was given a slot with no name, so nobody filled it. I was there when the silence broke — at Lord’s in 2026, when India lost by nine runs and my editor let me file a daily diary from the team hotel instead of another match report. After Harmanpreet Kaur’s 171 against Australia, the piece I wrote about her father’s sweet shop went viral. Remember, that information was not new. It had always existed. That day, someone chose to read it.

This is my standing complaint against a system that always looks full. A filled slot and a correct slot are two different things, and our industry prints them in the same colour. An analysis claiming a strike rate is impressive is no more trustworthy than one stating that information is unavailable. The second is honest. The first is decoration.

During sixty days inside the UAE bubble in 2026 I wrote a nightly diary. It carried what no scorecard has room for — the entry from a nineteen-year-old uncapped player who wrote that his mother’s surgery fell on match days and nobody had told him. That entry led to a team-wide mental health check-in. The beat never stops, even in a bubble; it only needs someone watching. The information that matters most usually sits in the slot that protocol has marked optional.

And when I say we miss things by watching only the scoreboard, I do not mean the numbers are false. Numbers are true and incomplete. In January 2026 at the Gabba, after eight injuries, the attack that walked out had four Tests of experience between them. The scoreboard recorded a three-wicket win. I spent that week with T Natarajan and Washington Sundar at the nets, and what I wrote was that bench strength was really bench community. That sentence did not come from a number. It came from a room with no camera in it.

Back to the empty file. In one respect it was scrupulously honest: everywhere it said insufficient information. I think it was a truer document than any fully filled report on my desk that night.

Our instinct is to treat an empty file as a failure — the writer could not deliver. I read it the other way. The empty file was the most honest object in that room; everything else was filled slots with no guarantee of being right. When a template is full of text and empty of facts, it is not analysis, it is upholstery — and stopping upholstery from reaching a reader is editorial discipline, not cowardice. That document even refused a one-star rating, because one star would imply that a little content existed. The content was zero. Calling something unmeasurable less than zero or more than zero are both lies.

The same logic applies to cricket’s numbers, and here is something three decades on the beat taught me that no analyst did. We look at a bowler’s economy rate and treat it as his ability. An over that nobody covered, that no scorer logged, does not become a zero in the record — it disappears from the record, and another number quietly takes its place. Thousands of domestic overs are missing in exactly this way. They have no tragic statistic, because they have no statistic at all.

In the quiet between plays, the real game lives — and the care of that quiet appears in nobody’s job description.

The next morning I closed the file and went back to the source. The source was not there. So I did what I have done for thirty years: I picked up the phone and found the man who had been in the room on that day. The answer came late, but it came. The record often hides not in a file but in somebody’s memory, and no automatic route to it has ever been built.

My recommendation going forward concerns process, not personnel. Any pipeline carrying a cricket report needs a hard gate: at least three information points and at least one identified name, or the next stage must not start and a clear error must be returned instead of silence. The check is cheap and the payoff is large, because it blocks an entire class of outputs that read analysis complete and contain nothing.

The question is not why the file was empty that night. The question is who will own the filling of the next empty file — and who keeps the account of all the emptiness we wave through each day by calling it no news.