The Empty Field and the Full Rumor Mill: Why Cricket Coverage Needs Source Grading

There is a spreadsheet open on my desk in Liverpool and the transfer window is filling it a row at a time. Ten rows are full — one holds a release clause, one a wage bill, one an agent's route between Delhi and London. The eleventh row came back with nothing. No title, no source, and the information-points column entirely empty. No match, no player, no team, no date. Thirty-six years of habit told me to find the scorecard. There was no scorecard.

I read that empty row three times. The first time I assumed a broken file. The second time I assumed a hurried colleague had pasted into the wrong cell. The third time it became clear that this was the most honest item of the week. In transfer-window season the thing we fear most is not the false story. It is the empty story that we fill ourselves. I closed my notebook. I stopped collecting quotes when the whiteboard began asking better questions, and that evening the whiteboard carried one question: when the input is zero, what is the analyst's job?

To answer that, you have to see how a cricket story reaches us. Coverage moves through two layers. The first extracts — pulling out title, source, date, information points and named entities from whatever arrives. The second interprets — format context, a player's trend, a team's structure, the flow of money, rules, risk and mood. If the first layer returns empty, the second has nowhere to sit. The oldest disease in this trade is that the second layer builds its own seat anyway.

This is not new. In 2026, when I built a twelve-minute breakdown of how Rising Pune Supergiant used Washington Sundar's off-spin inside the powerplay — eleven matches, a 6.86 economy — the desk pressure was identical: give us something fast. Because speed was the condition, I counted both the eleven matches and the four-ball spell, because that season's final went by one run. On 21 May 2026 in Hyderabad, Mumbai Indians beat Rising Pune Supergiant by one run. A one-run margin makes numbers non-negotiable. The empty row is the inverse of that pressure. Nothing there to count, so the temptation to invent runs at its fastest.

A null result is itself a result, and publishing it as news is the actual mistake. Where there is no title, no source, no date and not one named entity, the only remaining path is a fabricated scorecard. A fabricated scorecard is more dangerous than a wrong one because it reads cleanly. I have watched an invented economy rate circulate for three months while the real figure trailed behind it.

Now the single schematic this piece is allowed. On the whiteboard I drew a four-rung reliability ladder. Top rung: the official document — a board release, an ICC register, an NOC, a signed-contract announcement. Below it, the reporter who puts a name on the story and carries responsibility for the sourcing chain, the bylined work at ESPNcricinfo or Cricbuzz. Third: general media that lifted it from an agency and enlarged the headline. Fourth: the aggregator that rewrote the third rung and stripped the conditions out. Each rung down loses one hedge — 'it is understood', 'sources indicate', 'talks are at an early stage'. By the fourth rung, that same sentence reads 'has signed'.

The ladder shows where the risk is born. It is not born in lying. It is born in the deletion of conditions. Most of the items that reached me this window had a genuine story in them — a release-clause structure, a wage-bill shape — and most were converted into a headline about who buys whom. My view is blunt: bidding wars between elite clubs are a brand race, not a sporting one; the real value sits on smaller clubs' tables. The same holds in cricket. The IPL auction's four big names absorb the conversation while the real story is the twenty-year-old on a fifteen-lakh base whom nobody can name. That story needs sourcing, and sourcing now has to be a precondition of analysis rather than an afterthought.

The real carrier of bad cricket information is the number, not the name. Fitness stories arrive every week and expire in three days. A Tuesday-evening 'declared fit' is worthless by Friday's toss, because the player redistributes weight in the warm-up and the physio writes a note. Any cricket claim without a date hangs in the air — form, selection, injury status and rankings all shift within weeks. The analyst who writes 'recently' hands his reader nothing and his editor no defence.

No date usually means no format either, and this is the expensive one. Test, ODI and T20 metrics are not comparable, so publishing a number without a format tag is contamination. My notebooks have carried the same example for years: Washington Sundar's powerplay economy in that 2026 season was 6.86 across eleven matches. Someone will print 'economy 6.86' and a reader will attach it to a Test first spell, where a figure near six means something entirely different. The same contamination runs through Duckworth-Lewis-Stern: a revised target after rain and a full-innings target are different worlds that look identical in a headline. Net run rate, powerplay and death-over splits, toss effect — all of it sits on the format tag.

If those three fields are missing, one filter remains: named entities. Fewer than two named teams, players or leagues in a package and its value is suspect. I added this rule because traffic-driven items often arrive without names — 'a star player said', 'a franchise offered'. A story without a name can be argued about; it cannot be checked. And the unchecked story travels fastest in a transfer window, because it could belong to anyone.

One clarification, because it gets argued with me often. People say that when the facts are thin, write both sides and be balanced. Not every question is symmetrical. On BCCI's calendar power, or on the split of resources between the IPL and the Ranji Trophy, 'both have a point' is not fairness, it is laziness. I rank causes explicitly: name the primary driver, label the rest secondary. The IPL's rise and Ranji's declining relevance are not two sides of one coin — one causes the other. When the scheduling window goes to the franchise season, Ranji is not merely less visible; it is less played. And the consequence lands on selection, which is why I keep returning to the argument that the hardest team in world sport to make is India's second XI, and that the difficulty is structural — scheduling and zonal scouting — not a shortage of talent.

When an item comes back empty, the first question is why. Three possibilities: the fetch failed and no text body arrived; the payload was non-text — a video or an image with nothing extractable; or the item was out of scope and never contained a cricket name. Each has a different fix, all diagnosable within minutes. What matters more is telling the reader. I sat alone in that room and remembered the crowd that chose silence — Dubai in 2026, near-empty stands, broadcast mics catching only fielders' calls: 'inside', 'keeper's', 'no run'. The loudest lesson I ever learned came from a crowd that chose silence: when there is no sound, the intelligent act is to listen, not to generate. That was the year I started the pooled newsletter, forty contributors, revenue split down the middle. I still attach a payment plan to every pitch, because I cannot sell a series I cannot staff fairly.

And then there is the Hindi question, which is personal. Thirty-one days in Russia taught me that a Hindi subtitle can be a bridge or a blind spot. I still think of the reader in Pune who translated my column without asking; I hired her on a retainer instead of sending a notice. From her I learned that the first thing to die in translation is the most necessary thing — the hedge. 'The player is understood to have agreed terms' becomes, in Hindi, 'the player has agreed terms'. A tentative sentence turns certain and the reader never sees where. That is not a translator's error; it is a structural one. Hindi needs its own grammar of sourcing — 'bataya jaata hai', 'samjha ja raha hai', 'do sources confirmed' — and every translator, every branded commentator and every desk editor has to agree on it. The day they do, Hindi cricket commentary becomes the country's largest gatekeeper, because its audience is far bigger than the English-first press corps can reach.

Money sits underneath all of this. Broadcast rights, franchise valuations and player contracts all need content, and the content factory runs faster than analysis. A transfer story's value is set by speed, not accuracy, because the first to publish gets the clicks and the correction gets none. That is an incentive structure, and moral appeals do not move structures. Injury news travels fastest and is checked least. My third standing view: the biggest cause of injury is fixture congestion, not the medical team — no physio can save a player who is playing twice a week. Proving it requires load data, and load data does not glitter like a story, so it does not get printed.

Now the turn where I disagree with myself, or this becomes a complaint rather than a piece. The easy conclusion is that the tool that returned the empty row is at fault. I refuse it. An empty result is the gate working, not failing — the failure is the desk that decides to fill it. The weakest link in my thirty-six years was rarely a machine; it was an editor who needed something by six. Nor is the problem mostly tooling. Newsrooms that never taught reporters what source-grading means will fill that column as a formality. I rank it plainly: the primary driver is the incentive to publish first and correct later; the secondary driver is the loss of hedges in translation, which damages Hindi and other Indian-language readers most; the third is tooling, and it is the cheapest to fix. Those who claim a new tool solves this are promoting the third cause to first because it is the cheapest.

One more thing, because the both-sides habit sneaks in here too. Some will say the rumour market runs on reader demand, so blame the reader. I do not, because telling the reader which rung a story sits on is our job. A reader who knows what a fourth-rung item means does not stake money on it, in fantasy or anywhere else. In Indian cricket that responsibility is heaviest because the reader is emotionally invested — the team is his, the selection is his. Leaving an incomplete story in front of that reader is a form of theft.

The value of this whole episode is zero on three fronts. Sporting: no match, no player, no team. Industry: no league, no broadcast deal, no auction event. Timeliness: no date anchor. All three zeroes at once is rare, which is exactly why it becomes a story. Five years ago I would have deleted the row. I keep it now, because it shows where the machine is drawing air from. A coach draws lines; a commentator finds the story hiding between them. Some days there is no story between the lines. On those days, that is the story.

My next step is public, because in this trade opinions are not enough — conditions are. For the rest of this window, four fields are mandatory on every item I touch: source grade, event date, format tag, and count of named entities. An item missing all four does not go out, however good the story sounds. And I am recording a claim you can hold me to, because advice like 'grade your sources' is chatter until it is counted. If cricket desks in Britain and India attach both a source grade and an event date to every transfer-window item for the next sixty days, I claim that fewer than half of the 'talks at an advanced stage' stories printed in that period will end in a signed deal — under fifty per cent, meaning half of that coverage is market noise rather than transaction. If I am wrong, the credit goes to the reader who forced me to count. If I am right, at least that reader will know which rung he was reading.