Scope
The ruleset and dates used here
This page applies the Marylebone Cricket Club Laws of Cricket 2017 Code, 3rd Edition (2022), the general Laws in force on 26 August 2026. MCC is the custodian and interpreter of the Laws. A league, national board or tournament may replace parts of that baseline through its playing conditions.
MCC has published the 4th Edition (2026), but it takes effect on 1 October 2026. Relevant forthcoming changes are identified below; they are not treated as current before that date. The international timing comparison is limited to the named ICC men's playing conditions and effective dates.
At a glance
Do not collapse the four rulings
- Hit wicket — MCC Law 35: only the striker; wicket broken by the striker's bat, person, clothing or qualifying detached equipment during a listed phase of the delivery.
- Obstructing the field — MCC Law 37: either batter; usually a wilful attempt to obstruct or distract while the ball is live, with separate rules for a prevented catch and returning the ball.
- Retired - out — MCC Law 25.4: the final record when a batter retires for a reason other than illness, injury or another unavoidable cause and does not resume.
- Timed out — MCC Law 40: the incoming batter; failure to meet the applicable readiness deadline after a dismissal or retirement.
Appeals
The umpire does not manufacture a dismissal
MCC Law 31.1 says neither umpire may give a batter out without an appeal by a fielder, even when the facts satisfy a dismissal Law. That applies to Hit wicket, Obstructing the field and Timed out. A batter may nevertheless leave voluntarily when out.
Under Law 31.3, the appeal must come before the bowler begins the run-up—or bowling action if there is no run-up—for the next ball, and before Time is called. Calling Over does not itself close the appeal window. The fielding captain may withdraw an appeal with the responsible umpire's consent before the next ball comes into play, or before the umpires leave if the innings has ended.
Timed-out misconception: the fielding side does not have to appeal before the late batter eventually becomes ready. The deadline determines liability; Law 31 determines whether a later appeal is still valid.
Hit wicket · trigger
Breaking the wicket is only the first test
Under MCC Law 35.1, the striker can be out Hit wicket only after the bowler has entered the delivery stride and while the ball is in play. Law 29 says the wicket is broken when at least one bail is completely removed or a stump is struck out of the ground. Merely rocking a bail is not enough.
The contact may be from the striker's held bat, a bat no longer in hand, the striker's person, or clothing or equipment that becomes detached. A detached protective helmet is expressly excluded by Law 29.2.1.4. The Law therefore can catch a released bat or dislodged item, but not a helmet falling onto the stumps.
Hit wicket · timing
The action must fit one of four phases
MCC Law 35.1.1 limits Hit wicket to the striker:
- preparing to receive or receiving the delivery;
- setting off immediately for the first run after playing or playing at the ball;
- setting off immediately for the first run after having the opportunity to play, when no attempt was made; or
- lawfully striking the ball again solely to guard the wicket under Law 34.3.
MCC's official 2023 clarification confirms that “receiving” includes the follow-through and movement needed to recover balance after the stroke. A ball travelling far away does not by itself end that action; the umpire judges whether the striker has completed it.
Hit wicket · limits
No-ball and later running are important exceptions
Law 35.2 rules out Hit wicket when the delivery is a No ball; when the bowler enters the delivery stride but does not deliver; during later running rather than the immediate start of the first run; while the striker is trying to avoid being Run out or Stumped; or while avoiding a throw-in. If the striker breaks the wicket before the bowler enters the delivery stride, Law 35.1.2 directs either umpire to call Dead ball.
A No ball prevents Hit wicket, not every dismissal. MCC Law 21 still permits, among the relevant possibilities, Obstructing the field or Run out from a No ball if that other Law is satisfied.
Hit wicket · outcome
The dismissal kills the play at the decisive incident
Under Laws 20.1.1.3 and 35.3, the ball is dead from the incident causing the dismissal. No batting runs are scored; only the one-run penalty for a Wide and any five-run Penalty award can stand. A shot that later crosses the boundary does not produce four or six if the striker was already out Hit wicket during the receiving action.
The bowler receives credit for a Hit wicket dismissal. The important contrast is that MCC Laws 37.6 and 40.2 expressly deny the bowler credit for Obstructing the field and Timed out.
Obstruction · core test
“Wilful” means more than being in the way
MCC Law 37.1.1 applies while the ball is in play when either batter wilfully attempts, by word or action, to obstruct or distract the fielding side. Law 37.2 protects accidental obstruction, action taken to avoid injury and a lawful second strike used solely to guard the striker's wicket, subject to the special catch rule.
A collision or a throw striking a runner is therefore not automatically out. In an April 2026 official interpretation, MCC explained that a batter changing direction away from the quickest route—particularly by crossing onto the pitch—can establish a wilful act. Remaining on the same natural running line may leave the batter in the way without making the contact deliberate. Except where a catch is prevented, it is not necessary to prove that the obstruction stopped a likely dismissal.
Obstruction · special cases
Catches, the free hand and returning the ball
- Prevented catch, not a No ball: if wilful obstruction by either batter prevents the striker being Caught, Law 37.3 makes the striker out.
- Prevented catch from a No ball: the batter who caused the obstruction is out, except that a striker making a lawful second strike to defend the wicket from a No ball is protected.
- Hand not holding the bat: a striker who wilfully strikes the delivered ball with that hand while receiving it is out under Law 37.1.2, whether or not No ball was called.
- Returning a live ball: under Law 37.4, either batter is out if they use the bat or person to return the ball to a fielder without a fielder's consent. MCC's February 2026 clarification treats this as a firm consent requirement, even when the gesture appears helpful.
A striker may lawfully hit the ball again solely to guard the wicket before a fielder touches it, but may not use that protection to prevent a catch. That boundary between Laws 34 and 37 depends on purpose and effect.
Obstruction · outcome
Who is out and which runs count depend on the play affected
For obstruction other than preventing a catch, the batter responsible is out and completed runs before the offence count, together with an applicable one-run No ball or Wide penalty and any five-run Penalty awards. If the obstruction prevented a catch, completed runs do not count; only five-run Penalty awards stand, and the not-out batter returns to the original end under the 2022 Laws.
The bowler does not receive the wicket. Once the incident causing dismissal occurs, the ball is dead under Law 20.1.1.3.
Handled the ball
It is no longer a separate dismissal
Since the October 2017 Code, conduct once scored as Handled the ball has sat within Obstructing the field. Under the current Law, a wilful free-hand strike while receiving the delivery is covered by Law 37.1.2, and returning a live ball without a fielder's consent by Law 37.4. Older scorecards can therefore use a dismissal name that does not appear as a separate Law today.
That history does not make every hand contact out. The current exceptions for accident and avoiding injury still matter, as does the separate consent rule when returning the ball.
Retirement
Reason first, then permission and eventual resumption
MCC Law 25.4 allows a batter to retire only when the ball is dead. Before play continues, the umpires must be told why. If illness, injury or another unavoidable cause prompted the retirement, the batter is entitled to resume; if the innings never resumes, the score records Retired - not out.
For any other reason—including a tactical retirement—the batter may resume only with the opposing captain's consent. If the innings is not resumed, the final record is Retired - out. In either category, a return may occur only at the fall of a wicket or the retirement of another batter.
Not an immediate appeal decision: the batter does not become “Retired - out” merely because they cross the boundary. The reason and whether the innings is later resumed determine the final entry under Law 25.4.
Timed out · MCC baseline
Three minutes means ready, not merely present
Under MCC Law 40.1.1, after a dismissal or retirement the incoming batter must be ready to receive the ball—or the other batter ready to receive the next ball—within three minutes, unless Time has been called. Walking onto the field or reaching the crease is not the stated test; readiness to receive is.
If the requirement is missed, the incoming batter is liable to be Timed out on a valid appeal. No delivery is needed, the bowler receives no credit, and Law 40 contains no separate equipment-failure extension. If no batter appears for an extended period, Law 40.1.2 sends the umpires to the match-award procedure in Law 16.3, starting from expiry of the three minutes.
ICC variation
International deadlines can be shorter
The MCC three-minute period is not universal. In the ICC Men's Test Match Playing Conditions effective June 2025 and the ICC Men's ODI Playing Conditions effective July 2025, clause 40.1.1 uses two minutes. The ICC Men's T20I Playing Conditions effective July 2025 use one minute 30 seconds and say the incoming batter is expected to make for the wicket immediately.
Those ICC documents also exclude Timed out from a Player Review under DRS. Other international events, domestic competitions, junior cricket and local leagues can publish different playing conditions, so the appointed document for the match controls.
Worked case 1 · MCC 2022
The follow-through removes a bail
Situation: the striker hits the ball high, finishes the swing and, still recovering balance from the stroke, lowers the bat onto a bail before the ball reaches the boundary.
Ruling: Out Hit wicket on appeal, assuming a legal delivery and a live ball. MCC's interpretation treats balance recovery as part of receiving the ball. The dismissal incident makes the ball dead, so the later boundary is not scored.
Worked case 2 · MCC 2022
A helmet falls onto the wicket
Situation: while playing a legal delivery, the striker's protective helmet comes off and removes a bail.
Ruling: Not out Hit wicket. Law 29.2.1.4 excludes a detached protective helmet and its parts from the equipment capable of breaking the striker's wicket for this purpose.
Worked case 3 · MCC 2022
The runner changes line across a throw
Situation: after turning back, a batter leaves the natural return line, crosses the pitch and places their body between an incoming throw and the wicket.
Ruling: Out Obstructing the field on appeal if the umpire judges the route change wilful. Under MCC's April 2026 interpretation, the fielding side need not show that the throw would certainly have produced a Run out. If the batter had kept the natural line and been struck accidentally, Law 37.2 would protect them.
Worked case 4 · MCC 2022
A tactical retiree asks to return
Situation: Batter A retires while the ball is dead for tactical reasons. A later wicket falls and A asks to resume, but the opposing captain refuses consent.
Ruling: A cannot resume and, if the innings ends without a return, is recorded Retired - out under Law 25.4.3. The umpires' permission cannot replace the opposing captain's required consent.
Worked case 5 · named rulesets
A batter is ready after two minutes 20 seconds
MCC 2022 baseline: not Timed out because the three-minute limit has not expired, provided no local playing condition shortens it.
ICC men's Test or ODI conditions named above: liable to be Timed out on appeal because the two-minute readiness limit has expired. Becoming ready at 2:20 does not erase the missed deadline, although the appeal must still be valid under Law 31 and may later be withdrawn through Law 31.8.
Decision path
How to analyse an unusual dismissal claim
- Name the ruleset and date. Start with MCC, then check the competition's adopted playing conditions.
- Identify the correct category. Broken wicket, interference, retirement and delayed readiness use different tests.
- Freeze the decisive time. Was the ball live? Which part of receiving or running was under way? When did the dismissal or retirement occur?
- Apply the exact exception. Check No ball, accident, avoiding injury, lawful defence of the wicket, consent to return the ball and the retirement reason.
- Check procedure. Was there a timely appeal? Has it been withdrawn? Does the competition permit the relevant review?
- Record the consequence. Decide who is out, which runs survive, whether the bowler gets credit and who faces next.
Common mistakes
Six claims that are too broad
- “Knocking over your own stumps is always Hit wicket.” Law 35 has a delivery window, listed phases and exclusions.
- “A No ball makes the batter immune.” It prevents Hit wicket, but Obstructing the field can still apply.
- “Being struck by a throw is obstruction.” Ordinary accidental contact is not the wilful act required by Law 37.
- “A harmless return of the ball is safe.” A batter needs a fielder's consent while the ball is live.
- “Retired hurt and Retired out are synonyms.” The cause and whether the batter resumes determine the record.
- “Timed out is always three minutes.” That is the MCC baseline; current ICC men's conditions use shorter periods.
From 1 October 2026
MCC's 4th Edition changes two relevant edges
The MCC 2017 Code, 4th Edition takes effect on 1 October 2026. Revised Law 35 expressly codifies balance recovery as part of the Hit wicket window and adds protection where contact with a fielder directly causes the striker or held bat to break the wicket. It also protects a striker when detached equipment or a bat not in hand touches another person before breaking the wicket.
New Law 37.1.3 expressly makes a striker liable for Obstructing the field when, while receiving the ball, the striker deliberately drops or throws the bat in an attempt to affect the ball or prevent a dismissal other than Hit wicket. Matches before 1 October remain governed by the ruleset actually adopted for them; MCC notes that some competitions may already have adopted individual changes as playing conditions.
Official references
Governing-body sources and effective versions
- Back to cricket overview
- MCC — Laws of Cricket editions and role of competition playing regulations
- MCC 2017 Code, 3rd Edition (2022) — Law 25.4, Batters retiring
- MCC 2017 Code, 3rd Edition (2022) — Law 20, Dead ball
- MCC 2017 Code, 3rd Edition (2022) — Law 21, No ball
- MCC 2017 Code, 3rd Edition (2022) — Law 29, The wicket is broken
- MCC 2017 Code, 3rd Edition (2022) — Law 31, Appeals
- MCC 2017 Code, 3rd Edition (2022) — Law 34, Hit the ball twice
- MCC 2017 Code, 3rd Edition (2022) — Law 35, Hit wicket
- MCC 2017 Code, 3rd Edition (2022) — Law 37, Obstructing the field
- MCC 2017 Code, 3rd Edition (2022) — Law 40, Timed out
- MCC — official Hit wicket receiving-action interpretation, 27 July 2023
- MCC — official Law 37.4 return-of-ball clarification, 23 February 2026
- MCC — official running-line obstruction interpretation, 30 April 2026
- ICC — Handled the ball incorporated into Obstructing the field from the 2017 Code
- ICC — Men's Test Match Playing Conditions, effective June 2025, clause 40
- ICC — Men's ODI Playing Conditions, effective July 2025, clause 40
- ICC — Men's T20I Playing Conditions, effective July 2025, clause 40 and Appendix D
- ICC — Men's and Women's T20I Playing Conditions addendum, checked for later amendments
- MCC — 4th Edition commencement notice, effective 1 October 2026
- MCC — Changes to the Laws of Cricket for the 2026 edition, Laws 35 and 37
Checked on 26 August 2026 against the MCC 2017 Code, 3rd Edition (2022), current MCC interpretations, the named ICC men's playing conditions and the posted T20I addendum, which does not amend clause 40. The MCC 4th Edition is published but does not take effect until 1 October 2026. Competition, tournament, domestic and age-grade playing conditions may supplement or replace the baseline, especially the Timed out period and review procedure.