The Review Ledger: Auditing Umpire Decisions in a World Cup Cycle

In June 2026, at a group match in New York, the ball-tracking graphic had already been on the big screen. Outside the ground, thousands of viewers had reached the same conclusion: no bat involved. The third umpire's announcement still took another forty-eight seconds. Those forty-eight seconds are the story I care about, not the verdict. A review in cricket is never simply right or wrong; it is a process, and a process has a duration, a rule, a duty and a cost — all measurable. The ledger I began in 2026, when I counted 1,142 yellow cards across 380 Premier League matches, now carries a second column: every DRS review logged since 2026. DRS arrived in July 2026, at a Test in Colombo between India and Sri Lanka, initially with ball-tracking and slow-motion only. Then came UltraEdge, real-time Snicko, and that contested idea, umpire's call — where a delivery can strike more than half the stump and the on-field decision still stands. The 2026 World Cup gave each side two reviews. The 2026 Champions Trophy, England 2026, Australia 2026, the USA and Caribbean in 2026: every cycle changed the economics of the review while the rule structure stayed almost frozen. The 2026 T20 World Cup cycle in India and Sri Lanka compresses the pressure further. Fifty-five matches across roughly six weeks, twenty teams, February dew, different ball-tracking installations at different venues, and the same two reviews in every captain's hand. In T20, one ball is roughly 0.8 per cent of an innings — a wasted review does not merely burn an option, it rewrites the arithmetic of the whole innings. For every review, my ledger fills six fields: over, phase, type, outcome, decision time, and the run rate across the next ten overs. Those six fields produce the Review Efficiency Index. I publish the weights before the argument, not after, so that nobody can claim the numbers were arranged backwards: retained-review rate 40 per cent, correct-overturn rate 30 per cent, average decision time 20 per cent, post-review over-rate impact 10 per cent. Where the input is still human judgement — a captain's reasoning, for instance — it sits in a separate column marked as such. It does not get blended into the arithmetic. Reviews taken in the death overs perform worst. Under pressure a captain trusts the batsman's face, hears the crowd, and spends the last card in his hand. Rohit Sharma, Babar Azam or Kane Williamson all operate inside the same two-review limit. In my count, the success rate of reviews between the 16th and 20th overs is clearly lower than in the middle phase, and the run rate rises across the ten overs after a failed review. The reason is simple: the last five overs need decisions most and tolerate patience least. Umpire's call does two jobs at once. It protects the on-field official, and it admits that the tracking technology carries its own error band — roughly a ball's width. Here is the trouble: we broadcast the tracking and we do not broadcast the error band. The crowd sees out and hears not out, and the decision looks like caprice. The third umpire's time is a measurable number too. On 29 June 2026, in the press box at Kensington Oval in Bridgetown, I was logging the final with a stopwatch running. The tracking graphic appears on the big screen before the official verdict, which means the public verdict now precedes the official one. That inverted order is where suspicion is manufactured, and it is the current rule. On the match referee's sheet, a review is also a cost. Every review stops play, presses on the over rate, and in a compressed tournament schedule that pressure accumulates. A captain who spends two reviews also spends time, and those two expenditures are never audited together. Our habit is to blame the official. The umpire had a shocker — that sentence contains no count, which makes it a feeling rather than evidence. Behind any decision sits an error band, a training budget, a technology installation and a time limit. Judging the individual without publishing those four numbers is how the environment stays unexamined. Discipline is not a mood. It is a structure with timestamps. This is where cricket and football part, and the limits deserve to be stated plainly. Football's VAR hides the audio; cricket puts ball-tracking on the big screen. Cricket's decisions are discrete — ball by ball, with stoppages; football's play is continuous, and its review economics are different. Cricket's model does not transplant whole. One element does travel, though: publishing the process. When VAR landed at the 2026 World Cup, referees received training, received protection, and nobody published their full decision record. Cricket has not yet lost the chance to avoid that mistake. One proposal, then. The ICC could publish an umpire decision audit after every tournament: which review, which outcome, which decision time, which venue — as open data. Until then the spectator holds only memory, and memory is a poor auditor. The question is straightforward: a sport willing to show ball-tracking on a giant screen, why will it not show the ledger of its own officials?