Post
travel

Why LBW starts more arguments than any other dismissal

Every village club has one. The bowler who appeals for leg before wicket from mid-on, the batter who taps the pitch twice and stares at the umpire as if a personal insult has just been offered, and the tea-time inquest where everyone is suddenly an expert on trajectory. LBW is the most technical dismissal in cricket and, at grassroots level, the one most often decided on a single angle and a moment's judgement. Understanding how the decision is actually reached makes it easier to accept as a player — and much easier to give with confidence if you find yourself standing at the bowler's end on a Saturday afternoon.

The umpire's checklist: what has to be true

A leg before wicket decision is not a single opinion, it is a sequence of conditions. The umpire at the bowler's end works through them in order, and if any one fails, the finger stays down.

  • It must be a fair delivery. A no ball cannot produce an LBW, however plumb it looks. The front foot and the bowler's arm both matter, and the umpire should be watching the line before they watch the ball.
  • The bat must not have touched the ball first. If the ball hits the bat, or the glove of the hand holding the bat, before it hits the pad, it is not out.
  • Where did the ball pitch? A ball pitching outside leg stump kills the appeal instantly, no matter where it hits the batter.
  • Where did it hit the batter? In line with the stumps, or outside the off stump. This is where most of the confusion lives.
  • Would it have gone on to hit the stumps? The umpire has to be satisfied the ball was heading for the wicket, not sailing over the top or sliding past leg.

Pitching and impact: the two lines that decide most shouts

The pitching condition is the simplest and the least forgiving. If the ball pitches outside the line of leg stump, the batter cannot be out LBW under any circumstances. It does not matter that it would have thudded into middle. It does not matter that the batter was padding up with no intention of playing a shot. The line of the pitch, from the umpire's view, ends the conversation.

Impact is subtler. When a batter has played a shot — and a half-hearted prod counts as a shot — the ball must strike them in line with the stumps, between wicket and wicket. If the point of contact is outside the line of off stump and a shot has been offered, the answer is not out, full stop. So when a seamer nips one back and raps a batter on the front pad a foot outside off, the umpire should be shaking their head, however loud the appeal.

If no shot is offered at all — a batter shouldering arms, or padding up with the bat behind the pad — the impact can be outside the line of off stump and it is still out, provided the ball pitched in line and was going on to hit. Those two contrasting rules are precisely why the same delivery can look out to the bowler and not out to the batter, and both can be technically right depending on what the batter did with the bat.

Height, bounce and the "would it have hit?" question

The final condition is the one that causes the most quiet agonising. From 22 yards, the gap between clipping the top of middle and clearing the bails is a matter of inches, and the umpire has to project a moving ball forward through the stumps after it has already bounced, seamed or spun.

Three things help. First, the trajectory after pitching: a ball that has already started to loop up is unlikely to hit the stumps, while one that skids through low is a strong candidate. Second, the height of contact: a ball hitting the batter above the knee roll on a slow, low village pitch is usually going over, whereas on a damp early-season track it may well be hitting. Third, the bowler's type: a tall seamer extracting steepling bounce and a slow left-armer turning it into the pads create very different projections. Where there is genuine doubt about whether the ball would have hit, the batter gets the benefit. Giving LBW on guesswork is how an umpire loses a dressing room.

Umpiring at club level: one angle, no replays

Most grassroots matches have one umpire at the bowler's end and, if you are lucky, a volunteer at square leg who is probably keeping a close eye on their own team's interests. There is no ball tracking, no replay, no third umpire, and no slow-motion zoom on the point of impact. What you have is a line of sight straight down the pitch, which is genuinely the best position for judging line, and a great deal less help with height.

Practical habits make a difference. Watch the bowler's front foot first, then lock your eyes on the ball. Judge where it pitched while it is still in the air, not after it has hit the pad. Do not be swayed by the volume of the appeal — a good club side appeals for everything, and a young bowler appealing alone is not evidence of anything. And be consistent: if you have given the waist-high ball on the knee roll all afternoon, give it at 5pm when your own club is batting.

Talking it through afterwards

Part of what makes village cricket so enjoyable is that the LBW debate carries on over the tea table and into the bar. Bowlers are entitled to be disappointed, and batters are entitled to disagree, but the umpire's decision stands. If you play, learn the two lines — pitching and impact — well enough to know when you have genuinely been hard done by and when you simply misjudged one off the pads. If you umpire, take your time, work through the conditions in order, and remember that "not out" is a proper, defensible answer to a difficult question. Then go and put the kettle on.

Michael Greaves
Web developer since 2006. Create hundreds of websites, HTML and CSS3 expert, who started to learn web design on a world-class level.

Leave a comment