Umpire's Call in DRS Explained

The Decision Review System made its Test debut in a 2008 series between Sri Lanka and India, and within a few seasons it had changed how every close lbw appeal in international cricket was argued, reviewed and replayed. Yet no part of the system generates more confusion — or more televised outrage — than umpire’s call: the verdict where ball-tracking shows the ball clipping the stumps, the big screen flashes its graphic, and the original decision stands anyway. Two batters can receive opposite outcomes from identical deliveries, purely because two umpires made different initial calls. That is not a glitch. It is the system working exactly as designed.

The Three Zones Ball-Tracking Judges

When an lbw review goes upstairs, the ball-tracking technology assesses three separate questions in sequence. First, where the ball pitched — it must not have pitched wholly outside leg stump. Second, the point of impact with the pad — for an out decision, impact must be in line with the stumps, unless the batter offered no shot. Third, the projected path — whether the ball would have gone on to hit the stumps. These mirror the requirements of the lbw law itself; the technology simply answers each question with a measurement instead of a judgement.

Umpire’s call can arise on the pitching, impact and wicket-hitting elements. On each one, the system distinguishes between a conclusive answer and a marginal one. If less than half the ball is shown hitting the relevant zone, the evidence is deemed too marginal to overturn a human decision — so the on-field call survives, whatever it was. Only when the tracking shows a clear majority of the ball doing what the fielding side claims does the technology overrule the umpire.

Why the Margin Exists at All

Ball-tracking does not photograph the future. It records the ball’s actual flight up to the moment of impact with the pad, then projects the remainder of the path mathematically. The shorter the distance between pitching and impact, and the further the impact point from the stumps, the more the projection relies on extrapolation rather than observation. The system’s makers have always acknowledged a small margin of error in that projected path.

Umpire’s call is the sport’s answer to that uncertainty. Rather than pretending the projection is perfect, the protocol says: where the technology’s answer falls inside its own error margin, the human decision — made in real time by a professional umpire standing in the best position on the ground — is the tiebreaker. It is a deliberate philosophical choice by the game’s lawmakers and the International Cricket Council: technology exists to remove clear mistakes, not to re-officiate every marginal decision. Critics argue a ball clipping the stump would still dislodge a bail and should always be out; defenders reply that “clipping” on the graphic is a probability, not a certainty, and the graphic’s clean animation disguises that.

How the Protocol Has Evolved

The system has been tuned repeatedly since 2008. The most consequential adjustment came in 2021, when the wicket zone used for the “hitting” judgement was enlarged so that its upper edge ran to the top of the bails rather than the bottom — a direct response to bowlers’ complaints that deliveries clearly brushing the bails were being returned as not out on height. The same package of changes confirmed another crucial mechanic: a side does not lose its review when the outcome is umpire’s call. The logic is fair enough — the review was not wrong, merely unproven — and it changed how aggressively captains could afford to review.

The third umpire’s role has grown alongside the technology, from a run-out adjudicator to the manager of a full review protocol involving tracking, UltraEdge audio and slow-motion replays. The way the third umpire now shapes modern matches is a story in itself, and umpire’s call sits at the centre of it: the one verdict the TV official is explicitly forbidden from overturning.

How Captains Play the Grey Area

Because a review survives an umpire’s call outcome, sharp captains treat marginal lbw shouts differently depending on the original decision. When the on-field call was not out, the fielding side knows a “clipping” projection will not overturn it — so a review is only worth burning when the bowler and wicketkeeper genuinely believe the ball was hitting a substantial part of the stumps. When the on-field call was out, the batting side faces the mirror image: even a review showing the ball only just hitting will confirm the dismissal.

This is why the wicketkeeper has become the most important voice in any review conversation. Standing directly behind the line, the keeper judges height and direction better than anyone, and the best fielding units have turned the fifteen-second review window into a structured drill: bowler’s instinct, keeper’s line, captain’s decision. Reading an umpire’s signals and body language matters too — a slow, reluctant not out invites a review far more than an emphatic one, which is one of several reasons understanding umpires’ signals repays any close watcher of the game.

The Case For Keeping the Grey

Umpire’s call will never satisfy everyone, because it makes visible something sport usually hides: the limits of measurement. But the alternatives are worse. Removing it and trusting every projection as gospel would hand marginal decisions to a simulation with a known error margin. Widening it would gut the review system’s power to fix real mistakes. The current balance keeps umpires meaningful, keeps technology honest about its own precision, and — not incidentally — keeps the drama of the tracking replay alive. When the graphic rolls and half the ground goes silent, the sport has lost nothing by admitting that some decisions live on a knife’s edge.