Skip to content
Rules5 min

Running Between Wickets Explained: Communication, Judge of a Single, and Famous Run-Out Disasters

The craft of running between wickets — calling conventions (yes, no, wait), the role of the non-striker in judging, famous run-out disasters including the 2019 WC semi-final Martin Guptill run-out by Dhoni's throw, Ricky Ponting's 2003 WC Final run-out call that ended Australia's chase, and how modern cricket has transformed running standards.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

Running between the wickets is one of cricket's most technical and psychologically complex skills — it involves real-time communication between two batsmen, judgment about ball position, pitch length, and fielder positioning, all under time pressure measured in fractions of a second. Poor running between wickets is one of the most common causes of wicket loss in all formats — run-outs account for approximately 3-5% of all dismissals in ODI cricket and a higher percentage in T20 cricket where aggressive running is rewarded more than caution.

Calling Conventions: Yes, No, Wait

The standard cricket calling convention: (1) the batsman who plays the ball calls 'yes' (come) or 'no' (stay) immediately after the stroke — because they can see where the ball has gone while the non-striker initially cannot; (2) the non-striker responds: if they agree and have started running, they continue; if they disagree, they call 'no' and both must abort; (3) 'wait' is used when the ball is in an uncertain position — a fielder may or may not take a catch, or the fielder's throw position is unclear. The principle: the striker's call is always first; the non-striker's run is conditional on the striker's call. Breakdowns in this protocol — both batsmen running without a clear 'yes', or the striker calling 'yes' and the non-striker hesitating — produce run-outs. The most famous running breakdowns often involve a 'yes' followed immediately by a 'no' (the striker realises mid-call that the run is not available) or a 'wait' that converts to 'yes' too late.

Famous Run-Out Disasters

Cricket's most significant run-out moments: (1) 2019 World Cup semi-final (India vs New Zealand, Old Trafford, July 10, 2019): New Zealand needed 27 from 3 overs to reach the Final; Martin Guptill played a ball toward mid-wicket and set off for the second run; MS Dhoni (batting) could not make his ground as Guptill's direct throw hit the stumps. Dhoni was run out for 50 — the most consequential run-out of his India career, ending his last chance at a World Cup Final appearance. New Zealand fell 18 runs short; (2) Ricky Ponting, 2003 WC Final: Ponting's 140* helped Australia to 359/2 — in the context of that match, this was not a run-out of Ponting but Australia's decisive performance. However, Ponting's earlier-career infamous run-out: 2001 Test vs India (Kolkata), when he was run out attempting a third run that cost Australia significantly in a match they lost after India followed on — the famous Laxman 281*/Dravid 180 Test. Ponting has acknowledged the Kolkata run-out as one of his career regrets.

The Mankad run-out (non-striker backing up): when the bowler runs out the non-striker backing up too far before delivery (the 'Mankad' dismissal, named after Vinoo Mankad who dismissed Bill Brown this way in the 1947-48 Ashes). Deepti Sharma's Mankad of Charlie Dean (England vs India Women's ODI, Lord's, September 24, 2022) is the most recent famous example — Deepti ran out Dean backing up too far from the non-striker's end. Despite controversy over sportsmanship, the dismissal is entirely legal under the Laws of Cricket (Law 38.3). The ICC updated playing conditions in 2023 to specifically authorise Mankad dismissals as run-outs rather than the separate category they had been — removing the ambiguity that had generated the sportsmanship debate.

Modern Running Standards and Direct Hits

Modern fielding standards (particularly the athletic direct-hit ability of outfielders) have changed running strategies in limited-overs cricket: (1) The 'one-run maximum to mid-off or mid-on' convention in T20 cricket — fielders at these positions are so accurate with direct-hit throws that taking a second run (which requires turning around and running back) is very high-risk; (2) The 'impossible second' in the outfield: as fielding athleticism improved in the 2010s, the distance-required for a safe second run to the outfield boundary increased — fielders now cover ground in 3-4 strides and throw accurately from 30-40 metres; (3) Backing up: non-strikers backing up at the bowler's end (legal pre-delivery, within their crease) has become a standard modern technique — giving the striker 1-2 extra steps of running start on a 'yes' call, potentially converting a 'no' into a 'yes' on quick singles to close-in fielders.

Frequently asked questions

What is a run-out in cricket?

A run-out occurs when a batsman, while attempting to complete a run, is out of their crease (has not made their ground) when the fielding side breaks the stumps with the ball in hand, or when a direct throw hits the stumps with the batsman out of their crease. A run-out is one of cricket's ten dismissal methods under the Laws. It requires no appeal — the third umpire can adjudicate independently on a close call; on the field, the umpire signals out if the batsman is clearly short of their ground. It is the only dismissal type that does not credit any bowler.

What is a Mankad dismissal?

A Mankad dismissal (officially a run-out under Law 38.3) occurs when the bowler, during the delivery stride, runs out the non-striker who is backing up outside their crease before the ball has been delivered. Named after Vinoo Mankad (India) who used the method against Bill Brown (Australia) in the 1947-48 Ashes. The most famous recent example: Deepti Sharma ran out Charlie Dean (England Women, Lord's, September 24, 2022). The dismissal is entirely legal; the ICC updated playing conditions in 2023 to classify it explicitly as a run-out. The sportsmanship debate around the Mankad arises because convention expected a warning before dismissal — convention is not law.

How does communication between batsmen work in cricket?

Standard calling convention: the batsman who played the ball calls 'yes' (run), 'no' (don't run), or 'wait' (uncertain) immediately after the stroke — they can see where the ball has gone; the non-striker initially cannot. The non-striker responds: if the striker calls 'yes' and the non-striker agrees, both run; if the striker calls 'no', both stay. The striker's call always takes priority because they see the ball direction first. Breakdowns — both calling simultaneously, a 'yes' followed by a 'no', or a 'wait' converted to 'yes' too late — produce run-out risk. When both batsmen miscommunicate and run or stay simultaneously when they should not, the striker's end is typically the one at risk (the fielder throws to whichever end the backing-up batsman is furthest from).