The Tournament of the Blank File: When Cricket's Loudest Claims Travel Without a Single Count

On Wednesday afternoon a file arrived on my desk with eight sections. Format, match nature, key-phase performance, venue, weather, player data, squad structure, league economics, governance, risk matrix, public narrative, industry transmission. Every cell said the same thing — N/A. One line was brutally plain: "No information points provided." No source name. No publication date. No team. No player. No format. Every row of the risk matrix repeated the same sentence: "Cannot assess."

And on that same afternoon, inside the same tournament cycle, the claim this file was commissioned to verify was still moving across the timeline. A claim about a margin. A claim about a bowling plan. A claim that "the change had to come." A claim that "his form has returned." Everything was there except one thing — a count.

I opened the file again, then a third time. I am the kind of man who watches the same over three times, so I did the same with a spreadsheet. First reading: someone had been careless with the boxes. Second reading: the entity-extraction stage had quietly died. Third reading: this file was not reporting on cricket at all. It was reporting on verification.

Twelve parts in, the thread stopped being a thread and became a badge. That is my oldest habit, and in this tournament cycle it is the one earning its keep.

What the sheet is, and when it lies

Cricket has a particular shape of deconstruction. You take an event — an innings, a retention, an auction price, a broadcast filing — and break it into segments. Then you place a question against each segment. What is the format? What is the nature of the match? What happened in the key phase? What does the venue say? What do weather and dew say? The player's average, strike rate, economy, situational splits, recent trend? The team's batting depth, bowling combination, bench depth, age structure? Broadcast-rights value, franchise valuation, player salaries? Power and revenue distribution, playing-rule disputes, integrity, eligibility and selection, political factors?

The sheet is not a paper instrument. It is a habit instrument. Its entire load-bearing capacity rests on one thing — numbered information points. Facts that can be counted, dated, and independently checked by a second person. The moment information points stop arriving, the sheet changes status. It stops being an analytical tool and becomes a form in which every field says we do not know.

I write from Manchester, and that fact is the foundation of this entire piece. From here, Chepauk's heat reaches me through a stream, pitch wear through a scorecard, crowd silence through a clip. My distance can hand me the false confidence of clarity, which is why every claim I make must travel with a count. When I say a bowler loses his length in a third spell, I need the number of deliveries on which that length broke. When I say a batter has started playing outside cover, I need a record of fielder depth. Otherwise I am doing what the commentary box does — sitting in a studio and calling guesswork analysis.

A tournament cycle inflates the problem. In an ordinary week the desk receives five claims a day. During a major tournament it receives fifty, and half of them have no source, no date and no format. The pressure of flag and story is so great that the verification queue runs short. Readers swim in emotion, and the analyst is tempted to swim with them. This is where my one condition sits, and it is not negotiable — a claim that arrives without a format, a source and a date has no right to join the verification queue at all.

A blank file is also a result

At first glance, a blank file means no result. I think that is wrong. A blank file produces a firm, useful, verifiable finding: the input is incomplete.

This is not a joke; it is the most neglected fact in media operations. When a sheet with eight sections returns zero information points, the sheet is not saying nothing happened in cricket. It is saying that the material sent for analysis contained no entity, no format, no event and no source. Every row of the risk matrix is empty because it has not been established whose risk, in which season, for which team. All three links of the transmission map — youth development, national teams and leagues, broadcast and commercial markets — read N/A, because there is no event to flow from top to bottom.

There is a clear benefit here. When the material is empty, the analyst has exactly one honest route: to write that he does not know. And that is hard to write, because a tournament cycle treats "I do not know" as weakness. But I have a lesson that arrived in 2026.

Four thousand three hundred balls of silence, and I counted every one. That was the bio-secure summer when England's series against West Indies and Pakistan were played behind closed doors at Emirates Old Trafford. Lancashire had furloughed a third of the performance department and six staff were allowed inside. I was one of them. There was no crowd, so the stump mics carried everything. I logged 4,300 deliveries with the audio track open, recording which bowler-batter exchange preceded which length. For four months nothing publishable emerged. I watched the same overs twice, then a third time, and filed it all under research.

That period taught me that an empty result is still a result, provided you say plainly what is empty. A blank file says nothing at all about cricket. It says one very clear sentence about process.

No format means no legal benchmark

The most irritating line in this file was this: "Format: N/A." That does not mean the format was difficult. It means I cannot even establish whether anyone was discussing Test cricket or T20.

This sounds technical. It is actually the door to the whole analysis. A Test average and a T20 strike rate belong to different worlds. An opener averaging 42 in first-class cricket does not give that 42 any meaning in T20. A spinner conceding 2.1 an over on a fourth-day pitch cannot be measured against a powerplay benchmark. With no format fixed, every comparison becomes illegitimate. The greatest danger is that the analyst quietly picks whichever format suits him — the one in which the player looked good — and lifts that number.

Here I must confess a sin of my UK base. The analytical vocabulary built in England — county workloads, rotation metrics, the pre-meditation language of Bazball — was calibrated for English pitches, an English schedule and an English board. Applying it unchanged to Indian conditions is dangerous. In India the domestic calendar bites differently; the Ranji schedule, the IPL window and the BCCI's international calendar are three separate clocks running at once. A metric that works in England only applies in India after translation. And if it breaks in translation, I have to say so in print rather than hide it.

The commonest professional error is treating an imported metric as neutral until it has been tested against Indian conditions and the BCCI calendar.

Toss, DLS and home ground: stripping the noise off the result

Another line in the file unsettles me more than the rest — "result-versus-process analysis cannot be performed: no result, margin or match events are reported."

That line is the spine of my work. In cricket the result is the least reliable data point and the most heavily sold. A team wins by four wickets and by the next morning the verdict is that its planning was superior. The planning may not have been superior at all; the coin fell its way, dew arrived in the second innings, and DLS reshaped the target into something it never originally was.

I always remove three things first. The toss — what was chosen after winning it, and how much that choice shaped the first-innings score. Duckworth-Lewis-Stern — a rain-adjusted target can render a batting card meaningless, and a strike rate in a reduced-overs innings cannot sit beside a strike rate in a normal one. Third, home-ground bias — an average built at home tells a different story from an away average, and merging the two is the laziest dishonesty in data work.

DRS is even more tangled. Umpiring controversy surfaces in every tournament cycle, and every time the same sequence plays out: emotion first, count later. I do not think DRS should be treated as an explanation of a result. It belongs in a separate column headed "decisions technology overturned, and their effect on the score." If that effect can be counted, it is analysis. If it cannot, it is noise. And dressing noise up as analysis is the oldest habit in this trade.

A result is one sentence; a process is a hundred-page file. Those who build files out of sentences are writing stories, not sport.

Twelfth to sixteenth: the count that never comes back blank

The most startling part of this blank file was where squad structure should have been. Batting depth, bowling combination, bench depth, age structure — all four read "no squad details provided."

For me that is impossible. Bench counting is the easiest and most necessary count in the world. You do not need a pitch, weather or DRS. You need a squad list — names, numbers, ages, domestic sides, recent domestic seasons.

This is my firmest opinion and it comes directly out of the work. India's second XI is the hardest team in world sport, which makes selection the story, not talent. The men sitting from number twelve to sixteen are the ones who never appear to win a series, yet the entire structure of a series rests on their quality. One injury, one bad run, one visa problem, and the twelfth man is standing at the crease on day three.

This method was born in 2026. I was 33, nine years into freelance radio shifts, holding a broadcasting degree I had never used on air. That year I wrote a twelve-part breakdown of T20 death-over geometry from 1,140 balls of Lancashire's 2026 NatWest T20 Blast footage — where yorkers actually landed against where fielders actually stood. Lancashire's T20 coach read it, argued with me for two hours about third man, and hired me as video analyst at Emirates Old Trafford. The job came with a desk behind the dressing-room door, no microphone, and a laptop that crashed every fourth innings.

That is where my writing changed. I stopped writing about shots and started writing about squares. A bowler's identity began at his release point rather than his reputation. Every claim carried a ball count. And I began ending each piece with the single number my model could not explain. Readers started quoting it back at me.

When it comes to the bench, a blank file buys no excuses. Squad lists are public. Counting fifteen names takes three minutes. A writer who cannot count fifteen names — what exactly will he tell you about the four thousand deliveries he never watched?

The paperwork is the power: retention slabs, auction purses, broadcast filings

The league section of the file was equally vacant. Broadcast-rights value: cannot assess. Franchise valuation: cannot assess. Player salaries: cannot assess. And the auction-and-transfer section was barren.

I find that vacancy honest, because my view here is plain. IPL auction purses, retention slabs, broadcast filings and BCCI calendar decisions are the real text of Indian cricket. Covering a board's press conference will never give you what its files give you, because the money that runs this game is administered in an office, not performed on a stage.

I have an expensive example of this. In January 2026 I wrote a forty-page pre-auction file arguing that my Lancashire teammate Jos Buttler was worth double his likely price as an opener. At the Bengaluru auction Rajasthan Royals bought him for ₹4.4 crore, pushed him to the top of the order in April, and he made 548 runs in IPL 2026 with five consecutive fifties. Lancashire responded by making me assistant coach for the 2026 Blast.

The 4.4-crore file stayed closed for a month, and that was the work. The file was right about the player and wrong about nearly every other price in the room — a fact I noted in the margin and never published.

That single episode permanently changed how I write. I now separate the mechanism from the money. Auction pieces open with the match-up and bury the figure in the fourth paragraph. I am interested in what a room cannot see, not in who will pay what. Editors who wanted a price list stopped calling; the ones who wanted an argument started.

Every transfer window is a spreadsheet pretending to be a story. That applies to cricket as much as football. The prices settled on auction night say less about a player's value than about a room's need. One franchise buys three spinners because its home pitch dries out; another buys three quicks because its calendar begins in April. That is not cricket — it is geography and scheduling.

The model's 40%, and the column that is always full

Everything I have argued so far rests on one belief: that counting is possible and that counting tells the truth. That belief is necessary and incomplete. This is where the trade's biggest deception hides.

In July 2026 England chased 378 to beat India at Edgbaston, their highest successful Test chase. Jonny Bairstow finished 114 not out, Joe Root 142 not out. I spent three weeks coding all 79.4 overs — fielder depth at release, how many stood outside the frame, how early each batter committed. The pre-meditation index that emerged explained roughly 60% of the innings. In a 6,000-word piece I published the model in full and then named the 40% it could not reach. That 40% was, more or less, Jonny Bairstow.

Writing the limits of my own model changed my sentences. "Probably" stopped being decoration and became structure. I began marking the exact over where my explanation ran out. The pieces got longer and more honest, and I stopped pretending that a clean diagram was the same thing as a correct one.

I keep a column for what the model cannot see. It is always full.

In this tournament cycle that column is fuller than usual, because the file came back empty. When there is no data, one hundred per cent of the model relocates into that column. That is not a tragedy. It is an honest position, and every analyst should be forced to admit it at least once a month, or his confidence will outrun his evidence.

The real blind spot: we audit the claim, never its address

Now the part where I disagree with my own trade.

When the blank file landed, my first reaction was to ask why it had not been filled. My second was to ask whether the claim it was commissioned for should be checked too. My third, and least comfortable, was this — we are professionally auditing the wrong thing.

We look inside the claim. We ask: is this number right? Is this margin right? Is this average right? We argue, we screenshot, we build threads. And we never ask where the number was born. In which match. In which format. On what date. From which source.

That is the real blind spot, and it does not sit inside the claim — it sits in the claim's address. Debating the contents of a claim with no source, no date, no format and no entity is the single greatest waste of time available. You are repaving the floor of a building with no foundation.

There is an obvious reason, and a tournament cycle sharpens it. Arguing pays; provenance-checking does not. Say "that statistic is wrong, here is the right one" and you get attention. Say "that statistic has no source" and you get called tedious. The entire media structure rewards the first.

I should also admit my own weakness. My verification compulsion is strong enough that I sometimes pile on so many qualifications that no claim reaches the reader at all. That is a failure too. So I have a rule: every piece must contain one plainly stated, falsifiable assertion, placed early. The caveats can work around it; they cannot erase it.

The second thing this trade must accept is that tournament cycles do not lack data — they flood with it. Every over, every angle, every graphic. The problem is that what can be counted is not always what should be counted. I spent the longest stretch of my career learning what to count. I spent longer still learning what cannot be counted.

Which is why a blank file is a relief. It removes the excuse. No model, no index, no diagram. When the data is zero, all that remains is the source, the demand for a count, and the plain admission that I did not watch it.

What to look for off the next ball

This whole exercise produced one conclusion, and it is not about cricket. The next time a large claim arrives — "his form has returned," "this is the payoff of squad depth," "the change was demanded by the situation" — there is only one question to ask, and it is a polite one: how many deliveries come with this, which format, and what is the date?

If an answer comes, there is an argument to be had. If no answer comes, there is no argument — only a blank file, which belongs in a drawer.

I know that in the next match I will do the same thing again. The stream will be on, the scorecard open, and I will watch the first over twice, then a third time. And that column will contain something the model cannot see. The only question is whether I hide it this time, or make it the headline.

Because the day we stop being embarrassed by blank files is the day counting finally outranks storytelling in cricket coverage.