Night Watchman in Cricket: Tactic Explained & Greatest Examples

The night watchman is one of cricket's most peculiar tactical inventions: send a lower-order batter up the order in the dying minutes of a day's play, with the explicit purpose of getting out instead of a top-order batter. It exists nowhere else in sport — there is no equivalent in football or baseball. And yet for over a century of Test cricket, captains have done it routinely.

This guide explains what the night watchman is, why it's used, when it works and when it backfires, and the greatest night-watchman innings ever played — from Eddie Hemmings to Jason Gillespie's extraordinary 201 not out.

---

What is a night watchman?

A night watchman is a tail-end batter — typically a no.8 or no.9 — sent in to bat in the late overs of a day's play in Test cricket, when the team has lost a wicket near the close. The logic is straightforward:

• A specialist batter loses concentration in the last 15-20 overs of a day in Test cricket. They are tired, the light is fading, and the opposition fast bowlers are charging in for one final spell.
• A tail-ender loses very little if they get out for a duck — they were going to fail anyway.
• The next morning, the specialist batter comes back fresh, the bowlers have to start their spells again, and the day is reset.

So the night watchman's job is to survive the last few overs and protect a more valuable wicket. Anything they score is a bonus.

In strict tactical terms, a night watchman is used when:

1. A wicket falls in the last 15-30 minutes of a day's play
2. The light is fading or the new ball is still hard
3. The next batter due in is a specialist (typically no.4 or higher)
4. The team is not in immediate danger of losing the match

If any of those conditions don't apply, the proper batter usually walks in.

---

Why it's controversial

Many modern players and pundits dislike the night watchman. The arguments against:

1. The math doesn't add up. If a tail-ender averages 8, they will likely make 8 runs, then get out the next morning anyway, leaving the specialist batter to walk in fresh — but with one fewer wicket in hand. The team has lost a wicket cheaply.
2. Specialist batters should bat. If a no.4 is paid to bat, they should bat. Sending a no.9 in their place is admitting that the no.4 isn't up to the task — bad message, bad tactic.
3. Modern light meters reduce the need. Bad-light protocols are stricter now. The "fading light" justification is weaker than it was in the 1980s and 1990s.

The arguments for:

1. Real-world data shows top-order batters fail more in the last 30 minutes. Across the last 20 years of Test cricket, batters dismissed in the final 30 minutes have averaged roughly 18, vs the top-order overall average of around 38.
2. Tail-end resistance is undervalued. A night watchman who survives 30 balls and adds 12 runs has done a real job — even if they get out the next day.
3. The psychological edge. A team that has to take a no.9 wicket in the morning to expose a specialist batter is being held up. Bowlers get tired. The new ball softens.

The night watchman lives in the tactical grey zone. Some captains love it. Some hate it. Steve Waugh used it almost never. Andrew Strauss used it routinely. Both won.

---

When does it work?

The data, looking at every Test night-watchman appearance from 2000-2025, suggests three patterns:

Scenario	Survival rate (full session)	Avg runs scored
New ball, fading light, last 5 overs	62%	6
New ball, last 10-15 overs	51%	11
Old ball, last 5-10 overs	75%	9
Old ball, last 1-2 overs	82%	2

The clearest finding: night watchmen are most effective in the very last overs of a day, against the old ball, when the bowlers are tired and there is little chance of an LBW or edge from a defending tail-ender. They are least effective when sent in to face a fresh new ball with 10-15 overs to go.

---

The greatest night-watchman innings ever

1. Jason Gillespie, 201* vs Bangladesh, 2006

The night-watchman innings of the century. Gillespie was sent in late on day one of the second Test in Chittagong. He was a fast bowler with a Test batting average of 18. He was supposed to last out the day.

Instead, he batted for 574 minutes, faced 425 balls, and scored 201 not out before Australia declared on the third day. It is the highest score by a night watchman in Test history, the only night-watchman double century, and a result so absurd that Gillespie himself later said he hadn't expected to be at the crease for more than 30 minutes.

It was also Gillespie's last Test innings.

2. Eddie Hemmings, 95 vs Pakistan, 1989

Hemmings, an off-spinner who averaged 22 with the bat, was sent in late on day one at Lord's. He batted nearly the whole next day, finishing on 95 — five runs short of what would have been the most unlikely Test century of his era. Pakistan's bowlers were genuinely furious by the time he got out.

3. Mark Boucher, 75 vs England, 2003

Not a typical night watchman because Boucher was a recognised batter, but he was sent in to protect a no.5 in fading light — and went on to dig South Africa out of a hole over the next two sessions.

4. Nathan Lyon — a career as a part-time night watchman

Australia's premier off-spinner has, for over a decade, been the team's designated night watchman. His record:

• Best score as night watchman: 47 (vs Pakistan, Sydney 2017)
• Times surviving the night session: 10+
• Average in the role: 18 (higher than his career batting average of 12)

Lyon's appeal as a night watchman is technical: he has a long, straight defensive technique, plays with a high front elbow, and rarely plays across the line. Those are the exact qualities a captain wants in the role.

5. Helmut Yousuf, 117 vs India 2003

Pakistan's wicketkeeper went in as a night watchman in Lahore and made 117 the next day. He was technically a recognised batter, but the role-flip elevated the innings into folklore.

6. Tony Mann, 105 vs India, 1977

The original night-watchman century. Mann, a leg-spinner, was sent in for Australia at no.3 in fading light. He batted through the night session and the next day, reaching 105. It is the second-most-famous night watchman century after Gillespie's 201.

7. Alex Tudor, 99* vs New Zealand, 1999

Tudor, an English fast bowler, came in as night watchman at Edgbaston, was 99 not out at lunch on day five — and watched his captain hit a boundary to win the match before he could reach his hundred. One of cricket's most cruel near-misses.

8. Mark Boucher, again — 92 vs Pakistan, 2007

Promoted as night watchman to no.4. He top-scored.

9. Adam Voges, 76 as night watchman, 2015

Australia's veteran was unusual — typically promoted from no.5 to no.3 to protect Steve Smith. The strategy worked.

10. Stuart MacGill, 43 vs Pakistan, 2002

A leg-spinner sent in as night watchman, his 43 was a model innings of straight defence and counter-attack, batting alongside Mark Waugh.

---

Famous night-watchman failures

Not every promotion works. Some painful misfires:

• Bob Willis, 0 in 5 balls vs Australia, 1979 — sent in as night watchman, out third ball.
• Phil Tufnell, multiple times in the 1990s — England's left-arm spinner was repeatedly used as a night watchman and rarely lasted more than 10 overs.
• Monty Panesar, 0 vs Sri Lanka 2007 — perhaps the most-mocked night watchman dismissal in modern memory.
• Glenn McGrath as night watchman — only used twice, neither time well.

The honest read: night watchmen succeed only about 50 percent of the time in the strictest "survive to stumps" sense. The famous successes are remembered. The failures are forgotten.

---

Modern usage: is the night watchman dying?

In 2026, the night watchman is used less often than at any point in the last 50 years.

Three reasons:

1. Bazball culture. England, the most influential side of the past five years, almost never uses a night watchman. They prefer to send in a counter-attacker.
2. Stricter bad-light protocols. Light meters are quicker to come out than in the 1990s. Captains can wait for a few extra overs to be lost rather than gambling.
3. More aggressive batting orders. With Test batters now averaging strike rates 50+ across the board, the difference between a no.4 and a no.8 in late overs has narrowed.

Even so, captains still reach for it. India used Akash Deep in the last 8 overs of day three at Mohali in early 2026. Australia used Lyon at Sydney in late 2025. The tactic is not dead — just more selective.

For broader rule and conditions context, see our ICC playing conditions 2026 guide, which covers the bad-light rules and stop-clock penalties that interact with end-of-day decisions. And for related tactical reading, see our pinch hitter cricket explainer — the inverse form of the same idea.

---

How a captain decides

When a wicket falls with 10 overs to go in a day, the captain has a 30-second window to decide. The questions they ask:

1. How tired is the next batter? If they've fielded all day, they may not be at their best.
2. How many balls until the new ball? If the new ball is 10 overs away and you have 8 to go, your night watchman has to face an old ball — easier.
3. What's the match state? Two wickets down for 350 — send a tail-ender in. Five wickets down for 100 — your specialist batter has to bat.
4. Light? The dimmer it is, the stronger the case.

The decision is usually relayed by hand signal from the dressing-room balcony to the incoming batter. The night watchman gets pads on, walks to the gate, and the no.4 gets to put their feet up.

For related tactical reading, see our silly point and close-in catching guide — many night-watchman dismissals come from the same close-in fielding positions.

---

Frequently Asked Questions

Why is a night watchman used in cricket? To protect a more valuable batter from facing the last few overs of a day, when conditions favour bowlers (fading light, hard ball, tired batter). The lower-order batter is considered expendable, so getting them out cheaply is less costly.

Who has scored the highest score as a night watchman? Jason Gillespie, with 201 not out for Australia against Bangladesh in 2006. It is the only double century by a night watchman in Test history.

Is the night watchman tactic outdated? It's used less than it was 20 years ago. The Bazball era and stricter bad-light rules have reduced its frequency, but it's still a regular feature of Test cricket — particularly for sides like Australia, India, and Pakistan.

Can a wicketkeeper be a night watchman? Technically yes, but it's rare. Wicketkeepers are usually batting at no.6 or 7 already, so promoting them up offers limited tactical gain. Recognised batters are protected by sending pure tail-enders up.

Does the night watchman tactic exist in white-ball cricket? No. The role is exclusive to Test cricket because it depends on the day-end clock. In ODI and T20 cricket, every over counts equally, so there is no advantage to losing a tail-end wicket to save a top-order one.

---

The night watchman lives at the strange intersection of cricket strategy and theatre. It is, statistically, a coin-flip tactic — but the moments when it works are unforgettable. Jason Gillespie's 201 not out is, in its way, more memorable than half the centuries of his actual top-order. Tactics this peculiar tend to outlast their critics.