Umpire's Call: When the Machine Knows Everything, the Human Still Hesitates

Fifty thousand people stopped breathing at once. On the giant screen the ball turned in slow motion — grazing leg stump, almost touching, almost not. Then two words floated up: Umpire's Call. The man standing in the middle of the ground nodded, and his original verdict survived. The batter walked off, slapping his knee. In the stands was born a strange silence — the silence of anger, of helplessness, the silence that does not understand why the machine, knowing everything, refused to speak the last word.

Inside that single moment sits modern cricket's most contested question. We called the machine in to reduce error. Yet the more precisely the machine sees, the more it falls quiet, handing the decision back to the human on the field. The machine's job here is not to tell the truth but to legitimise human doubt — and that legitimacy is cricket's deepest discomfort.

DRS first stepped onto a field in July 2026, in the Test series between India and Sri Lanka. Hawk-Eye's ball-tracking, UltraEdge's sound detection and the third-umpire protocol together built a new judicial system. Initially batters had limited reviews; later came LBW, catches, even some wide and no-ball reviews. What entered the rulebook was a protected verdict: the on-field umpire's call.

The law looks simple. For LBW, if ball-tracking shows the ball would hit the stumps and more than half the ball is hitting, it is out. But if the ball would have hit the stumps only marginally — less than half the ball — the decision returns to the on-field umpire, whose original call stands. Impact line, turn, bounce: the machine computes all of it, yet the final step is touched by a human hand.

That is where the real tension begins. Covering the 2026 World Cup in Russia, I logged 455 VAR checks. When the first VAR penalty arrived in the 58th minute of France vs Australia, I understood something: the machine never argues, it only shows. In Russia the replay did not argue; it showed me my blind spot. Cricket's DRS does the same, but adds a layer — it legitimises the machine's certainty and human doubt at once.

DRS was never designed as a truth machine; it was designed as a system of checks and balances — where the machine supplies proof and the human keeps final authority. That design is historical. Handing complete power to technology would render umpires irrelevant. And cricket cannot run without them: no-balls, wides, time-wasting, on-field discipline, player conduct. So the protocol never let the machine become a dictator; it made the machine a witness, not a judge.

Yet that safeguard carries a price. To the spectator the message reads: the ball was hitting the stumps, the screen showed it, and still nobody is out. That is where reason and feeling crack apart. Reason says the decision is correct. Feeling says we have been made fools of. The more I watch, the more I believe DRS's biggest problem is not its error but its explanation.

Imagine a batter reviews and the screen flashes 'Umpire's Call'. Who won? Nobody. The batter lost a review, the umpire was protected, the crowd got another unfinished story. Umpire's Call is not a decision at all; it is the name of an undecided state — a ball suspended between machine and human.

In 36 years of watching I have seen this suspended state hurt spinners most. Spin turns into the stumps at an angle, often clipping them with less than half the ball. Pacers drive straight through and cover a larger portion, so they earn more 'out' verdicts. Same rule, different outcome — a silent bias.

Accuracy itself is questioned. Hawk-Eye predicts the ball's path over the final few feet. Prediction is never fully certain, so the protocol keeps a margin — and that margin becomes the centre of the dispute. At the 2026 U-17 World Cup in Delhi, covering all 52 matches, I explained Spain's 10th-minute goal and England's 44th-minute equaliser by timestamp. I learned then: spectators do not accept a decision, they want to see its reason.

Why is Umpire's Call not scrapped? The reason is tactical, not moral. If umpires knew every doubtful call would be overturned, they would unconsciously lean on reviews, or stop giving decisions out of fear. Either way the game suffers. The protocol gives them a safety net: the ball was hitting, so I was not wrong — at least in proof. That net saves the umpire's confidence, but it taxes the batter's faith.

And who pays that tax? Usually the batter, especially the touring side. Home conditions, camera calibration, pitch behaviour, even crowd noise — together they shape the umpire's instinct. With limited reviews, teams are forced into arithmetic: which doubt deserves a review. A strange tactic is born — the cricket of saving reviews.

In 2026, when the world stopped, I called Borussia Dortmund 4-0 Schalke from Delhi with zero fans in Signal Iduna Park. Referee Deniz Aytekin's whistle echoed through the empty ground; I logged 22 fouls, four yellow cards, the players' shouts. The empty stadium taught me that silence can be the loudest decision. Umpire's Call is one form of that silence — nobody says anything, yet everyone understands.

Now the angle the camera misses. We all watch the ball-tracking screen, but nobody watches the decision process behind it. What the third umpire sees, which frame he reads, how much margin he uses — all hidden from spectators. So an uncomfortable truth surfaces: we trust the machine's verdict, yet nobody can audit its settings.

Here lies DRS's hidden gap: a technology that arrived claiming transparency has itself become a black box — where everyone sees the input, no one sees the process, and the output hangs in front of all.

At fifty-two I still hear the old whistle beneath every new replay. The umpire once decided in a second; the machine takes five or seven — and in those seconds the whole stadium's emotion accumulates. A human decision was instant, so even when wrong it was forgiven. The machine's decision is slow, so even when right it is not forgiven.

Now the reverse, where I question my own side. Defending umpires, we forget that before technology cricket kept no account of error. Nobody knew what percentage of calls were wrong. DRS lit that darkness — and with the light came liability. We now keep accounts, so we feel the error. The question should not be 'how wrong is the machine', but 'how much accountability are we willing to give humans'.

Still, one truth must be admitted. Technology has reshaped cricket's power structure. The umpire was once final; now he is a reviewed official. That shift touches player psychology — some now raise a hand after every ball, looking at the screen, as if the game is being played not on the field but on the display. In football, VAR gave me the right angle but not always the right feeling — in cricket the phrase is literally true.

So what should be done? My proposal has three levels. First, the Umpire's Call explanation should be shown visually on the stadium screen — how much of the ball was hitting, why the verdict survived. Second, ball-tracking margins and settings should be independently audited regularly, and that data made public. Third, whether spinners and pacers are judged on the same standard should be published at fixed intervals.

Reform in technology comes not from changing rules but from widening the transparency of explanation — and explanation is cricket's next great struggle.

I thought I knew the whistle until Delhi hummed in binary. Even now, when 'Umpire's Call' appears, I understand the question is not machine versus human. The question is how much room we are willing to give humans when the machine has already seen everything. The answer still hangs there, exactly like that ball — grazing the stump, touching, not touching.