Cricket can move quickly from a routine delivery to a disputed decision. This practical cricket laws glossary explains common umpire calls, extras, free hits and dismissal types, then shows how to read a live scorecard, commentary feed or replay without losing the context of the ball.
Overview
Most unfamiliar cricket rules fall into three groups: illegal or interrupted deliveries, dismissals and scoring adjustments. A wide or no-ball changes the total and the legal-ball count. A caught dismissal, run-out or stumping changes the wicket column. A dead-ball call may explain why a delivery appears to have produced no runs or wicket even though play briefly continued.
The exact application can vary between Test cricket, one-day internationals, T20 matches and domestic competitions because playing conditions may add to or modify the standard Laws of Cricket. Treat the explanations below as a match-viewing guide rather than a substitute for the regulations of a particular competition. When a decision is reviewed, the on-screen explanation and the competition’s playing conditions take priority.
For broader context, pair this glossary with our guide to reading a cricket scorecard and explanation of DRS, reviews and umpire’s call.
What to track
Wides
A wide is called when the ball is too far from the batter to be fairly playable under the conditions of the match, or passes outside the permitted playing area. It adds one run to the batting team’s score, and any additional runs completed or conceded as byes or boundary extras are added as well. A wide does not count as one of the over’s legal deliveries. The umpire generally signals a wide by extending both arms horizontally.
A wide is not automatically determined by a fixed distance from the stumps. Batter movement, the marked wide guidelines and the competition’s interpretation all matter. That is why a delivery can be judged differently depending on where the batter stood and how the ball passed the wicket.
No-balls
A no-ball is called when the bowler breaks a delivery condition. Common examples include overstepping the popping crease, delivering an illegal type of ball under the match conditions or breaching restrictions on the bowling action or field. The umpire signals a no-ball with one arm extended horizontally.
A no-ball normally awards a penalty run and does not count as a legal delivery in limited-overs cricket. Runs scored from the bat, running or boundaries may be added to the penalty. Some formats and competitions apply different delivery-counting or penalty provisions, so the scorecard and playing conditions should be checked when the situation is unusual.
Free hits
A free hit is a limited-overs playing-condition provision that usually follows certain kinds of no-ball. It gives the striker protection from most forms of dismissal on the next delivery. A batter can still be dismissed in circumstances such as being run out, stumped in an applicable situation, obstructing the field or hitting the ball twice under the relevant law. A free hit is not a separate type of delivery in the Laws; it is a competition rule attached to the previous no-ball.
When following live cricket updates, look for three separate details: why the no-ball was called, whether the next delivery is a free hit and whether a subsequent wide or no-ball changes the sequence. A free hit is normally carried forward if the next ball is not legal, depending on the competition rules.
Leg before wicket, or LBW
For an LBW dismissal, the ball must first meet the conditions about where it pitched, where it struck the batter and whether it would have hit the stumps. The batter must generally have been struck on the leg or body rather than the bat or hand holding the bat. The law also considers whether the ball pitched in line with the stumps or outside the off-stump line, whether the impact was in line and whether the batter made a genuine attempt to play the ball.
LBW is therefore more than simply ball-to-pad followed by a ball-tracking image. DRS may assess pitching, impact and the projected path, while the review framework can include umpire’s call. For a fuller explanation, see our Cricket DRS guide.
Common dismissals
| Dismissal or call | What it means during a live match | What to check |
|---|---|---|
| Caught | The ball touches the bat or the hand holding the bat and is fairly caught by a fielder before it touches the ground. | Whether the ball carried, the catch was controlled and the ball made contact with the bat. |
| Run out | A wicket is fairly broken while a batter is out of the relevant ground and the ball is still in play. | Which batter was short of the crease, whether the ball was dead and whether the wicket was broken before the batter grounded the bat or body. |
| Stumped | The wicketkeeper breaks the striker’s wicket while the striker is out of the ground and not attempting a run, provided the delivery is not a no-ball. | The striker’s position, the attempt to run and whether the delivery was a legal ball for this dismissal. |
| Bowled | The delivery breaks the striker’s wicket, even if it first touches the bat or batter, subject to the law’s conditions. | Whether the ball actually dislodged a bail or broke the wicket and was not declared dead first. |
| Obstructing the field | A batter deliberately obstructs or distracts the fielding side, subject to the circumstances defined by the law. | Whether the act was deliberate and how it affected the fielding attempt. |
| Hit wicket | The striker breaks their own wicket during the delivery in circumstances covered by the law. | Whether the ball was delivered, the wicket was broken by the batter or equipment and the relevant exceptions apply. |
Dead balls and penalty runs
The ball becomes dead when the umpire decides that play has ended for that delivery. This can follow a dismissal, a boundary, an injury, an interruption or another event recognised by the law. A dead-ball call prevents further action from being taken from that delivery and explains why an apparent run or appeal may not remain in the final score.
Penalty runs are separate from ordinary bat runs, byes and leg-byes. They can be awarded for specified fielding or conduct breaches, equipment or other situations covered by the Laws and playing conditions. The scorecard usually places them among the extras or records them in a separate notation. Do not assume that every five-run addition came from a boundary: check the commentary description and extras breakdown.
Cadence and checkpoints
During a live match, use a simple three-step checkpoint whenever the score changes unexpectedly:
- Read the call: Identify whether the commentary says wide, no-ball, byes, leg-byes, penalty runs, wicket or dead ball.
- Check the legal-ball count: A wide and most no-balls do not use up a legal delivery in limited-overs scoring. The over may therefore contain more deliveries than its nominal length.
- Check the wicket and extras columns: Confirm whether the run went to the batter, extras or the bowling figures, and whether a batter was dismissed.
At the end of an over, compare the ball-by-ball commentary with the scorecard. This is especially useful after a sequence such as no-ball, free hit, wide and wicket, where the apparent order can be confusing. For lineup context, consult our playing XI and squad news guide; for a rain-affected match, use the DLS explanation to distinguish revised targets from ordinary scoring changes.
How to interpret changes
Do not judge an umpire signal in isolation. First identify the delivery state, then the scoring result and finally the decision’s effect on the match. For example, a batter can hit a six from a no-ball, but the innings total includes both the no-ball penalty and the boundary runs. A batter can also be caught from a legal delivery after an appeal, while a review may overturn the original not-out or out decision.
Signals provide a quick visual summary, but the written scorecard is the better long-term record. Look for the extras line, the over number, the wicket description and the batter’s dismissal notation. If the feed and scorecard disagree briefly, allow for a delay between the on-field signal, third-umpire review and statistical update.
For LBW or caught decisions, separate the factual question from the review question. Factual questions include whether the ball hit the bat, whether it pitched legally and whether the wicket was broken. Review questions concern which evidence is available and whether the protocol permits the decision to be changed. This distinction helps explain why a review can confirm an outcome without proving that every part of the original decision was straightforward.
When to revisit
Return to this glossary whenever you follow a new tournament, switch between formats or encounter an unfamiliar scorecard entry. Competition regulations can change how free hits, reviews, over counts, boundary procedures or penalty provisions are applied. A sensible update routine is to review the relevant tournament playing conditions before its season begins, then check the official match regulations when a major rule interpretation becomes part of the cricket news cycle.
During a match, save this page for quick reference after a disputed call. Before making fantasy selections or a match prediction, confirm whether the event affected a player’s dismissal, legal-ball count or bowling figures; our fantasy cricket selection framework can help with the wider decision process. Finally, when a competition ends, compare your notes with the final scorecard and update any terminology that has been clarified by the organisers.
The practical habit is simple: record the call, verify the legal delivery, identify where the runs were credited and then check the applicable playing conditions. That workflow turns confusing live updates into a reliable reading of the match.