The Match That Was Never Played

It is twenty-five past eleven at night. Outside the window of my London flat it is raining; inside, the blue light of the laptop. I opened a file — a file that was supposed to hold ball-by-ball data for an entire match: the speed, line and length of every delivery, the angle of every shot, the second of every run-out, the position of every fielder. What I saw when the file opened was not a scorecard. The whole page was blank.

A cursor is blinking. Blinking, blinking, blinking — as if it is staring back at me, asking: what will you do now?

In twenty-nine years of journalism and cricket research I have seen this moment many times. An empty file, and a brain sitting in front of it that has already built a story — because without the story there is no writing, and without the writing there is no work. This is where cricket analysis hides its biggest trap. And the trap is not a trap of the pitch, nor of the death overs. The trap is inside us.

I was born in Bangladesh and now live in London. Moving between the cricket cultures of two continents, I learned one thing: the ability to tolerate empty space is the real difference between an analyst and a storyteller. Today I am sitting down to write about that difference.

Context: the data pipeline and its silence

Modern cricket coverage is no longer only the work of eyes and a pen. Every big tournament now runs on an invisible pipeline. In the first stage, someone — a scorer, a video analyst, an automated system — harvests the raw data. Every ball is a separate unit, and behind every unit sits a small information point. In the second stage, the analyst arranges those points into a story. I have worked both stages for years, so I know this: the whole pipeline rests on one thing — the information point. To write a sentence, you first need a point. Without the point, the sentence cannot stand.

But a pipeline sometimes falls silent. Someone skips a stage, someone forgets to upload a file, someone assumes someone else has done the work. And then the dangerous thing happens: the file is empty, yet the writing still goes out. Because a brain cannot tolerate empty space. It fills the gap with its own memory, its own bias, the story the audience wants to hear.

In my experience the most dangerous analysis never begins with false data. It begins with missing data — and nobody admits the data is not there. This silence does the most damage, because the reader assumes that if something is written, the data must exist.

Three threads, one lesson

My method grew out of a simple habit: I have never treated a number as decoration. Inside every number hides a human decision, and my job is to pull that decision out.

In October 2026 I began pulling at a thread. Chelsea were winning match after match in a three-at-the-back shape, and everyone was explaining it as a "shape." I logged the touch maps of Marcos Alonso and Victor Moses, and saw which half-spaces the wing-backs were leaving empty. The result was this: the three-at-the-back was never a shape; it was a thread, and I pulled it until the whole method unravelled. A formation is really a hypothesis, and the players are its peer review.

Then I spent five weeks in Russia, counting passes and logging recovery times. On 1 July, Spain made 1,004 passes, held seventy-four percent possession — and lost on penalties. So I stopped, and asked: what did that possession actually buy? One thousand and four passes taught me that possession is a story — with a pulse, a breath, a fear. Who was trusted, who was isolated, what the team was actually afraid of — the number tells you all of it, if you are willing to listen.

Then came 2026. The stadiums closed. I lost access to the grounds, but suddenly gained a vast natural experiment. In the behind-closed-doors matches, home wins fell from 43 percent to 33 percent, and away teams' yellow cards dropped too. The numbers were clean. The loneliness was not. I spoke with twelve hundred supporters in nine countries and listened to three hundred voice notes — people watching alone in their kitchens. Some said that recording was the first cricket conversation they had had in months.

The extra match is where the body confesses what the spreadsheet hid. Croatia played three consecutive 120-minute knockouts, and by the final had played exactly ninety minutes more football than France. Those ninety minutes show up in no average, no model. They show up in the legs, the lungs, the sleep.

I tell these three stories for one reason. In every case I could ask the right question only when the data was really there. Sitting in front of an empty file, I could not have written a single one of them. I could not, because the story would have been my invention, not cricket's truth.

The price of empty space in cricket

Now back to cricket. Suppose a fast bowler sends down four overs in a day, and after the match everyone writes that he "lost his rhythm." But ask, and it turns out there is no delivery-tracking data. Which over he bowled at what speed, which delivery his line slipped on, on which ball reverse swing began — if there is not a single point of this, then whose memory is the phrase "lost his rhythm"? The commentator's? The spectator's? Or the writer's, who wrote exactly the same sentence yesterday about a different match?

The same goes for a batting collapse, a story we hear daily. Three wickets fall for ten runs, and at once a narrative appears — pressure, weak technique, a bad pitch. Yet without seeing which balls took the wickets, how much was luck, how the field was set, the story is only a comfortable guess. A collapse is never one thing. Sometimes it is the bowler's skill, sometimes the batsman's decision, sometimes plain misfortune. Without data, telling these three apart is impossible.

I have often seen a pace bowler's decline explained by age, by injury, by form — while nobody checks how many spell-breaks he took, how many minutes lay between two spells, in which overs he was pushed hardest. Load management is a fashion today, and some sell it as science. But the real question is: where is the load coming from? If the length of a spell, the rest between two spells, the travel inside a tour, the airports, the nights are not counted, then whose rest is it? The bowler's body's, or the calendar's?

In this transfer window, countless stories spread every day. Who is going where, who has spoken to whom, who is unhappy. Yet the real information usually sits in quieter places — the structure of a release clause, the balance of a wage bill, how many days remain on a contract. People do not want to read these quiet facts, because they contain no story. Yet the real story hides exactly there — the direction a human being's future is leaning is written there. A reader drowning in rumours actually needs a reliable filter, one that tells him which news is data and which is guesswork.

The contrarian angle: the failure is not technical, it is human

We easily assume that a failure of analysis means a technical failure — a server went down, a file was lost, someone forgot to press a button. But the real problem is the person standing at the end of the pipeline. Nobody wants to say his hands are empty. Because the one who says his hands are empty is not called back next week. The one who can say "I don't know" has a short career.

So an empty file is never empty. The file is empty, but the article fills up — with inference, with memory, with approval. What the reader finally receives is not a description of cricket but a description of the writer's expectations.

The second contrarian truth is this: data alone does not make an analysis true. Data shows what happened; the body shows when it happened. Living in London taught me that culture is the most invisible periodisation — who rests when, who is worked when, is not written in a chart, it is written in power. The August heat of Dhaka and the grey cold of England read the same piece of data in two different ways. The ball a bowler sends down in the heat of Lahore he would have bowled differently under Manchester cloud — yet our spreadsheet holds the same number for both.

I do not optimise athletes. I help them become more legible to themselves — and that can be done only with real data, not with invented stories.

What must be done now

Next match I will open the file again. I know it may be empty again. But this time I have made a decision: in front of an empty file, I will not invent a story. I will write that there is no data here, and that absence is now the biggest fact of all.

If you watch the game, try one thing next match. Whenever someone says a player has lost his rhythm, or a team is losing the possession battle, ask quietly inside yourself — which information point did that come from? If no answer comes, then know that you are watching someone's imagination, not cricket. And the next time someone brings you an analysis with data behind it, you will be able to recognise it — because truth smells different.