The Review Ledger: How the 2026 Tournament Cycle Turned Umpiring Into a Public Audit

My ledger shows 47 reviews across the first 24 matches of the 2026 cycle. Twenty-nine failed. That is a 61.7 percent failure rate. Twelve of those 29 were Umpire's Call — ball-tracking standing with the umpire's verdict rather than the player's appeal. The remaining 17 were straightforward miscalculations: a misread of the pitch line, a misjudgement of bounce height, a failure to separate bat from pad at the moment of the catch.

There is a small, clean trend inside the number. Across the first ten matches, teams burned an average of 2.4 reviews per game. Across the final fourteen, that fell to 1.6. The players learned that not every doubt is worth a challenge. But the failure rate did not move: 63.3 percent in the opening block, 60.7 percent in the closing block. Fewer reviews, identical quality. That is the real story of this cycle, and it is why I opened the ledger again.

I have been watching match officials for 45 years. When I launched The Referee's Ledger in 2026 at the age of 52 — coding all 380 Premier League matches of 2026-17, logging 1,142 yellow cards and 34 red cards — colleagues told me this was bookkeeping, not sport. They were right, and it did not matter. The 2026 database turned discipline from a whispered verdict into a public pattern, and cricket's review system now sits in exactly that position, with nobody willing to open the book.

Context: what the law says, and what the law does

DRS first appeared in a Test in July 2026, a trial during India's tour of Sri Lanka at Colombo. From 2026 it became permanent, built on three pillars: ball-tracking, UltraEdge, HotSpot. On top of them sits one remarkable legal invention — Umpire's Call. If the evidence does not prove the on-field decision clearly wrong, the decision survives.

On paper the rule is elegant. It protects the authority of the on-field umpire and refuses to hand total power to the machine. In practice it has produced a strange economy. A batter knows that if the ball grazes the line by centimetres, a review is simply a wasted challenge. And if the review succeeds, the challenge is returned — the retention rule is the real centre of the confusion.

July 14, 2026, Lord's. England 241, New Zealand 241. A Super Over. Then a boundary count: 26 to 17. The match ended because of a number, not because of anything that happened on the field. I was in the Lord's press box that evening and understood something permanent: in this game, technology and law can never again be examined separately. When VAR landed at the 2026 World Cup in Russia, the referee became an operator — his role on the pitch shrank, his role in front of a screen grew. Cricket went the other way. The umpire stays on the field, but his decision now stands waiting for reconsideration in the hands of three technicians.

Core analysis: one review, four angles

First angle — the arithmetic of appeals. Of my 47 reviews this cycle, 31 came from batting sides and 16 from bowling sides. Batting success: 35.5 percent. Bowling success: 43.8 percent. That is reasonable. Bowlers generally review situations where the trajectory came from their own hand; their information is better. Batters are largely guessing. But the gap did not hold. In the opening week, bowling sides succeeded 60 percent of the time. In the final week, 33 percent. Fatigue shapes review outcomes. That is not a technology failure. It is a human-resource failure.

Second angle — the interior of Umpire's Call. In 18 of my 47 reviews, ball-tracking supported the umpire. In nine of those 18, the centre of the ball was on the line, but the proportion of stump it would have struck fell inside the margin of prediction. Yet with a different pitch line, the same delivery overturned the decision. Viewers see three different 3D animations, receive three different verdicts, and conclude that the umpire is biased. In truth, the technology is describing a probability while the law delivers a verdict. Those are not the same sentence.

Third angle — over rates and the stop clock. At Qatar 2026, FIFA's added-time directive produced 27 minutes of stoppage time in England's 6-2 win over Iran. Cricket taught me the same lesson in 2026, in empty stadiums: pressure does not disappear, it moves into the protocol. This cycle, the stop clock and the over rate are both disciplinary instruments. Across 24 matches I logged nine over-rate breaches, and behind every one I found two time-consuming events: a review and an injury break. The instruments brought in to restore order are eating the clock.

Fourth angle — the umpires themselves. I tracked eight on-field umpires this cycle against three metrics: (a) decisions overturned via review per innings, (b) visible player confrontations per innings, (c) average time to announce a DRS outcome. The weights, declared up front: 50 percent, 30, 20. One warning is essential — metric (b) is largely my interpretation, not a count, so I keep it separate and name no individual. My complaint is not with people.

What I found: the three strongest umpires averaged 1.1 overturned decisions per innings and the fastest announcements (58 seconds). The three weakest averaged 2.3 and 94 seconds. But the real difference sat elsewhere. Two umpires handled 11 matches in four weeks. Others handled six. Discipline is not a mood. It is a structure with timestamps — and the heaviest component of that structure is workload, which nobody ever publishes.

Here I have a contentious proposal. Every cricket review should be written into a public ledger: date, over, umpire, bowler, batter, outcome, reason. The moment passes; the entry stays. If someone tells me that sounds like a blockchain, I agree. That is precisely what the game needs — an immutable, timestamped, publicly readable record. I built that for the Premier League in 2026. Cricket still has not.

The contrarian angle: players blame the technology, not the protocol

Mid-tournament, one phrase kept returning: we need consistency. From commentary boxes to social media, the demand is uniform. Nobody defines it. Does consistency mean every review produces the same outcome? Or that the same law is applied the same way?

My ledger says the second has never been missing. The law was identical every day, every match. What was missing is the first — and it should stay missing, because every delivery is different. Ball-tracking is a probability model, not a prophecy. A viewer who cannot accept that is not frustrated with technology; he is frustrated with the concept of probability.

A second uncomfortable truth. Most reviews this cycle came from LBW appeals against spinners. Yet spinners requested the fewest reviews of anyone. The reason is simple: a spinner knows the ball is turning, the bounce is dropping, prediction is hard — so he does not challenge. The seamer does, because his line is comparatively predictable. Technology usage is tracking the nature of the craft, while we accuse players of being reckless. The reality is that players understand the limits of the technology better than the umpires do.

Third, retention. The rule effectively grants a free mistake. The transfer market has its own red cards, and most are never shown on television; cricket's review economy runs on a similarly invisible subsidy. I support changing it — conditionally. Retain the review only when the original decision is proven clearly wrong. Returning a challenge after an Umpire's Call that upheld the decision is rewarding error.

Toward a takeaway: five steps and a deadline

In June 2026, sitting in an empty Etihad, I logged 18 fouls and four cards and learned that the real evidence of discipline lives in the protocol, not the pitch. For cricket, my proposal fits in five numbers.

One: publish the review ledger after every tournament, within 21 days. Two: define Umpire's Call numerically, with at least a fixed half-stump boundary. Three: revisit retention, measured against clear error. Four: cap each umpire's match load at eight in four weeks. Five: pair the stop clock with a review-time budget, so the process stops eating the clock.

None of these is a revolution. They are a request to open the book. One question now belongs to the federations: if the review ledger is public, who draws the line between an umpire's error and a protocol's error? In a game where the time taken to decide has become more contentious than the decision itself, the problem is no longer the umpire.