The Art of the Draw: How Teams Bat to Save a Test Match
The tactical and psychological elements of batting for a draw in Test cricket — when a draw becomes the realistic target, the concentration demands of batting all day to save a Test, famous rearguard innings throughout history, the role of the lower order in survival situations, and why draws are considered a legitimate and valued result in the five-day format.
When the Draw Becomes the Goal
In Test cricket, a draw is not a failure — it is a result that denies the opposition two points in a series and preserves a team's position. Batting for a draw becomes the primary objective when a team has followed on (been forced to bat a second time in the same match, typically after conceding a large first-innings lead), or when rain has compressed the match schedule to the point where the required runs to win are mathematically too large to chase in the available time. The transition moment — from 'we are trying to win' to 'we are trying to draw' — is a critical tactical decision that captains and coaches must make explicitly, as the batting approach required for survival is fundamentally different from the approach required for run-scoring.
The key draw-batting principles: play every ball on its merit, avoid driving hard at pitched-up deliveries (the highest caught-and-bowled risk), leave anything outside off stump with margin to spare, survive the new ball when it arrives, negotiate the best bowlers session by session rather than ball by ball, and mentally break the challenge into manageable time units. A batsman tasked with batting all day (90 overs) who thinks about the full day will be overwhelmed — the mental approach is to survive to the next drinks break, then the next session end, building the whole from small components.
Famous Rearguard Innings
Test cricket's most celebrated draws often involve lower-order or tail-end batting partnerships of extraordinary concentration and determination. Monty Panesar and James Anderson's partnership at Cardiff in 2009 — the last pair batting for 11.3 overs to save the opening Ashes Test — is among the most famous. Both batsmen are recognised primarily as bowlers (Anderson as one of England's greatest ever, Panesar as a specialist spinner); neither is known as a batting technician. Yet the partnership survived 69 balls against Australia's attack, including Shane Watson's extreme pressure bowling, to deny Australia the win and preserve England's series position.
Mike Atherton's 185 not out at Johannesburg in 1995 — batting for nearly 11 hours against a South African attack including Allan Donald and Shaun Pollock — is regarded as one of England's greatest individual saves. Atherton faced 492 balls in extreme heat against an aggressive pace attack, refusing to play a single attacking shot that was not necessary. The innings is studied as a template for draw-saving concentration: Atherton later described the approach as making the bowlers tire of bowling at him rather than him trying to tire them — a psychological framing that made each delivery an individual battle he could win.
The Lower Order's Role
Draw-saving situations often require tail-enders to contribute significant batting time. In modern Test cricket, the gap between number 8-11 batting skill levels varies enormously by team — some teams (England in the Anderson-Broad era, Australia with Mitchell Starc and Nathan Lyon) have tails capable of adding 50-80 runs; others have tails that regularly fold for single-digit contributions. Training specifically for draw situations — recognising leave opportunities, playing late, defending with soft hands — has become part of fast bowlers' conditioning programmes in teams who regularly play five-day cricket. Tail-enders who can bat for 30-60 balls in a draw situation provide enormous value beyond their nominal batting average.
Frequently asked questions
Is a draw the same as a tie in Test cricket?
No — a draw and a tie are distinct results. A draw occurs when a match ends without a result (stumps drawn on the final day with the match in progress, or the batting team still short of the target with wickets remaining). A tie is an extremely rare result where both teams finish with exactly the same total runs (the team batting last is dismissed having reached exactly the required total, or the team batting last has all 10 wickets fall while level on runs). Only two Test matches in cricket history have ended in a tied result; hundreds end in draws every year.
Can a team deliberately declare to avoid defeat in a Test?
Yes — a team can declare their innings closed at any point, which means the opposing team must then bat again. In theory, a team could declare to avoid being bowled out (which would leave them with no wickets and a certain defeat). In practice, however, declaring in a clearly losing position would be tactically unusual because it hands the fielding side an easier scenario — it requires the fielding team to bowl the batting side out again rather than chase a theoretical target. Declarations in draw-saving situations typically occur to put the opponents in to bat with a target that is theoretically achievable but practically very difficult, converting a loss into a draw attempt.
How many overs must a team bowl per day in a Test match?
ICC playing conditions require that 90 overs be bowled per day of Test cricket. If play is lost to weather or poor light and a full day's overs cannot be completed, the regulations allow for make-up time — extending play beyond the scheduled close to compensate for lost overs. Teams can face penalties (runs added to the opposition total) if they consistently bowl too slowly. The 90-over per day requirement is central to draw calculations: knowing how many overs remain in the match and how many runs the bowling team needs to take the required wickets determines when a draw becomes statistically achievable.