The Nightwatchman: Why Teams Send a Bowler to Bat
A nightwatchman is a lower-order batsman — typically a bowler — sent in to bat higher in the order when a top batsman is at risk of getting out near the end of a day's play. This guide explains the nightwatchman strategy, its history, famous examples, and whether it still makes tactical sense in modern cricket.
The nightwatchman is a Test cricket tactical device — when a wicket falls close to the end of a day's play, the captain sends a tail-end batsman (typically a bowler) in ahead of a more valuable batsman to protect them from getting out in the final few overs of the day. The logic: losing a key batsman (say, a number three) with two overs remaining is costly — they'd be dismissed and start fresh on the next morning. Better to send the tail-ender to survive those two overs, preserving the batsman for a full day's start.
The Theory
The nightwatchman theory rests on asymmetry: if the nightwatchman gets out in those final overs, it doesn't matter much (the tail would face anyway eventually). If they survive, the recognised batsman comes in fresh the following morning. The tactic is most valuable when conditions are difficult (overhead, pitch deterioration) or the bowling attack is in form — situations where getting through a session without playing a shot matters more than scoring runs.
When the Nightwatchman Works
The nightwatchman works best when: the bowler can defend competently (not necessarily score but not give their wicket away); conditions are genuinely difficult (suggesting a good batsman might get out anyway); the captain has assessed that losing the tail-ender is less costly than risking the recognised batsman; and the nightwatchman has the mental composure to handle the moment. It works least well when the nightwatchman is recklessly dismissed (wasting the tactic) or when the recognised batsman was capable of handling the conditions regardless.
Modern Nightwatchman Debate
The modern debate around the nightwatchman: with tail-enders in some teams capable of scoring quickly (Axar Patel, Mathew Wade in limited-overs contexts), the distinction between 'nightwatchman' and 'promoted lower-order batsman for aggression' has blurred. Some analysts argue the strategy is overused — the probability of a batsman getting out in 2-3 overs is low enough that the nightwatchman's benefit doesn't always justify the disruption to the batting order. England under Bazball (2022 onward) have largely abandoned the nightwatchman in favour of always sending the next recognised batsman.
Frequently asked questions
What is a nightwatchman in cricket?
A nightwatchman in cricket is a lower-order batsman — typically a bowler — sent in to bat higher in the order than their usual position when a wicket falls near the end of a day's play. The purpose is to protect more valuable recognised batsmen from getting out in the final overs of the day, by sending a tail-ender who has less to lose by being dismissed. The tactic is unique to Test cricket where the day's end is a strategic point.
Has a nightwatchman ever scored a century?
Yes — Jason Gillespie, Australia's fast bowler, scored 201* as nightwatchman for Australia vs Bangladesh in 2006, making it the highest Test score ever by a designated nightwatchman. He came in at number 9 in the order and completely dominated the Bangladesh bowling. Other notable nightwatchman high scores include several half-centuries by recognised tail-end batsmen who were given the role.
Do modern teams still use the nightwatchman?
Usage of the nightwatchman varies by team and captain philosophy. England under Ben Stokes' leadership (2022-present) has largely abandoned the nightwatchman in favour of aggressive batting regardless of timing. Other teams (India, Australia) still use it selectively when conditions are difficult. The debate has intensified as tail-enders have become more capable batsmen and the strategic value of the nightwatchman has been questioned by analysts.