Hook

At Delhi's Arun Jaitley Stadium on 6 November 2026, Bangladesh and Sri Lanka were twelve overs into a World Cup league match. Angelo Mathews walked towards the crease, discovered his helmet strap had snapped, and asked for a replacement. Two minutes passed. Shakib Al Hasan appealed. The on-field umpire raised the finger: timed out, the first such dismissal in the long history of international cricket.

That night two documents sat open on my desk: the ICC match playing conditions and Law 40.1.1 of the MCC code. The clause was not new. The real question was who on the field had read it, and who had not. The controversy was born of habit, not of a gap in the law.

Months later the ICC removed the soft signal. The burden of the on-field umpire's tentative initial call on a low catch shifted directly onto the third umpire. The controversy did not leave the field. It simply changed address: from the pitch to the screen, and from the screen to the grey zones of the rulebook.

At the 2026 T20 World Cup, across Indian and Sri Lankan venues, the most frequent form of that controversy will carry a three-word name: Umpire's Call. And almost every debate about it begins in the wrong place.

Context: 2026 to 2026, the journey of one clause

DRS was first used on 23 July 2026 at the Sinhalese Sports Club Ground in Colombo, in a Test between India and Sri Lanka. The question that day was not technical but constitutional: who holds the right to decide, the umpire in the middle or the camera?

The answer landed somewhere in between. Tests and ODIs allow two unsuccessful reviews per innings; T20Is the same. A successful review is retained, and success includes Umpire's Call, not only an overturn.

That is where the definition matters. In an LBW review, when ball-tracking projects the ball hitting the stumps but less than half the ball inside the stump line, the on-field decision stands. The technology says the ball would have hit. The protocol says that is not enough certainty.

In mid-2026 the ICC abolished the soft signal. Previously, on a low catch, the on-field umpire gave a tentative call, and the third umpire needed visible, conclusive evidence to overturn it. After the change, the third umpire has no default answer.

Responsibility did not shrink. It concentrated.

Add the structure of T20 cricket: 120 balls, two reviews per innings, and a decision-changing power every over. In a format where a match turns inside six deliveries, review management is planning, not chance. At the 2026 World Cup, the ball-tracking graph will shape results as directly as the scoreboard.

Core analysis: protocol archaeology

I opened the ICC playing conditions again. The prose is dry; the consequences are theatrical.

Who wrote the clause, and for whom

Umpire's Call is not a natural phenomenon. It is a deliberate design. Ball-tracking is a predictive model, and every predictive model carries a band of uncertainty. The protocol acknowledges that band and rules that where the model is uncertain, the human decision prevails.

But the design has an awkward consequence. The same delivery, the same track, the same stump projection, yet two different outcomes, depending on whether the on-field call was out or not out. In both scenarios, the on-field decision survives.

Umpire's Call does not shield the umpire. It legitimises the uncertainty window of the tracking model, and the on-field decision takes shelter inside that window.

Two conclusions follow. The comfortable one: the technology is modest and refuses to overrule the human. The uncomfortable one: because the window depends on the on-field call, weak on-field umpiring will automatically generate more Umpire's Calls, and no review will ever correct them.

In my fifteen years of watching, my notebook shows the pattern clearly. In the same tournament, matches officiated by stronger umpires visibly produce fewer Umpire's Calls. Technology does not create equality. It applies a seal of legitimacy to an existing inequality.

The review economy: not justice, but resource management

Almost every major side now employs a dedicated review analyst. They compute per-over probabilities, weigh them against the team's remaining resources, and decide when to go upstairs. A batsman's stance, a bowler's line, the age of the pitch, even the camera angle enter the model.

This is the core tension. The declared purpose of a review is correction. But in T20 cricket a review is a scarce resource, and in the language of scarce resources truth is a variable, not an objective.

A review is no longer an instrument of justice. It is asset management, and in that ledger nobody has a right to stand in front of the camera before the 30th over.

The practical situation is harsher still. Lose both reviews and the most obvious error in the final overs remains unaddressed. And because an Umpire's Call outcome returns the review to the team, going upstairs in that window carries low risk.

So a decision that is never proven protects a team's assets. The protocol has effectively handed teams a cheap form of courage. That is why my notebook records not only outcomes but the seconds each review consumes. The variance in duration tells you whether the third umpire was certain or stranded.

New responsibility after the soft signal

In the soft-signal era, the third umpire held an advantage: the on-field umpire's tentative call was a default answer, and overturning it required extra proof. The 2026 abolition removed that.

Now the low catch, the catch near the toe of the bat, the ball brushing the webbing of a fielder's fingers, all of it rests on one person. Removing the soft signal did not remove responsibility. It centralised it.

The benefit is singular accountability. The cost is cultural. When evidence is inconclusive and no default exists, the decision becomes a personal judgement, and personal judgement has always been hard to appeal.

The broadcaster's edit: what the third umpire actually sees

Here is a truth that appears on no page of the protocol. The third umpire does not see reality. He sees an edited version. Which angle comes first, which follows, which is slowed, which is dropped: that sequence is set by the replay director.

The protocol calls the third umpire independent. In practice, a truck sits outside his room, and inside that truck the order in which the law is shown to him is decided. What the third umpire sees is not reality but an edit, and the order of that edit is fixed by the broadcast director, not by the rulebook.

Football offers a comparison here, of process rather than technology. At the 2026 Qatar World Cup, the first semi-automated offside decision took a three-minute review, and the result was presented as absolute and final on a three-dimensional image. Cricket took the opposite road: it gave institutional recognition to a band of uncertainty.

Yet football is ahead on one count. Football has built a culture of public explanation about what actually happened. Cricket produces a decision without an explanation. A decision without an explanation becomes a lonely decision.

The audit ledger: an unfinished requirement

Here is my proposal, and it is nothing like a hot take. Every DRS decision needs an immutable, publicly auditable record: the over, the ball-tracking outcome, the seconds consumed, the order in which evidence was shown, and the final verdict. Published at the end of a tournament, such a ledger would let journalists, coaches, and umpires measure themselves.

Today's situation is different. The ICC releases some statistics but not the chain of evidence. Two teams therefore carry two readings of the same clause, and the controversy lands not on the ICC but on the teams.

A protocol that cannot be audited in public cannot build trust, however precise it may be.

That is the forward question. The more a sport's decisions depend on technology, the more its auditability matters. Otherwise technology will not reduce controversy. It will simply become the controversy.

Contrarian: why the comfortable defence fails

The standard defence of Umpire's Call is simple: it protects umpires and does not diminish their authority. It sounds generous. The arithmetic does not support it.

The uncertainty of tracking itself creates a bias towards whoever is standing in the middle. A high-quality umpire produces fewer Umpire's Calls than a weak one, because his original decision is more accurate. Yet both outcomes receive identical protection. The protocol does not measure real skill. It only widens the window.

This is the most uncomfortable truth. Umpire's Call does not protect umpires. It makes on-field error permanent, because where a review carries no penalty, the pressure to be corrected also falls.

The counter-argument is fair, and I accept it. Abolishing Umpire's Call entirely would not reduce the problem but increase it. Ball-tracking predicts, and prediction fails at the margins, and at that moment a millimetre of arithmetic would erase a human eye. Football's semi-automated line has already taught that lesson about confidence.

So the centre of the argument should not be whether Umpire's Call survives. It should be: who keeps the accounts of decisions that land on Umpire's Call, and will those accounts be public?

A second complication gets far less attention. On-field umpires sit under regular ICC performance review, and every review feeds that assessment. If a large share of decisions falls inside the technology's uncertainty band, part of an umpire's evaluation moves beyond his control. Responsibility is split, and split responsibility belongs to no one.

The same logic touches players. A batsman dismissed on Umpire's Call sees his series numbers change, and possibly his contract valuation, while the technology itself says the certainty was insufficient. An absence of proof should never harden into a permanent verdict. In practice, it does.

Takeaway

At the 2026 T20 World Cup I will watch one thing more than outcomes: duration. A slow review means hesitation, and hesitation means either weak evidence or a weak protocol.

Second, I will watch how many different verdicts two teams' identical reviews produce in the same match. The data will tell us which is the limit of the machine and which is the limit of interpretation.

Cricket has not changed its nature. The bowler still releases the ball off the seam, the batsman still misjudges, the crease still holds a man convinced he was safe when he was a centimetre out. Only the language of the verdict has changed.

One question remains, and it presses on everyone, not only the umpire: to know whether the ball really hit, what do we call the space between the triangle at the top and the calculation at the bottom, error, or the limit of our evidence?