Empty Data, Full Confidence: Cricket's Analysis Economy Has a Bigger Problem Than Wrong Numbers

It was 2:47 a.m. in a small room outside a broadcast studio in Abu Dhabi, and the fifteen-page "match insight pack" in front of me had a headline on page one — 'Powerplay Efficiency: Trends and Deviation' — four colour-coded charts, two gauges and one heat map. Under every chart, in the same light grey font, the same line repeated: 'insufficient information'. An eighteen-year-old production assistant was looking at me with a marker in his hand. 'Do we take this on air, sir?' I asked him which format it was. He turned page one, then page two, then put the marker down without saying anything.

I closed the pack that night. It did not close. Over the next three months the same shaped pack arrived from four different production houses — headings complete, charts complete, the conclusion column empty. Every page carried the confidence that only a populated document can carry, and every cell carried an emptiness nobody had filled.

Before you decide this is a story about software, let me take you to the evening my doubt began. 19 September 2026, Sheikh Zayed Cricket Stadium. Empty seats, and piped crowd noise fixed at 65 decibels. I called twenty matches at that ground that season. Inside the bio-bubble we heard everything a full stadium never lets you hear — a bowler swearing, an umpire breathing, the flat sound of ball on pitch that a crowd always buries.

During that stretch I started a WhatsApp group with fourteen grounds staff, scorers and stranded fans so that somebody would tell me what a match feels like when nobody is watching it. The overnight fan desk taught me that fandom is a night shift of hope — and the hardest labour on that shift is not scoring, it is sourcing.

From scorebook to screen: the life of a feed

When I covered my first Test as a freelancer in 2026, I saw for the first time how many hands a single run passes through. The scorer fills the sheet in the box. The sheet enters the board's feed system. An agency picks it up. The agency feeds the broadcaster's graphics server, the graphics server feeds the analyst's deck, the deck feeds the commentator's monitor, the monitor feeds your phone. Something is dropped at every handover — sometimes context, sometimes the format, sometimes the timestamp.

The biggest lesson from my cross-domain columns — 'Out of the Box' in The Indian Express and 'Hitting Hard' in The Sportstar — was this: when you come from outside cricket, you ask where the number came from before you ask what it means. People who come from inside the game tend to do it the other way round.

Consider the economic weight of that chain in 2026. Data rights are sold alongside broadcast rights. A league has its own data partner, a board has its own, a broadcaster has its own graphics engine. Windows like the ILT20 are not just calendar slots; they are data-production windows. When the UAE fills its grounds in January, the pipeline behind them is running at full capacity too. The league that gets the better window gets the better visibility, and whoever gets the better visibility gets their numbers cleaned more carefully. Information in cricket is distributed the way money is, and with the same inequality.

Format is the anchor that makes a number mean something

January 2026, Sydney Cricket Ground. India declared at 622/7 and Cheteshwar Pujara made 193 off 450 balls. Work out the strike rate: about 42.9. Drop that number into a T20 match and it loses you the game. That same number built the whole architecture of India's first series win in Australia in 71 years.

This is where cricket analysis makes its most common error. A strike rate of 145 is elite in ODI cricket, ordinary in T20 and all but unimaginable in Test cricket. The number is not lying. What is happening is that without a format tag, a number loses its location — and a number without a location is not analysis, it is noise.

18 June 2026 gave me the second lesson. The Champions Trophy final at The Oval. Pakistan made 338/4 on the back of Fakhar Zaman's 114 and bowled India out for 158, Mohammad Amir taking 3/16, a 180-run win. I was on a junior digital desk in Abu Dhabi, tasked with a 4,000-word overnight live blog built from 41 reader voice notes. Forty-one voices, one match. Not one of them said 'a 180-run defeat'. One wrote: 'The shadow of the Pakistani fielder fell under the floodlights and I cried.' Another: 'I told my son to watch Amir's spell again.'

I stopped opening with the result after that night. But something else became clear: 180 runs is a format-specific, venue-specific, toss-specific number. Put it in the same chart as a T20 hundred the next year and the chart will not lie. Its designer will.

Sharjah's microphone and the fiction of home advantage

December 2026. Sharjah Cricket Stadium handed me a microphone for the inaugural T10 League: six teams, ten-over innings, and a crowd of about three thousand that sounded louder than any full house I had sat in. That night I learned that a crowd's size and a crowd's volume are two different things, and we measure both with one number called attendance.

Sharjah gave me a microphone and taught me to leave room for the crowd. That is not an editorial habit, it is a technical requirement. On a ground with no home team, the 'home advantage' in the graphic becomes a fiction. Three thousand people, half of whom may think in Malayalam and half in Punjabi, half born in Sharjah and half in Thiruvananthapuram — their noise belongs to no side. It belongs to the match.

That was sharpened in 2026 when Sheikh Zayed had zero spectators. What survived as home advantage was purely technical: knowing the pitch, the humidity, the dew. The crowd's pressure disappeared, and so did an entire theoretical support for the way we explain results. When the UAE now fills its January ILT20 window, the stands are mixed in the same way. The noise out of those stands, in my experience, is more honest than any home crowd's.

The template trap: the real danger is not a wrong number

Back to the fifteen-page pack. Eight major headings — format and match analysis, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk analysis, public narrative, industry transmission. All eight headings were present. Under all eight were tables. In the tables were cells. In the cells: 'insufficient information'.

A fully populated eight-dimension framework does not prove that analysis exists; it proves that the shell of analysis exists. And a reader cannot separate the shell from the substance.

The pack contained a risk matrix: seven rows, four columns, every cell reading 'undetermined'. I asked the producer how he intended to read it. 'So that means no risk, sir?' That is the exact point where the language of analysis converts into trust, and trust stops being trust and becomes habit.

Absence of evidence and the presence of innocence are different findings. An empty integrity checklist is not 'clean', it is 'unverified'. Reading a blank risk matrix as 'no risk' is a worse error than misreading a strike rate, because it removes the space in which a correction could happen.

I now have a rule. Before any pack goes on air I ask three questions. What is the format? What is the source timestamp? Who extracted this, and did they put their name on it? If any one of the three has no answer, the pack stays shut. That rule has kept at least nine graphics off air in two years which would have shown true numbers and told a lie.

We audit players. We never audit the feed

Cricket media's default belief is that more data means better coverage. That holds up to the point where the data is verified. Past that point it reverses: more data becomes more confidence, and confidence becomes a brand.

We audit a batter's elbow, backlift, line and length every week. We have never audited the feed that brings those numbers to us. We have never asked whether the scorer had a backup, whether the agency ran two servers or one, or what happened to last season's numbers when a board changed its data partner.

There is an inequality here that cricket prefers not to discuss. When a smaller team beats a bigger one, its best players are signed away the following season — the win becomes the prelude to another raid. Information behaves identically. An associate board without data staff outsources its score, its archive and eventually its story. The next time that team produces an upset, the story will be told by whoever owns the feed, not by whoever won the match.

There is a second face to the same inequality. Deep squads turn the final twenty minutes into a war of attrition under the five-substitution rule, and the data version of that is already here. A broadcaster with a deep analytics bench turns the last ten overs into a graphics contest; a broadcaster without one loses the audience inside that contest. Capacity is not the same thing as fairness.

Following the money is not a betrayal of fandom. It is the most honest form of it. Broadcast contracts, auction purses, scheduling windows, data rights — the most fan-friendly stories in this sport hide in those files. When you ask why a match is at this hour, you are really asking who it is for.

The frame that stays

I do not think a fan will remember, ten years from now, what a team's expected runs were on a given night. I think they will remember which way the man watering the outfield at Sheikh Zayed was walking while 65 decibels of fake noise played. They will remember how a fielder's shadow fell under the floodlights. I write a memory line into every match piece — the detail a fan will still repeat a decade later. To that habit I have added one more: naming the source the line came from.

There will be more data next season, brighter graphics, fatter packs. The question is not how much data you have. The question is when you last asked where a number came from — and whether, when the answer did not arrive, you let it stay on screen anyway.