When the Scorecard Went Silent: Data's Silence and Cricket's Human Margin

Eleven at night. In a London flat a laptop screen glows with an analysis file that contains no runs, no wickets, no overs. Every field carries the same sentence—insufficient information. The pipeline that was supposed to chew a cricket match into fine, edible analysis returned an empty husk and only two words: cricket_world. The floodlights on a cricket ground do not lie; they hum. But this file has no ground, no floodlights—only a blank cell and a blinking cursor.

I stare at the screen and drift back to June 2026. Football was returning, cricket was returning, but the grounds were full of human absence. Silence has a formation, and behind closed doors it played a low block. That day I learned the scorecard writes a number, but the match is written by someone else. This blank file taught me the same lesson again, this time in cricket's language.

Cricket's data era arrived like weather. T20 rewrote the grammar of arithmetic. Strike rate, economy, powerplay, death overs, World Test Championship points—every broadcast runs a parade of digits. Every franchise now hires analysts, every dugout carries a tablet, every slow-motion replay is preceded by a percentage. The promise is simple: the number tells the truth.

But any analysis runs through a pipeline. In the first stage someone gathers the raw material—events, names, information points. In the second stage that raw material is analysed in depth. However long the chain, every conclusion is tethered to an information point behind it. And if the first stage returns empty, the whole chain stands on a zero—exactly as on my screen tonight. The analyst did the most honest thing available: he did not guess. He wrote, there is nothing here.

This is where cricket's largest truth hides. A number never explains a match; a number only counts an outcome. A strike rate of 150 looks identical in a chase under lights and in a dead rubber, yet they are two entirely different lives. Who made 70 off 40, when, and against whom—without that, the number paints a false sameness. An economy of 6.2 looks polite, but the match may have broken in one over, where two full tosses and a misfield ended a television vigil in seven minutes.

Cricket has now absorbed calculations like "expected runs" and "win probability," and this is precisely where my objection sharpens. We use them like incantations, as if a digit will narrate an innings. Yet these metrics cannot explain a player's in-game decision, cannot capture form, cannot measure an umpire's standard. The decision taken in that instant—why the batter abandoned cover for midwicket, why the bowler shelved the yorker for a slower ball—does not appear in a probability sum. It appears in testimony, in context, in a human's wavering confidence.

My memory tells me that in 2026 I spent eleven weeks collecting 340 voicemails from supporters about what they missed. In that series the scorecard said 92 matches; the voices said something else. The silence of four thousand absent people is more than a list. No analysis pipeline will ever seat those four thousand in one room, because that data never arrives in a feed; it arrives along a memory's groove, in the corner of an older supporter's eye, in the echo of an empty stand.

Here is my second objection. We have leaned so hard on the information pipeline that we have outsourced memory itself. If a system tells us what happened in a match, we stop watching—we verify. We abandon witness for the wall. The file that returned empty tonight is not cricket's failure; it is a mirror for our worship of numbers. The mirror says: when you handed truth to arithmetic, and arithmetic came back blank, you were left holding nothing.

The pipeline is never bigger than the match. A number that guards no provenance has no source and no date—and a number without provenance is a rumour. Cricket's most reliable evidence has always come from people: a spectator's eye, a teammate's applause, a bowler's slight knee tremor. My profession taught me that the best columns do not argue; they witness. And a witness's first condition is consent—permission before telling someone's story, patience to listen before delivering the last word.

One small rule governs my reporting life: of every scene I ask whether it will be remembered in ten years. A bowling figure will not be remembered; the knee will, the stretching handshake will, the empty stand will—where a crowd returned six months later and sang for the first time. This blank analysis file is itself a scene: a technological silence that reminded me the things we cannot measure are the things we remember most.

Every season a battalion of analysts chases a perfect model. They measure pace, spin angle, bat swing. Then comes rain, comes dew, comes a lost toss—and the whole model drifts away like a paper boat. However precise the Duckworth-Lewis-Stern digits, they do not tell you how a batter's hand trembles chasing 35 off 31 on a wet outfield. That tremor is cricket.

I know an objection will come: is data meaningless, then? No. Data is ears, data is eyes—but data is not a mouth. Data tells me how fast someone ran; it does not tell me why. Data tells me a catch was dropped; it does not tell me whether the fielder's hand still burned from an earlier blow. Data has one duty—to raise a question, not to sit down as the answer. Analysis that declares itself the final verdict has quietly abandoned the job of asking.

This is why the empty file is not a failure to me but a courteous honesty. An analyst who does not know has said, I do not know. In today's cricket arena that is rare. Everyone knows, everyone is certain, everyone dangles a graph on social media and delivers a verdict. One person wrote that there is nothing here—and in that instant I stopped, because honesty obliged me to look at the room once more.

So instead of pointing a finger at the pipeline, I look at myself. In my notebook there is a page with no runs on it. I do not tear it out. I keep it, because it reminds me—testimony is my job, not verdict. Silence has a formation, and by breaking that formation apart, a match's real story emerges, one inch at a time.

Analysis does not always mean more numbers; analysis means the right questions. If I hold even a single information point, I can work it across eight dimensions—format, player, team, commerce, governance, risk, public narrative, industry transmission. But nothing stands on a zero. If I stuff imagination into a verdict to keep it standing, I only manufacture a lie—and lying is cricket's gravest offence, because cricket punishes a lie slowly, year after year, through a wrong selection.

I remember how many selection verdicts were issued by data, and how the field broke their arithmetic. An average quietly decides who plays; yet the average does not know whose hand was steady at the last ball of an innings. Bangladesh and England—I have watched the cricket of both countries for seventeen years, and every season I see data standing at the door of a decision. But who opens the door? A person.

This blank file will one day turn to dust. Another feed will arrive, another match, another analysis. But I will carry one habit away: beside any number I will write its source, its context, and who stood outside it. In cricket, data has one honest place—the margin of my notebook, not the centre. At the centre sits the person whose name may be in no database, but whose knee my memory keeps.

A few days from now another match will begin, another scorecard will light up. The numbers will return, confident again. But I know that every pitch is a page, and the crowd writes in the margins. I will keep my pen in the margin too—where, telling a human story, a number does not interrupt. Who knows—ten years from now someone may remember this night: the night an analysis fell silent, and cricket laid a hand on its shoulder and said, come, let us now tell the real story.