Zero Information Points: What an Empty File Taught a Cricket Desk in the Middle of Transfer-Window Noise

At 7:12 on a Tuesday evening, a file opened on the Chennai desk. The template was complete — headline, source, article type, domain, core viewpoint, information points, entities, time sensitivity. Against every field stood the same mark: N/A. The information-point list was empty. Not one entry. Article type read 'Unclassified' and the domain label read 'cricket_world' — not even the standard token our system usually stamps.

From the far end of the desk the intern asked, 'Sir, the template is filled in. Shall we publish?' I said wait. Then the desk went quiet, so I followed the noise — not the noise of the file, but of the question every empty file brings with it: is our job to fill it, or to say that it cannot be filled?

In 2026, on the Mid-Day sports desk, I was given one rule: a report with no name, no date and no format is not a report, it is a mood. After eleven years on a print desk, at thirty-three, I took a pay cut to become a travelling writer — a knee had ended my Tamil Nadu Under-23 career at twenty-two, and the desk had taught me that a story beginning with the score never finishes.

Now the noise this file arrived inside. In a transfer window the real story is never the fee — it is the release-clause structure and the wage bill. Agent phones start ringing three days before the retention list; WhatsApp groups circulate 'heard it from' lines; and every forward attaches a name who heard the line somewhere. At eleven at night the desk has forty forwards open, three with a date, two with a source, and not one carrying what the headline claims.

This is where my old desk gets restless. The distance between a rumour and a report is set by three things: the language of the contract, the movement of the agent, and the arithmetic of the salary cap — the rest is weather. In a transfer window the fastest writer usually knows the least; the slowest often holds the one line that stays true until the next season.

Two dates live permanently in this desk's memory — 2026 and 2026. These are not old anecdotes, they are audits. After Cronje we learned how quickly one phone call can rewrite trust in an entire sport; after the IPL spot-fixing years we learned that printing a claim you cannot verify is itself a claim. Verification is slow work, and slowness is now treated as a luxury in this trade — when it is the basic safety rail.

Back to the file that reminded me of all this. Five things should have arrived from the Stage-1 extraction: the article's title, the outlet, the publication date, at least five information points, and one named entity — a team, a player, a league or a board. None of them came. What came was a beautifully built empty vessel.

My desk runs three checks, and the order matters. First, the name. Who? Second, the date. When? Third, the format. Test, ODI, T20, The Hundred, or a non-match matter? Format is the door without which no cricket number means anything; a Test average, a T20 strike rate and an ODI economy are three languages, and blending them is the most common error in this trade. When the format itself is undetermined, player evaluation, team depth and auction premium all become guesswork.

This is where the temptation arrives, every night. A filled template looks like evidence, and a filled template whispers: put something in. Add a team from memory, a player, an incident — the reader will never know. But this is exactly where sports journalism does its deepest damage: a filled structure on an empty base is indistinguishable, to the reader, from the truth. The risk in front of me was not theoretical — had this file gone downstream to a summarising model, it would have populated teams, dates and figures on its own, and nobody would have challenged them.

I remember learning Washington Sundar's pre-match routine at Chepauk during the 2026 TNPL before I learned his bowling average. Then the Ranji season: sixty-four days, nine cities, thirty-eight filed pieces — and there I learned that the forty minutes before play tell you more than forty overs. Every report I file now starts in a bus, a corridor or a dressing room. I keep the beat by counting what the box score forgets — and what was forgotten that evening was the entire story.

My position on data has clarified over the years. Analysts have entered dressing rooms over the last few seasons, and that is good news — as long as a number is not mistaken for a verdict. I have seen rooms where a strike-rate sheet is cut down by the pitch, the powerplay pressure and the pace of the batter at the other end. Numbers are evidence, not witnesses. An analysis with no identifiable human in it — no coach, no keeper, no bowler wiping his face in the third over — belongs to a different sport.

One thing is permanent in my copy: a 150-word stand report. The habit dates to 2026, when Moscow gave me a rail pass and fan zones and nothing else. In Rostov-on-Don, Japan lost 3-2 to Belgium in the 94th minute, and their supporters cleaned their section before they let themselves cry. Since that night I refuse to file from a match I have not watched at least once from the stands. The crowd is a primary source, not colour. This time there was no crowd — the source was a document that never arrived, and recording its absence is part of the same discipline.

So the conclusion that evening was not nerves. It was a finding: extraction failed before entity recognition. All eight analytical dimensions — format, player technique, team landscape, league economics, governance, risk, public narrative, industry transmission — returned empty, because every dimension requires at least one solid information point. Status logged: insufficient input.

Now the part I do not expect anyone to agree with. The industry reflex is clear — whoever fills the empty page fastest wins the click, and whoever writes 'insufficient information' is called slow. In a transfer window that reflex is fastest of all, because the audience is hungry and every claim is stale by morning. But the biggest error was not the empty file; the biggest error would have been the confident story built on top of it — because the reader would never learn that the foundation held nothing.

And one more thing, a desk habit I will not hide from myself: when the desk goes silent, it is read three ways — nothing happened, something is being hidden, or the desk is lazy. That evening the truth was a fourth: nothing had arrived at all. Never read silence as consent; sometimes it only means the system did not work, and saying so is the story.

Three concrete fixes follow, all doable at desk level. First, a hard pipeline assertion: any output with fewer than five information points does not move forward. Second, every extraction must carry outlet name, publication date and byline. Third, no player or team analysis is accepted without a format tag, however elegantly written. The information gain this time was procedural, not dramatic — and procedural gain is what will save us next time.

Tomorrow morning another forty forwards will arrive, and one of them will carry a true story. The question is not whether we can spot it. The question is how many of tomorrow's stories will stand on an empty file that nobody opened to check.