LBW in Cricket: Complete Guide to Leg Before Wicket Rules and Decision-Making
The complete guide to LBW dismissals — all five conditions that must be met, impact outside off stump, playing a shot, DRS interaction with LBW decisions, and why LBW is cricket's most complex dismissal to judge.
Leg Before Wicket (LBW) is cricket's most complex dismissal — a batter is out if the ball hits their leg (or body, excluding the bat) before the wicket, provided it would have gone on to hit the stumps. The complexity comes from multiple conditions that must all be satisfied simultaneously, and the umpire must assess each on a ball they have only seen once in real time. LBW is the dismissal most affected by DRS technology, which can verify three of the five conditions through ball-tracking and edge detection.
The Five LBW Conditions
All five conditions must be met for an LBW dismissal: (1) The ball must not have first touched the bat (no edge before hitting the pad); (2) The impact must not be outside the line of off stump — the ball must hit the leg or body on the stumps line or further toward leg; (3) The ball must have pitched on the stumps line or on leg-side (if pitched outside off, it cannot be LBW); (4) The ball must be going on to hit the stumps — it cannot be missing the stumps; (5) If the batter played a genuine shot, the impact must be on the line of stumps or further — impact outside off stump can still be out if no shot was played.
The Shot-Playing Rule: Padding Up vs Playing
The distinction between playing a shot and padding up creates one of LBW's most contested decisions. If a batter plays a genuine shot — swings the bat toward the ball — and is hit on the pad outside the off-stump line, they cannot be out LBW regardless of where the ball was going. If a batter 'pads up' — deliberately deflects the ball with their pad without playing a shot — they can be given out even if the impact is outside off stump, as long as the ball would have hit the stumps. The question of whether a batter 'played a shot' is highly subjective and is one of the most contested aspects of LBW umpiring.
DRS and LBW: How Technology Changed Decisions
DRS technology can verify three of the five LBW conditions: UltraEdge can detect whether the ball touched the bat before the pad (condition 1); Hawk-Eye ball tracking can show where the ball pitched (condition 3), where it impacted the batter (condition 2), and where it was predicted to travel after impact (condition 4). The one condition DRS cannot easily verify is whether the batter was playing a shot (condition 5) — this remains a judgment call. The introduction of DRS has increased the number of LBW dismissals overall, because umpires who previously gave batters the benefit of the doubt now know that marginal not-out decisions will be reviewed.
Frequently asked questions
Why do LBW decisions remain so controversial even with DRS technology, and is the Umpire's Call element of DRS appropriate for LBW decisions?
LBW decisions remain controversial with DRS because ball-tracking prediction involves a margin of error that the 'Umpire's Call' rule explicitly acknowledges, and the two different outcomes from the same marginal decision (given out upheld vs given not-out upheld) create asymmetric results that batters and teams find frustrating. The ball-tracking controversy: Hawk-Eye's LBW predictions are based on the ball's trajectory before impact, extrapolated to show where it would go after impact. The model uses the ball's pace, spin, and trajectory at impact to predict the post-impact path. For straight deliveries on pitches with no turn, the prediction is relatively accurate. For deliveries that are cutting in or swinging late, the prediction is less reliable because the model assumes the ball continues its trajectory without the complex physics of post-pad-contact ball movement. Teams dispute specific LBW predictions regularly, particularly for spin bowlers. The Umpire's Call asymmetry: if a given-out LBW is reviewed and ball-tracking shows the ball is Umpire's Call (marginally hitting the stumps), the on-field out decision stands. If a given-not-out LBW is reviewed and ball-tracking shows Umpire's Call, the not-out stands. Same ball-tracking result (marginal hit), different outcomes depending on the original umpire decision. This asymmetry means the original umpire decision matters even in the review system — a system that was intended to remove human error still preserves it in marginal cases. Is Umpire's Call appropriate: the ICC's defense is that ball-tracking is not accurate enough in the marginal zone to override an experienced umpire's real-time judgment. If the ball is clearly hitting (outside Umpire's Call zone), the review overturns; if marginal, the umpire's view is preserved. This is technically defensible but creates the frustration of a technology-review system that still depends on the original decision in close cases.