Where the Review Chain Breaks: Why Cricket's Decision Log Needs Blockchain-Style Integrity

The Broken Helmet and the Stopped Clock

November 6, 2026. Arun Jaitley Stadium, Delhi. Bangladesh versus Sri Lanka, a World Cup group match. In the 24th over of Sri Lanka's innings, Angelo Mathews walks out to bat. He does not face a ball. The strap on his helmet has snapped. A replacement is being fetched from the dressing room. On the ground, a two-minute countdown is running, and nobody is stopping it.

Shakib Al Hasan appealed to the third umpire. The third umpire checked the screen, checked the playing conditions, and ruled Mathews timed out. The first such dismissal in the history of international cricket.

Bangladesh won that evening with 53 balls to spare. Shakib made 82 and took two wickets and was named player of the match. Yet the most replayed frame of the night contained no cricket at all — only a stopwatch.

I was watching from a desk in Dhaka with my own review-log template open in front of me. The question resolved itself quickly: whether the call was right or wrong is an argument. Whether anyone can audit how the call was reached is a structural fact. Nobody can. A process that cannot be audited does not earn trust, even when it follows the rules.

The Chain We Never See

The Decision Review System was first used in July 2026, in the India–Sri Lanka Test at the SSC in Colombo. A decade and a half later it is a permanent fixture, and since the mid-2010s the ICC has effectively made it mandatory across formats.

What DRS does is not verify a decision. It recalculates one. That distinction is small and enormous at the same time.

The on-field umpire gives a verdict. The batter reviews. The third umpire examines a handful of camera angles, studies a ball-tracking projection, listens to a snickometer or UltraEdge window, applies a threshold, and rules. The whole thing takes seconds to minutes. A graphic flashes on the stadium screen, an announcer reads a sentence, and the matter closes.

What disappears? The raw input. How many angles were examined, at what frame rate; how much uncertainty sat inside the ball-tracking projection; how loud the audio spike was; how the original on-field call was recorded. None of it is retained. When the broadcast ends, the graphic ends too.

In 2026 I remotely tracked all 64 matches of the Russia World Cup for my outlet. My tally: 29 penalties awarded, 22 scored, 20 VAR overturns. I logged every incident by minute, camera angle and outcome. A year later, when someone asked why a specific call was made, my own spreadsheet was the only surviving source — because the governing body had published nothing raw.

Cricket's problem is sharper. Football at least debates referee audio, and some leagues experiment with releasing it. Cricket keeps the third umpire's conversation off the broadcast, never publishes raw ball-tracking output, and states the umpire's call margin nowhere in public documents.

DRS gave cricket decisions. It did not give cricket the accounting behind them. And what is unaccounted for becomes controversy.

The Dhaka Five-Point Log

1. A Bangladesh Premier League fixture, Abahani Limited Dhaka versus Sheikh Russel KC. Abahani won 2-1. An 89th-minute penalty was awarded. I reviewed the incident from six angles, logged the referee's original call, recorded the 48-second VAR check, and wrote the final decision on its own line.

That single log became our desk's first standardised review template. From then on, five fields had to be filled for every incident: the law, the camera angle, the contact, the clear-and-obvious threshold, and the final call.

The habit taught me something that cricket analysis usually lacks. A decision becomes reviewable only when each of its steps is written down separately. Without the ability to compare steps, memory takes over — and memory is partisan.

I built the five-point log in Dhaka because memory is not a review protocol. Who saw what, for how long, on which frame — unless those are separated, two honest people can give two confident, contradictory accounts of the same ball.

That is exactly what happens in cricket. Two people watch the same ball-tracking projection. One says it was on the line. The other says it was outside the margin. Both watched the same television graphic. Neither saw raw data, so neither can prove anything.

Six Links in the Chain

Break a cricket review into stages and you get six links. Each link alters information. Each link loses some.

Link one: the on-field umpire's original call. A human observation made in milliseconds, recorded in the scorebook as a single word. Why he decided it is never stored.

Link two: the review request. Which side, which player, at what moment. Classified as a player review or an umpire review — a distinction that frequently vanishes from later analysis.

Link three: the input package. Which cameras the third umpire examined and which he skipped is entirely unknown. On a catch, a rear angle can be decisive while a front angle is useless. The selection of angles can change the path of a decision.

Link four: the technology output. Ball tracking, UltraEdge and Real-Time Snicko are three different systems owned by different companies, each with its own error margin. None of those margins sits in a public document.

Link five: the threshold. "Clear and obvious" appears in the playing conditions without a numerical definition. The umpire's call margin — how far inside the stump line the ball must be — is also unpublished.

Link six: the announcement. One sentence in the stadium, one graphic on the screen, a few seconds of broadcast. Then nothing.

Four of the six links lose information. Two never generate it. In a system that does not account for its own losses, every disputed call stays permanently disputed. The storm over the boundary countback after the 2026 World Cup final was not really an argument about a rule. It was an argument about opacity. The ICC scrapped countback in October 2026 in favour of repeated Super Overs — and the opacity of the process remained.

Why Blockchain Is the Right Analogy

This is not a conversation about cryptocurrency. It is a conversation about an immutable ledger.

A blockchain has three properties: data, once written, cannot be altered; each entry is timestamped and cryptographically linked to the one before it; and anyone can verify the chain independently.

Cricket's review decisions have none of the three. Imagine each DRS review as a block. Inside it: match ID, innings, over and ball, venue, the UTC timestamp of the review request, the on-field call, the review type, the list of camera angles examined, the raw ball-tracking output, the snickometer audio window, the applicable clause of the playing conditions, the final decision, and the elapsed time.

Chained in sequence, those blocks form an audit trail. If someone claims the ball was missing leg stump, they can open the chain and see what the first frame showed, what changed by the second, and which clause the threshold came from.

In 2026, during the empty-stadium period, I worked on Borussia Dortmund 4-0 Schalke. I built a 48-hour emergency protocol: isolate referee audio, map silent-stadium echoes, and verify offside calls with two independent angles. Three South Asian desks adopted it.

A live tracker taught me that chaos is just data waiting for a sequence. Every disputed decision has a fixed order behind it. It is simply never written down.

What a Review Block Should Contain

From my own log structure, a minimum block needs fourteen fields: identity (match, series, date, format, venue); context (innings, over, ball, batter, bowler, match state); time (UTC of request and of ruling, to the second); original call and who reviewed; inputs (number and identity of angles); technology (projection point, audio spike timestamp, UltraEdge frame); threshold (clause number, basis of decision); outcome (final call, and whether it upheld the original); duration in seconds; the analyst's confidence score in percentage; a field for what was missing or ambiguous; the applicable playing-conditions version; a short explanation where publishable; and the signature of the official accountable for the process.

How many of those fourteen are stored today? Two — the ball reference and the final decision. The other twelve are generated every match and destroyed every match.

When I logged penalty reviews in football, the uncertainty field proved the most valuable. If I was not certain, my language had to change. Cricket analysis almost never performs that self-correction. Everyone has a confident opinion about every decision and nobody holds verifiable input.

Three Failure Modes

First, proprietary technology. Ball tracking is privately owned. Raw data reaches the ICC or the broadcaster already processed. Independent verification is effectively impossible, which leaves both sides of any argument relying on inference.

Second, rendering versus raw data. What we see on television is an animation, not a measurement. How much of the ball was inside the stump line is never shown; a simplified projection is. A few millimetres of simplification can flip a decision on a ball near the margin.

Third, the opacity of umpire's call. If tracking shows the ball hitting the stumps but not clearly, the on-field call stands. Behind "not clearly" sits a specific geometric margin. It is not published. Two similar deliveries can therefore produce one umpire's call and one dismissal, with no visible reason why.

Umpire's call is cricket's least intelligible phrase, because it is not a rule — it is a threshold, and the threshold is secret.

The three failures reinforce each other. Proprietary technology blocks raw data; missing raw data blocks verification of the rendering; unverified rendering breeds suspicion of the threshold; suspicion of the threshold undermines the legitimacy of the decision.

"Spirit of Cricket" Is a Bad Audit Standard

Most of the Mathews debate was not about the law. It was about the spirit of the game. Was it against cricket's soul to dismiss a man for a broken helmet strap?

I disagree with that framing, on procedural grounds. The spirit of cricket is not a measurable standard. It shifts by situation, by person, by the bias of the observer. When a rule favours a player, nobody invokes the spirit. When it turns against him, the spirit becomes suddenly relevant. A standard cited only when convenient is not a standard; it is a rhetorical weapon.

The rule is explicit: an incoming batter must be ready to face within two minutes of a wicket falling. Mathews was not ready. Both sides held the same right to appeal. Shakib appealed inside the law.

The real problem is not that someone broke a rule. It is that nobody recorded who kept the clock, which frame started the countdown, and who determined the two minutes had expired. We know the outcome. We do not know the process.

Consider the non-striker run-out debate. For years it sat under Unfair Play, tangled with the spirit of the game. In October 2026 the MCC's new Code of Laws moved it from Unfair Play into the Run Out section. One administrative change converted a moral argument into a rule question.

Judged by the spirit, every decision stays disputed forever. Judged by the law, there is at least a path to verification — provided the path is recorded.

In Russia in 2026 I logged 20 VAR overturns. The stadium reaction after each ruling had nothing to do with the decision itself. It was a reaction to uncertainty. People can accept a verdict. They cannot accept a verdict whose basis is invisible.

Transparency Does Not Reduce Argument — It Changes Its Subject

The expected objection is worth taking seriously. Publish raw data, the argument goes, and the arguments multiply. Every number spawns a new fight. Fans will sit with frame-by-frame software and reconstruct the geometry.

That objection is an accurate observation attached to a wrong conclusion.

Transparency does not reduce the volume of argument. It changes its subject. Today the argument centres on suspicion: was the decision biased, was the system tilted toward one side? Tomorrow it centres on the threshold: how far inside the stump line was the ball, and was that enough under the law?

The first kind of argument never settles, because it is a question of belief. The second settles, because it is a question of definition — and definitions can be changed.

Two cautions apply to my own method. The five-point log has a bias toward ordering every event into a sequence, and not every cricket event sequences neatly. Some calls are genuinely uncertain, and the best analysis there is to admit it. My log now carries an uncertainty column and a confidence score; where I am unsure, I file a provisional read rather than a verdict. The referee's eye is not intuition; it is a habit built frame by frame — and not every frame is equally clear.

The second caution matters more. A fully transparent ledger will not prevent wrong decisions. It will only make them visible. Cricket's deeper problem is not process transparency but technological reliability. If ball tracking projects incorrectly and that projection is written into a public ledger, the error becomes more visible, more authoritative, and more damaging.

So the ledger must be paired with independent verification: two separate technologies measuring the same delivery, both results published. Football's semi-automated offside, which fuses multiple cameras into a three-dimensional projection, is the instructive model. When a technology's output comes from several independent sources, a single source's failure does not discredit the whole system.

Forward

Three changes are coming within three to five years, and the first has begun. Review logs will become public — not the full raw dataset, but a structured summary: which cameras, which threshold, how long. The ICC's 2026 removal of the soft signal was a signal in this direction. The soft signal was a layer built on umpire intuition that could not be verified; removing it conceded that intuition should not be part of the process. The next logical step is publishing the input, not just removing the guess.

Second, the threshold will be quantified. "Clear and obvious" will become a measurement — a percentage, a millimetre. From that day, every umpire's call will be explainable, and explainable decisions attract less anger.

Third, the broadcast layer will change. Viewers will see the raw projection alongside the animation, and the difference between them.

None of this will end cricket's arguments. It will relocate them. Today we ask whether the decision was right. Then we will ask whether the rule is right — a far more productive question, because rules can be changed and suspicion cannot.

I played Dhaka league cricket for Udity Club in 2026 as an opening batter and wicketkeeper, when decisions were final and irreversible. Today they are revisable but their reasoning is invisible. We have taken one step forward and one step back.

The question is no longer about technology. It is whether cricket is willing to keep the accounts of its own most consequential decisions. A sport that tracks every run, ball, over and strike rate — why would it refuse to track the calls that decide matches?