Three Minutes Thirty-Two Seconds: Why Cricket's Review Room Now Demands a Public Ledger

Three Minutes Thirty-Two Seconds: Why Cricket's Review Room Now Demands a Public Ledger

The screen flashes two green words — Umpire's Call. On the big board the thin red line of ball-tracking loops again from release to stumps, forty-seven thousand people exhale at once, and I clock it in my notebook: 3 minutes 32 seconds. Inside that single review sat twenty camera angles, the audio trace from Snicko and UltraEdge, the physical model of the ball's flight, the delivery ID, the frame number where leather met pad. The data was all there. What was missing was an address and a signature.

After the match the third umpire's report drops into a file, finds a shelf in the board's archive, and the following season nobody has anything to answer with — only memory and inference. My notebook, though, keeps everything. In 2026, coding all 380 Premier League matches, 1,142 yellow cards and 34 red cards into one table, I learned something: discipline is not a mood. It is a structure with timestamps. For cricket's review decisions, that structure still does not exist.

Context: Where the Law Stops and Conditions Begin

Law 3 spells out the umpires' powers, but the review process lives outside the Laws — in the Playing Conditions, which are competition-specific, change from cycle to cycle, and rarely reach an ordinary fan in full. DRS was first used in July 2026, in the India–Sri Lanka series. The architecture has barely moved since: the field umpire's call, a fifteen-second review window, two reviews per innings, retained on success, burned on failure.

The least discussed part is the error margin. Ball-tracking prediction is not centimetre-perfect truth; every frame from pitch to bounce carries measurement uncertainty, and the safety ring around that uncertainty is called Umpire's Call. The boundary-count controversy after the 2026 World Cup final was the same question wearing a different shirt — the rule was written down, but why it was written, and by whom, produced no public document. An undocumented rule is not law. It is habit.

VAR arrived at Russia 2026. Across 64 matches I logged 29 penalties and 20 interventions, and built the Referee Discipline Index in that same cycle. Cricket can learn one thing from it and must refuse another. The lesson is public accounting. The refusal is treating the comparison as universal. Football is continuous play; cricket is discrete delivery. In cricket every decision has a natural address — ball number, over number, innings number. Football has none. That is why cricket is simultaneously the easiest target for technology scrutiny and the best laboratory for it.

At Qatar 2026, FIFA's added-time directive produced 27 minutes of stoppage time in England's match against Iran, and across 64 matches I logged 227 yellow cards. One directive, many changed behaviours — and no central ledger for the change. The same thing happens in cricket every time a review protocol is updated. The directive arrives; the effect, and the data, do not.

Core: What a Ledger Actually Is

What I am calling the Decision Ledger treats every review as a block. A block carries the match ID, innings, over and ball number, the field umpire's original call, the time the review was requested, the third umpire's final ruling, the time taken to reach it, the hash of the ball-tracking file, the hash of the audio trace, the camera calibration certificate number, and the hash of the previous block. Once written, nothing can be quietly edited — because altering one block breaks every hash after it, and the mismatch surfaces immediately.

Copies sit distributed: home board, touring board, ICC, broadcaster, and an independent panel. This is where blockchain's only practical meaning appears — immutability is not a technical toy, it is a way of drawing a limit around power. Anyone can read the record. No one can delete it alone.

Nothing in that ledger is currently uncollected. Hawk-Eye files, tracking data, audio traces, camera-setup documents are all generated. They are simply not published. Which venue last calibrated its cameras, how long a given third umpire averages, how often a ruling is overturned — none of it is compiled anywhere. In January 2026 I worked out the accounting behind Chelsea's £106.8m signing of Enzo Fernández on an 8.5-year contract by asking one question: where is the rule written, and where is the gap in the book. Cricket's review system is missing precisely that second table.

Call it the Review Discipline Index. The weights must be published up front, or the arithmetic will launder opinion into a score. Six pillars in my proposal: Official Stand Rate (30%) — the share of a field umpire's original calls that survive review; Time to Decision (20%) — the third umpire's average and range; Umpire's Call Ratio (15%) — how many reviews end inside the uncertainty ring; Review Economics (15%) — failed-review rate, cost per over, time lost; Post-Review Dissent (10%) — verbal exchanges after a ruling; Venue Integrity (10%) — punctuality of camera, audio and calibration work.

Five of those six are arithmetic. The sixth is still human judgement, and it must be flagged in a different colour so nobody forgets which column holds a number and which holds a transcript. An index that hides that distinction does not prevent dishonesty; it only makes dishonesty legible.

A review is itself a market. Two reviews mean limited currency — returned on success, burned on failure. Under that design players rationally become risk-averse and stay silent on doubtful calls, when the spirit of the rule was to correct the big errors. The third umpire's time cost is welded to the same problem: a long review breaks the rhythm of play, and a broken rhythm means extra pressure on the field umpire in the next over.

Every technology-adoption autopsy ends at the same three questions — who was trained, who was protected, who was never audited. Training modules for third umpires, simulation scores, and each official's accuracy trend over time would separate a decision error from a training gap. Right now the two are blended into one fog.

The ledger also serves anti-corruption work directly. An investigating unit's weakest point is the chain of evidence — when a message arrived, who called whom, when a witness statement was recorded. A timestamped, immutable record makes a case buildable from the first day of suspicion. The same logic applies to T20 league contract registries: player contract, agent commission, third-party ownership. Put those three facts in a public register and who plays for whom stops being a reporter's guess.

Contrarian Angle: Where the Ledger Stops

Start with what ledger enthusiasts skip: Umpire's Call is not physics. It is policy. The half-ball-width safety ring did not arrive by revelation; a committee chose it. Shrink the ring and review outcomes change, umpire behaviour changes, and not one digit of the underlying data changes. The ledger only records who judged, when, and under which doctrine.

Second, publication has its own effects. A third umpire who knows his average time is published daily will decide faster — and speed is not accuracy's friend. A field umpire who knows his stand rate is public may push doubtful calls upstairs to shift the burden. Accountability structures change behaviour. That is why stand rate must never be published as a standalone score; unpaired from third-umpire time and venue conditions, it collapses into referee-blaming. Scoring the individual before scoring the environment is simply unfair.

Third, cricket's emotion and its rulebook run on different clocks. At the moment of a review the crowd wants justice; the rule tests probability. Give every layer readable public data, from the turnstile to the ball-by-ball ruling, and cricket becomes the first sport whose governance is an open book. The transfer market has its own red cards, and most are never shown on television — likewise cricket's largest administrative errors get buried in the results column. Before importing review logic from football, state the limits: continuous flow cannot be block-partitioned, discrete events can. Nobody should tip two sports into one barrel out of love for data.

And one item in my notebook never sits in a number column — the third umpire's pause. The person in front of the monitor carries no weight on his shoulders, yet his ruling carries a team's semi-final. Discipline is a structure, and at the far end of that structure sits a tired human being. The calendar arithmetic we never do — how many matches an official sits as third umpire in one tournament, how many hours in transit, how many nights in the same hotel room — belongs in the ledger too.

Takeaway

My expectation is that within the next cycle the ICC will publish a minimum disclosure standard: for every review, the time, the outcome, the reasoning and the camera calibration status, in a machine-readable file, within twenty-four hours of a competition ending. That will not shrink the umpire. It will, for the first time, measure the structure around him. The question is simple: next final, when the screen flashes Umpire's Call again, will we actually know why?