The Grey Zone of Umpire's Call: DRS Technology and the New Geography of Cricket Verdicts

The Grey Zone of Umpire's Call: DRS Technology and the New Geography of Cricket Verdicts

On the big screen, the 3D ball-tracking line froze and the stadium held its breath. The projection showed the ball clipping the inner edge of leg stump — the path dipping less than half a centimetre inside the line of the stumps. The on-field umpire had given it out. The tracking said the ball would have hit, but inside the 'umpire's call' margin. The verdict stood: out.

The batter walked off with his head down. From the dugout the coach spread his hands at the replay. In the commentary box I stayed silent, because I know the entire contradiction of cricket's most disputed rulebook lives inside that single second. Is umpire's call a genuinely 'correct' decision, or a diplomatic excuse for hiding technology behind procedure?

I have seen this scene many times. When I was working on VAR in football, the same question followed me: does technology clarify verdicts, or open a new door for dodging responsibility? In cricket the answer is even more complicated, because a cricket verdict does not rest on a line; it rests on a margin — the margin called umpire's call.

[Context: Law, History, Application]

DRS first took the field in July 2026, in a Test between India and Sri Lanka. It began as an experiment. Ball-tracking, Hot Spot, Snicko, UltraEdge — the technology basket grew heavier. But the more technology advanced, the sharper one question became: if the machine is more accurate, where is the room for human judgement?

This is where umpire's call is born. For LBW, if ball-tracking shows the ball would hit the stumps but the projection is very close to the edge — that is, if less than half the ball is predicted to strike the stumps — the technology declines to decide. It says: let the on-field umpire's decision stand. In cricket's language, that is umpire's call.

Two arguments sit behind the rule. The first is technical: ball-tracking is not perfect, it carries a margin of error, so deciding on the boundary line invites mistakes. The second is institutional: the authority of the on-field umpire cannot be entirely erased, or the human pillar of the game weakens.

But neither argument answers a third question: why does the same ball, the same projection, produce two different outcomes in two matches? If the ball hits the edge of the stump and the umpire has already given it out, it stays out; if he gave it not out, it stays not out. The technology's answer is nearly identical, but the verdict depends on the human's prior call. This is where the grey zone is born.

During the 2026 U-17 World Cup I built a database — 52 matches, 1,248 referee decisions, 78 VAR checks, an average of 4.2 minutes of added time. That football database does not map onto cricket exactly, and I state the limit plainly: football offside and cricket LBW are entirely different geometries. But the architecture of decision-making in both games raises the same question — does technology decide, or does it share the blame for a decision?

[Core: Four Angles of the Replay]

The Mathematical Limit of Ball-Tracking

Ball-tracking works by analysing multiple camera frames. Ball speed, spin, bounce, air movement — together they estimate the future path. But an estimate means a chance of error. If the ball turns off the pitch, or swings in the air, the error near the boundary line grows. The half-ball-width margin of umpire's call is designed precisely to absorb that error.

Here lies the first discomfort. If the machine's error margin is known, why is it not shown transparently to the crowd? On the big screen we see the ball's line, but not the margin of error. We see the words 'umpire's call', but not the number behind them. Without transparency, technology simply creates a new kind of mystery.

Umpire's Call and the Clash with Human Authority

Say an LBW review shows the ball would have hit the stumps, but on the boundary line. The on-field umpire gave it out, so it is out. In another match, the same projection, but the umpire gave it not out, so it is not out. In both cases the technology says nearly the same 'truth', yet the outcomes differ.

This is not a question of justice but of consistency. Players cry bias, but something else is happening — the verdict depends on the on-field umpire's prior estimate. Umpire's call is not the technology's decision; it is a protective ring around the field decision. This design protects the umpire, but it muddles the idea of fairness.

The Lesson of the Soft Signal

For catches there was once a 'soft signal' system — the on-field umpire signalled his initial estimate, then the TV umpire searched for evidence. If evidence was inconclusive, the field signal stood. In 2026 the ICC removed it, because the soft signal valued assumption over evidence.

That is a telling precedent. When cricket realised the soft signal was creating problems, it scrapped it. So why is the same question not asked of umpire's call in LBW? The answer: because in LBW 'evidence' and 'margin' blur together, and deciding on the boundary is risky even for technology. But the question remains.

Player Psychology and the Arithmetic of Reviews

Losing one review means losing one of two. So a player's first question becomes: am I inside the margin or outside it? This arithmetic changes the tempo of the game. From my years of watching matches, I can say batters now review on probability rather than proof. 'It was probably outside leg' — that doubt alone often burns a review.

Yet the same batter accepts being out inside the margin, because he knows the rule. The problem arises when the same projection gives two outcomes in two matches. Then the player feels the rules have changed. A lack of consistency breaks trust, and when trust breaks, technology itself falls under suspicion.

[Contrarian: Emotion versus Rule]

The biggest confusion around umpire's call is that it is debated in the language of emotion, not of law. After a match, commentators call it 'heartbreaking'. Fans say 'the umpire wronged us'. But nobody spells out what the half-ball-width margin actually is, and why it sits exactly where it does.

There is an unpopular truth here. If we remove umpire's call entirely, every boundary-line projection must be handed to the machine. Then a ball striking just under half the stump is out, and just over half is not out — a difference so fine no human eye could grasp it. The crowd would be more confused, not less.

And if we keep umpire's call, the same projection will produce two outcomes, which some will read as discrimination. Both paths carry a problem. The real problem is neither technology nor umpire — it is that cricket has never properly explained the logic of this margin to its audience.

This is where the lesson of football's offside reform matters. The semi-automated offside at the Qatar World Cup was not just technology; it was a new way of seeing the line. The offside revolution was not merely a machine; it was a new way of seeing the line. Cricket now stands at exactly that moment — but cricket has not yet crossed its offside moment.

[Takeaway: Forward]

When I say 'I built the Referee', I am not boasting; I am speaking of responsibility. Because building a referee means building rules, and building rules means erecting a framework that gives the same outcome in the same situation. Cricket's next reform must therefore be about the LBW margin, not merely the boundary line.

Step one: every ball-tracking replay should display the margin of error transparently, so the crowd understands why a verdict fell under the shadow of umpire's call. Step two: the umpire's call decision log should be stored and analysed over a decade, just as I logged referee decisions in the 2026 U-17 World Cup database. Step three: with the courage that scrapped the soft signal, cricket should openly reconsider the LBW margin itself.

I know this reform is not easy. Every margin is a question of power, and nobody yields quickly on power. But if cricket truly trusts technology, it should trust technology's limits too — and admitting a limit is the first step of trust.

So the question remains for players, for fans, and for those decision-makers holding the rulebook: do you want to give technology the power to decide, or keep it merely as a defence of your own decision? Cricket's next decade of reform will be settled here.