Drawing a Test Match: Tactics for Batting Teams Saving Games
Deliberately drawing a Test match — defending for hours to prevent defeat — is as skilled an art as winning. This article covers the tactical and psychological approach to saving a Test, the specific batting techniques used when a team is batting to draw, and why successful draws are considered creditable performances in Test cricket.
When a Draw Becomes the Goal
A team shifts to draw-saving mode when: they are behind by a significant margin in their second innings with insufficient overs remaining to score enough runs for victory; they have been asked to follow on and must survive Day 4 and Day 5 to prevent defeat; or they are chasing an impossible target (needing 450 from 70 overs) where the only realistic outcomes are a draw (batting time out) or a loss (being bowled out before the match ends). The tactical shift is explicit: the team's target is no longer runs but time — specifically, surviving until the scheduled close of play on Day 5. Every over that passes without a wicket falling is a victory; every boundary is a bonus.
The Draw-Saving Batting Approach
Specific draw-saving batting techniques: leave everything outside off stump that doesn't threaten the stumps (the most common dismissal in draw-saving cricket is the batsman reaching for a ball that could have been left — disciplined leaving is the most important draw-saving skill); play defensive strokes with 'soft hands' (relaxing the grip at contact so that any edge produces a ball that falls short of the catching fielders rather than carrying); occupy the crease time rather than scoring runs (every ball played defensively consumes the same time as every run scored); and specifically avoid hook and pull shots against pace bowling (these shots sacrifice timing control and produce catches to boundary fielders more often than they score boundaries).
The Psychology of Batting for a Draw
The psychology of batting for a draw is unique in sport: the team is explicitly not trying to win, only not to lose. This requires suppressing the competitive instinct to score, attack, and attempt victory — instead embracing a patient, defensive mindset that can feel passive but is actually demanding high concentration. Batsmen who succeed in draw-saving situations describe 'shutting out the scoreboard' (not looking at the overs remaining or the required total), instead focusing exclusively on each ball as an isolated event. The biggest psychological danger: the batsman who becomes too comfortable after 50 balls of survival and attempts an attacking shot — the mental reset required to maintain defensive concentration for 100-200 balls without a single aggressive shot is one of batting's hardest psychological achievements.
Frequently asked questions
Can the fielding team accelerate the game to prevent a draw?
Yes — the fielding team has several tools to try to prevent the draw: setting aggressive fields close to the bat to create catching opportunities from defensive strokes; using the full range of bowling variations to create dismissal opportunities; and applying sustained pressure to induce the concentration lapses that end partnerships. However, the fielding team cannot force dismissals if the batting team defends correctly — the toss of the ball against the bat, in conditions where the batsman is playing within their ability, will not produce a wicket every time regardless of bowling quality. The draw is a legitimate result precisely because cricket's laws allow batting teams to legitimately defend without penalty for slow scoring.
Is there a minimum over rate the fielding team must maintain?
Yes — ICC regulations require fielding teams to bowl a minimum of 15 overs per hour in Test cricket, which equals 90 overs per day across 6 hours of play. Teams that fall behind the required over rate face fines (proportional to how many overs they are short) and in some cases, points deductions in the ICC Test Championship standings. Over rate violations are a significant issue in modern Test cricket — pace-heavy attacks that use long run-ups and many over-changes run behind rate regularly. From the draw-saving batting team's perspective, a slow over rate is actually beneficial (fewer overs need to be survived) — which is why captains of draw-saving teams are less likely to complain about a slow opposition over rate.
What is the most overs survived in a draw-saving innings?
Extended draw-saving innings in Test cricket have produced some of the format's longest individual batting performances. Hanif Mohammad's 337 against the West Indies in 1958 — which was also a draw-saving innings against a West Indies first innings total — involved batting for over 16 hours. In the post-2000 era, draw-saving innings from Brian Lara (multiple occasions) and Rahul Dravid (particularly his India draw-saving partnerships in difficult away series) involved 200+ ball innings across 5-8 hours. The sheer volume of time that certain Test batsmen have committed to draw-saving performances is among cricket's most underrated athletic and mental achievements.