Batting with the Last Wicket: Tactics When You're Number 11
When a team has one wicket remaining, the recognised batsman must protect the tail-ender while also scoring enough runs to be competitive. This article covers the tactics of batting with the last wicket — keeping the strike, farming the bowling, and the rare occasions when tail-enders contribute significantly to a last-wicket stand.
The Last Wicket Challenge
Batting with the last wicket (number 11 in the lineup) presents the recognised batsman — often a number 8, 9, or 10 who has reached the end of their own innings — with a specific tactical challenge: the partner cannot reliably bat, so the primary goal is to retain the strike as much as possible while scoring runs. In Test cricket, the last-wicket stand's purpose depends on the match situation: if the team needs to avoid defeat, the goal is to bat for time (every ball faced reduces the opposition's opportunity to bowl); if the team is in a strong position and adding to a lead, the goal is to score as quickly as possible before the tail-ender is dismissed.
Farming the Strike
Strike farming — ensuring the recognised batsman faces most deliveries and the tail-ender faces as few as possible — is the primary tactic with the last wicket. Methods: scoring singles from the 5th or 6th ball of an over (so the recognised batsman is at the non-striker's end for the beginning of the next over, giving the tail-ender only the last ball of the over to face); deliberately leaving some balls as dot balls to avoid the risk of giving the tail-ender strike; and occasionally playing defensively when the tail-ender could rotate strike with a risky single. The trade-off: strike farming necessarily reduces the scoring rate (because the recognised batsman cannot always attack every delivery when managing strike), but the alternative (the tail-ender facing 3-4 deliveries per over) dramatically increases the dismissal risk.
When Tail-Enders Contribute Significantly
Occasionally, the tail-ender makes significant contributions to a last-wicket partnership. This typically occurs when: the tail-ender has unexpectedly good batting ability for their nominal position (many fast bowlers have first-class batting averages of 15-20 that exceed their reputations); the bowling team becomes complacent (setting attacking fields for the tail-ender that leave gaps the tail-ender can exploit with a swing of the bat); or the batting conditions become extremely favourable (a flat pitch where even a tail-ender can survive and score from loose deliveries). Cricket history has multiple examples of last-wicket partnerships exceeding 100 runs — Jim Southerton and Tom Emmett's 173 in 1868 was the first recorded century last-wicket partnership, and the record has been extended multiple times since.
Frequently asked questions
What is the record last-wicket partnership in Test cricket?
The record last-wicket (10th wicket) partnership in Test cricket is 163, shared between Ashton Agar (98) and Phil Hughes (103) for Australia against England at Trent Bridge in 2013. Several other last-wicket partnerships have exceeded 100 runs in Test history — the existence of multiple 100+ last-wicket stands demonstrates that bowling teams occasionally fail to dismiss genuine tail-enders efficiently when the conditions and the tail-ender's form align. Last-wicket records should be verified against current ESPNcricinfo or official ICC databases, as first-class and Test records are regularly reviewed.
How do bowling teams attack the last wicket more effectively?
Bowling tactics when the last wicket falls: target the tail-ender directly with the most difficult deliveries their technical ability can't handle (a genuine tail-ender struggles most with: pace that rises sharply from a good length; spin that turns away from their naturally open stance; and full straight deliveries that aim directly at the stumps without swing that a tail-ender might outside-edge defensively). Field placement against the last wicket: more aggressive close catching positions (accepting that the tail-ender's defence is unreliable, so close catchers have higher chance of success); and potentially a slip cordon with a mid-on and mid-off (to prevent the recognised batsman from scoring freely in front of the wicket while the tail-ender is at the non-striker's end).
Should a recognised batsman take risks to score quickly with the last wicket?
The decision to take attacking risks with the last wicket depends entirely on the match situation: if the team is saving a draw (batting for time), the recognised batsman should be conservative regardless of the scoring rate — every delivery survived is a delivery that reduces the opposition's bowling opportunity; if the team is setting a target and the last wicket is extending an already-strong lead, attacking quickly to add 20-30 runs is justified because the marginal run value (from 200 ahead to 220 ahead) may matter for a declaration or for setting a psychologically larger target. In limited-overs cricket, the recognised batsman with the last wicket should always attack — every run matters in a total that the opposition must chase.