The Scoreboard Filled With Empty Data: Why Cricket's Analytics Revolution Stalls Where the Real Match Begins

In a Bengaluru studio last year I watched a screen that told me, with total confidence, which bowler had been the most effective of the match. There was a name, a percentage, a graph. The next morning I met the bowler himself, and he mentioned that his wrist had been sore that night and he had not told the coach. The data was complete. The information was not. That gap sits at the centre of cricket's analytics argument today, and it is not a technical failure so much as a reporting one.

A document reached me that looked, at first glance, like a deep analysis of cricket. The title field was empty. The source field was empty. The summary field was empty. Only one tag was filled in: cricket_world. That tag alone opens the real problem. In our industry the most populated part of any document is now the label, and the emptiest part is the question.

When the frame exists and the substance does not, what survives is not analytics but a skeleton. Over three years I have seen at least a dozen dashboards built for IPL and international coverage, thick with expected runs, wicket probability and matchup matrices. When I asked their makers where the most basic thing lived — which player played through which injury on which day — the answer was usually that the data sits "with the team." The information that matters most is the information least shared.

This is not only an Indian problem. At the 2026 World Cup in Russia I spent two evenings with a Croatian stringer who taught me that every tournament is also a translation problem. Data speaks English; the ground thinks in Hindi, Tamil, Bangla and Sinhala. When an analyst says a batter's strike rate is 12 percent below his career average, he does not say the man's wife was in hospital that day or that a contract conversation had stalled. Analytics that walks into the dressing room is often detached from the rhythm of the match, because it treats the match as a list of events while the match is a sequence of decisions.

My cleanest lesson came from 2026, when at 44 I ran the live blog for the IPL final. Mumbai Indians made 129/8 and beat Rising Pune Supergiant by one run. I built a widget around Krunal Pandya's 47 off 38 and wrote a 600-word underdog sidebar, and the speed thrilled me. What was real that evening was not the metric but the phone call to Krunal's father. I decided then that every match file would carry one human detail. That decision also taught me that a live blog is a stadium with no walls: fast, but without memory until someone writes it long.

The biggest problem in cricket analytics today is not mathematics. It is provenance — not knowing who produced a number, when, and under what conditions. I have seen models that normalise for weather to produce batting averages without noting that humidity was 84 percent and the spinner had tape on a finger. When the source vanishes, the number stops being advice and becomes rumour, and rumour has only one use in cricket: to cut someone.

That produces a contradiction the media under-covers. Teams buy data and do not share it. Broadcasters build graphics and do not disclose their sourcing. And reporters, who hold the least data, are forced into the fastest conclusions because the live blog does not pause. The result is that in the one era where cricket has more data than ever, our reporting is less verified than before. After 37 years since 2026, this is my bitterest observation: a shortage of information never damaged journalism as much as the appearance of information has.

The other half of the argument is that data analysts now influence dressing-room calls — who plays, who rests, who is promoted. I do not call that wrong outright. But a model can tell you which delivery is most likely to dismiss a batter. It cannot tell you what that batter promised his son on the phone that evening, and cricket's biggest turns are often built on exactly that promise.

My objection is not to data. It is to data being treated as evidence when it is only observation. Journalism's job is to place observation in context — to say on what pitch, in what weather and under what pressure 145.2 arrived. Without that, we convert a player into his numbers, and then those numbers set his price at the next auction, so a man's future is written by a figure nobody audited.

There is one more discomfort. A tag like cricket_world is innocent in itself, but it creates the illusion that the subject has been settled. For me cricket_world is not only matches, teams and transfers. It is the curator, the regional commentator, the Ranji professional, and the press conference nobody attended. Filing a story into a single tag cuts away its most necessary human part. An empty form with only a label filled in is the loudest warning my profession can receive: we built the structure and forgot the substance.

The reverse is equally true. When crowd noise and data disagree in the same direction, I trust the story. In a Ranji knockout last season I watched a fast bowler whose figures looked ordinary while he kept landing the ball on second slip. No camera was on him. In the scorebook that over was just an over. For that young man it was an entire career. That is where analytics and reporting must meet — starting from the number and walking to the person the number rests on.

I am not asking for less data. I am asking that a number's source matter as much as the number. Until every public cricket figure carries a note on where it came from, much of analytics will remain guesswork, only now delivered with decimals.

The next time your phone shows a new "impact score" for a batter, ask one question: who can testify to this number? If there is no answer, you are reading the same report I saw in that empty form — no title, no source, one tag holding it up. And cricket's longest match only begins when someone is willing to say what they saw, where they saw it, and whom they asked.