Umpire's Call: Cricket's Most Controversial Decision Is Actually Its Most Honest

The ball struck the pad. The umpire said not out. The batter reviewed. On the giant screen the ball-tracking arrived — three red dots travelling into the stumps. The decision stayed. Two words appeared: “Umpire’s Call.” The crowd seethed, social media filled with fury, and the scoreboard did not move an inch. For 26 years I have stood between the laws of the field and the frames of the camera, watching exactly this moment — where technology states a truth and the law interrogates it.

I have long believed that the error is rarely in the pixel; it is in the premise. The argument that returns every tournament around umpire’s call rests on the same foundational fault line: what we ask technology to do, and what the law actually asks of it.

Context: the framework that builds the decision

The Decision Review System began in July 2026 with India against Sri Lanka in Colombo. The original purpose was simple: correct the obvious error the eye could see. Over the years the system split into three layers — line, height of impact, and point of impact on the pitch. Each layer acquired its own tolerance, its margin of error.

Here sits the terminological crack. Ball-tracking answers a physical question: would the ball have hit the stumps, and by how much. The law asks a different question: was the umpire’s on-field decision “clearly wrong.” The camera answers the first; the protocol answers the second. They are never the same question, yet the crowd merges them every time.

The protocol states that if tracking shows the ball would have hit the stumps but the extent of contact falls inside the uncertain band — the ball’s centre and the stump’s position effectively level — the on-field call stands. Technology does not change the verdict here; it merely shows the probability on either side. When doubt remains, it returns to the human.

The core: three thresholds, three gaps

I trace every disputed decision backward until I find the doubt. Suppose tracking shows the ball entering the stumps but the outcome is umpire’s call. That does not mean technology lied; it means the protocol judged the decision uncertain within a threshold.

The first gap — line. If the distance between the ball’s centre and the inner edge of the stump on the projected path is under half a ball, the decision stays with the on-field umpire. However sharp the resolution, control stays with the law.

The second gap — height. Height is assessed by comparing the ball’s centre against the stump’s height. That comparison is not fixed; it shifts with pace and bounce. The same action can produce different results across two matches because the projection model runs on two different pitch conditions.

The third gap — impact. Whether the ball struck bat or pad depends on video frame rate. At a low frame rate the precise instant of impact can vanish between two frames, forcing the protocol to rely on incomplete information.

The sum of these three gaps is the space umpire’s call occupies. And that is cricket’s most uncomfortable truth: umpire’s call is not a technological failure; it is a deliberate acknowledgement of technology’s limits.

The crowd’s anger always arrives at the same place — technology sees the ball going in, yet it was not out. But technology does not say “out”; it says “probable.” And the law will not convert probability into a verdict unless it clears the threshold of certainty. Technology and law are speaking two languages, and there is no interpreter.

The contrarian view: is doubt itself the problem?

The instinctive argument says removing umpire’s call solves everything. Let the law accept what technology says. I question the premise.

First, without umpire’s call every projection uncertainty would have to be treated as certain fact. But ball-tracking is a model, not a measurement. A model forecasts the future, and forecasts carry error. Imposing it as truth would force cricket to accept decisions that never happened — only that they were meant to.

Second, the game is governed not only by technology but by umpires. Reducing an umpire’s authority to make the machine supreme collapses control on the field. An umpire who knows his call can be overturned at any moment will hesitate. More hesitation means slower play, poorer over rates, and a game that loses its rhythm.

Third, umpire’s call is a form of transparency. It tells the viewer that technology, too, is uncertain. A system that admits its weakness earns trust; a system that claims infallibility loses everything on its first error.

None of this makes the system perfect. The real failure is that the protocol is never explained to the crowd. The screen flashes a word; it never explains why the threshold is a threshold. An unfamiliar term becomes a pronouncement, and the crowd’s anger lands on the technology when it belongs on the protocol’s lack of transparency.

For years I have kept a notebook habit — logging every review in every tournament, noting at which layer each decision stopped. One pattern stands out: umpire’s call controversy is fiercest in matches where play is slow, over rates are poor, and the rhythm of decisions has already broken. The anger is not about one call; it is about the felt justice of an entire day. Justice here is not a sentimental idea — it is measurable, through consistency, tempo and the ledger of over rates.

I learned cricket in Bangladesh and now apply its laws in English conditions and English committee rooms. In those two places “common sense” means two different things. In the subcontinental culture the benefit of the doubt tends to lean toward the batter; in the English convention it leans toward the umpire. Same ball, same protocol, two expectations. Much of the umpire’s call argument is really this collision of cultural translation, which no camera measures. Senior bowlers such as India’s Ravichandran Ashwin have publicly questioned the threshold, and not unreasonably — the question is not about technology, it is about interpretation.

Takeaway

Umpire’s call is cricket’s most criticised decision and perhaps its most honest. It concedes that technology is not certain, the law is not certain, and neither is the human. As the 2026 tournament cycle arrives and every review of every match is dissected, the real question will not be whether it was out. It will be how we explain technology’s limits to the people watching. The day the protocol learns to explain its own boundaries, umpire’s call will stop being a controversy and start being a lesson.