Follow-On and Declaration in Test Cricket Explained
Updated: 31 October 2026 · Author: Cricket Match Scorecard Editorial
A Test match has no over limit, but it does have a clock. Two rules, the follow-on and the declaration, exist largely because of that clock. They let a captain try to win before time runs out, and they are behind some of the most dramatic decisions in the game.
What is a declaration?
A captain can end their team's innings at any time, even with wickets in hand. A score such as 450/7d shows that the side declared on 450 for 7.
The reason is that a Test win usually requires taking all 20 of the opposition's wickets. If a team bats too long, it may not leave enough time, and the match ends in a draw. So declaring is a trade: give up the chance of more runs in return for more time to bowl.
A typical declaration decision
Suppose it is the morning of day five, and your team leads by 350 with 90 overs left in the match. Bat on for another 15 overs and you could add 80 more, leaving the opposition needing about 430, an almost impossible chase, but with only 75 overs to bowl them out. Declare now, and you have more time, but more chance of defeat. There is no formula, which is what makes it fascinating.
What is the follow-on?
If the team batting second finishes its first innings a long way behind, the side that batted first can make it bat again straight away. The trailing team then has its second innings immediately after its first.
Under the Laws of Cricket (Law 14), the first-innings lead required depends on the scheduled length of the match:
| Match length | Lead needed |
|---|---|
| 5 days or more | 200 runs |
| 3 or 4 days | 150 runs |
| 2 days | 100 runs |
| 1 day | 75 runs |
Worked example
In a five-day Test, Team A makes 480. Team B must reach 281 to avoid the follow-on, because at 280 it would trail by exactly 200 and the lead would be enough. This is why commentators keep track of "the follow-on target", and why the crowd will cheer a tail-end single that gets a team past it.
It is a choice, not a requirement
A captain does not have to enforce the follow-on, and in recent decades, many have opted not to. There are good reasons:
- Tired bowlers. The fielding side has just bowled a full innings and would have to go straight back out.
- The fourth-innings risk. Batting last on a worn pitch is often the hardest job in Test cricket. If you enforce the follow-on and the opposition posts a big score, you may have to chase on a crumbling pitch.
- Time. If plenty of time remains, a captain can bat again, build the lead and then declare.
On the other hand, if rain has cost time or the pitch is still good for bowling, enforcing may offer the best chance to win.
The most famous follow-on in Indian cricket
In March 2001 in Kolkata, Australia enforced the follow-on against India, having led by 274. VVS Laxman made 281 and Rahul Dravid 180 in a huge partnership in the second innings, and Harbhajan Singh's bowling then helped India win by 171 runs. It remains one of the rare occasions a team has won a Test after following on, and is the best advert for why captains now think twice.
How to read this on a scorecard
A score written 312 & 245/6d shows two innings, with the second declared. "f/o" beside a team's second innings shows it followed on. Our guide to Test, ODI and T20 cricket covers how a Test is structured, and this one shows how to read the numbers.