What Is a Nightwatchman in Cricket?

A nightwatchman is a lower-order batter, usually a bowler, promoted out of turn to bat in the closing overs of a day’s Test cricket. The point is to shield a specialist batter from the hardest conditions of the day and let them start fresh the next morning. It exists only in red-ball cricket, and it is falling out of fashion.

The last half hour of a day’s play is a nasty time to bat. The light is going, the bowlers are pushing for one more wicket before stumps, and a batter’s concentration has been stretched for hours.

The basic idea

A nightwatchman is a lower-order batter sent in out of turn, usually a bowler, to bat in the closing overs of a day. If a wicket falls late, instead of sending in the next specialist batter, the captain promotes a tail-ender to see out the remaining time.

The reasoning is basic economics. A frontline batter is worth a lot of runs, so you would rather not expose them to the toughest conditions of the day when there is little to gain. A tail-ender is worth fewer runs, so it hurts less if they get out.

Why late in the day is so hard

Several things make the end of a day’s play the worst time to arrive at the crease:

• Fading light makes the ball harder to pick up.
• Tired eyes and feet slow a fresh batter’s reactions.
• Bowlers are motivated to grab a wicket before the break.

Send your best batter in there and they might fall cheaply after all that effort. Send a nightwatchman and your star can walk out fresh the next morning, when batting is easier.

When it works, and when it backfires

Outcome	What happens
Nightwatchman survives to stumps	Top batter is protected — tactic succeeds
Nightwatchman gets out quickly	You may lose two wickets in a session instead of one
Nightwatchman digs in next day	A bonus: some go on to score valuable runs

The tactic is not universally loved. Critics argue that a nightwatchman can simply hand the bowling side an extra wicket, and that a set specialist might have survived anyway.

When it went spectacularly right

Jason Gillespie holds the answer to the trivia question. Sent in as nightwatchman against Bangladesh at Chattogram in April 2006, the Australian fast bowler batted through the next day and the one after, finishing on 201 not out. It remains the only double hundred by a nightwatchman in Test history, and Australia declared with him still there.

The detail that makes it better: it was the last Test innings Gillespie ever played. He was dropped afterwards and never picked again, retiring with a Test batting average boosted permanently by one absurd week.

Other nightwatchmen have made the tactic pay without going that far. Alex Tudor was left stranded on 99 not out for England against New Zealand at Edgbaston in 1999 when the winning runs came, denied a century by his own team’s victory. Tony Mann made 105 for Australia against India in 1977, the first nightwatchman Test hundred.

Why teams are dropping it

The tactic has quietly declined. England under Brendon McCullum has largely stopped using it, and the reasoning is straightforward: a nightwatchman who fails costs you two wickets in the session instead of one, and a top-order batter has better technique to survive the same overs. The arithmetic that justified the tactic assumed the tail-ender’s wicket was nearly worthless, which is less true now that lower orders bat better than they did.

Australia has stuck with it more consistently, and the split is less about evidence than temperament. The nightwatchman is a red-ball gamble: risk a cheap wicket now to keep a valuable one safe for tomorrow. It belongs to Test and first-class cricket, where days end and begin again, not to the non-stop world of T20.