CRICARCADE
Updates
Leaderboard
← Guides / The Follow-On Rule, Explained

The Follow-On Rule, Explained Guide

By · Published · Updated · Sources

The rule the game is named after: what it is, when a captain can use it, and why it's a much rarer sight than it used to be.4 min read

What the follow-on is

In a two-innings match, the team that bats second can be made to bat again immediately, without the side that bowled them out batting in between, if they fall far enough behind on first innings. That's the follow-on: instead of Team A batting, Team B batting, Team A batting again, Team B declaring, it's Team A batting, Team B batting, Team B batting again straight away. It saves the team that's ahead a whole innings of time, which is the entire point in a match with a hard five-day limit.

It is the fielding captain's choice, not automatic. Enforcing it is not always the right call: it can mean bowling two long innings back to back on a wearing pitch, with no rest for your attack in between, and if the follow-on side bats well the pressure flips back onto the team that enforced it.

The margin

The side that bowled first has to be at least a set number of runs ahead to have the option. In a modern five-day Test that margin is 200 runs. Cricket has never used one number for every match length, though: the Laws set smaller margins for shorter first-class games, and in Test cricket's early decades, when matches were often scheduled for three or four days rather than five, the working margin was smaller too, closer to 150.

How often captains enforce it

In the archive, a side has been made to follow on 339 times in 2,537 Tests. The captain who enforced it went on to win 262 of those matches, drew 73 and lost only four. On the numbers alone, enforcing looks almost free: more than three times in four it ends in a win, and a defeat is close to a one-in-a-hundred event.

The trend over time tells a different story. Counting only matches from 1980 onwards, when almost every Test was scheduled for five days and the margin was 200, and only the cases where the side batting second was bowled out at least 200 behind, captains enforced the follow-on in 94% of chances in the 1980s, 88% in the 1990s, 67% in the 2000s, 47% in the 2010s and 44% in the 2020s so far. The option comes up more often than it used to; captains simply take it far less.

The four times it backfired

Only four sides in Test history have lost after enforcing the follow-on, and three of the four matches are among the most famous Tests ever played.

  • Sydney, 1894. Australia made 586 and led by 261, but England followed on, set a target of 177 and bowled Australia out on a pitch that rain had made treacherous. England won by 10 runs.
  • Headingley, 1981. England followed on 227 behind and were still behind with three wickets left when Ian Botham made 149 not out. Set 130, Australia were bowled out by Bob Willis, who took eight wickets. England won by 18 runs.
  • Kolkata, 2001. Australia, on a run of sixteen straight Test wins, led India by 274. VVS Laxman made 281 and Rahul Dravid 180 in a stand that lasted the whole of the fourth day, and Harbhajan Singh bowled Australia out on the fifth. India won by 171 runs.
  • Wellington, 2023. England led New Zealand by 226 and enforced. New Zealand's second innings set 258, and England were bowled out one run short. New Zealand won by 1 run.

Why captains stopped enforcing it

In real cricket, the case against enforcing is mostly about the bowlers. A side that has just bowled the opposition out has usually been in the field for most of a day or more. Enforcing asks the same bowlers to go again at once, on a pitch that is getting harder to bowl on as it flattens or easier to bat on as the ball softens, and it means batting last yourself, on the most worn surface of the match. Batting again instead rests the attack, adds to the lead, and lets the captain choose when to declare, with the target and the time left both under their control.

Kolkata 2001 changed how many captains think about it, and modern workloads, with fast bowlers playing all three formats, have pushed the same way. The draws tell you why they can afford to be cautious: in the archive, 45.9% of Tests in the 1980s were drawn, against 14.4% in the 2020s. Results come faster than they used to, so a side that bats again rarely runs out of time to win.

How The Follow-On models it

The simulator is era-aware here, not just in the modern game. A Test drawn from the 1880s-1930s uses the smaller, period-correct follow-on margin that matched those shorter scheduled matches; a Test from the post-war five-day era uses 200. The AI captain then weighs the same trade-off a real one does, pitch wear, the state of the bowling attack, and how many overs are actually left in the match, when deciding whether to send you back in.

Captain a five-day Test yourself and you'll get the choice from the other side too: bowl a team out cheap enough, and it's your call whether enforcing it is worth the risk.

See it happen

Every follow-on actually enforced in a real Test since 1877 is in the archive, searchable by team, year and venue. Or captain your own: play The Follow-On.

Sources