Umpire's Call: The Decision Technology Refuses to Own

A wet evening in a knockout match, the 47th over. The spinner releases, the batter goes for a sweep, the ball thuds into the lower pad. Fielders erupt, but the umpire does not move. A review is taken. On the giant screen the ball-tracking graphic floats up: the ball is striking the stumps, but only just. Three words appear: 'Umpire's Call'. The on-field decision stands. Thousands in the stands raise their hands in protest, yet what the screen actually showed is more uncomfortable still: technology itself refused to make the call. The whistle blew, and the rulebook started breathing. This is modern cricket's most awkward moment, where the camera shows the truth but no one is willing to sign their name to it.

To understand the context, we must go back. The Decision Review System was first trialled in July 2026, during the India-Sri Lanka Test series in Colombo, then called 'Player Review'. At first only batters could review, not the fielding side. From the 2026 World Cup it entered a regular framework, and the fielding side was permitted too. Today's rule is roughly this: in Tests, two reviews per team per innings, retained if successful; in ODIs and T20Is, one review per team per innings, also retained if successful. A review must be signalled within fifteen seconds of the delivery, meaning the decision is made almost blindly, in the dark. And that fifteen-second decision can go on to write the fate of an entire match.

For LBW, ball-tracking estimates the trajectory and shows whether the ball would have hit the stumps. Here comes the disputed threshold. Under the rules, if the ball would strike the stumps so marginally that less than half the ball would have made contact, the system returns 'Umpire's Call', meaning the original on-field decision stands. The ICC and MCC logic is clear: respect the margin of technological error, and preserve the on-field umpire's authority. But this is where the question turns complex. From years of watching matches, what I have learned is this: the spectator never looks at the percentage of the threshold; the spectator sees whether the ball is going into the stumps. And if it is, they believe it is out. When technology says 'it clipped the edge, so I will not overturn', to the spectator that is not justice but muddled accounting.

The core problem is not the accuracy of technology, but the murkiness of how responsibility is divided. A review passes through four separate layers: the umpire's instantaneous call, the ball-tracking software's mathematical estimate, the UltraEdge or replay operator's signal, and finally the third umpire's interpretation. None of these four layers owns the decision entirely. The result is a state where no one takes responsibility: the umpire says 'technology said so', technology says 'outside the margin', the operator says 'we only show frames'. The spectator argues all night, yet no one is accountable, and that is the deepest gap in modern review culture.

I watched that first VAR penalty in France-Australia at four in the morning during the 2026 World Cup, and it taught me that technology does not make decisions; it only supplies material for a decision. In cricket that lesson is sharper, because a fraction of a threshold can change a match. With ball-tracking, one thing must be remembered: the system estimates the future path from where the ball ended. Camera frame-rate, the seam, pitch moisture, even the ball's rotation can nudge that estimate slightly. When a few centimetres of this uncertainty returns as 'Umpire's Call', it is not a distortion of truth but an acknowledgement of honesty, yet it remains unexplained to the spectator.

Here lies the second problem, and it is communication. A review decision is shown on the big screen through a few graphics and three words. But why the decision came that way is never explained to the spectator. Yet the ICC's own protocol allows the match referee and broadcaster to offer a clear explanation. In practice that does not happen. I have seen the same kind of LBW given out one day and not the next, and the spectator places the two events side by side and suspicion grows. Where technology avoids responsibility, the responsibility of explanation becomes the greatest duty of all, and no one lifts that duty onto their shoulders.

Now to the uncomfortable side rarely discussed. Who are the review operators, how are they trained, and how far can an error in frame selection affect a decision? These questions are almost never formally examined. The ICC regularly assesses umpires' performance, but independent audits of ball-tracking software and operators' skill are largely absent from public view. I have watched cricket for nearly two decades, and I have seen again and again that when a technology debate arises we talk about the software, we talk about the person, but not the human running that software. Yet during a review the replay operator selects one frame, and that single frame can set the direction of an entire match.

The opposite must also be admitted. When I wrote in 2026 about an umpire's decision in a Chattogram match, a retired FIFA referee corrected me: I had cited the law, yes, but had left out the context of match management. That mistake was a lesson. In cricket too, the umpire is not merely a machine; he reads the rhythm, the pressure and the weather of a match. So the 'Umpire's Call' convention is not entirely unreasonable; it prevents technology from becoming the sole owner of the decision. But the problem is that this argument is never explained to the spectator. We show only the outcome, never the reason. And where the reason is not explained, trust erodes.

Honestly, I do not want to blame technology. My fear is the opposite: excessive faith in it. When that VAR explainer was shared fifty thousand times in 2026, I felt a little proud, but then I grew afraid too: what if I oversimplified it, and people began to see technology as infallible? That risk exists in cricket. We treat a ball-tracking graphic almost like a verdict, though it is a probability, a mathematical estimate. 'Technology does not make mistakes' is technology's greatest weakness, because it strips people of the right to question technology.

But here is my hesitation. If technology can be questioned, where is the limit? Is a review decision final, or should it too be appealable? This much I am certain of: however advanced technology becomes, the last word will be spoken by a human, because cricket is not merely a game of numbers; it is a game of relationships and memory. The night an 'Umpire's Call' keeps thousands awake tells us that the decision is not technology's; the decision is ours.

So what is the solution? In my view, three directions are needed. First, the review decision on the big screen should show not only a graphic but a one-line explanation, stating clearly why it is 'Umpire's Call'. Second, independent audits of ball-tracking and operators' competence, with reports made public. Third, regular reassessment of whether the threshold percentages are shifting. With many believing that the number of 'Umpire's Calls' has risen over recent seasons, we need to know whether that reflects improved technology or a realistic use of the threshold.

My closing words are not for spectators but for decision-makers. If you want justice, showing an image of the ball hitting the stumps on screen will not be enough; you must let the spectator understand why it was not out. Because in cricket the foundation of trust is not the accuracy of a machine but the honesty of explanation. And where there is no explanation, one review can create another controversy, shaking not just a match but faith in the whole game.