Dead Ball in Cricket: When Play Is Suspended and Runs Cannot Be Scored
What the dead ball rule means in cricket — the circumstances under which the ball is called dead (and all scoring, dismissals, and running stops), the difference between automatically dead and called dead by the umpire, how the dead ball interacts with penalty runs and appeals, common misconceptions about the dead ball, and why the dead ball rule is essential for the game's fairness.
What Dead Ball Means
A dead ball is a ball that is no longer in active play — no runs can be scored, no dismissals can occur, and no appeals can succeed while the ball is dead. The dead ball period is the gap between deliveries: from the moment the umpire signals dead ball (or conditions automatically make the ball dead) until the bowler begins their run-up for the next delivery. During this window, the fielding team can discuss tactics, the batting team's non-striker can leave their crease freely without run-out risk, and the umpires assess any issues from the previous delivery.
Automatic vs Called Dead Ball
Some situations make the ball automatically dead (no umpire call required): the ball crosses the boundary; a batsman is dismissed; a fielder catches the ball (once the catch is completed); or the wicket-keeper catches the ball when no run-out or stumping is being attempted. Umpires also call the ball dead in response to events: when a batsman is seriously injured during play; when an external disturbance affects play; when the fielding team or umpire requires an assessment of a law breach; or when a batsman requests time.
Common Dead Ball Scenarios
Several scenarios produce dead ball calls that are counterintuitive: if a bowler's foot slips in their run-up and the umpire calls dead ball before the ball is actually delivered, the delivery does not count — the over continues from the same count. If a batsman's bat breaks during a shot and the break of bat touches the stumps, the ball is dead before any stumping or run-out attempt could complete — the broken bat contact does not count as hit wicket.
Frequently asked questions
Can runs be scored from a ball that is called dead?
No — once the ball is called dead, no runs score from any subsequent action. However, runs already completed before the dead ball call do count: if two batsmen have crossed and the ball hits the boundary rope simultaneously, the boundary (4 runs) takes precedence over the completed single, and only boundary runs count. Penalty runs can be awarded after the ball is dead — they are a disciplinary mechanism, not a scoring action dependent on live ball status.
Is the ball dead when a fielder is treating an injury?
Yes — if a fielder is injured during play and requires treatment, the umpire calls dead ball immediately. The injury treatment takes priority over the live ball's status. If the ball is in the air (a catch in progress) when a fielder is injured, the umpire waits for the catch to be completed or clearly not completed before calling dead ball — they would not call dead ball mid-catch, as this would prevent a legitimate dismissal.
Why does the ball become dead when it crosses the boundary, not when it hits it?
The ball is dead when it crosses the boundary rope or reaches the boundary marking — not when it hits the rope. This distinction matters in cases where the ball hits the rope but bounces back into the field of play: if the ball touches the rope and bounces back, it has crossed the boundary at the moment of rope contact, and any subsequent action (a fielder catching it after the bounce-back) is irrelevant — the boundary 4 runs are already scored. This rule prevents the ambiguity of whether a ball 'bounced off the rope' is still in play.