Cricket laws every fan should know, from lbw to DRS

Cricket's Laws are unusual among sports codes in that they were written to be read, not merely enforced. They are drafted in continuous prose, they contain long passages on the spirit in which the game should be played, and they explain their own reasoning more often than most rule books do. This is worth knowing, because almost every law that appears arbitrary turns out to be a solution to a specific piece of gamesmanship that someone tried once and everyone hated.

What follows is not a substitute for the Laws themselves, which are maintained by the Marylebone Cricket Club, nor for the playing conditions of any particular competition, which modify them. It is an explanation of the ones that decide matches and confuse newcomers, and of why each says what it says.

Leg before wicket

Lbw is the law that new viewers find hardest and experienced viewers argue about most, and both reactions come from the same source: it is a conditional law with several tests that must all be satisfied, and a decision can fail on any one of them.

The purpose is straightforward. The bowler's target is the stumps. If a batter could simply stand in front of the stumps and let the ball hit their leg, defending would be trivial and bowling would be pointless. Lbw exists to stop the pads being used as a second bat. Everything complicated about the law comes from trying to write that principle without punishing a batter who is genuinely trying to play the ball.

The tests, in the order an umpire applies them:

Was it a legal delivery? A no ball cannot produce an lbw, or any dismissal other than run out, obstructing the field or hitting the ball twice. This is checked first because it makes everything else irrelevant.

Where did the ball pitch? If the ball pitched outside the line of leg stump, the batter cannot be out lbw, no matter what happens next. The reasoning is about fairness of angle: a ball pitching outside leg is attacking the batter from a line where the pads necessarily get in the way of the stumps, and the batter has no reasonable opportunity to play it with the bat. A ball that pitches in line, or outside off, or does not pitch at all, passes this test.

Where did it strike the batter? If the point of impact is between wicket and wicket, the test is passed. If the impact is outside the line of off stump, the batter survives only if they were genuinely attempting to play a stroke. Offer no shot outside off and you can be given out; offer a shot and you cannot. This is the clause that produces the padding-away controversies, and it is the closest the Laws come to legislating for intent.

Would it have hit the stumps? The ball must be going on to hit the wicket. A ball turning or swinging past the stumps, or one striking a batter so far forward or so high that it would have cleared them, is not out.

Did it hit the bat first? Any contact with the bat or the glove holding the bat before it strikes the pad means not out, regardless of everything above. The bat has precedence.

There is a sixth consideration that never appears as a numbered test but governs the whole thing: the further forward the impact, the less confident anyone can be about the projection. This is the human reason umpires historically gave batters the benefit on the front foot, and it is the reason ball tracking is treated as less certain the longer the extrapolation.

No balls, and what they cost

A no ball is the umpire's declaration that the delivery was not a fair one. The common causes:

• Overstepping. Some part of the bowler's front foot must be behind the popping crease at the moment it lands, and the back foot must land inside the return crease. Every no ball for overstepping is measured at the instant the front foot lands, not where it slides to.
• Height. A delivery that passes above the striker's waist without bouncing is a no ball. A bouncer that passes above shoulder height is a no ball in the short formats and, beyond a permitted number per over, in the longer ones too.
• Too many short balls. Playing conditions limit bouncers per over, more generously in Tests than in Twenty20. The count varies by competition.
• An illegal action. Straightening the arm through the delivery swing beyond the permitted tolerance.
• Bouncing more than once, or rolling. A ball that pitches twice before reaching the popping crease, or that comes to rest in front of the striker, is a no ball.
• Fielding infringements. Too many fielders on the leg side, too many behind square leg, too many outside the circle in a restricted phase, a fielder or the wicketkeeper encroaching before the ball is played.

The common thread is that every one of these is a way of taking an advantage the batter cannot reasonably counter. A ball delivered from two feet down the pitch, a beamer at the head, a fielder already moving before release: the law does not distinguish between the deliberate and the accidental, because the batter's disadvantage is identical either way.

A no ball costs the fielding side a run, an extra delivery, and immunity for the batter from every mode of dismissal except run out, obstructing the field and hitting the ball twice.

Free hit

In white-ball cricket a no ball is followed by a free hit: the next legal delivery on which the batter cannot be dismissed by any means other than the ones listed above. The field may not be changed for a free hit unless the batters have crossed and swapped ends.

The free hit exists because the ordinary penalty for a no ball, one run and one extra ball, is trivially small in the context of a total in the two or three hundreds, and front-foot no balls were being treated as an acceptable cost of bowling flat out. Making the following delivery effectively unlosable for the batter turned a one-run penalty into an expected cost of several runs, and the frequency of no balls fell accordingly.

Two details catch people out. A free hit is not a free ball: the batter can still be run out, and dismissals do occur. And if the free hit delivery is itself a no ball, the free hit rolls over to the next legal ball.

Wides

A wide is a delivery judged to be out of the batter's reach, such that they could not play a normal cricket stroke at it from where they are standing. It costs a run and an extra ball.

The underlying principle is the same as the no ball: the bowler must give the batter something to hit. Without a wide law, the safest way to bowl at a set batter would be five yards down the leg side, and cricket would be unwatchable within one season.

Where confusion arises is that the standard differs sharply by format. In Test cricket the wide is judged generously to the bowler, and a ball passing outside off stump is very rarely called, because a Test batter is entitled to leave and a Test bowler is entitled to bowl a probing line outside off. In white-ball cricket there are painted guide markings on the popping crease, and anything passing outside them is usually called. Down the leg side the standard is strict in every format: a ball passing well down the leg side is a wide almost automatically, because there is no legitimate tactical reason to bowl there.

The other complication is the moving batter. A batter who charges down the pitch and moves outside leg stump changes what is within reach, and umpires judge the delivery against the batter's position when the bowler enters their delivery stride rather than at the moment of release. This prevents a batter from manufacturing a wide by walking across their stumps after the ball has been let go.

A ball that touches the bat or the batter is not a wide. A wide can still result in a stumping, a run out, a hit wicket or obstructing the field.

Obstructing the field

A batter is out obstructing the field if they wilfully obstruct or distract the fielding side by word or action. It is a rare dismissal and an uncomfortable one, because it always involves an accusation of intent.

The law absorbed the old separate dismissal of handled the ball, which is now treated as a form of obstruction. The current position is that a batter may not deliberately strike the ball with a hand not holding the bat, and may not use their body to prevent a fielder from making a play, unless they are acting to avoid injury.

Two distinctions matter.

Changing course while running is not automatically an offence. A batter is entitled to run where they like, but not to obstruct a throw at the stumps deliberately by moving into its path. Umpires look for a movement that has no purpose other than to interfere.

Playing the ball a second time is a different law. A batter may lawfully play the ball twice to defend their wicket, and only that. Knocking the ball away from the stumps with a second tap is permitted; hitting it a second time to score, or to stop a fielder gathering it, is not.

The reasoning is simple and worth stating: the fielding side is entitled to attempt a play, and a batter is entitled to run, but neither may use their body as an instrument against the other.

Timed out

An incoming batter must be ready to receive the next delivery, or for their partner to receive it, within a fixed period of the fall of the previous wicket. The period is three minutes under the Laws and shorter under some international playing conditions. If they are not, and the fielding side appeals, they are out timed out without facing a ball.

It is one of the rarest dismissals in the game and one of the most disliked, but the reasoning behind it is sound. Cricket has no clock, and without a limit there would be nothing to stop a batting side from running down the light, or a nervous player from taking a very long time to arrive. The law exists to make delay a losing tactic rather than a viable one.

Appealing for it remains a matter of intense argument about the spirit of the game, on the entirely reasonable grounds that a genuine equipment failure and a deliberate stall look the same from the boundary.

Retired out and retired hurt

These are two different things and the difference is the presence or absence of consent.

Retired hurt applies when a batter leaves the field because of injury or illness. They may return and resume their innings at the fall of a subsequent wicket or at the end of the innings. If they do not return, their innings is recorded as retired not out. No dismissal is credited to anyone.

Retired out applies when a batter retires for any other reason without the consent of the opposing captain. They may not return unless that captain consents. The innings is recorded as retired out and counted as a dismissal, though again no bowler or fielder is credited.

For decades retired out was effectively a dead letter, used only in exhibition circumstances. Twenty-over cricket revived it as a genuine tactic: a set batter who is struggling against a particular type of bowling, or is out of gas in the last few overs, can be replaced by a fresh striker better suited to the situation. It is a legal and rational use of the law, and it still provokes a strong reaction, largely because a batter walking off unbeaten offends an instinct that predates the format.

Dead ball

The ball is dead when it is finally settled in the hands of the bowler or the wicketkeeper, when it reaches the boundary, when a batter is dismissed, and in a list of other defined circumstances. Nothing can happen while the ball is dead: no runs, no dismissals.

The umpire may also call and signal dead ball. The reasons include a serious injury, a ball that leaves the batter unsighted, an unfair distraction, an intervention by someone not part of the game, or a delivery the umpire judges the batter was not ready for. The most common practical use is the one nobody notices: an umpire calling dead ball when a batter pulls away because a sightscreen has moved or a bird has landed on the pitch.

The purpose is to give the umpire a general-purpose reset. Cricket is played over long periods in open public spaces, and the Laws could not possibly enumerate everything that might interrupt a delivery. Dead ball is the clause that lets the umpires deal with all of it.

Its edge cases are among the most disputed in the game, because a dead ball call can wipe out a boundary or a wicket that has already visibly happened, and there is no appeal against it.

The Decision Review System

DRS is a process, not a law, and it sits on top of the Laws rather than changing them.

It has two components. Umpire reviews are initiated by the on-field umpires, typically for run outs, stumpings, boundary calls and whether a catch carried. These are unlimited. Player reviews are initiated by the fielding captain or the dismissed batter, within a short window after the decision, by making a T sign. Each side has a fixed number of unsuccessful player reviews per innings, more in Tests than in the white-ball formats, and the exact allowance and any top-up provisions vary by competition.

The third umpire has access to several tools: multiple camera angles, super-slow-motion, a real-time snickometer or equivalent audio waveform to detect faint contact, a thermal camera in some competitions, and ball-tracking software that models the delivery's path from a series of high-frequency camera frames.

Why umpire's call exists

Umpire's call is the single most argued-about element of modern cricket, and it is best understood by taking the tracking system's own limitations seriously.

Ball tracking measures the ball's path up to the point of impact with the batter, then extrapolates forward to predict where it would have gone. The measurement is very accurate. The extrapolation is a prediction, and like all predictions it has an error margin that grows with distance. A ball striking the pad on the crease has a short projection; a ball striking a batter a long way down the pitch has a much longer one.

Umpire's call is the formal acknowledgement of that margin. When the predicted path shows the ball clearly missing the stumps, or clearly hitting them, the technology is confident enough to overturn the on-field decision. When the prediction shows the ball only clipping the stumps, the margin of uncertainty overlaps both answers, and the system cannot honestly say the umpire was wrong. In that case the on-field decision stands, whichever way it was given, and the reviewing side keeps its review.

This produces the outcome that irritates viewers: identical replays yielding opposite results, because one batter was given out and the other not out. That is not a bug. It is precisely what "we cannot tell" looks like when the system is required to produce an answer either way. The alternative, treating a marginal prediction as definitive, would replace umpire judgement with false precision.

The same principle applies to where the ball pitched and where it struck. Both are measurements rather than predictions and are therefore treated as more reliable, and the margins applied to them are correspondingly tighter.

DRS was introduced to eliminate the clear error, the decision that everybody in the ground can see is wrong. It has done that. It was never designed to adjudicate the delivery that shaves the outside of leg stump, and the arguments about umpire's call are really arguments about whether the game should pretend it can.

Two more that cause arguments

The run out at the non-striker's end. A bowler may run out a non-striker who leaves their ground before the ball is released. It is now listed under run out in the Laws, having previously sat under unfair play, and the change was deliberate: the governing body wished to make clear that it is a legitimate dismissal rather than an act of bad faith. The reasoning is that the non-striker who backs up early is stealing ground, and the only remedy available to the fielding side is this one.

Leg byes. Runs scored after the ball hits the batter's body count as leg byes only if the batter was either attempting a stroke or attempting to avoid the ball. A batter who deliberately pads the ball away and runs is not entitled to the runs. This is the same instinct as the lbw law: the pads are not a bat, and no benefit should flow from using them as one.

The pattern across all of these is consistent once you look for it. The Laws are not a neutral set of procedures. They are a long accumulation of decisions about what constitutes a fair contest between a bowler trying to hit the stumps and a batter trying to stop them with a bat, and almost every clause exists because somebody once found a way to make that contest unfair.

Related reading: how to read a cricket scorecard, which covers how these dismissals and extras are recorded, and cricket fielding positions explained for the positions the fielding restrictions govern.