
The nightwatchman: why the tactic exists and when it backfires
Sending a bowler in to bat ahead of a specialist, purely to survive the last few overs of the day, is one of cricket's oldest defensive tricks.
The idea behind a nightwatchman is straightforward: if a wicket falls late in a day's play in a Test match, rather than sending in the next specialist batter to face a short, high-pressure period with the close of play in sight, the batting side sends in a lower-order bowler instead. The logic is that losing a bowler's wicket cheaply the next morning costs the team far less than risking a genuine batter's wicket in a scrappy, low-value passage of play.
The tactic only makes sense in Test cricket, where an innings unfolds over days and preserving a specialist batter's wicket for a fresh start the following morning has real value. It doesn't translate to white-ball cricket at all, where every over matters roughly equally and there's no 'overnight' to protect a batter from.
It backfires in two predictable ways: either the nightwatchman gets out quickly anyway, meaning the side burned a wicket for nothing and still has to send in a specialist under the same pressure; or the nightwatchman bats unexpectedly well and stays in deep into the next day, which sounds like a bonus but actually delays a genuine batter's start and can disrupt the order the captain wanted lower down.


