The Empty Dossier: Where Asian Cricket's News Supply Chain Breaks Before Verification

On Tuesday morning a file landed on my desk. N/A where the headline should have been, N/A where the source should have been, an empty player list, a match format marked "unclassified", and one tag glued to the bottom — cricket_asia. The eight-dimension framework our desk has run for three years had every box present and nothing inside them. I read the file twice, then looked at the whiteboard. I drew three vertical lines: the claim, the type of source, the verifiable anchor. The first column was full. The second was half full. The third was entirely empty.

Looking at that third column, I understood that this was not a bad file. It was the most honest document of this signing season. We are not short of information. We are short of information's roots.

Asian cricket news does not "arrive". It is built through four layers. The first is a board or franchise press note, which usually carries the date, the contract length and the role. The second is agency copy, which lifts half a fact from the first layer and attaches a comment — and the comment, not the fact, becomes the headline. The third layer is language: a translator on the Hindi, Tamil, Bangla or Telugu desk with two minutes and one sentence. The fourth is the aggregator and the feed, where every detail from the third layer falls away and one number survives.

I want to stop at the third layer, because that is where my own account is weakest. Thirty-one days in Russia taught me that a Hindi subtitle can be a bridge or a blind spot. On 15 July 2026 France beat Croatia 4-2 at Luzhniki; a reader in Pune rendered my column into Hindi without asking and it reached roughly 300,000 people. I did not send a notice. I put her on a monthly retainer and let her choose the next five pieces. It was the best deal of my career and the loudest warning of it. The day I read my own column in her translation, one tactical detail that carried the entire argument had gone missing.

At the 2026 IPL in Dubai I called Mumbai Indians' title from a near-empty stadium. With no crowd, the microphones caught the fielders — "inside", "keeper's", "no run". I built a nine-part series on fielding geometry from that audio alone. That is where I learned to hear the moment the roar becomes a question — and that the loudest voice in the room is usually the least checked.

I now sort signing stories into three tiers by default. The first tier has a contract's anatomy: length, option clause, NOC window, retainer versus match fee, the agent's share. The second tier has only a round number — and a round number almost always comes from the agent, because the cheapest way to set a price in a market is one large, clean, divisible figure. The third tier has a name and a verb: "interest", "talks", "close".

In my experience the most reliable information in cricket is never in the headline — it is in the schedule. My first video in 2026 was about a use nobody was watching: 17-year-old Washington Sundar's off-spin inside the powerplay for Rising Pune Supergiant, eleven matches, a 6.86 economy, and a final lost to Mumbai Indians by one run. Roughly 400,000 people watched it. I opened it with a hand-drawn pitch diagram rather than a quote, and that was the day I stopped collecting quote sheets, because the whiteboard had started asking better questions.

This season's real tactical question sits in the calendar, not on the pitch. The domestic season has been squeezed into one corner of the year, A-tours have not grown in proportion, and zonal scouting still runs on the old road. The result is that India's second XI has become the hardest team in world cricket to make — a scheduling problem, not a talent shortage. A player without three consecutive domestic matches has no use for the word "form", and that is why every selection debate collapses into personal preference within a week.

19 November 2026, Ahmedabad. What got written most after that final was that Australia chased 241 with four wickets down in 43 overs. The fact is correct. The question that came home with me from the stadium that night was different: how many people could say how often India changed the field in the last ten overs? Everyone had the number. Nobody had the mechanism. A statistic looks like an answer when it is usually only a starting point.

The conventional complaint is that rumour is eating sports journalism. I want to invert the order. The first and largest cause is not rumour but the newsroom CMS, which has no field for source type at all. When the system does not record whether a claim came from a press note, an agent or someone's timeline, the editor is left with no scale on which to weigh fifty stories. The second cause deserves separate treatment — the speed economics of the window: in signing week the first publisher takes the headline, the second does the verification and returns empty-handed. The third is the English-first wire agenda, which cannot hear what the Hindi desk already knows.

The counter-intuitive finding is that more coverage has not made verification better; it has made it more expensive. Volume grows, anchors do not. Thirty years ago a story meant one checked note. Today a story means three desks, two aggregators and a thread, and none of them has the contract length. A coach draws lines; a commentator finds the story hiding between them. The story hiding in this window is that we multiplied the headlines and left the sources where they were.

The proposal is clean and testable: every desk covering Asian cricket should print a provenance line with each signing story — source type, date of the claim, and one hard element of the contract. A story that cannot fill that line is not coverage, it is market noise, and it should not get a headline. That is not an instruction, it is a test, and I stake my byline on it.

The next signing you read first thing in the morning — was its third column full or empty? The whiteboard is asking that question right now, and the answer is with you, not with me.