Mankading Rule 2026 Explained: Spirit of Cricket Debate

Share this article
The mankad has been cricket's most-debated dismissal for nearly 80 years. It is also, as of 2022 and confirmed across the global game in subsequent updates, simply a run-out. The rule itself is no longer the controversy. What persists is the optics, the debate over what counts as "backing up too far," and the cultural memory of a play named after Vinoo Mankad in 1947. This piece walks through the current 2026 framework, the MCC's decisive Law 41.16 update, real IPL examples, and the spirit-of-cricket debate that refuses to settle down.
The Hook: A Real Example
April 2022, IPL: Ravichandran Ashwin runs out Jos Buttler at the non-striker's end. The crowd in Jaipur boos, then applauds. Buttler, on television replays, has been outside the crease before Ashwin's arm comes round. The umpires confer; the third umpire confirms the dismissal. Ashwin walks back to his mark and bowls the next delivery. The post-match interviews are subdued and direct: it is a legitimate run-out.
That moment was the visible end of decades of grey-area enforcement. The MCC's 2022 update had moved mankading from the "Unfair Play" section to the "Run-Out" section of the Laws. The 2024 and 2026 IPL playing conditions have followed.
A Short History Of The Rule
The mankad takes its name from Vinoo Mankad, who ran out Bill Brown of Australia at the non-striker's end during the 1947-48 Test series. Mankad had warned Brown earlier in the same match. The dismissal was legal then and is legal now; the controversy was always cultural.
For decades, the convention was a warning before the dismissal. Some captains insisted on it; others declined. The 1987 Courtney Walsh non-mankad of Saleem Jaffer in the World Cup is often cited as the platonic case of "spirit-of-cricket" restraint - although Pakistan went on to lose the game.
The MCC, custodian of the Laws of Cricket, formalised the dismissal as a legitimate run-out in October 2022, moving it from Law 41 (Unfair Play) to Law 38 (Run-Out) and renumbering as 41.16. The rationale was simple: the bowler is not doing anything unfair; the non-striker is gaining ground he or she should not.
How It Works In 2026
The mechanics are precise:
- The bowler must complete the dismissal before the moment they would normally release the ball - the "instant when the bowler would be expected to release the ball."
- If the non-striker is out of his or her ground at that moment, the bowler may run them out.
- No warning is required.
- The dismissal is a run-out and is credited as such (not to the bowler).
A key 2022-onward refinement: the "expected release" window has been clarified, removing the older ambiguity about whether a bowler could pause indefinitely.
For broader rule-context examples, our no-ball types explainer and free hit rule guide cover related law applications.
Recent IPL And International Examples
| Year | Match | Bowler | Batter |
|---|---|---|---|
| 2019 | KXIP vs RR (IPL) | R Ashwin | J Buttler |
| 2022 | RR vs RCB (IPL) | R Ashwin (decl) | A Padikkal |
| 2023 | SL vs ENG (ODI WC) | C Karunaratne | S Curran |
| 2024 | West Indies vs IRE (T20I) | A Joseph (decl) | A Balbirnie |
| 2026 | Multiple IPL warnings, no dismissals | - | - |
The 2026 IPL has seen several public warnings - bowlers gesturing to the non-striker, fielders alerting umpires - but no actual dismissals through the first half of the season. The behavioural shift from non-strikers has been visible.
Common Misconceptions
The most common is the belief that the bowler still owes a warning. Under the current Law, no warning is required. Some captains and bowlers continue to give one as a courtesy; this is choice, not requirement.
The second misconception is that the dismissal is credited to the bowler. It is not - it is a run-out, recorded as such in the scorecard.
The third is that the laws differ between formats. They do not. ICC playing conditions for Tests, ODIs and T20Is, IPL playing conditions and other domestic competitions all reflect the MCC reclassification.
The Critic Vs Supporter Case
The critic case has two parts. First, that the play is "unsporting" even if legal - the cultural muscle memory remains. Second, that it disrupts the rhythm of an over.
The supporter case is straightforward. The non-striker who leaves the crease early is gaining a 0.5- to 1-metre advantage on the run between wickets - a meaningful edge in T20 cricket where every second counts. The MCC's reclassification followed years of data showing this advantage was being exploited.
The middle ground - and where most players currently sit - is that the dismissal is fair, but the warning is good manners. Most coaches now actively coach non-strikers to stay in the crease until the bowler's release, eliminating the need for either side of the debate.
The IPL Captain's Position
Most IPL 2026 captains have publicly stated they will use the dismissal if the situation requires it. Hardik Pandya, Ruturaj Gaikwad and Shreyas Iyer have all said as much in pre-season pressers. The change in cultural posture is visible.
For broader IPL context, our IPL points table tracks the season. Fantasy followers can track related picks via our Dream11 hub. For T20 World Cup squad context, our T20 World Cup 2026 India squad debate covers the related conversation.
FAQ
Is mankading still controversial? The legal status is settled - it is a legitimate run-out under MCC Law 41.16 (2022 onwards). The cultural debate continues, but quietly.
Does the bowler need to warn the batter first? No. Under the current Law, no warning is required.
Who is credited with the wicket? Nobody, in bowling terms. It is a run-out, credited to the fielder/bowler effecting the dismissal.
Can the dismissal happen in any format? Yes - Tests, ODIs, T20Is and all domestic competitions follow the MCC reclassification.
Why is it called mankading? After Vinoo Mankad, who used the dismissal in the 1947-48 Test series in Australia.
Share this article
Karthik Iyer
Expert in: ExplainerCricket analyst and content writer at CricJosh, covering Explainer with 473 articles published.