The Scorecard of Empty Columns: When Cricket's Data Analysis Returns Nothing

Late last night. A small studio in north Manchester — an old framed scorecard on the wall, a cold cup of tea in the corner, and a screen in front of me. Open on that screen was a report with a heavy-sounding name: Deep Professional Analysis, Stage Two. Eight large sections, each with a table beneath it, each table full of rows. But every box was empty. No name, no date, no runs, no wickets, no event. The analysis had done its job flawlessly — it processed every cell, and returned zero.

I looked at the clock. I counted the seconds like they were strangers at the door. A machine, a form, and twenty-odd empty boxes — what is a person supposed to do with that?

This piece is about that emptiness. But not by leaving cricket behind. Rather through cricket — because this empty report is the perfect image of something I know well: the vast, beautiful, immaculate structure of modern cricket, which often holds nothing inside.

Context: From Scorebook to Pipeline

Cricket's relationship with data is not new. For decades, in hand-written scorebooks, people recorded names, runs, overs, catches. Only the hand changed. Paper to typewriter, typewriter to computer, computer to ball-tracking camera. With each change, the ambition of analysis grew — and with each ambition grew a quiet fear: if data is this powerful, what is the human eye for?

That fear is not idle. In the 2026 World Cup semi-final, after rain, South Africa were suddenly handed an impossible equation — twenty-two runs off one ball. The rain rule then was a simple average-run-rate calculation. On paper it added up; on the field it did not. Because cricket is never played on paper. After that, in 2026, Frank Duckworth and Tony Lewis built a new method, which, once Steven Stern joined in 2026, became known as DLS. Here the data was honest — it admitted the earlier model had failed to read the human rhythm.

DRS arrived in 2026. India refused it at first, because there was little trust in a prediction of where the ball pitched and where it went. Today no big match runs without DRS. But notice — DRS is a machine for decisions, not the owner of the decision. Still, we often forget the technology only supplies the evidence; the umpire makes the call.

I have worked in match commentary for twenty-seven years. In the last few, cricket analysis has taken a strange shape. Once, analysis helped tell a story — names, runs, one nice fact after the game. Now analysis is itself an industry, a factory with many stages. In the first stage the raw material is gathered — matches, players, information points. In the second, that raw material is processed deeply — format, tactics, rankings, market, governance, risk, public opinion, industry flow.

The report in my hands had returned zero from its first stage. No raw material. Yet the second stage printed in full — eight sections, more than forty tables, over a hundred rows. Every cell read: insufficient information, cannot assess. The sight stopped me. Because it is exactly cricket's most confident and least knowing place.

What Data Sees, and Cannot See

Ball-tracking measures a delivery's pace, the angle of spin, the height of bounce. Hawk-Eye says how many centimetres outside off the ball pitched and whether it would have hit the stumps. A speed gun measures velocity. A wagon wheel shows where the batter sent the ball. These facts are true. But how true?

Take a ball that passed two centimetres outside the stumps. Hawk-Eye says out. On paper the number is clear. But the batter played at it from nine centimetres too early — because his hands were shaking, because the previous bouncer had hit his chin, because his father was sitting in the stands. None of these three appears on a wagon wheel.

Data turns time into a photograph. A photograph is still. But a match is moving. Here is the limit of data. DLS is a superb tool, but who will say that the batter returning after rain had cold hands? Who will say that Duckworth-Lewis's number was exact while the ghost of defeat sat on the team's head? In these places data falls silent, and we assume it knows everything.

For years now I have kept a habit. When I cover a match, I draw two columns in a small notebook. One column holds data — runs, balls, strike rate. The other holds rhythm — who stopped when, which fielder's shoulders dropped, which coach began pacing the boundary line. In every match the second column tells me more. The first column gets printed. The second does not — but it is the real event.

Dressing Room versus Spreadsheet

I will speak plainly. Analysts have now walked into the dressing room. Their slides are immaculate, full of colour, arranged with arrows. But their conclusions are often detached from the rhythm of the field. Because a spreadsheet does not know when a batter will open his arms in the sixteenth over of a T20, and when he will fold himself away.

Virat Kohli's chasing reputation is known to all. More than twenty-seven ODI centuries, his tally of hundreds in the thirties. But the thing data has never measured is the moment he decides to take the game into his own hands. Numbers say he starts slowly and accelerates later. Rhythm says he waits for that one ball when the seamer's focus slips a fraction. This patience does not appear in a strike rate.

Kane Williamson is more mysterious in this respect. His data is steady — undramatic, therefore less discussed. Yet on the evening of the fourth day of a Test, when the pitch begins to break, that calm rhythm is the team's most valuable asset. Data says his strike rate is under fifty. Rhythm says he is buying time for his side. Which is worth more?

My suspicion is that the greatest weakness of analysis lies here. Numbers measure the present, but cricket lives in the future. How do you capture Ben Stokes's Headingley innings in any number? Hope of victory was nearly zero, yet he played on. No model predicted that decision in advance, because the model does not know when a person decides he will not give up.

I entered media work twenty years ago, with a habit of cricket writing already in hand. In the newspaper newsroom we were taught: facts first, then words. Today the order is reversed. Words first, facts after — words are assembled, then facts are gathered to match. That reversed order is the real danger.

The Vanishing Anchor in the Age of the Template

As inverted wingers have made football uniform, so the template T20 batter has done to cricket. Everyone is alike — see off the first six balls, then open up. No one steps outside the line, no one does something strange with the field behind the wicket. Everyone's strike rate moves the same way, because every coach has read the same model.

Here a particular kind of player is slowly erasing — the anchor. The batter who keeps the fire burning at the other end. Think of Mushfiqur Rahim. More than twenty years of international cricket, remaking himself across formats, at one point giving up keeping to focus on batting. His value was never only in numbers; he was the man who stood in a crisis, who steadied the young batter at the other end. Data now labels him slow. Rhythm calls him the team's heartbeat.

I hold a simple view, inconvenient in the age of analysis — modern T20 batting is flattening itself into sameness, and we are losing variety because of it. The batter who hugged the line, who stepped out against spin, who played the strange-angled shot — they are not surviving, because their strike rate does not fit the model. We sell the variety of rhythm for the exactness of numbers.

Muttiah Muralitharan's record of eight hundred Test wickets has not been broken. But his real lesson is not in numbers. He bowled in a way that first looked odd to the analytical eye — a different action, a different angle, a different rhythm. Had a model of that era built him from data, we would probably not have had him at all.

The Emotional Invoice of Data

The story of a player dropped from selection I have seen many times. The decision comes from a slide — average, strike rate, performance against the opponent. The numbers are honest. But what follows does not fit any table. The player picks up his phone and goes home. His father asks why. He does not know the answer, because the model did not explain it to him.

I have a favourite line: a transfer is never just a transfer; it is a stranger who suddenly arrives at your door. Behind every data-driven decision in cricket stands such a stranger — who grew up loving the game, who rose at dawn for the nets, whose parents trembled in the stands.

Tickets, trains, membership queues, class codes — how much people give to love this game, no one keeps the account. Analysis knows how much a match earns. Analysis does not know how a family rides a five-hour train and spends a day in hardship. The gap between these two facts is cricket's real economy.

Look at Shakib Al Hasan's career. His statistics are extraordinary, but beneath the numbers lies the exhaustion of carrying a burden for years — the expectation of an entire nation, every match. Data says he is an all-rounder. Rhythm says he is one man's lone hope for a country. Which is truer?

The Rituals Data Cannot Hold

In June 2026 I commentated on a strange match. A pandemic across the world, more than fifty-five thousand blue seats in the stadium, every one empty. Artificial crowd noise pumped at seventy decibels, yet I could hear every stud. The footsteps of a lone ball boy, the echo of a coach's curse — these became the characters.

That night I understood: cricket's biggest fact lives in no table. It is time. Rain delays, the tea interval, bad light, the long wait — to the eye of data these are only interruptions, waste. But to the cricket lover they are ritual.

Eight hours is not a long time until you spend it inside a rumour. I once spent that eight-hour Deadline Day in a small studio with twenty-two thousand strangers. Data decided nothing that day. Data only showed where the money was going. But the story was elsewhere — in what the family of the boy joining a new club was thinking.

During rain breaks I have often walked into the stands. There is no data there. There is the smell of wet coats, the tea stall, children's slip-up catches, and one elderly gentleman who has sat in the same seat for sixty years. If I ask him why he comes, he will not answer in numbers. He will say, it has to be done. That obligation is the world outside data.

The Contrarian Angle: Is Emptiness Failure, or Honesty?

Now I ask an uncomfortable question. Suppose the empty report in my hands is not a failure. Suppose it is honesty. A machine tested, found no raw material in hand, and so did not invent a false story. It declared — I do not know, because I have nothing to know from.

We treat that declaration as weakness. We want analysis to always give an answer. We want the tables full. But if someone invents a story to fill the table, that is not analysis, that is fiction — bad fiction.

In cricket we make this mistake daily. When a team loses, we hunt for an excuse. When a star loses form, we manufacture a reason. If a Test is drawn in rain, we think victory could have been proven with data. But not every question has an answer. Sometimes the truth is — we do not know.

An old memory returns here. Twenty years ago, when I was moving from one format to another, a veteran journalist told me: write what you know, ask about what you do not, and what can never be known, do not sit down to write at all. He would say an empty column is far more honourable than a false fact.

When writing about a national team's defeat, I keep this in mind. After a loss a silence descends that only exists when a nation forgets how to lose — because it was not used to losing, or had grown used to winning. That silence is not of data, but of rhythm. No strike rate will measure it.

I believe cricket's data industry must learn a new quality to grow — to honour the empty cell. The analyst who does not know, if he admits it, earns trust. The analyst who does not know but speaks with confidence deceives the reader.

Why This Is a Question of Cricket's Future

I know someone will say this is not a cricket story, it is a story of information systems. I disagree. Cricket stands exactly here today — a vast structure of data around it, while doubt grows over how much play lives inside that structure.

In future, selection will become more data-driven. Contract values will be set by models. Coaches will be handed huge dashboards. All of this is good, if we remember one thing — data can supply the basis of a decision, but someone makes the decision. And that someone is human, sitting in the dressing room, whose hands shake, whose father sits in the stands.

I want two kinds of analyst in cricket's future. One will say what happened. The other will say why it happened. The first is a person of data, the second a person of rhythm. Cricket needs both. The problem comes when the first believes he has the last word, and the second is made to stand outside the dressing room.

Takeaway: A Moment Frozen in a Frame

I think again of that studio. The empty report, the hollow cells, the cold tea. The old scorecard on the wall is full — names, runs, wickets, the complete story of a match. And the new report on my screen is empty — no story, because no information.

But between the two lies a bridge I have crossed many times. It is the field. Standing on the field, you understand both data and rhythm are needed, but which comes first, the match decides. Sometimes data wins — a correct review saves a side. Sometimes rhythm wins — a batter defies the statistics and writes history.

If I could give one piece of advice to the cricket lover of the future, it would be this — read the numbers, but do not forget to see the human sitting beneath them. Behind every strike rate is a family, a hardship, an expectation. The day analysis learns to see that human, its cells will no longer be empty.

And that empty report of mine? I did not delete it. I kept it, right beside the framed scorecard. A memento that admitting the absence of knowledge is itself a kind of honesty. In cricket, and in life, both.

I do not know what will happen in the next match. No one does. This not-knowing is what draws us to watch the game. And however powerful data becomes, before the first ball on the field, all numbers suddenly fall silent.