The Night Watchman: Cricket's Most Unusual Batting Tactic
Why Test teams send a lower-order bowler to bat near the end of a day when a specialist batsman is dismissed — protecting a top-order player from having to begin a fresh innings late in the day, the risk calculation, famous night watchman performances including Alex Lees and Jason Gillespie, and why the tactic is controversial.
The Purpose of the Night Watchman
A night watchman is a lower-order batsman (typically a bowler) sent in to bat at a higher position than usual when a wicket falls late in a day's play in Test cricket. The purpose is to protect a specialist batsman from having to face a small number of overs in difficult conditions at the end of the day — and then return the following morning to face the fresh-ball, fresh-bowler challenge of a new session in an unfamiliar mental state (having only faced 3-4 balls the previous evening).
The theory is that a night watchman accepts the risk of being dismissed cheaply at the end of the day, allowing the team's specialist batsman (who would be the next in the natural order) to come in fresh at the start of the following day's play. The bowler/lower-order player is expected to survive the remaining overs without scoring substantially, then be dismissed quickly the next morning — freeing the specialist to come in with fresh conditions and full focus. If the plan works, the specialist batsman avoids the psychological pressure of a brief late-day innings.
The Risk Calculation
The night watchman tactic carries inherent risks. If the night watchman is dismissed before stumps, the specialist batsman must come in anyway — and now the team has also used up an additional wicket. If the night watchman survives to the next morning and continues to bat for an extended period (blocking specialist batting time or getting dismissed early in the morning session), the plan partially backfires. The ideal scenario: the night watchman survives the final 4-8 overs of a day, is dismissed within the first 15-20 overs of the following day, and the specialist arrives refreshed.
The most famous counter-argument against the night watchman is that it implicitly accepts that the number-3 or number-4 batsman is less capable of surviving difficult late-day conditions than a bowler — an assumption some batting coaches reject. Teams like Australia under Steve Waugh were noted for rarely using night watchmen, believing that their top-order batsmen should be capable of handling any conditions regardless of when in the day they bat.
Night Watchman Successes
The most famous night watchman innings in Test history is Jason Gillespie's 201* against Bangladesh for Australia at Chittagong in 2006. Gillespie, a specialist fast bowler, was sent in late on day one and proceeded to bat across multiple sessions the following day, scoring a double-century (the only double-century by a night watchman in Test history). Gillespie had a first-class batting average of approximately 11 — his 201* was 19 times his usual run total per innings. It remains one of cricket's most delightful statistical anomalies.
Frequently asked questions
Can a captain send any player as a night watchman, or just tailenders?
A captain can theoretically send any player as a night watchman — the batting order is entirely within the captain's discretion (there is no rule requiring batsmen to come in a specific sequence). In practice, a night watchman is almost always a bowler or genuine lower-order batsman; sending a recognised batsman as a night watchman would waste their top-order skills and expose them to an unnecessary wicket-taking opportunity. Some teams have sent their number 7 or 8 (all-rounders) as night watchmen on specific pitches.
Is the night watchman tactic specific to Test cricket?
Yes — the night watchman is only used in Test cricket (and occasionally first-class cricket), because it relies on the existence of an overnight break that makes the start of a new day's play a distinct psychological moment. In ODI and T20 cricket, there is no overnight break; every ball follows the previous delivery in a single continuous session. The night watchman concept has no equivalent in limited-overs cricket.
What happens if a night watchman is still batting when a declaration is made?
The captain can declare the innings closed at any time, regardless of which batsman is at the crease. If a night watchman is still batting and the captain decides to declare, the night watchman's innings ends with the declaration (they are not dismissed, so they are recorded as 'not out' in the scorecard). This situation occasionally produces awkward optics if the night watchman is batting fluently and feels robbed of further runs — but the captain's tactical prerogative overrides any individual batsman's ambitions.