The Empty Filing Room: When a Cricket Story Reached the Desk With No Headline, No Source and Not One Information Point

Two twenty-seven in the morning. On the third floor of the Ahmedabad desk half the lights were already off, and one file sat open on the screen. Headline: N/A. Source: N/A. Article type: unclassified. Information points: an empty set. Entities: none. The only populated field was a domain label — cricket_asia. Time sensitivity? "Not assessed." Source quality? "Judge from the source fields" — while the source fields themselves were N/A.

The first thing I heard was not the roar but the filing room. And that night the filing room had no paper in it. Only empty racks, and one corner where fifteen years of Gujarat stringers' slips used to pile up, swept clean.

At the bottom of the file sat a section headed "Additional Notes." I hoped for a clue. What it said was: "identify from the information points above." That is not an answer. That is an instruction to itself. The deconstruction step had stopped halfway and written its own next line before closing the file.

Every cricket story — a board meeting, a retention list, a rain-washed day, a young quick's first Ranji innings — leaves behind at least one fixture, one name, or one date. This file had none. The moment it opened, the story of what happened on that ground stopped being writable.

An empty payload is more dangerous than a wrong conclusion, because it leaves one label behind — and a reader who sees a label assumes he is holding a fact.

From the Eden Gardens night desk to a Navrangpura showroom

I joined The Times of India's sports desk in 2026. The first rule of that newsroom was that every story had a place, a time and a person behind it, or the chief sub would not let it into the paper. Thirty years on, that is the rule that broke first.

March 2026, Eden Gardens. On the small television above the desk, V.V.S. Laxman was making 281 and Rahul Dravid 180, and India were winning by 171 runs after being made to follow on. The agency copy was in my hand and the lead was the win. I did not write the lead. I opened with the tea stall near Law Garden that had kept its radio on all night. The chief sub cut it to two lines. I kept the clipping in my wallet for eleven years.

That night I started a private notebook of crowd sounds, vendor talk and weather, and asked for the Gujarat Ranji beat so I could write about players before they were famous. I have never since filed a match report that begins with the toss. The habit keeps returning me to one question: how do I know this is true? Who saw it? Where is it written?

24 March 2026, Motera. A World Cup quarterfinal in my own city. Australia 260 for 6, Ricky Ponting 104; India 261 for 5 on Yuvraj Singh's 57 not out and Suresh Raina's 34 not out, ending Australia's 34-match unbeaten run in World Cups. I spent the last five overs not in the press box but in the queue at Gate 4, among 48,000 people where no scoreboard was visible and everyone was taking the news off someone else's shoulders. I filed "The Ground's Other XI" at two in the morning. It became a standing column built on scorers, gate staff and tea sellers, and out of it came a WhatsApp group of thirty Gujarat stringers that turned into an informal mentorship network.

18 June 2026, The Oval. Three weeks into a digital-first job after nineteen years in print. Pakistan beat India by 180 runs in the Champions Trophy final, Fakhar Zaman making 114. I was in Ahmedabad, so I wrote about a Navrangpura electronics shop where forty television sets went silent at once. The piece drew 400,000 reads; a franchise's communications officer emailed to complain. I rewrote the ending twice and asked three colleagues whether the last line was too sharp.

All three files had one thing in common, and it was not a scoreline. It was a source. A place, a time, a witness.

Now back to that night's file. It had no source. And without a source, everything else — statistic, analysis, opinion, projection — hangs in the air. Cricket copy today passes through three or four pairs of hands before it reaches a desk: agency, syndicated copy, scraped feed, aggregator. Each hand drops something. Sometimes the byline, sometimes the timestamp, sometimes the difference between a feature and a report. In a scraped feed, metadata does not arrive with a date stamp but with a taxonomy, which means the labels are made first and the content follows. What survived in front of me was not content. It was a collection-level tag.

Eight columns, one answer in each

The analytical frame in front of me had eight columns. I did not try to fill them one by one. I looked at why they were empty.

Until the format is fixed, no number is comparable with any other number. Test, ODI and T20 speak different languages; putting them at one table is the cheapest mistake and the most expensive. That file had no format, no over count, no innings, no session, no DLS revision. The instrument with which comparison is normally postponed did not exist.

The player column being empty means more than a missing name. It means the role cannot be classified — opener, anchor, finisher, pace, spin, all-rounder, keeper — and without a role the correct metric set cannot be chosen. My old habit is to cut a player's reputation against his numbers so that market value and sporting value stay apart. There was nobody to cut. Nor was there a sample-size marker — matches, innings, balls, overs — so any trend claim would have failed the small-sample test on day one.

The team column being empty is the heaviest omission, because cricket's largest structural variable, home advantage, cannot be measured without it. Home batting averages, away economy rates, spin's share on a slow subcontinental pitch, the fast-bowling load on English bounce — all of it rests on two names and one format.

The league column being empty means the framework's central commercial test could not run: price paid against sporting fair value. An auction price and an international utility are not the same thing; retention, right-to-match, broadcast cycles and franchise valuations were all absent. Where there is no transaction, no "premium" can be diagnosed either — not the local young star, not the scarce all-rounder, not the panic bid.

The difference between N/A and unratable

Here is a small vocabulary point I give every mentee on day one. "N/A — insufficient information" means the input is missing. But in the compliance and risk rows the word used was unratable — meaning it was not examined at all.

A blank compliance row is never read as "cleared." It is read as "not examined." Whether it is an anti-corruption queue, a board-governance question or the political clearance for an India–Pakistan tour, leaving a compliance check empty is the most dangerous kind of honesty in this business, because the reader so often takes it for a green light.

The only live risk in that report

No sporting risk was recorded — no injury, no workload, no selection dispute, no weather. But one risk existed, and it was the report itself: analysis built on a null evidential base. Its likelihood was certain because it had already happened, and its impact was high. That is process risk, not cricket risk.

This is not one file's disease

I will not say an aggregator broke one file. I will say the same disease has been eating the least-read and most necessary part of cricket coverage for two decades.

Ranji Trophy coverage has shrunk. Duleep and Irani have become a layer where franchise scouts go and reporters do not, and every argument about India's second XI begins with results and never with process. Twenty years on that beat taught me that India's bench strength is a selection problem, not a talent problem — and the one thing that makes a selection problem unsolvable is a missing source. If you do not know which report came from which scout, on what date, and whether it was Ranji or Duleep, you cannot challenge a selection. You can only repeat an opinion.

The same applies to writing about board power. Retention rules, auction purses, broadcast instalments, the Impact Player, net run rate — that is the theatre behind the spectacle, and seeing it needs documents, not commentary. The route to the document is the same: who made it, when, and who released it.

The habit of mistaking a label for evidence

The easy road that night was to read cricket_asia, assume an Asia Cup, and file a decent piece. Traffic would come, the desk would be happy, social would warm up. I did not take it. Nor will I claim I was brave alone. I asked first. I called three colleagues from that WhatsApp group of thirty Gujarat stringers, because my habit is to seek permission before a loud claim.

Three answers. "Asia Cup, obviously." "India–Pakistan scheduling, that's the story of the season." "Just file it, the desk will fix it."

All three were plausible. All three were unevidenced. And that is the most uncomfortable lesson of my career: when everyone agrees on the same guess, the agreement does not become evidence — it only makes the guess collective.

The habit is general. Filling the blank. "Strong batting depth." "Balanced bowling attack." "Low compliance risk." "The next Tendulkar." Those sentences do not come from a file; they come from the desk's muscle memory. In thirty years I have not seen a single Asian batsman labelled "the next" inside his first three years fulfil the claim — and I write that not to diminish anyone but because that filling reflex is the door through which a null payload walks in.

On Pakistan I want to be careful, because this is where slips happen. Saying "Pakistan cricket is in the news" without a date is a sentence that is true every year and means nothing in any of them. The Oval night of 18 June 2026 I will date-stamp — 180 runs, Fakhar Zaman's 114, a Champions Trophy final. Everything after that stays inside ICC and Asia Cup frameworks, the non-bilateral structures. The rest is speculation, and speculation needs a date.

On the industry, the safest thing I repeat is that the bulk of global cricket revenue comes from the Indian market — the figure of roughly seventy per cent circulates widely, and I do not repeat it line by line without checking it against a primary document. The same caution applies to IPL cross-ownership: SA20, MLC and ILT20 run on the same owners' map. That is background, not evidence. Treating background as evidence is the same error as treating a label as a source.

The next file on the desk

After midnight I did something unglamorous. I made a list of what that file would need to contain if it ever came back, so that all eight columns would open by themselves.

Format first: Test, ODI or T20, with overs, innings and session. Then names: at least one player or one team, so role and metric set can be fixed. Then an event: an auction figure, a central contract, an NOC, or a rule change, so the price-versus-value comparison can begin. Then a timestamp, both publication date and time, because presenting stale news as current is the oldest dishonesty in this trade. And then the question of whether that label came from the content or from the collection.

Without those five, whatever gets written is not analysis. It is well-made prose built on a guess.

The radio at the Law Garden tea stall is still on. The one that read out the score all night in 2026 is still there, and people still come to ask it for the score. Somebody still has to tell them — somebody who can say where this match was played, when, and who saw it.

The file arrived empty. I sent it back empty. This column is the accounting for that emptiness, and perhaps the most useful sporting lesson in it is this: a story that cannot name its source cannot name its score either.

Next time a file lands on the desk with N/A where the headline should be, the question will not be what we write. It will be whether we can hide from our readers that we wrote it anyway.