The Empty Spreadsheet: Cricket's Data Economy Has a Silent-Failure Problem

A report was placed on my desk last week. Eight sections, clean bordered tables, a tidy 'N/A' in every row. Title blank, source blank, match blank, player blank. And at the very bottom, a fallback value more honest than any sentence in the document — 'Article Type: Unclassified'. No error raised. No red flag. The system's message was clear: process complete.

On the Times of India sports desk in 2026, one thing was drilled into me — the most dangerous sheet on the copy desk is not the one marked 'story not found'. It is the one that looks fully typed and carries not a single fact. Forty years later, that sheet has come back to me in digital format, with graphics attached.

This document is the most honest piece of cricket's data economy that has reached me this year, because it admitted it had nothing. The five hundred dashboards that land in my inbox every week mostly hide the same emptiness in a better font.

In the nineties, doing commentary for ABC and then the BBC, we had three instruments — a scorecard, a run-rate chart, and a statistician on the phone who could tell you mid-over how many dot balls had been bowled in the last ten. The same broadcast box now holds ball-tracking, pitch maps, win probability and an entire data desk. The money arrived in proportion: the IPL's 2026-27 media rights sold for ₹48,390 crore, a single decisive number for any league in this sport.

That money built an industry whose job is to manufacture numbers. And that is where the trouble starts: the speed of production has always outrun the speed of audit.

On the night of the 2026 IPL final I was in my Pune studio. Mumbai Indians were bowled down to 129/8, Rohit Sharma's side kept Steve Smith's Rising Pune Supergiant to 128/6, and the match turned on 1 run. Pune needed 41 off the last five overs and lost four wickets getting them. I re-scored that chase, and the number that fell out was cleaner than any dew model: Mumbai bowled 18 dot balls in the last five overs. The dew was the first analyst to file a report — but the report that decided the match was filed by the dot ball. I followed the quiet variable until it became the loudest fact.

A year later in Russia I built a public sheet across 64 matches, logged every major bookmaker price, and recorded that France won at 7/1 while Germany went out at the group stage at 5/1. The lesson was identical both times, and it applies to this empty report today.

What I am watching now is this: cricket's data economy has come to treat structural validity as substantive validity. If the frame is right, the columns look populated, the dashboard loads, the work is assumed done. The document in front of me is the purest specimen of that delusion: it raised no error, because to the system an error means 'the format broke', not 'the truth went missing'.

There are three reasons, and all three have been running since the day cricket replaced commentary with numbers.

First — N/A is a boundary, not a placeholder. When I re-scored that 2026 chase, the easy route was to write the dew narrative and put the phone down. It was easy because the dew story explains everything and proves nothing. The work was to write three numbers first: sample size, phase split, one counterfactual. Filling a blank with a story is the oldest habit in cricket journalism. Leaving it blank and writing 'information not available' is a professional act. That report's N/A was not its flaw; it was its most honest line. An empty stadium gave the numbers nowhere to hide; so does an empty report.

Second — the heatmap is the new astrology. I have said for years that a heatmap hides a player's role inside the system. A batter's shot map tells you where he hit the ball; it does not tell you what the team made him do. The pipeline carries the same disease — a populated template conceals the absence of evidence exactly as a dense heatmap conceals the absence of a team plan.

Third — the incentive runs on tempo, not on truth. A broadcaster needs a graphic after every over. A newsroom needs a story every hour. An agency needs an 'insight' after every match. Nowhere in that chain is anyone rewarded for returning 'insufficient information'. The empty shell is not a malfunction; it is the culture's most natural product.

The scorecard is a headline; the receipts are the story. Receipts mean: how big was the sample, which phase does the number belong to, and what would the score have been if the number were wrong. A claim without those three receipts is not a headline, it is noise. And noise's great advantage is that it can be packaged in a clean table.

Let me disclose my own interest. I sell 90-second videos, and their entire value rests on viewers believing I looked at the numbers. If that much trust can be generated inside an empty template, my shop's rent expires the day viewers work out that a platform and a receipt are not the same object. My quarrel is not personal with the pipeline; it is with the claim that a correct format means correct work.

The most dangerous thing here is not that the report was empty. It is that it was silently empty. Cricket has a name for that kind of miss: a no-ball nobody appeals. Play continues, the scoreboard is wrong, and nobody notices until the result changes.

Now the part I would rather skip.

It is possible the empty report was the correct output and the error is mine. The honest answer to most cricket questions is 'insufficient information' — one phase split, a twelve-match sample, runs made in a single domestic season. The moment we fill that blank with narrative, confidence begins. If that is so, then the problem is not the pipeline; it is me, selling noise.

There is also the fact that I am writing on a template myself — hook, context, core, contrarian, takeaway. The man attacking templates runs his column on one. I have no way out of that contradiction, only a condition.

So I will write it now, before publication, the thing that would prove me wrong: if within the next twelve months an automated broadcast segment outperforms the human desk across at least twenty matches — calling a batting collapse three overs early and matching the outcome — I will concede publicly that the problem was never the pipeline but the audit.

My prediction, and note the date on it: inside the next IPL rights cycle, some major rights holder will put a data segment on air whose pipeline has no minimum-population gate. The first embarrassment will not come from a wrong number. It will come from a missing one.

So the next time a clean table appears on your screen, do not look at the graphic. Ask where the N/A is. The report with no N/A anywhere is usually the one that hid the most.

And if you do find the N/A, do not read it as a fault. It is the most honest sentence in the document.