The Follow-On Rule Explained: When Captains Enforce It and When It Backfires

Few decisions in Test cricket are as quietly dramatic as the one a captain makes when the opposition has been bowled out well short of his own first-innings total. Enforce the follow-on and the other side must bat again immediately; decline it and your own team bats a second time. It sounds like an easy call. History says it is not.

What the Law says

The follow-on is covered by Law 14 of the Laws of Cricket. It applies only where each side normally bats twice, which means first-class and Test cricket. The lead the first-batting side needs depends on the length of the match: 200 runs in a match of five days or more, 150 runs in a match of three or four days, 100 runs in a two-day match and 75 runs in a one-day match. If full days are lost before the start, the required lead falls accordingly; if a match is shortened after it has begun, the required lead does not change.

Only the side that batted first may enforce it, and even then it is an option, not an obligation. If the side batting second has scored more than the first, no follow-on is possible however the match has gone. The World Test Championship final has its own adjustment: the 200-run requirement drops to 150 only if no play takes place on the first and second scheduled days.

Why captains often say no

On paper, enforcing the follow-on is attractive. The opposition is under pressure, the bowlers keep their rhythm and the match can end quickly. In practice the captain weighs the scores, the relative strength of the two sides, the weather, the state of the pitch and the time that remains, and several of those point the other way.

The first is workload. A bowling attack that has just dismissed a side now has to do it again without a rest, and in a five-day Test that matters. The second is the pitch: if it is deteriorating, batting last on it can be harder than bowling on it, which is why some captains would rather bat again, extend the lead and make the opposition chase a large total in the fourth innings. The third is the weather, because a delayed or shortened day changes how much time is available to bowl a side out twice.

Headingley 1981: the lesson in risk

In 1981 at Headingley, Australia made 401 and bowled England out for 174, enforcing the follow-on. Ian Botham then scored 149 not out in England's second innings to give them a lead of 129, and Australia were bowled out for 111 in their second innings. England had followed on and won.

Kolkata 2001: the same story, a different continent

At Eden Gardens in Kolkata in 2001, Australia scored 445 and India replied with 171, so Australia enforced the follow-on. V.V.S. Laxman made 281 and Rahul Dravid 180 in India's second innings, and India declared on 657 for 7, a lead of 383. Australia were all out for 212 and India won by 171 runs. Both matches are famous because they are rare, and because the team that followed on turned the decision against the captain who made it.

What to look for when you are watching

When a side is bowled out far behind, watch three things before the captain walks out to decide. How tired do the bowlers look? What is the pitch doing, and is the ball turning, cracking or staying low? How much time is left, and what is the forecast? If the answers are favourable the follow-on can win a Test quickly; if they are not, a captain who declines it is not being timid, he is protecting a winning position.

That is why the follow-on remains one of the most debated calls in the game. It is a choice between pressure and risk, and the numbers on the scoreboard are only part of it.