Reading the Empty Scorecard: The Discipline of Saying ‘I Don’t Know’ in Cricket Analysis

The file took three seconds to open. Inside it was nothing.

August 12, Wednesday, half past eleven at night. My flat beside the Baltic Triangle in Liverpool, a laptop open on the kitchen table, a cup of tea going cold next to it. A colleague had sent over a “deep analysis” file. Cricket. Some Asian series. The first page read: Title — none. Source — none. Core viewpoint — blank. Beneath it, eight large headings: format and match analysis, player technique and data, team landscape, league and commercial environment, rules and governance, risk analysis, public narrative, industry transmission. Under each, one sentence repeated eight times: “Insufficient information — assessment not possible.”

I scrolled twice. Then I leaned back in the chair and sat there, not touching the tea.

What I felt that night wasn’t a reaction to analysis. It was relief. Nobody had invented anything. Nobody had dropped a format into the blank space, attached a name to it, or built a story out of a landing leg.

To explain where that relief came from, I have to go back seven years.

The thread that taught me to wait

1. I was eighteen, a first-year kinesiology student at Liverpool John Moores University, writing a blog called The Anfield Load about Liverpool’s under-18s. Ben Woodburn had just played three games in eight days. I worked through the minutes, the injury history, the recovery days, and posted a thread on the striker’s hamstring load. It earned 1,200 retweets. A local editor offered me part-time work covering the under-23s.

Before saying yes, I asked for something: two weeks shadowing the club’s medical staff.

From then on I kept a daily notebook — who played how many minutes, how long each previous injury had lasted, how many days each player took to return. Before posting, I checked training data with club staff. That slow, suspicious habit became the spine of my writing. Not speed but accuracy — that, I decided then, should be the voice of new media.

Later that year I went to Dhaka. Covering the Wills Cup for Prothom Alo was my apprenticeship, and there I learned that a match story does not begin with the scorecard; it begins with the morning practice. Then I stepped into the BPL commentary box alongside Danny Morrison and Athar Ali Khan. Moving between languages and cultures, I saw that the question a viewer asks and the question a professional asks are usually different questions.

July 11, 2026. At Moscow’s Luzhniki Stadium, England lost the World Cup semi-final 2-1 to Croatia. I stood in the mixed zone for three hours waiting for Jordan Henderson. His match workload was 13.7 kilometres, and his face carried more than fatigue. I did not ask about the chances England missed. I wrote 1,500 words on workload and emotional exhaustion; two national outlets syndicated it. That night’s lesson: ask a player about fatigue, not controversy.

July 22, 2026. On the evening of Project Restart, Liverpool beat Chelsea 5-3 at Anfield, and the trophy was lifted in front of 53,394 empty seats. I collected fourteen audio notes — the sound of emptiness, a shout, Henderson’s voice. I filed 2,000 words to a local outlet with no sensationalism, and stayed late to help the skeleton stadium staff.

An empty Anfield taught me that silence has a tempo too — it can be measured, and it can be reported.

The state of the analysis market

In this 2026 tournament cycle, the supply of cricket analysis has never been higher. Five graphics after every over, twenty threads after every match, three hundred videos after every series. Within seven minutes of a result, a piece appears explaining why that result was inevitable.

But the speed of supply and the speed of accuracy are not the same speed. And this is where my eight-year-old notebook earns its keep.

Anyone who has covered cricket for a few years knows a strange reality: the most confident statements about a match usually rest on the least information. Certainty does not require a large sample. It requires nerve — and a reader who forgets.

In the past few months I have read at least a dozen “analyses” in which a Test-format number was dropped into a T20 context, or a bowler’s first-session fatigue in a red-ball game was repackaged as death-overs skill. The reader could not catch it, because the number was true. Only its address was false.

That is where the empty file matters.

A format is not one country of numbers

Cricket has three major formats — Test, ODI, T20 — and their physiological and tactical logic differs fundamentally. A Test bowler’s job is to build a pattern across five days, to come back for four spells of ten overs, to find accuracy inside fatigue. A T20 bowler’s job is to change plan twice inside four overs, to set a field, to force a batter into the yorker-and-slower-ball trap.

A number cannot walk from one format into another — it only travels, and changes meaning on the way.

A spinner’s Test economy can look excellent because wickets sit there, batters wait, and nobody is chasing runs. The same bowler in a powerplay tells a completely different story. Yet in our analysis culture, the format tag is often the least verified thing in the piece.

What I do is write three things beside every number: which format, which venue, and which phase of the game — powerplay, middle, death; or, in a Test, which day and which session. If one of the three is missing, the number does not enter my notebook. It makes my writing slower. But it is why the injury thread reached 1,200 retweets: it was one boy, eight specific days, one specific load — not a vague sentence across three formats.

The humility we have lost about sample size

What football calls the young-player premium has its cricket equivalent at the auction. A teenager with fewer than fifty top-level matches can be priced alongside an established senior. That is not a judgement of form; it is a judgement of possibility — and possibility demands a sample.

My notebook rule is simple: below twenty-five matches, I draw no conclusion, only write the question down. Cricket’s small samples tell beautiful stories — two fifties in three games, five wickets in a series — but long-run form is a different narrative.

Age curves enter here too. A batter’s technique at twenty-four and at thirty are not the same technique, even if the average is identical. A fast bowler’s pace begins to decline after thirty, but the decline is not linear — it arrives in jumps, often after an injury. Miss those two curves and the analysis is just a list of numbers.

The body is the real scorecard

My biggest lesson came from a kinesiology lab, not a cricket ground: decay shows up in tissue before it shows up in averages.

A bowler’s true scorecard is written in the landing leg, not on the board.

The plantarflexion of the foot and the abduction load at the elbow do not appear on a scoreboard, yet they tell you how sharp a bowler will be in the last two overs of a spell. A fielder’s gait tells you what load he carried onto the ground — the weight of his first three steps in the first two overs says everything.

One more thing stopped me repeatedly this season: the way expected-type metrics are entering cricket repeats what happened to xG in football. The metric is not the problem; the problem is that we use it to answer questions it cannot answer. Why a decision was taken mid-match — why the cover fielder moved up, why a spinner was brought on in the powerplay — no expectation model will tell you. Nor a player’s form. Nor the standard of umpiring.

On the last two: in at least four series in the past six months, players in mixed zones have declined to comment on decisions, retreating into polite, safe sentences. The reason is commercial. Contracts, branding, the “politically correct” personal brand — these have removed the exact sentence that would have told the truth. I count the breaths in the tunnel, not the headlines. And what the tunnel’s breathing says is more reliable than the words of a press conference.

That is why, in a mixed zone, my most useful instrument is not a microphone. It is a watch.

The pause says more

In the mixed zone, the pause says more than the answer.

I learned this in Moscow. The question was easy — recovery, sleep, the weight in his legs. He could have answered in one sentence. Instead the man stopped for four seconds. In those four seconds I had the structure of the whole piece: not the arithmetic of missed chances, but how a body carries seven matches of a tournament.

A pause is not a sentence; a pause is information. And it does not appear in any index or spreadsheet.

At the empty Anfield in 2026 I recorded fourteen audio notes. Footsteps, a distant shout, then silence again. I wrote 2,000 words — but the most honest part of the story was those files, which I never published.

Let me be clear about one thing, because it is the centre of my method: I keep separate what I saw myself and what I was told. Two columns on opposite pages. The moment they merge, I stop being a journalist and become the team’s spokesperson. And nobody reads a spokesperson, because everything is already known.

The most honest document is blank

Now back to that file.

A blank analysis report looks like failure. It looks like a broken pipeline, like nobody did the work. But if the source genuinely has no title and no information, then the analyst who wrote “insufficient information” and stopped has produced the most honest document in cricket analysis right now.

“Insufficient information” is itself information.

It tells you about the health of the pipeline, and about the incentive structure. We have built a market that measures an analyst by how fast he spoke, not how correctly. The result is inevitable: the analyst who cannot wait files his injury news first, and files it wrong.

Here is my second doubt. Had my colleague skipped the file and written an educated guess — “bowling depth is under question in this Asian series” — nobody could have caught him. The sentence would have felt true, because in almost every Asian series, bowling depth is under question. False information often arrives dressed as a true sentence.

And this is precisely where our trade is most at risk. We open a blank file, we are disappointed, and from that disappointment we fill the empty space. That is not the machine’s fault. The machine simply returned an empty table. The empty table frightens us because we are used to reading cricket as a story, not as a document.

I have kept a notebook for seven years. Its first page carries one date — those eight days in 2026. Even now, when a young journalist asks me the quickest route to traffic, I say: find a blank space and leave it blank. That is the hardest work there is.

What I will watch next

My expectation for this tournament cycle is simple, and precisely for that reason probably wrong: if boards start publishing load-management data — spell load per bowler, recovery days per innings — the pace of analysis will not fall. It will rise, because the guessing stops.

Until then, one suggestion. The next time a piece tells you that “this series revealed his true worth,” stop. Ask which format, what sample, which venue, and where the injury history sits. If those four answers are missing, it is not analysis. It is only a fast sentence.

And one question remains for me, unanswered: if patience is the greatest virtue in a five-day Test, how do we write cricket in a five-second culture — and who will believe what we write?

I did not delete the file. I kept it, in a folder I named: “What I do not know.”

This week I added a line to the notebook — an empty Anfield taught me that silence has a tempo; an empty file taught me that you only become an analyst once you can measure it.