Skip to content
Rules5 min

Umpire's Call in DRS: What It Means, Why It Exists, and the Controversy Around It

Umpire's Call is one of cricket's most contentious provisions — the rule that preserves the on-field umpire's original decision when the ball-tracking system (Hawk-Eye) predicts the ball would have hit the stumps, but within a 3.5cm margin of error zone. When the DRS review shows the ball 'clipping' the stumps but within this uncertainty zone, the on-field decision stands — whether Out or Not Out. Critics argue this creates perverse outcomes: an umpire who gave Not Out can survive a review even when Hawk-Eye shows the ball hitting the stumps. Supporters argue it correctly represents the limits of technology.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

What Umpire's Call means: when a batsman or fielding team reviews an lbw decision using DRS, Hawk-Eye reconstructs the ball's predicted trajectory — where it would have gone if the batsman's pad had not been in the way. The Hawk-Eye prediction then either: (A) Shows the ball missing the stumps entirely → Not Out confirmed, review upheld. (B) Shows the ball hitting the stumps clearly → the umpire's decision is overturned to its opposite (if Not Out → becomes Out; if Out → stays Out). (C) Shows the ball within the Umpire's Call zone — clipping the edge of the stumps within the 3.5cm margin of error → the original umpire's decision stands. The 3.5cm zone: Hawk-Eye's margin of error is approximately 3.5cm in predicting ball trajectory. When the ball is predicted to be within this zone of hitting or missing the stumps, the result is treated as genuinely uncertain — and the on-field umpire's judgment is deferred to rather than overridden. The perverse outcome: if the on-field umpire gave Not Out, and Hawk-Eye shows the ball clipping the stump edge (within 3.5cm), the decision remains Not Out. If the on-field umpire had given Out for the same ball, it would remain Out. The same Hawk-Eye image produces a different final decision depending on what the umpire said — critics find this logically inconsistent.

Why the ICC Defends Umpire's Call'

The ICC's reasoning for Umpire's Call: (1) Hawk-Eye is a prediction, not a measurement. The system uses cameras filming at 100fps to reconstruct where the ball travelled before impact (the gap between the pad and the stumps). But the ball's predicted path after impact is extrapolated from this data — not directly observed. Over a distance of 0.5-1.5 metres of reconstruction, small errors compound. The 3.5cm uncertainty zone represents where the technology's confidence falls below a threshold. (2) 'More likely out than not' is not enough: the ICC's philosophy is that Hawk-Eye should override the umpire only when the evidence is clear — not just marginally more likely one way than another. If a ball is 60% likely to clip the stumps, that means 40% of equivalent balls miss. In a justice system (where 'beyond reasonable doubt' is the standard for conviction), a 60% probability is insufficient. (3) The umpire should not be removed entirely: DRS was designed to remove clear errors ('howlers'), not to replace umpire judgment entirely. Umpire's Call preserves a domain of uncertainty where the umpire's visual judgment (on the ground, in the moment) is given weight. The counter-argument: critics note that the same ball produces a different result depending on the umpire's original call — this violates the basic principle of consistency. A batsman dismissed Out by an umpire has no recourse even if Hawk-Eye shows the ball clipping the stumps, while a batsman given Not Out is saved by the same Hawk-Eye image. The inequity is particularly stark when: the fielding team reviews (seeking Out) and gets Umpire's Call — the Not Out stands and they lose a review. The batting team reviews (seeking Not Out) and gets Umpire's Call — the Out is upheld and they lose a review. The batting team is always worse off when Umpire's Call upholds an Out decision.

The 2023 World Cup Final lbw — Umpire's Call controversy: the 2023 ICC World Cup Final (India vs Australia, Ahmedabad) produced the highest-profile Umpire's Call controversy in the rule's history. In the Australian second innings, a review showed the ball clipping the stump edge — within the Umpire's Call zone. The on-field decision was Not Out; Umpire's Call preserved Not Out. The batsman (Travis Head) went on to score 137 — winning Australia the match by 6 wickets. The post-match debate: critics argued the ball was clearly hitting the stumps and Hawk-Eye's visualisation showed it clipping middle stump. Supporters noted that the 3.5cm zone is there precisely to handle this situation — if the ball is this close to the stump edge, it is genuinely uncertain whether it would have hit. The broader debate this provoked: this specific incident — a World Cup Final decided partly by Umpire's Call — reignited calls for either abolishing Umpire's Call entirely or for separating ball-tracking accuracy from the decision threshold. Some analysts called for a 'best estimate' model — where Hawk-Eye's central prediction is used regardless of margin of error, accepting that technology has a known error rate but is more accurate than human judgment. The ICC has not implemented this change.

How Reviews Work Under the Current System'

DRS review process for lbw: when a team uses a DRS review on an lbw decision, three elements are checked in sequence: (1) Ball-tracking for impact location: where did the ball pitch? (Off stump, outside off, on leg stump, etc.) A ball pitching outside leg stump cannot be lbw — Not Out immediately regardless of trajectory. (2) Ball-tracking for impact with pad: where did the ball hit the batsman's pad? If above knee roll (approximately waist-high impact), Not Out regardless of predicted trajectory. (3) Ball-tracking for predicted trajectory: where would the ball have gone? This is where Umpire's Call applies — if the ball would have clipped the stumps within the 3.5cm zone, Umpire's Call activates. How reviews are consumed: each team starts with 2 reviews (Tests) or 2 reviews (ODIs/T20Is — though in some tournaments it's 1). Unsuccessful reviews are lost; successful reviews preserve the review count. Umpire's Call result: an Umpire's Call verdict does NOT cost the reviewing team their review — even though the decision stands, the review is retained. This was a later addition to the DRS rules — originally Umpire's Call DID cost a review, which was perceived as doubly unfair (the umpire's error was close but not overridden, AND the reviewing team lost a review). The retention of reviews on Umpire's Call outcomes is considered the correct rule — it doesn't penalise a team for a genuinely marginal decision. Review strategy: teams increasingly use statistical analysis of when to review — knowing which umpires tend to err on lbw decisions (more 'Out' or more 'Not Out' biases), which grounds favour lbw dismissals (drier pitches = lower bounce = more lbw risk), and which batsmen tend to play with pad-bat gaps that increase lbw vulnerability.

The lbw criteria summary — all must be satisfied: (1) Ball must not pitch outside leg stump → if it does, Not Out regardless. (2) Ball must not impact above the knee roll → if it does, Not Out regardless. (3) Ball must be hitting the stumps → if Hawk-Eye shows it missing, Not Out. The additional criteria for bat-first contact: if the ball hit the bat before the pad, it cannot be lbw (the ball must hit the pad first, or simultaneously). If the ball hit bat before pad, Not Out regardless of trajectory. The 'playing a shot' exception: if the batsman is NOT playing a shot (pad is simply in front of the stumps, not an attempted defensive or attacking stroke), the ball does not need to pitch in line with the stumps — it can pitch anywhere outside off stump (not outside leg stump) and still be given lbw. If the batsman IS playing a shot, the ball must pitch in line with the stumps (between off and leg stump, or on the stumps) to be lbw. This is why batsmen sometimes pad the ball deliberately on the off side — if they play no shot, the ball must be pitched in a very specific corridor to be lbw; if they play a shot and miss, the ball pitched anywhere can be lbw.

Frequently asked questions

What is Umpire's Call in DRS?

Umpire's Call is a DRS outcome that occurs when Hawk-Eye predicts the ball would have hit the stumps, but within a 3.5cm margin of error zone. When Umpire's Call is triggered, the on-field umpire's original decision stands — whether Out or Not Out. The reviewing team does not lose their review in an Umpire's Call outcome (a rule introduced to reduce the unfairness of the provision).

Why is Umpire's Call controversial?

Umpire's Call is controversial because the same Hawk-Eye image produces a different result depending on what the on-field umpire originally said. If the umpire gave Not Out and Hawk-Eye shows the ball clipping the stumps within the zone, Not Out stands. If the umpire gave Out for the same ball, Out stands. Critics argue this is logically inconsistent; supporters argue the 3.5cm uncertainty zone correctly represents the limits of ball-tracking technology.

How many DRS reviews does each team get?

In Test cricket, each team has 2 DRS reviews per innings. In ODIs and T20Is, each team typically has 2 reviews per innings (though some tournaments use 1). Reviews are lost on unsuccessful challenges; successful challenges preserve the review count. Umpire's Call decisions do not cost the reviewing team their review — even though the original decision is upheld.

What happens if a ball pitches outside leg stump in cricket?

A ball pitching outside leg stump cannot result in an lbw dismissal, regardless of the ball's subsequent trajectory or where it hits the pad. 'Pitching outside leg stump' means the ball's first bounce was to the leg-side of the leg stump. This is checked via ball-tracking in DRS — if confirmed, Not Out is the immediate outcome before trajectory prediction is even considered.