Non-Striker Tactics in Cricket: Running, Backing Up, and the Mankad Rule
How the non-striker end affects cricket — backing up, running between wickets, calling between batters, the Mankad controversy, and the partnership dynamics that define Test batting.
The non-striker — the batter at the far end from the bowler — is involved in every delivery even when not facing the ball. Their backing up position, their calling for runs, their response to the striker's call, and their awareness of fielder positions collectively determine how many runs a partnership scores and how many run-outs a team suffers. Running between wickets is one of the most underpractised and critical skills in cricket.
Backing Up
Backing up is the non-striker's act of moving towards the striker's end as the bowler delivers, so they are closer to completing a run if the striker hits the ball. Good backing up — moving 2-4 metres out of the crease as the ball is bowled — is the difference between converting a single into a two, or a two into a three. Elite Test batters (particularly in India where quick singles are culturally emphasised) back up aggressively and are always running on the first-step decision rather than waiting to see where the ball goes.
Calling Conventions
- Hard YES: Run immediately. No hesitation.
- YES: Come for the run but be ready to dive.
- WAIT: Assess; the call may come late.
- NO: Stay, do not run.
- Caller convention: For balls hit in front of the wicket (straight, mid-off, mid-on, covers), the striker calls. For balls behind (fine leg, square leg, point), the non-striker calls — they can see the fielder's body position the striker cannot.
The Mankad Controversy — Now a Standard Run-Out
The Mankad (now officially called the 'non-striker run-out') occurs when the bowler, during the delivery action, breaks the non-striker's end stumps while the non-striker is outside the crease. Named after Vinoo Mankad (India), who ran out Bill Brown (Australia) this way in 1947. For decades it was legal but considered unsporting — convention held that the bowler should warn the non-striker first. In 2022 the ICC moved the Mankad from the 'unfair play' section of the Laws to the standard 'run-out' section, fully legitimising it with no warning required. Deepti Sharma's dismissal of Charlie Dean (England, 2022) brought the rule into the spotlight just before the law change.
Partnership Dynamics in Test Cricket
A partnership in Test cricket requires far more communication than in limited-overs formats. Batters at the crease for 3+ hours together develop run-calling systems, agree on which bowler each handles (the better player takes the more dangerous bowler), and monitor each other's mental state. Famous Test partnerships — Dravid and Laxman's 376 vs Australia in 2001, Hobbs and Sutcliffe's 172 at Melbourne in 1924-25 — required constant non-verbal and verbal communication to manage 40-50 overs together. A breakdown in communication during a 100+ run stand often costs a wicket to a run-out — the most momentum-shifting dismissal in Test cricket.
Frequently asked questions
Who calls for a run in cricket — the striker or the non-striker?
The convention is: for balls hit in front of the wicket (mid-on, mid-off, straight, covers), the striker calls because they can see the ball leaving the bat and the fielders. For balls behind the wicket (square leg, fine leg, point, backward point), the non-striker calls because they can see the fielder's body position and reaction from a better angle. Both batters say 'YES', 'WAIT', or 'NO' — and the decisive call takes precedence. A call of NO by either batter is absolute. Communication and decisive calling are the most important factors in successful running between wickets.
Is the Mankad run-out legal in cricket?
Yes — as of 2022, the ICC moved the Mankad (non-striker run-out) from the 'unfair play' section to the standard 'run-out' section of the Laws of Cricket. It is now fully legal and requires no prior warning. The bowler may attempt to break the non-striker's wicket at any point during the delivery action, before the ball is released, if the non-striker is outside their crease. If the non-striker is inside their crease when the stumps are broken, it is not out. The dismissal requires the ball to be live (the delivery cannot have already been a dead ball).
What is the penalty for a run-out in cricket?
A run-out has no direct penalty — it is simply a dismissal. The batter who was run out is out; no runs are scored from the delivery (unless runs were completed before the wicket fell). However, the batter who caused the run-out through a poor call can face significant team consequences: a top-order batter run out by an unnecessary single costs not just their wicket but potentially 50-100 runs of future scoring. Run-outs are particularly costly in Test cricket where rebuilding partnerships takes sessions. Statistics do not clearly attribute blame for run-outs, making it a somewhat invisible statistic in batting records.