Follow-On Rules in Cricket: When Can a Team Be Asked to Bat Again?
Share this article
The follow-on is one of cricket's most dramatic rules — a provision that allows the fielding side, after building a large first-innings lead, to immediately send the opposition back in to bat again rather than taking their own second innings. When enforced, it creates the possibility of a team losing a Test match without the fielding side ever having to bat a second time. When declined — as it famously was in Kolkata in 2001 — it can produce the greatest comebacks in cricket history.
This complete guide explains everything about the follow-on: the exact lead required, when and why captains enforce or decline it, why it does not exist in limited-overs cricket, and the matches that have defined how we think about this unique rule.
What is the Follow-On?
The follow-on is a provision in the Laws of Cricket that allows the team batting first in a Test match to compel the opposition to bat again immediately after completing their first innings — rather than allowing them to field while the leading team takes its second innings in the normal batting order.
In a standard Test match, the batting order is: Team A bats (1st innings) → Team B bats (1st innings) → Team A bats (2nd innings) → Team B bats (2nd innings). The follow-on disrupts this order: if Team A has a large enough lead after both first innings, they can send Team B back in for their second innings immediately — Team A skips their second innings for now. The order becomes: Team A bats (1st innings) → Team B bats (1st innings) → Team B bats (2nd innings) → Team A bats (2nd innings, if needed at all).
The follow-on's practical consequence: if Team B cannot score enough in their enforced second innings to avoid defeat, Team A wins without needing to bat a second time at all. This collapses a five-day Test match into a much shorter conclusion, which is the fielding team's goal when enforcing the follow-on.
The follow-on is governed by Law 14 of the MCC Laws of Cricket.
How Large Must the First-Innings Lead Be?
The lead required to enforce the follow-on is fixed by law and varies depending on the scheduled length of the match:
| Match type | Lead required to enforce follow-on |
|---|---|
| Five-day match (Test) | 200 runs |
| Three or four-day match | 150 runs |
| Two-day match | 100 runs |
| One-day match | 75 runs |
In the overwhelming majority of follow-on discussions, we are talking about five-day Test matches, where the threshold is 200 runs.
This means: if Team A bats first and scores 450, and Team B is all out for 220, Team A has a first-innings lead of 230 runs. Since 230 exceeds the 200-run threshold, Team A's captain may enforce the follow-on and ask Team B to bat again immediately.
The captain does not have to enforce it — it is entirely optional. But the option is available the moment the lead reaches 200 runs.
The lead is calculated at the moment Team B's first innings concludes — when the 10th wicket falls. If at that exact moment the lead has exceeded 200 runs, the follow-on option is available.
When Can a Captain Enforce the Follow-On?
The captain of the side that batted first — the side with the lead — can enforce the follow-on as soon as the opposition's first innings is completed and the lead exceeds the relevant threshold.
The captain must communicate the decision to enforce the follow-on to the on-field umpires promptly after the opposition's first innings ends. There is no formal time limit specified in the Laws for this communication, but the convention is that the decision is announced immediately — within the over interval or drinks break between innings.
Once announced, the follow-on is confirmed and the opposition must bat again. The captain cannot change their mind after announcing the follow-on.
Can a Captain Decline to Enforce It?
Yes, absolutely. Declining to enforce the follow-on — when the option is available — is completely legal and, at times, tactically very wise. If the leading team's captain declines the follow-on, normal batting order resumes: the leading team takes their own second innings before the opposition bats for the second time.
Declining the follow-on means accepting a slower path to victory. The leading team will bat, potentially adding to their lead further, before the opposition needs to bat again. If the opposition was well beaten in the first innings, this delayed follow-on still typically leads to a comfortable win — just over a longer timeframe.
Why would a captain decline an advantage like the follow-on? The answer lies in the tactical complexities of Test cricket, covered in the next section.
Why Would a Captain Not Enforce?
Declining to enforce the follow-on, despite having a 200-run lead and the legal right to enforce it, is a more common tactical choice than many fans realise. The reasons:
1. Bowler fatigue: If the fielding team's bowlers have just completed a very long first-innings spell — for instance, bowling out a team that batted for 130 overs — their fast bowlers may be exhausted. Sending the opposition back in immediately means those same tired bowlers must bowl again right away, potentially for another 80-100 overs. A captain may prefer to bat, rest the bowlers, add more runs to the lead, and then attack a refreshed but now massively daunted opposition.
2. Pitch deterioration: Test pitches typically worsen as the match progresses. Day four and five pitches often crack, crumble, and offer significantly more turn and uneven bounce than day one and two pitches. A captain who declines the follow-on may be strategically planning to bat again on day three (easier pitch conditions) and then bowl the opposition out on day four and five when the pitch is at its most difficult for batting.
3. Weather protection: If rain is forecast, a captain might decline the follow-on to ensure their team bats again and consolidates a safe lead before rain can interrupt and prevent a result.
4. Psychological reset concerns: Some captains feel that asking the opposition to follow on too soon can galvanise them — give them a "backs against the wall" mentality that produces exceptional resistance. By batting again and building an even larger lead, the fielding captain makes the required fourth-innings target even more daunting, potentially breaking the opposition's spirit more completely.
5. Conditions that favour batting: In flat conditions with a hard pitch and no movement, a rested batting side on day three may find batting easier than struggling bowlers would find taking 10 wickets. The captain may prefer to control the session by batting rather than risking wickets falling cheaply due to tired bowlers in unhelpful conditions.
The Follow-On in ODIs and T20s (It Does Not Exist)
The follow-on does not exist in One-Day International cricket or T20 cricket. It is exclusively a Test match rule.
This is because limited-overs cricket has a fixed structure: each team faces a set number of overs (50 in ODIs, 20 in T20s) per innings, and both teams bat once. There is no concept of a team batting twice. The match consists of two innings total — one per side — and the result is determined by which team scores more runs in their single innings.
The follow-on rule only has meaning in a match format where innings are defined by the fall of wickets rather than a fixed over count, and where batting twice is a standard part of the game. Test cricket is the only format that meets both conditions.
Some analysts have suggested that a follow-on concept could theoretically be applied in first-class cricket (four-day county or state cricket) — and indeed, county championship matches do use the follow-on under the same Laws that apply to Tests. But in any format where both teams bat only once by design, the follow-on has no application.
Famous Follow-On Matches (Kolkata 2001 — Laxman and Dravid)
The most celebrated follow-on match in cricket history — arguably one of the greatest Test matches ever played — occurred in Kolkata in March 2001, during India's second Test against Australia in a three-match series.
The context: Australia, led by Steve Waugh, had won the first Test convincingly and arrived in Kolkata with a 16-Test unbeaten run — the longest in cricket history. Australia batted first and scored 445. India were bowled out for 171, giving Australia a first-innings lead of 274 runs — well beyond the 200-run follow-on threshold.
The follow-on enforced: Steve Waugh enforced the follow-on. India batted again, still needing 274 runs just to avoid an innings defeat.
The comeback: VVS Laxman, batting at number three rather than his usual position, and Rahul Dravid came together in India's second innings. Laxman scored 281 — the highest score in the match — and Dravid scored 180. Together they added 376 runs for the fifth wicket. India declared at 657/7, setting Australia a target of 384 to win.
The result: India bowled Australia out for 212, winning by 171 runs. A team that had followed on 274 runs behind had won the match. Australia's world-record unbeaten run ended. The series was tied, and India went on to win it.
The Kolkata Test remains the defining example of why enforcing the follow-on is not always the right decision — not because Waugh made an error (he had every reason to enforce it at the time) but because it illustrates the extraordinary range of outcomes cricket can produce.
Other famous follow-on matches:
- England vs Australia — 1894-95 Sydney Test: Australia, enforcing the follow-on, became one of the first famous victims of a follow-on reversal. England won after being asked to follow on.
- Bangladesh vs India — Mirpur 2007: Bangladesh famously dismissed India for their second innings cheaply after India were forced to follow on, contributing to one of cricket's greatest upsets.
Is the Follow-On Rule Still Relevant?
The follow-on rule remains fully part of Test cricket's Laws and ICC playing conditions. It is enforced regularly — every season of international Test cricket produces follow-on situations, though the actual enforcement varies significantly by match circumstances.
Whether the rule is "still relevant" in the modern era is a genuine debate:
Arguments that it remains highly relevant:
- The follow-on is still a realistic match-winning tool, particularly for dominant teams bowling on helpful pitches
- It creates match tension and dramatic narrative that fans value
- It reflects the multi-innings structure that makes Test cricket unique
Arguments that it is used less than it once was:
- Modern international teams are far more physically conditioned and bounce back from first-innings deficits more readily than in earlier eras
- T20 and franchise cricket has produced a generation of aggressive lower-order batsmen who can dramatically reduce a first-innings deficit
- Captains have become more cautious about bowling fatigue, making the follow-on less automatic at even large leads
- The pitch preparation era of the 1980s-2000s — when pitches deteriorated dramatically between day two and day five — has partially given way to more closely monitored pitch conditions
Despite these shifts, the follow-on remains a powerful tool in the right conditions. In England, where pitches can change dramatically with swing and seam movement, or in the subcontinent, where pitches turn sharply by day four and five, the follow-on enforced on a large lead remains as potent as ever.
Quick Reference Table
| Rule | Detail |
|---|---|
| Lead required (five-day Test) | 200 runs |
| Lead required (three/four-day) | 150 runs |
| Lead required (two-day) | 100 runs |
| Lead required (one-day match) | 75 runs |
| Who can enforce follow-on? | Captain of the team with the lead |
| Is follow-on mandatory? | No — captain's choice |
| Can follow-on decision be reversed? | No — once announced, it stands |
| Does follow-on exist in ODIs? | No |
| Does follow-on exist in T20s? | No |
| Does follow-on apply in county cricket? | Yes (four-day matches, 150-run threshold) |
| Governing law | MCC Law 14 |
Frequently Asked Questions
Has a team ever won after following on in a Test match? Yes, it has happened, and the Kolkata 2001 Test is the most famous example. There are other historical cases — England won at Sydney in 1894-95 after following on, and there are other instances spread through cricket history. The follow-on reversal is rare enough to be extraordinary when it happens, which is why each case is so celebrated.
Can a team follow on in the same innings more than once? No. The follow-on applies once per match — the team that followed on bats their second innings. There is no provision for a team to be made to follow on a second time. After both sides have completed two innings each (in any order), the match result is calculated normally.
What if the team that followed on reaches 200 ahead before losing their second innings? If the team that followed on bats second and sets the opposition a target (i.e., the match goes to a fourth-innings chase), the match proceeds normally from that point. The fact that they followed on is irrelevant to the fourth innings — the opposition must now chase whatever target has been set.
Can the batting team request a follow-on of themselves? No. The follow-on is entirely the choice of the side with the lead. The batting team cannot invite a follow-on of themselves. If the fielding captain declines to enforce the follow-on, the leading team must take their own second innings.
Does the follow-on rule apply if the first innings is affected by rain? Yes. The follow-on threshold is calculated on the actual first-innings scores, regardless of whether rain affected the match. If the first team scored 350 and the second team were bowled out for 140 despite rain affecting the match, the lead is 210 and the follow-on is available. Rain does not alter the follow-on calculation.
The follow-on rule is a fundamental part of what makes Test cricket different from every other form of cricket and from almost every other sport. It creates a specific type of pressure — the dread of batting twice against a superior bowling attack on a deteriorating pitch — that has no equivalent in limited-overs cricket. Understanding when and why captains choose to enforce or decline it is essential context for following the rhythm and tactics of Test cricket at its most complex.
For more in the series, visit /category/cricket-rules.
Sources:
Share this article
Rahul Sharma
Expert in: Cricket RulesRahul Sharma has played district-level cricket in Mumbai for 8 years and has personally tested more than 50 bats, pads, gloves, and helmets across different price ranges. He joined CricJosh to help Indian club cricketers make smarter equipment choices without overpaying. His reviews are based on real match and net session use, not sponsored samples.
Why trust this review: Rahul has used every product in this review across multiple match and net sessions before writing a word. He buys equipment at retail price and accepts no free samples.
Related Articles
13 min read · 24 March 2026
13 min read · 24 March 2026
14 min read · 24 March 2026
13 min read · 24 March 2026