The Broken Chain: Cricket's Invisible Ledger and the Testimony of Data

A single word hangs on the screen — N/A. Eight analytical dimensions, each with a flawless framework, and nothing inside. This week, in a small editorial room in London, I watched exactly this: a data pipeline whose first stage came back empty-handed — no title, no source, no information points, no entities identified. The second stage could only end with one sentence: insufficient information, analysis not possible.

But that blank screen is the most honest portrait cricket analysis has ever shown me. The faster we sprint toward data, the fewer questions we ask — where did this information come from? Whose testimony is it? From which point to which conclusion can we trace it? Cricket today stands on an invisible ledger, where every run, every dot ball, every review is deposited. There is only one question — who keeps the ledger, and does anyone verify it?

I have watched this game for eighteen years. When I started a small social-media page from Dhaka in 2026, cricket analysis meant paper and pen — strike rates, bowling averages, and a few memories. Today, at a desk in London, I see thousands of data points every over — ball-tracking, edge-detection, expected runs, win probability. There is so much information that the question is no longer "what happened"; the question is "which information is true".

In the DRS era we have grown used to a false comfort — that technology means neutrality. Ball-tracking shows where the ball pitched, where it would have struck the stumps. But technology only supplies data; interpretation is human. And that space of interpretation is the weakest link in the chain today. When an umpire's call is questioned, we turn to the technology; yet explaining the technology's output is also a person's job.

A piece of cricket analysis is really a chain — one block after another. The first block: raw information, the scorecard and ball-by-ball account. The second block: context — venue, conditions, format. The third block: interpretation — who did what, and why. The fourth block: the conclusion. If the first block is empty, then however beautiful the remaining blocks look, it is not analysis — it is arranged ornament. That is why an honest analyst, handed an empty input, cannot write "team X will probably win"; he writes, "I do not know." When one link in the chain of information breaks, the whole analysis collapses — and this is the most neglected truth in cricket journalism today.

Here lies the central lesson of the blockchain. On a blockchain, once an entry is written it cannot be erased or altered; each block carries the hash of the one before it, so if a single link in the chain breaks, the entire system catches it. Cricket's information should work the same way. When an analyst writes that "a certain bowler's economy is a concern," there should be a verifiable source behind it — which match, which over, which opponent. Without this chain of custody, analysis becomes a marketplace of opinion, where the louder the voice, the more believable the claim.

I have made this mistake myself. In 2026, sent to Russia to cover the football World Cup, I did not sit in the press tribune — I sat in the fan zones. What I learned there was outside the data, yet verifiable. Harry Kane won the Golden Boot with six goals; but what I remember is a bricklayer from Sheffield crying into his flag at two in the morning. Which information is "true" depends on which block you start counting from.

Or take Lord's, 14 July 2026. England versus New Zealand, the World Cup final. The match tied; the Super Over tied. In the end it was decided on boundary count — England 26, New Zealand 17. A rule written on paper settled the fate of a game. This is the most disputed entry in cricket's ledger. The information there was clear, but the interpretation rested in human hands — and that interpretation could not be independently verified by anyone. The technology delivered a result, but not a definition of fairness.

This is why I distrust metrics like expected runs, or xG. These numbers cannot explain why a decision was taken, why a player is out of form today, or why an umpire applied a different standard. The number is the ledger entry; the understanding is its context. Two different things — and yet we confuse the two. A metric that cannot explain the decisions inside the game forfeits its claim to explain the game.

Now to the uncomfortable side we avoid in the crowd of the data festival. Cricket analysis's real crisis is not a shortage of information — it is a surplus of it, and a blind faith in that surplus. Every broadcast now pours half a dozen graphs onto the screen; after every match come ratings, impact scores, match-ups. But the question is whether these numbers help us understand the game, or merely look good.

Borrow an example from football. The possession statistic is the most deceptive number in that game. A team can hold 60 per cent of the ball, passing sideways again and again, and create nothing in attack. The number is true, but meaningless. In cricket, dot-ball percentage or strike rate, stripped of context, performs exactly this deception. Information is never false; information is only incomplete. And passing off incomplete information as complete truth is the broken link itself.

In 2026 I wrote six long features called "The Silence Series," when Covid sent football back to empty stadiums. I collected 340 voicemails from supporters — people describing, in their own words, what they missed. No data dashboard could put in my hands what those voices did. The lesson is simple: where analysis stops at the number, human testimony moves ahead. And cricket's own strength is this — a game that banks three hundred balls in a day, that keeps a testimony for every ball. This is the game's own blockchain, one no one can erase.

Look at team selection and the transfer market. The price wars between big clubs are really brand wars; real value is created at smaller clubs, where scouting rests on verifiable information, not hype. A footballer does not merely change teams — he moves house with his family in public. In cricket too, if who plays for the national side is settled only on the most recent scoreline, the method is wrong. The right question: by what process was this decision made, and where is its evidence? Here the blockchain principle becomes relevant — evidence before decision, process before outcome.

Every pitch is a page, and the crowd writes in the margins. But to keep that writing alive we need a chain that pulls every claim back to its source. The best columns are not argued; they are witnessed.

So what is the way forward? First, keep a source behind every claim — which match, which date, which database. Second, do not fear the empty input; "I do not know" is an analyst's bravest sentence. Third, read the number and the testimony together — the ledger entry and the human voice, both. Fourth, weight process above outcome, because an outcome lasts a day, a process a decade.

Back to my desk. The screen still says N/A. But now I do not see it as a failure — I see it as a warning. Analysis that cannot be verified fails its own test; cricket that keeps no testimony fails the game. In the next innings, when someone makes a forceful claim again, ask — which block did this come from? If the answer is empty, it is written not in the ledger but in the air. And writing in the air does not survive ten years.