Fairplay’s fair play guide explains when complete control is needed to break a wicket for a run out or stumping—and when the ball itself hits the stumps.
Short answer: control applies to the hand-or-arm put-down, not every ball-to-stumps event
For a Run out or Stumped decision, complete control is required when the wicket is broken by a fielder’s or wicketkeeper’s hand or arm while holding the ball. A hand that merely brushes a loose ball onto the stumps is not enough to establish that the ball was held. MCC’s 8 October clarification says the ball must be held with complete control in the fielder’s palm or fingers, or in the palm or fingers of a wicketkeeper’s glove. MCC’s clarification is the direct source for that distinction.
That is not a rule that bans all deflections or makes a run out impossible whenever a ball is not caught first. MCC says that if the ball itself hits the stumps and dislodges the bails, the wicket is fairly broken; the hand-held-control question does not arise. Its clarification specifically identifies a ball deflected by a bowler, rebounding from a wicketkeeper’s pads or kicked onto the stumps as the kind of confusion the clarification addresses. The ball reaching the stumps is only one part of a dismissal: the applicable Run out or Stumped conditions must still be met.
Ask what broke the wicket. A hand or arm holding the ball requires complete control; this guide cannot decide a named incident.
- Hand or arm breaks the wicket while holding the ball: the ball must be held with complete control.
- The ball itself hits the wicket: the wicket can be fairly broken without the hand-held-control test.
- In either route, the batter’s ground, the ball’s status and the specific dismissal conditions still matter.
What MCC clarified on 8 October 2026
MCC posted the clarification on 8 October after saying that the Law change taking effect on 1 October had been misread online as a blanket rule that every run out requires a fielder to have complete control of the ball. MCC says that is not what the Law says. The relevant change is in Appendix A.2.7 and A.2.8 of the 2026 Code, not a replacement for every way a wicket may be broken. MCC’s 2026 Laws explanation gives the definitions.
Appendix A.2.7 defines a ball as held in a fielder’s hand only when it is held with complete control in the fielder’s palm or fingers, or the palm or fingers of a wicketkeeper’s glove. A.2.8 defines complete control functionally: assuming no contact with another person or object, the fielder could keep holding the ball for as long as they choose or dispose of it wherever they choose. That is a control test, not a requirement for an arbitrary pause or a particular number of replay frames.
The change distinguishes a held ball from one only in fleeting contact with a hand or glove. Cricbuzz and The Daily Star independently report the clarification; MCC governs the meaning used here.
Three ways to analyse the wicket-breaking moment
Current MCC Law 29 begins with the physical result: at least one bail must be completely removed from the top of the stumps, or a stump removed from the ground. Law 29.2.1 then lists routes by which that can be done fairly. The full current MCC 2026 Code is the operative primary text for the table below.
The table isolates the wicket-breaking mechanism. A run-out appeal still needs Law 38 facts, and a stumping still needs Law 39 facts.
| What contacts the wicket? | What the Law requires | Does the new complete-control test answer this step? | What remains to check? |
|---|---|---|---|
| The ball itself | Law 29.2.1.1 permits a bail to be removed or stump dislodged by the ball. | No. MCC says there is no question of hand-held control when the ball itself hits the stumps. | The relevant Run out or Stumped conditions and the match facts. |
| A fielder’s or wicketkeeper’s hand or arm while holding the ball | Law 29.2.1.5 requires the ball to be held in the relevant hand(s), or the hand of the relevant arm. | Yes. Appendix A.2.7–A.2.8 requires complete control for a ball to count as held. | Whether a bail was completely removed, the batter was out of ground and the dismissal requirements. |
| A fielder pulls or strikes a stump out with hand or arm while holding the ball | Law 29.2.1.6 applies the preceding hand-or-arm condition to this route. | Yes, through the same held-ball requirement as Law 29.2.1.5. | The same dismissal and evidence checks. |
After the put-down, apply the correct dismissal test
A fairly broken wicket is necessary but not automatically a dismissal. Under MCC Law 38, either batter may be out Run out while the ball is in play, out of ground and at the end where the wicket is fairly broken by a fielder’s action or a ball rebounding from a fielder’s person, subject to its exceptions.
Stumped is narrower. MCC Law 39 requires a delivered ball that is not a No ball, a striker out of ground without attempting a run, and a wicket fairly broken by the wicketkeeper without another fielder’s intervention. If met, Law 39.1.2 applies even if Run out would also be justified.
Law 39 also shows why ‘the ball hit the stumps’ is not automatically a run out. Where the ball rebounds to the stumps from any part of the wicketkeeper’s person or equipment, or is kicked or thrown onto the stumps by the wicketkeeper, Law 39.2 regards the wicket as having been broken by the wicketkeeper. On the remaining verified facts, that may be relevant to Stumped. It is not permission to skip the No-ball, no-run-attempt or intervention checks.
- Run out: ball in play, batter out of ground, wicket fairly broken, plus any applicable Law 38 exception.
- Stumped: delivered ball not called No ball, striker out of ground, no run attempt and wicketkeeper breaks wicket without another fielder’s intervention.
- A scorecard label can record an outcome, but it normally cannot show whether complete control existed at the instant the wicket was put down.
Four labelled hypotheticals: contact is not always control
These are fictional teaching examples, not real-match rulings.
Hypothetical 1 — loose hand contact: a ball merely brushes a fielder’s hand as it dislodges a bail, and the fielder could not retain or direct it without another contact. On those facts, the ball is not shown held with complete control for the hand-or-arm route. Whether the ball separately struck the wicket and whether a batter was short remain separate questions.
Hypothetical 2 — controlled glove put-down: a wicketkeeper has the ball secured in the glove’s palm or fingers and uses the glove-hand to remove a bail. Assuming the ball could be retained or disposed of without another contact, the complete-control element for a held ball is capable of being met. To call the striker Stumped, however, the remaining Law 39 conditions must also be shown: no No ball, no run attempt, the striker out of ground and no other fielder’s intervention.
Hypothetical 3 — ball deflects from a fielder: a return strikes a bowler’s leg and the ball itself then removes a bail while a batter is out of ground. MCC says a ball hitting the stumps can fairly break the wicket without a hand-held-control question. The precise Run out result would still depend on Law 38’s facts, including whether the ball was in play and which batter’s ground was at the broken wicket.
Hypothetical 4 — keeper-pad rebound: a delivery passes the striker, rebounds from the wicketkeeper’s pad and the ball itself removes a bail. The complete-control definition does not convert the rebound into ‘not a wicket broken’. Law 39.2 treats a ball rebounding to the stumps from the wicketkeeper’s person or equipment as having been broken by the wicketkeeper. If the other Law 39 conditions are not proved, this hypothetical should not be labelled Stumped simply because the bail came off.
What a replay or scorecard can—and cannot—establish
For the held-ball route, the decisive instant is when the fielder’s hand or arm breaks the wicket. A short replay may show the bail falling but not whether the ball was controlled in the palm, fingers or wicketkeeper’s glove at that instant. Conversely, it may show a ball striking the wicket but not the batter’s ground, whether the ball was live or which dismissal category applies. The responsible conclusion is limited to what the footage and official decision actually show.
An official scorecard can record ‘run out’ or ‘stumped’, while the extras and dismissal line provide useful context. It normally does not record hand position, the quality of control, a frame-by-frame sequence or the officials’ legal reasoning. Fairplay’s How to Read a Cricket Scorecard explains why a run out is a team wicket rather than a bowler wicket; it is not a substitute for the Law 29 evidence needed for a disputed put-down.
For a named incident, retain the current rule document and complete available footage. Live Score and Cricket analysis provide match context, not an unseen control point.
Use the current competition conditions before applying this guide
MCC says playing regulations can create differences, especially at international level; its Laws overview links the 2017 Code 4th Edition 2026. ICC says its updated conditions apply to men’s and women’s international series starting on or after 1 October 2026, while an ongoing series remains under prior regulations. ICC’s announcement states that scope.
For example, the current ICC Men’s ODI Playing Conditions, October 2026 contain both the Law 29.2.1.5 held-ball wording and Appendix 2.7–2.8 complete-control definition. That is evidence for ICC men’s ODIs under that document, not a shortcut for every domestic, franchise, school or historical match. The ICC’s playing-conditions index lists separate current documents by format and competition.
For any real decision, follow this compact order: identify the match and applicable date; establish whether the ball itself or a person’s hand/arm broke the wicket; if it was the hand-or-arm route, test complete control; then apply Law 38 or Law 39 and the event conditions. Use Fairplay’s Cricket Laws vs Playing Conditions document check for the broader verification workflow. If a decisive fact or current competition document is unavailable, say that it is unknown rather than filling the gap from a highlight clip.
- Check the competition, format, match date and effective document version.
- Separate the Law 29 wicket-breaking mechanism from the Law 38 or Law 39 dismissal test.
- Treat the official decision as authoritative for the match; this guide explains the source text, not a retrospective ruling.
Questions, answered
Does a fielder need complete control of the ball for every run out?
No. MCC’s 8 October 2026 clarification says the complete-control requirement applies when a fielder or wicketkeeper breaks the wicket with a hand or arm while holding the ball. If the ball itself hits the stumps and dislodges the bails, MCC says there is no hand-held-control question. The other Law 38 conditions still decide whether it is Run out.
What does complete control mean in the current cricket Laws?
Appendix A.2.8 says that, assuming no contact with another person or object, the fielder could continue holding the ball for as long as they choose or dispose of it wherever they choose. Appendix A.2.7 places the held ball in the fielder’s palm or fingers, or the palm or fingers of a wicketkeeper’s glove. See MCC’s 2026 explanation.
Can a stumping happen if the ball rebounds from the wicketkeeper’s pads onto the stumps?
The ball can fairly break the wicket without the hand-held-control question. Law 39.2 treats a ball rebounding onto the stumps from any part of the wicketkeeper’s person or equipment as broken by the wicketkeeper. A stumping still needs every Law 39 condition, including no No ball, no run attempt and the striker being out of ground.
If the wicket is fairly broken, is the batter automatically out?
No. Fairly breaking the wicket is only one element. Run out requires the facts in Law 38, such as the ball being in play and the relevant batter being out of ground. Stumped has the narrower conditions in Law 39. The applicable competition conditions and the officials’ decision govern a real match.
Can a scorecard prove that a wicketkeeper had complete control?
Usually not. A scorecard may record the dismissal but normally will not show the moment of hand or glove contact, whether the ball could be retained or directed, or the governing conditions. Check the official decision, full available footage and the current event document before making that claim.
Sources and evidence
- Marylebone Cricket Club — Clarification on breaking the wicket for a run out
Primary clarification posted 8 October 2026 and text-opened 18 October 2026. Defines the narrow hand-or-arm scope and distinguishes a ball that itself hits the stumps.
- Marylebone Cricket Club — Laws of Cricket 2017 Code 4th Edition 2026
Primary 2026 Code text-opened 18 October 2026. Supports Law 29.1–29.2.1.6 and Appendix A.2.7–A.2.8.
- Marylebone Cricket Club — Law 38: Run out
Primary current Law page opened 18 October 2026. Supports the Run out test, stated exceptions and team-wicket scoring point.
- Marylebone Cricket Club — Law 39: Stumped
Primary current Law page opened 18 October 2026. Supports stumping conditions and wicketkeeper rebound, kick and throw treatment.
- International Cricket Council — Key changes across formats with new Playing Conditions
Official ICC announcement dated 1 October 2026 and opened 18 October 2026. Supports international-series commencement scope and summary of the control change.
- International Cricket Council — Men’s ODI Playing Conditions, October 2026
Primary format-specific document opened 18 October 2026. Supports clauses 29.2.1.5 and Appendix 2.7–2.8 for ICC men’s ODIs.
- The Daily Star — ICC introduces new playing conditions: Key changes across formats
Independent report published 1 October 2026 and opened 18 October 2026. Corroborates the announced complete-control summary and implementation scope.
- Cricbuzz — MCC sharpens rules on ball control, overs and keeper movement
Independent report opened 18 October 2026. Used as comparator context; operative claims rely on MCC and ICC texts.
Scheduled facts and sourced history are separate from live match data. Source attribution does not imply affiliation with IPL, BCCI, ICC or players.