Umpire's Call: The Technology That Doesn't Change Decisions, Only Their Explanation

May 2026, Melbourne. The A-League Grand Final ended 1-1, Sydney FC beating Melbourne Victory 4-2 on penalties. In the 94th minute, the Besart Berisha and Alex Wilkinson collision had the entire stadium screaming for a penalty. I sat in a studio and built a 12-minute video — working through IFAB Law 12 line by line, frame by frame at 0.25 speed, logging every time-stamp.

Half a million people watched it. For one reason: I never said the referee was wrong. I showed where the gap sits between the written law and the events on the pitch.

A year later, in June and July 2026, I tracked 29 VAR reviews across Russia, travelling from Moscow to Nizhny Novgorod. When Antoine Griezmann's penalty arrived in the 58th minute of France versus Australia — the first VAR penalty in World Cup history — I understood something: technology does not change decisions, it changes the explanation of decisions.

After the grand final, I stopped arguing and started documenting.

---

In cricket, this crisis of explanation has a name: the Decision Review System. It first appeared in a Test match in July 2026, when India met Sri Lanka at the Sinhalese Sports Club in Colombo. Its architecture has barely changed since: a batter is given out, or a bowler's appeal fails, and the fielding captain may review. Ball tracking, UltraEdge, real-time Snicko — these tools paint a picture on the third umpire's screen. Then the third umpire decides.

But he does not decide freely. He must walk a fixed decision tree. For LBW, the steps run like this. First, was it a no-ball. Second, where did the ball pitch — outside leg stump means not out outright. Third, where was the impact on the pad — outside the line of off stump with a shot offered means not out. Fourth, the projection — would the ball have hit the stumps, and if so, how much of it.

That fourth step holds cricket's most contested phrase: umpire's call. If ball tracking shows the ball entering the stumps, but less than half of the ball landing inside the stump line, the third umpire upholds the on-field decision — out or not out, whatever it was.

The rulebook is a map; the match is the territory I walk.

The first crack appears right here. Reviews are rationed: two per innings in Tests, one in ODIs and T20Is. A successful review is retained, a failed one burns. From the 2026 Headingley Ashes Test through the 2026-21 Australia series, teams have repeatedly tried to hoard reviews, and when an umpire's call consumes one, an entire innings' strategy shifts. Tim Paine, Virat Kohli, Kane Williamson — each has been criticised in some series for review management.

---

Now the real question. Is DRS actually an accuracy technology? My records say no. DRS is not an accuracy machine; it is a decision-preservation machine. Its job is not to correct error, but to protect the on-field umpire's authority — and only when the technological evidence stands clearly against him.

From years of watching, keeping review-by-review notes, I have found a pattern. The same delivery, the same pitch, the same track — but if two umpires gave two different calls, DRS returns two different verdicts. Because the decision does not depend on the ball. It depends on what the human standing out there said first. A fifty-fifty call, technically doubtful, becomes permanent.

Break this into three layers.

Layer one — the arithmetic problem of the threshold. Half the ball hitting the stumps is out; a fraction less is umpire's call. But in reality the ball's path is an estimate, not a measurement. After pitching, air resistance, spin, seam movement — these are modelled to project a future. The model carries its own margin of error. Inside that margin we then draw a 50 per cent line. We are stacking error on error to manufacture an imaginary clarity.

Layer two — the economics of the review. When reviews are scarce, they become a strategic asset. A captain stops searching for truth and starts calculating risk. He knows an umpire's call is a failed review. So he estimates how far inside the stump line the impact sits before deciding whether to send it upstairs. Technology does not simplify the decision; it builds a betting table where probability outweighs proof.

Layer three — the language of the announcement. A spectator in the ground sees a red ball on the screen, a line, and the words 'umpire's call.' Three words, no explanation. Why this verdict, at which step, by how much it missed — none of it is told. And this is precisely where the entire VAR crisis sits. Tracking 29 reviews across Russia, I saw that 80 per cent of the argument was not about the decision, but about the absence of an explanation for it.

The quietest matches often carry the loudest rule violations.

One more dimension rarely enters the conversation. DRS today is not only an LBW tool. Doubtful catches, stumpings, run-outs — all fall under it. But the thresholds differ, the standard of proof differs, and the way it is displayed differs. That inconsistency is what breeds disbelief. When someone says 'the technology knows everything,' they are not being foolish — nobody ever told them that the technology here observes a limit, and that the limit is written into the law.

Now to governance. On 14 July 2026, the ODI World Cup final at Lord's was settled by a boundary count — after the Super Over also finished level, England won on 26 boundaries against New Zealand's 17. That clause was written into the playing conditions, yet had never been applied in ODI history. This is the ideal governance loophole: a clause sits quietly for years, and on the day it wakes up in the biggest match, nobody is prepared.

Umpire's call is exactly that kind of clause. It is plainly written, universally known, but there is no obligation to explain its consequence. The ICC playing conditions state what the decision will be; they do not state how it will be communicated. That gap is DRS's biggest weakness today — not technological, but communicational.

---

Here an uncomfortable truth must be admitted. We say DRS reduces error. Umpire's call does the opposite: when technology is 90 per cent certain, we keep the on-field fifty-fifty guess alive. We know the decision is probably wrong, and we uphold it anyway. This is not a bug. It is a deliberate design.

Why? Because of umpire authority. If technology overturned every borderline call, the on-field umpire would become a camera operator. Control of the game would move to a screen with no human in it — only a model and a threshold. The ICC is not willing to walk that road.

But that argument carries a price, and the spectator pays it. Because nobody tells the spectator he is watching a tolerated error. He is shown a red ball and a verdict. So he concludes the technology betrayed him — when in fact it followed its instructions.

A second uncomfortable truth: umpire's call does not behave identically for every team. A side whose batters plant far forward of the pad, and a side whose batters stay deep in the crease, generate different projections from the same delivery. One law, two different risk profiles. That is not proof of bias, but the possibility is never publicly quantified before a tournament.

I watch cricket the way an auditor reads a ledger: for what is missing.

---

So what is the fix? Three practical steps.

First, broadcast the reasoning of every review inside the ground. Why the third umpire decided, at which step he stopped — put it on the screen, the same way, in the same language, for every spectator. Russia offered one lesson on VAR: without explanation, even a correct decision breeds distrust.

Second, publish the projection margin. If the screen showed how many centimetres short the ball fell, umpire's call would stop being mysterious. Today that data lives in the broadcast booth and never reaches the crowd.

Third, release review data at the end of every tournament. How many reviews ended in umpire's call, at which step, for which side — an annual report would convert much of the argument into evidence. Any rule kept in the dark breeds rumour.

Someone will say this slows the game. Honestly, the fear of slowness belongs to broadcast design, not to the law. Adding three words to a screen costs no time. It costs intent.

---

The last word is not that umpire's call should be abolished. The last word is that if a rule is to stand, its reasoning should stand with it — publicly, in front of every spectator. We now live inside a system where the technology never errs, it simply never explains. Until that explanation arrives, half a million people will keep watching the video, and not one of them will be certain what they saw.