by The follow-on rule allows the side that batted first to make its opponent bat again immediately after their first innings, rather than returning to bat itself. In a five-day Test, that option becomes available when the first side holds a lead of at least 200 runs. It is designed to save time and improve the leading team’s chance of forcing a result, but it remains a captain’s choice rather than an automatic consequence of a large lead.
What the follow-on changes in a match
In an ordinary two-innings match, the batting order is straightforward: Team A bats, Team B replies, Team A bats again, and Team B has the final innings if required. A follow-on changes that sequence. Once Team B has completed its first innings well behind, it is asked to begin its second innings immediately. Team A’s second innings is delayed and may not be needed at all.
This rule applies only to formats in which both teams are scheduled to bat twice, including Test cricket and other multi-day first-class matches. It does not apply to one-innings formats such as ODIs and T20s. The central purpose is practical: if a match has lost time or is moving slowly, making the trailing team bat again can give the leading side more time to take the remaining wickets.
The following-on side has a difficult task, but its position is not hopeless. It must first erase the deficit from the first innings. Any runs beyond that point create a target for the side that enforced the follow-on. If the trailing team is dismissed before reaching the first-innings total, the game ends in an innings victory.
The 200-run margin in Test cricket
Law 14 sets the minimum lead required before a captain can enforce the follow-on. In a match scheduled for five days or more, including a Test, the team batting first needs a lead of at least 200 runs after the opposition’s first innings. A lead of 199 is not enough; a lead of exactly 200 gives the captain the option.
The requirement depends on the scheduled length of the match, not simply on the standard of cricket being played. The shorter the match, the lower the margin needed to enforce the follow-on. That recognises that there is less playing time available to complete four innings.
| Scheduled match length | Minimum first-innings lead |
| Five days or more | 200 runs |
| Three or four days | 150 runs |
| Two days | 100 runs |
| One day, two-innings match | 75 runs |
Only the side that batted first can enforce the follow-on. A team that bats second cannot use the rule, even if it finishes the first innings with a substantial lead. Equally important, the captain is never compelled to enforce it. Reaching the required margin creates an option, not an obligation.
If the start of a match is delayed by one or more full days, the lead required may be reduced to reflect the shorter match duration. However, a match shortened after it has already begun does not automatically alter the margin. These details matter in rain-affected multi-day matches, where the captain must balance the scoreline against the time still available.
A simple scorecard example
Consider a five-day match in which Team A makes 500 and Team B replies with 264. Team A’s lead is 236 runs, which exceeds the 200-run threshold. Its captain can therefore require Team B to follow on.
If the follow-on is enforced, the scorecard sequence becomes Team A 500, followed by Team B 264 and then Team B’s second innings. If Team B reaches 118/3 in that second innings, it is still 118 runs behind overall. It needs another 118 runs merely to bring the scores level; only runs after that would put Team A behind.
Scorecards commonly mark this second innings with “(f/o)”, indicating that it was played under the follow-on. Readers tracking these situations can use TheCricScope to follow cricket terms and match context alongside the score. The key calculation remains the same throughout: first remove the initial deficit, then build a lead.
Why a captain might enforce it
Time is the strongest argument for enforcing the follow-on. A captain with a large first-innings lead may feel that batting again would use up valuable overs and increase the chance of a draw. By immediately sending the opposition back in, the captain gives the bowlers a second opportunity to dismiss them while enough time remains to complete the match.
There is also a psychological element. A side bowled out for a low score has to return to the crease without the reset that comes from bowling and resting between innings. The leading bowlers may have momentum, while the batting side must quickly find a way to repair a major deficit. If bad weather is expected later in the match, pressing for wickets immediately can be especially attractive.
Pitch conditions can further influence the call. In some matches, bowlers may expect the surface to become harder to bat on as the game progresses. Enforcing the follow-on can mean making the weaker side bat under pressure before it has a chance to regroup. The prospect of an innings victory may also appeal when the deficit is particularly large.
Why captains sometimes decline the option
The main case against enforcement is bowler fatigue. A bowling attack that has just spent a long innings in the field may be asked to bowl again immediately. Fast bowlers in particular can be affected by a heavy workload, and a tired attack can make it difficult to take the ten wickets needed for victory.
Declining the follow-on also allows the leading team to bat again, extend its advantage and consume more time. That approach can reduce the risk of an unlikely defeat. It may lead to a draw more often than an aggressive declaration-and-bowl strategy, but it can be sensible when a captain considers the match situation, player workloads and the broader needs of a series.
Batting last can be another concern. If a pitch is expected to deteriorate, a captain may prefer to set a large fourth-innings target rather than risk chasing a smaller one on an increasingly difficult surface. In 2017, India had the right to enforce the follow-on in the First Test against Sri Lanka but declined and later won by 304 runs.
Famous follow-on matches
India’s victory over Australia at Eden Gardens in 2001 remains one of the defining examples of a team overcoming the follow-on. Australia made 445 before restricting India to 171 and enforcing the follow-on. India then declared at 657/7, built around V. V. S. Laxman’s 281 and Rahul Dravid’s 180, leaving Australia a target of 384.
Australia collapsed to 212 in its second innings, and India won by 171 runs. Harbhajan Singh took 6 for 73 in that innings after taking 7 for 123 in Australia’s first innings. The match demonstrated why a captain’s decision, even when fully justified by the score, can carry a small but memorable risk.
Headingley in 1981 produced another celebrated recovery. Australia made 401 and bowled England out for 174 before enforcing the follow-on. Ian Botham then made 149 not out as England established a lead, and Bob Willis took 8 for 43 when Australia were dismissed for 111. England won by 18 runs.
New Zealand’s one-run victory over England at Wellington in 2023 added a modern example. England declared at 435/8, New Zealand were bowled out for 209, and England enforced the follow-on. New Zealand then made 483, with Kane Williamson scoring 132, before England fell short of a target of 258 by one run.
Conclusion
The cricket follow-on rule is simple in principle: a 200-run lead in a Test gives the team batting first the choice to make the opposition bat again. Yet the decision is rarely simple. Time, weather, pitch behaviour, bowling workloads and the possibility of an extraordinary comeback all shape one of cricket’s most significant captaincy calls.
