The Silence of the Scorebook: How Empty Data Becomes Cricket's Most Trusted Story

In the fourteenth over of a match last season, the score terminal in front of me went blank for exactly one second and then refilled — with the non-striker's name attached to the striker. The over count dropped to zero and corrected itself. Nobody in the box noticed, because the broadcast graphic had already moved on and the microphone had already said the batter was 'well set'.

I spent the next two days recounting that passage ball by ball from the video log. Forty-one deliveries. The number I wanted was not the run count. It was how many balls that batter had received in the same length band, and how the crease width had shifted across them. The blank field the terminal showed for one second was never reconciled, because a blank field does not look wrong to anyone.

From the scorer — that was my first lesson. What fails loudly gets fixed. What fails quietly never gets fixed, because there is no visible reason to fix it.

Every cricket number passes through four hands, and each hand is a compression. The scorer turns a delivery into a digit. The feed operator turns the digit into a field. The graphics system turns the field into a picture. The commentator turns the picture into a sentence. What falls out across those four compressions is not noise — it is usually the context without which everything else looks correct.

This season I set one rule for my own work: I do not write a sentence about a number I cannot rebuild myself. The rule sounds harsh until you have paid for it once.

The net run rate column nobody re-added

Everyone reads the net run rate column mid-tournament. Very few re-read its definition. The international playing conditions contain a sentence that changes the shape of the whole table — a side bowled out has its run rate calculated on its full quota of overs, not on the deliveries it actually faced.

A team dismissed for 180 in 41 overs of a 50-over match has, to any viewer, a run rate of 4.39. The table records 3.60, because 180 is divided by fifty, not by forty-one. The chasing side that reaches the target in 30 overs has its rate divided by thirty, not by the full quota. Two different sums inside one match, and both are correct.

I once caught exactly this error in the final table of a domestic tournament. The broadcast graphic had computed the rate on actual deliveries, and a qualification story had been built on it. Re-added from the scorebook, the gap between third and fourth place was 0.11 — and that 0.11 came entirely from the disputed field. No player changed. No match changed. The table's story changed.

That is the scorer's real job: not to describe the game but to challenge its arithmetic. When a side needs 12 off the last over, the question is not how good the batter is. The question is which quota the 12 came from, and what that quota excludes.

What 214 deliveries taught

In 2026, seven years after a shoulder injury ended my Lancashire playing career at 31, I was coaching part-time and filming bowlers on a £40 camera. Over six weeks I logged 214 deliveries from Lancashire's seam attack at Emirates Old Trafford, plotting release points against crease position.

I counted 214 deliveries before the chart started counting me.

The finding was that the right-armers stood 0.4 metres wider to left-handers — a tell that existed in no coaching manual, only in the footage I was watching frame by frame at night. In that powerplay the habit cost 31 runs.

The pitch maps ran on a new digital cricket desk. Three weeks later Lancashire's head coach offered me a formal assistant-analyst post. The same week, a steward at a visiting ground redirected me to the family gate instead of the dressing-room corridor.

Both events teach the same lesson, and it is about sequence, not manners: arrive with the data first, make the argument second. When you have a measurement of crease width, you do not have to argue for your seat in the corridor.

I stopped writing 'he bowled well' and started writing coordinates — crease, release height, length band. Every piece since carries at least one number I collected myself, and there is no tactical claim I will publish that I cannot re-run on video.

An empty field looks like a zero

The industry's largest error sits here. A reader encountering a blank field reads it as a zero. A zero looks like a fact. A fact looks like a story. And nobody audits the story, because nothing in it looks wrong.

The dangerous data is not the data that is false. It is the data that is empty and looks complete.

Compare it with fielding. A misfield is visible — the ball spills, the crowd reacts, the director cuts, the clip runs all night. A wrongly set field is not visible. It stays invisible until the ball goes through the same gap twice, and even then nobody says the field was wrong; they say the bowler bowled the wrong length.

Data behaves the same way. A misspelt name is corrected within minutes because an eye lands on it. A miscalculation runs for weeks because it produces no visual cue.

When cricket returned in 2026, Emirates Old Trafford was one of England's two bio-secure venues. I spent eleven weeks inside the bubble on the support staff — England v West Indies and England v Pakistan behind closed doors.

There was no crowd, so the stump mics picked up everything. Across 12 matches I logged 1,900 audible calls: fielders talking, bat edges, bowler frustration. Mid-pitch communication errors fell by roughly a third in the silence, and by the third match fielding sides had switched to coded calls.

Eleven weeks in a bubble made the outside feel like a tactic. It also gave me a working habit I still use: I transcribe the stump mics before writing a word about a batting collapse. With no crowd, there was nothing to blame, so only a decision remained to describe.

The same disease at the auction table

At the 2026 mega auction I sat in on a franchise's analytics contract in Bengaluru — 600 shortlisted players, a ₹90 crore purse, ten teams rebuilding from zero.

I did not build a best-player list. I built a role-scarcity model — which block each team had to fill, how much supply existed for that block, and what that supply cost. Our franchise walked past the two biggest overseas names and bought three bowlers for ₹11.4 crore combined.

That is not a success story. It is an audit story. Every team at an auction holds a list, and the list is usually made of names. A name is a convenient unit: it can be put on television, sold, argued about. A role cannot be sold. So the tables fill with names and the teams are built out of roles.

After that auction I deleted one column from our sheet — 'best player ranking'. Three columns replaced it: which over block needs filling, how many domestic options exist for that block, and what the dependency cost is on an overseas option. More columns, fewer places to be wrong.

The contrarian angle: the data desk did not win the argument, it changed the language

The accepted story is that data desks won cricket's tactical argument. Look at the mechanism and what happened was not a victory but a transfer of vocabulary.

The number of people who can produce a chart went up. The number of people who can re-run one went down. The first is a tool skill. The second is a hand skill. Tools get easier every year. Hands do not.

So the debate moved from territory to taxonomy — from 'this player is elite' to 'what is this player's powerplay strike rate'. The question improved. An improved question does not mean a verified answer. A better question attached to an empty feed produces the most refined form of falsehood available, because nobody can accuse you of not watching. They have to accuse you of not counting, and demanding a count is now considered rude.

The bubble gave me one more thing. With no crowd, there is no external cause of defeat left. No roar, no pitch noise, no ambient pressure. What remains is a decision. Silence is a tactical variable — and once it is measured, the excuses disappear.

The same measurement should be applied to cricket's data. When a table arrives, the question is not how good it looks. The question is which field in it is empty, and how that field was filled.

What to check next

At the next tournament table, do not ask whose run rate is better. Ask whether the all-out innings in it was divided by the full quota — because that single field decides third from fourth and it is mentioned in no commentary box.

At the next auction, do not ask who the most expensive name is. Ask which role is scarcest, because prices are set by role scarcity while headlines are set by names.

And at the next broadcast, watch the fourth over of the second innings. That is where the feed is least supervised — everyone watches the first over, everyone counts the last, and the fourth over in between belongs to nobody.

I watched thirty-one matches from outside and found the game inside. The game inside was never in the graphic. It was in the field that was blank, and that nobody felt the need to fill.