Skip to content
Rules4 min

Night Watchman in Cricket Explained — Why Teams Send a Lower-Order Batter at No. 3

A night watchman is a lower-order batsman sent in to bat higher than usual when a wicket falls near the end of the day's play in Test cricket — protecting a specialist batter from having to face a fresh spell in fading light. Learn when captains use the tactic, its pros and cons, and the greatest night watchman innings in history.

Written by GeoCric EditorialUpdated Jun 25, 2026
ShareShareWhatsAppFacebook

A night watchman is one of Test cricket's most distinctive tactical decisions. When a wicket falls close to the close of play, the captain can choose to send in a lower-order batsman (typically a bowler) instead of the next specialist batter, to protect the remaining recognised batters from a difficult spell in poor evening light. The tactic is almost exclusively a Test match phenomenon — in limited-overs cricket the urgency of the run rate makes it impractical.

What makes a good night watchman?

  • Technically sound enough to survive: not expected to score quickly, just to see out the remaining overs without getting out.
  • Good temperament under pressure: batting in fading light with the field aggressive is stressful.
  • Able to bat for extended periods: a night watchman who survives the evening is expected to continue the next morning.
  • Dispensable at that moment: their wicket is less costly to lose than a key batter's.

The logic of the tactic

Batting at the end of the day in Test cricket is particularly difficult. The ball is often in useful swing/seam condition; the fading light narrows the batter's vision window; the fielding side is energised approaching the close; and the bowling side can take fresh overs without losing momentum overnight. A specialist number 4 or 5 batter facing 10 overs in these conditions risks a cheap wicket that costs the team dearly the next morning. The night watchman absorbs that risk.

The term 'night watchman' comes from a pre-lighting era when late-day cricket was genuinely harder to see in. Modern floodlights have reduced the visibility problem, but the tactical logic survives — the bowling side is still freshest at the start of a new spell.

Famous night watchman innings

  • Jason Gillespie, 201* vs Bangladesh, Chittagong, 2006 — sent in as night watchman, the Australian pace bowler scored a double century. The highest innings by a recognised night watchman in Test history.
  • Mark Boucher, 125 vs Zimbabwe, 1999 — the South African wicketkeeper sent in to protect a specialist batter ended up scoring a century.
  • Alex Lees, 67 vs West Indies, Grenada, 2022 — a modern example where the night watchman kept England's momentum going under the Bazball era.

Criticism of the tactic

Critics argue the night watchman disrupts batting rhythm, especially if they get out quickly anyway. Teams that are aggressively targeting a score (such as under England's Bazball approach) will sometimes send the next specialist in regardless, arguing the extra 30 minutes of batting time is worth the risk.

Frequently asked questions

What is a night watchman in cricket?

A night watchman is a lower-order batsman (usually a bowler) sent to bat higher than their usual position when a wicket falls close to the end of a day's play in Test cricket. The purpose is to protect remaining specialist batters from facing difficult bowling in fading light, trading a low-order wicket for the risk instead.

Why is it called a night watchman?

The name comes from pre-lighting cricket eras when batting in late-day fading light was genuinely dangerous and difficult. The lower-order batter 'watches over' the innings until close of play, like a night watchman guarding a building.

Who scored the highest innings as a night watchman?

Jason Gillespie scored 201* for Australia vs Bangladesh in Chittagong in 2006, batting as a night watchman. He remains the only specialist bowler to score a double century in Test cricket.

Is the night watchman used in T20 or ODI cricket?

Essentially never. The night watchman is a Test-match tactic. In T20 and ODI cricket, scoring rate is too important to risk with a lower-order batter, and matches are completed in a single day so there is no next morning for a specialist batter to resume.