The Scorecard Came Back Blank: Cricket's Feed Line Has a Credibility Problem

At 9:12 on a Wednesday morning, at my desk in Manchester, a record opened in front of me: title blank, source blank, date blank, and the information-points field completely bare. I have been keeping cricket's ledger for thirty-four years. Along the way I have published wrong numbers in a hurry, pulled an entire paragraph twice, and once waited until the next morning for a single line of a scorecard. But this was the first file that contained nothing wrong — and that was the difficulty. The colleague beside me asked, 'So what do we write now?' That question is the spine of this column, because empty space never stays empty. Something gets poured into it, and an estimate never asks for a source.

Cricket journalism stands on three things: the feed, the auction ledger, and one witness in the ground. Each moves at its own speed. The feed is fastest — a ball-by-ball string pushed out in minutes by platforms like CricViz and ESPNcricinfo. The auction ledger is the most solid, because the price gets printed on paper. In January 2026 in Bengaluru, the hammer fell on a shortlist of 578 players: Ben Stokes to Rajasthan Royals for ₹12.5 crore, Jaydev Unadkat to the same franchise for ₹11.5 crore, KL Rahul to Kings XI Punjab for ₹11 crore. Those numbers are not for argument. They are for audit. And the witness is slowest of all — the man sitting among 132,000 seats at the Narendra Modi Stadium in Ahmedabad on 19 November 2026, when Travis Head made 137 and Australia won by six wickets and a sentence I had been writing for six weeks collapsed inside one hour.

The chain of a news story runs in this order: gather, parse, verify, publish. When the first link snaps, the other three get filled from somewhere else. That is what happened this week. The record that arrived carried no format — not Test, not ODI, not T20. In cricket analysis this is no small gap. Format is the precondition without which no number means anything. A strike rate of 130 through the middle overs is fine in T20; a batter sitting on that rate on the first day of a Test will not get his side to 300. Economy rate behaves the same way — 9 an over is ordinary in T20 and expensive in ODI cricket. Strip out the format and the number becomes a count, not an argument.

The second gap is sample size. Three matches of form and a twelve-month trend do not belong on the same sheet. This is the most common failure in cricket commentary — declaring a batter 'back in form' after a series average of 40, when the following month he folds against pace on a bouncing pitch. The third gap is venue. An average built on home soil does not reveal the same player on an overseas tour. Without stripping that out, every comparison is half-finished.

One lesson follows from these three gaps and deserves repeating in this trade: result and process are different objects. 14 July 2026, Lord's — England 241, New Zealand 241, the Super Over tied too, and the title decided on boundary count. The scorecard says England are world champions. The process says two teams were level that day. A reader who stops at the first sentence treats cricket like a league table; a reader who continues understands the sport. The live blog taught me that narrative is rhythm, not record. On the night of 2 April 2026 at the Wankhede I filed 61 posts across seven hours, roughly 4,000 words, and the closing post carried MS Dhoni's 91 not out off 79 balls and the winning six off Nuwan Kulasekara. Accurate record. But the story lived in the eleven seconds of noise before that six, and those eleven seconds were in none of my posts.

The real lesson of this episode is that the weakest link in cricket's information chain is not the stadium. It is the software. When retrieval or parsing breaks, everything looks normal from the outside — files are arriving, reports are being produced, headlines are being printed. The emptiness is internal. And the oldest habit of this trade is to fill that emptiness with an estimate. A large share of the cricket coverage spent over the past five years on auction and transfer rumours was produced by exactly this pressure, because writing 'I don't know' is expensive. I keep the auction ledger beside the airport gate, because value always travels; but a price written in that ledger is also a claim, not a truth. ₹12.5 crore does not mean a player will survive a bouncing Test pitch. The price is the market's verdict; the performance is the ground's. Putting both in the same account is the error this week's blank file exposed.

A pause is needed here, because the easiest ending to this column is 'don't trust the data', and that ending is wrong. The blank record did not fail. It refused. The moment it found no player, no venue, no date, it closed the account with 'insufficient information' instead of inventing a fixture. That is rare honesty in my profession. The real crisis is that we have built a cycle in which silence is punished and speculation is promoted. In football, managers avoid a four-man line because the reputational cost of failure lands on them; on the cricket desk, an analyst avoids saying 'I don't know' for the same reason — that sentence has no headline in it. And there is a charge sheet against this column too: the entire argument is drawn from one empty file, so applying it to the wider game is a leap. Suppose this was an isolated technical fault and the feed is normal next week — then this piece will have solved a problem that never existed. The system is large; one blank file is a signal, not proof.

After 2026 I banned the word 'inevitable' from my drafts and added a mandatory paragraph to every long piece: one sentence naming exactly how the argument could lose. Editors read it as a hedge. It is a brake. Cricket's information economy needs that brake right now — a gate that refuses to pass a record with zero information points to the next floor. For an engineering team, that is twenty lines of code. For a reader, it is the difference between reading a fact next morning and reading a beautiful guess. The question is not when the feed will be fixed. The question is why we keep publishing while it isn't.