The Night Watchman: Protecting the Top Order at the End of Day's Play
What a night watchman is in Test cricket — a lower-order batsman sent in at the fall of a wicket late in the day to protect the more valuable top-order batsman from having to bat for a short, difficult period in the evening — when night watchmen are used, the skills required of a successful night watchman, why some teams no longer use the tactic, and the famous instances where night watchmen played long, productive innings.
The Purpose
In Test cricket, a wicket falling with 2-10 overs remaining in a day's play creates a specific problem: a top-order batsman must face the bowling in conditions that are often difficult (the new ball, the 'twilight zone' of fading light, or a pitch that behaves unpredictably in the evening session) for a short period before stumps, then return the next morning when conditions have reset. The night watchman is a tactical substitute: instead of sending in the next established batsman (who might be dismissed in those difficult overs, wasting an important wicket), the team sends in a lower-order batsman (typically a bowler) who protects the established batsman and can survive the difficult evening without great loss if they are dismissed (losing a tailender rather than a batsman is a smaller blow).
Skills Required
A successful night watchman must have specific skills that differ from their normal role. They must be able to defend their wicket under difficult conditions for a short period — typically 2-10 overs — without being reckless. They do not need to score quickly; their primary mission is to occupy the crease until stumps. A night watchman who can consistently defend their stumps with a straight bat, judge which deliveries to leave, and avoid the temptations of rash attacking shots in difficult light or conditions is fulfilling their role entirely, even if they score only 3-5 runs. The challenge: most lower-order batsmen lack the technical defensive skills to survive sustained accurate bowling. Bowlers who also have genuine batting technique (Test all-rounders, or bowlers with first-class batting experience) are the most successful night watchmen.
When Night Watchmen Stayed to Bat
The night watchman system occasionally produces unexpected heroes — lower-order batsmen who not only survive the evening but go on to bat productively the following morning, scoring runs well above their usual contribution. The most famous night watchman innings: Australia's Jason Gillespie scored 201 not out against Bangladesh in 2006 while being used as a night watchman (one of cricket's great statistical curiosities — a bowler with a career batting average of 13 scoring a double century). Mark Wood (England) and Dave Richardson (South Africa) also had notable night watchman innings that outlasted their protective function. These innings suggest that the night watchman occasionally benefits from reduced pressure on their own wicket — they are 'supposed' to get out early, so they bat more freely than normal.
Frequently asked questions
Can a night watchman be any player, or must they be lower-order?
By convention and logic, a night watchman must be a player who is a 'cheap' wicket — whose dismissal costs the team less than the dismissal of the established batsman being protected. In practice, this means bowlers (no.8-11) are the standard night watchman choice. Using a batsman from no.5-7 as a night watchman would defeat the purpose — you are not protecting the top order by sacrificing a similarly valuable middle-order batsman. There is no rule preventing any player from being sent in at any position; the captain's tactical choice is unrestricted by law. Some teams have experimented with sending their no.5 batsman in one-over early as a night watchman when a wicket falls at the 80th over, but the strategic logic is weaker unless the no.6 and no.7 are genuinely tailenders.
Does the night watchman have to give up their wicket the next morning?
No — there is no obligation for the night watchman to give their wicket away the following morning. Once a new day has begun and the specific 'night' risk that the tactic was designed to avoid has passed, the night watchman can bat for as long as they can. In practice, if the night watchman has survived the evening and is still batting the next morning, the captain typically allows them to continue (having already used the wicket). The batting order is effectively reorganised around the night watchman — the established batsman whose place was taken (e.g., no.4 in the order) now effectively bats at the position where the night watchman eventually falls.
Is the night watchman tactic used in limited-overs cricket?
No — the night watchman is exclusively a Test cricket tactic. In limited-overs cricket (ODIs, T20s), there is no concept of day/stumps (all overs are completed in one uninterrupted session, or at most two day-night sessions), and the batting order is fixed for the entire innings with no strategic benefit in sending in a lower-order batsman early. In T20s and ODIs, every delivery counts toward the total, and wasting batting time by sending in a tail-ender costs more than any potential protection of the batting order. The night watchman is specifically a response to the Test format's multi-day structure and the varying difficulty conditions create at different times of day.