LBW, Umpire's Call and DRS Reviews: A Practical Guide
LBW reviews in the DRS era require understanding 'umpire's call'. This guide explains when a review for LBW succeeds, when it fails despite looking out, and how to read DRS ball-tracking graphics.
DRS reviews for LBW are the most technically complex decisions in cricket officiating. The review process examines three questions in order: Did the ball pitch outside leg stump? (if yes: not out, review successful if on-field was out); Did it hit the bat? (if yes: not out, review successful if on-field was out); and Where would the ball have gone if uninterrupted? The third question introduces 'umpire's call' — a zone where the technology's prediction is not precise enough to overturn the on-field decision.
Understanding Umpire's Call
Umpire's call applies when the ball-tracking prediction falls in a marginal zone: impact on the outer 50% of the ball's width at the stumps (width call), or at the outer ball's width above the bails (height call). If the ball would have hit the stumps in this zone, the on-field decision stands — whether that was out or not out. An 'umpire's call not out' means the technology predicts the ball would have clipped the stumps but not clearly enough to overturn. Critically, a review that ends in umpire's call is NOT a wasted review — the team retains their review.
Reading the DRS Graphics
DRS LBW graphics show: (1) the ball's actual path to impact (yellow line); (2) the predicted path beyond impact (blue or green line); (3) the stump zone with a highlighted area showing where the predicted path meets the stumps. Red means clearly out; yellow means umpire's call; green means missing the stumps. These are shown on-screen for broadcast viewers and on the third umpire's monitor. The graphic reads left-to-right for the path, then shows an end-on view of the stumps with the impact zone coloured.
When to Review for LBW
Effective DRS strategy for LBW reviews involves assessing: did the ball pitch in line? (is there any doubt about leg stump pitching?); did the ball hit the bat? (any sound or movement suggesting an inside edge?); was it hitting the stumps? (was the ball nipping back, or going straight on?). Teams with strong review cultures practise the decision — the batter signals to their captain with a clear yes/no within seconds of the on-field decision. Reviews taken by gut feel alone, or after 15 seconds' deliberation, generally succeed at lower rates.
Frequently asked questions
What happens if a team has no reviews left and wants to challenge an LBW?
If a team has exhausted all their reviews, they cannot challenge any further on-field decisions in that innings, regardless of how clearly wrong a decision appears. This is why review management — not wasting reviews on marginal calls — is so important. In Tests, reviews reset after 80 overs of play to give both sides fresh opportunities later in long innings.
Does DRS apply to wides and no-balls?
No. DRS cannot be used to review wide calls or front-foot no-ball calls. Wide decisions are made by the on-field umpire and are not reviewable. Front-foot no-balls are checked automatically by the third umpire on every delivery in most ICC events, so no review is needed for them. Teams can review caught-behind, run-out, and LBW decisions only.