Explainer
Follow on rule cricket: the 200-run margin explained
What Law 14 says about the follow-on, how the margin changes with match length, the four sides that won after following on, and why captains now decline it.
By CricketTaken EditorialPublished Explainer18 min read
The tenth wicket falls, the fielding side gathers in a loose circle, and the crowd waits for a signal that used to be automatic. For most of Test cricket's history a lead of two hundred and fifty meant the beaten side turned round and went straight back out. Now, more often than not, it means the captain has a conversation with his bowlers and the openers who have just taken their pads off go and put them back on again.
The follow on rule in cricket is a single clause of Law 14 with a single number at its centre. In a two-innings match scheduled for five days or more, the side batting first that leads by at least 200 runs may require the other side to bat again immediately. Nothing about it is compulsory, nothing about it is automatic, and the interesting part of the modern game is not the arithmetic but the fact that captains keep saying no.
The number is 200, and it only applies to the longest matches
Law 14.1 sets four figures, and which one applies depends entirely on how many days the match was scheduled to last.
For a match of five days or more, which in practice means a Test, the required lead is 200 runs. For a match of three or four days, the standard length of first-class cricket in almost every country, it drops to 150. A two-day match uses 100 and a one-day two-innings match uses 75. The pattern is deliberate: the shorter the match, the smaller the advantage a side needs before it is allowed to compress the remaining time.
Two things about that figure surprise people. The first is that it is a floor rather than a target, so a lead of 199 leaves the captain with no option at all while a lead of 201 hands him the full choice. The second is that a captain with a lead of six hundred has exactly the same right as a captain with a lead of two hundred and one. The Law does not scale the entitlement with the size of the advantage.
Note also what the number is not. It is not a measure of dominance, it is not adjusted for the pitch, and it takes no account of how long the first innings took. A side that scored 500 in a day and a half and bowled the opposition out for 290 has the option. A side that ground out 320 across two days and dismissed its opponents for 118 also has it, despite having far less match left to work with.
What Law 14 says beyond the number
The rest of the Law is administrative, and each piece removes an argument that would otherwise happen.
Law 14.2 requires the captain to notify the opposing captain and the umpires of his intention to take up the option, and states that once notified the decision cannot be changed. There is no cooling-off period. A captain who announces the follow-on and then sees the clouds break has committed his side to the arrangement he chose.
Law 14.3 handles a lost first day, and it is the clause almost nobody knows. If no play takes place on the opening day of a match of more than one day, the margins in 14.1 apply according to the number of days remaining from the actual start of play. A five-day Test that loses its first day to weather becomes, for this purpose, a match of four days, and the required lead falls from 200 to 150. The day on which play begins counts as a full day however late it starts, and play is treated as having begun once the first over starts after the call of Play.
That clause matters more than its obscurity suggests. Washed-out opening days are common, the reduced margin genuinely brings the option into range in matches where it otherwise would not be, and a captain in a rain-shortened Test is the captain most likely to want it, because he needs to save every hour he can.
- 200Runs of lead required in a Test
- 150Runs required if the first day is lost
- 4Tests won by a side that followed on
- 0Times a captain may reverse the decision
Figures from Law 14 and from published scorecards. The count of comeback wins covers Test cricket only.
The lead is a first-innings comparison and nothing else
A surprising amount of confusion around the follow-on comes from people calculating the wrong lead.
The figure that matters is the difference between the two first-innings totals, full stop. Nothing else enters it. Not the state of the match, not runs scored since, not any adjustment for wickets in hand, and certainly not any notion of who is on top. The comparison is made once, at the moment the second side's first innings ends, and it either clears the threshold or it does not.
This produces a specific and quite common situation. A side is bowled out cheaply, follows on, bats far better second time round and takes the lead. The follow-on has not been undone and cannot be. The side that enforced it will still bat last if a fourth innings is required, and the sequence of the match remains as the enforcing captain arranged it. Whatever happens afterwards, the ordering of the innings is fixed.
It also means a captain cannot enforce the follow-on after his own second innings, or after a declaration in it. The option exists at exactly one moment, and if he lets it pass by starting his own second innings, it is gone. He does not need to announce a refusal; sending his openers out is the refusal.
What enforcing the follow-on is meant to buy
The purpose of the Law, when it was written, was to stop matches being wasted. A side that is two hundred behind is unlikely to win, and requiring the leading side to bat again before the beaten side could be dismissed twice would burn hours the match might not have.
Enforcing buys three things. The first is time, which is the original justification and remains the strongest one. Instead of an innings of its own, the leading side goes straight to work on the twenty wickets it needs, and depending on how long its opponents survive it may save the best part of a day.
The second is momentum, in the narrow and defensible sense. A batting order that has just been dismissed cheaply has to walk back out with the same bowlers running in, the same footmarks, the same ball behaviour and no interval in which to reset. Bowlers who are in rhythm keep bowling. This is a real effect, even if it is impossible to size.
The third is a guarantee about the ball. A side following on begins its second innings against a ball that is already somewhat used, but the enforcing captain knows exactly how old it is and can plan the availability of the next new one around it. The relationship between ball age and what a bowling attack can do is set out in the piece on when to take the second new ball, and it is one of the quieter inputs into the decision.
- The second side's first innings endsThe lead is now fixed. It is the difference between the two first-innings totals and no later event will change it.
- The margin is checked against the scheduled match lengthFive days or more requires 200 runs, three or four days requires 150, and a match that lost its opening day is judged on the days remaining from the actual start.
- The captain decides, usually with his bowlersNothing in the Law obliges him to enforce and nothing penalises him for declining. If he simply sends his own openers out, the option lapses without any announcement.
- He notifies the opposing captain and the umpiresThis is the formal act. Until it happens the follow-on has not been enforced, and after it happens the decision is irrevocable.
- The beaten side bats a second consecutive inningsIts batters have had, at most, the ten-minute interval between innings. Its bowlers get an unexpected rest, which is a cost the enforcing side rarely talks about.
- The enforcing side now bats last, if it bats againIt has traded the certainty of batting third for the chance of not batting again at all, and it will face any fourth innings on the oldest version of the pitch.
The order of events required by Law 14. The captain's deliberation is the only step with any discretion in it.
Four times in a century and a half it has gone wrong
Every argument about the follow-on eventually reaches the same four matches, because in the entire history of Test cricket only four sides have followed on and won.
At Sydney in December 1894, Australia made 586 and dismissed England for 325. England, following on, made 437, and Australia were bowled out for 166 chasing a modest target. England won by 10 runs, the first result of its kind.
At Headingley in July 1981, Australia declared on 401 for 9 and bowled England out for 174, a deficit of 227. England followed on, recovered through a famous unbeaten innings from Ian Botham, and set 130. Bob Willis took eight wickets in the second innings and Australia fell 18 short.
At Eden Gardens in March 2001, Australia made 445 and bowled India out for 171. India followed on, VVS Laxman and Rahul Dravid batted together for the better part of a day, India declared on 657 for 7, and Australia were dismissed chasing 384. India won by 171 runs and ended a long Australian winning run in the process.
At Wellington in February 2023, England declared on 435 for 8 and bowled New Zealand out for 209. New Zealand followed on, made 483, and England were bowled out one run short of a target of 258, with Neil Wagner taking the final wicket.
Four failures in about a hundred and fifty years is, by any reasonable reading, an argument for enforcing rather than against it. The follow-on has been enforced thousands of times and has produced a defeat four times, and two of those four were decided by fewer than twenty runs. What the four matches have instead is memorability, and memorability drives behaviour in a way base rates do not.
The workload argument, which is the one captains say out loud
The reason offered in press conferences is almost always the bowlers, and it is not a smokescreen.
A fast bowler who has just dismissed a side has typically been on the field for a day and a half, in whatever heat the venue provides, and has bowled somewhere between twenty and thirty-five overs. Enforcing the follow-on sends him straight back out with the ten-minute interval as his entire recovery. Declining it gives him at least a session and often a full day off his feet, some of which he will spend sitting with his boots off.
The physiology behind this is genuinely one-sided. Repeated high-intensity bowling loads accumulate rather than reset, and the injuries that end fast bowlers' seasons are stress-related rather than acute. A captain who wrecks his opening bowler in the third innings of a Test has cost himself the fourth innings of that match and possibly the next two Tests of the series.
The counter-argument is usually put badly, so here it is properly. The fatigue is not one-sided at all. A side that has just batted for a day and a half has fielders and bowlers who are equally tired, and enforcing the follow-on hands its bowlers exactly the rest the enforcing captain was worried about giving his own. The question is not whether the enforcing side's attack is tired, it is whether it is more tired than the other side's, and the answer is usually that both are.
There is also a scheduling dimension. In a congested calendar with Tests stacked close together and franchise commitments in between, the workload calculation extends beyond this match, and a captain protecting a bowler for a series is making a defensible decision even if it is the wrong one for the game in front of him.
The pitch argument, which usually decides it
Ask a coach in private and the answer shifts from bodies to surfaces.
A pitch in a five-day Test is at its best on days one and two and at its worst on days four and five. That progression is the whole reason batting last is hard. A captain who enforces the follow-on is choosing to bowl on the good surface and, if the match goes the distance, to bat on the ruined one. A captain who declines takes the reverse: his own side bats third on a surface that is still playable, and the opposition is left with the fourth innings and whatever the pitch has become. The survey of pitch types and how they age covers what actually changes underfoot across five days.
On a subcontinental surface that is already turning on the second afternoon, that calculation is not close. A side batting fourth against good spin on a fourth-day pitch is in genuine trouble at almost any target, so a captain who declines the follow-on and bats for two sessions has converted a strong position into an overwhelming one.
On a flat, unresponsive surface the calculation reverses. If the pitch is not going to deteriorate, batting again buys very little protection and costs a great deal of time, and enforcing is the way to preserve enough overs to take twenty wickets. This is the situation in which modern captains most often get it wrong, because the workload habit has become strong enough to override the specific conditions.
Scoring rates changed, and with them the case for batting again
The strongest structural argument for declining is not about bodies or pitches at all. It is that Test cricket is scored faster than it used to be.
The old objection to batting again was that it wasted time. Setting a lead of four hundred used to take the best part of two sessions, which was often two sessions the match could not spare. A side that scores at four and a half or five an over can build the same lead in a session and a half, and can then declare with more overs remaining than a slower side would have had after enforcing.
That change removes most of the sting from the time argument, and it is the reason the decline in enforcement tracks the rise in scoring rates rather than any change to the Law. It also explains why the sides most willing to decline are the sides that score quickest. A team that bats at two and a half an over does not have this option, because for it batting again really does cost the match.
The comparison of the three international formats sets out how far Test scoring rates have moved, and the shift is large enough to have changed a tactical convention that had held for a century.
What the enforcement rate has actually done
The pattern in the numbers is clear, and it turns on a single match.
Through the twentieth century, enforcement of the follow-on in Tests ran at around eighty-five per cent of eligible cases. Analysis of the decision by the statistician Andrew Samson puts it at roughly sixty-eight per cent across the 2000s and roughly forty-six per cent across the 2010s, with the 2020s sitting close to half. The turning point is dated to Kolkata in March 2001, after which the idea that enforcing was the default stopped being taken for granted.
Percentage of eligible cases in Test cricket, rounded to the nearest whole number, from the cited analysis by Andrew Samson. The twentieth-century figure is an average across the era rather than a single decade.
Show the numbers
| Item | Enforced |
|---|---|
| 20th century | 85% |
| 2000s | 68% |
| 2010s | 46% |
| 2020s | 50% |
The same analysis shows the decision is strongly sensitive to the size of the lead. With a lead of 250 or less, enforcement is comparatively rare. With a lead of 300 or more, it becomes much more common again, which suggests captains are not applying a blanket policy so much as a threshold well above the one the Law sets. In practice the working margin for a modern Test captain is nearer three hundred than two hundred.
That is a rational response to an asymmetric risk. Declining costs a probability of a win that the captain can partly recover by declaring aggressively later. Enforcing exposes him to the one outcome that will follow him around for the rest of his career, and to a bowling injury that will follow his team around for the rest of the series.
The follow-on below Test level, where the maths is tighter
In four-day first-class cricket the required lead is 150 and the arithmetic runs differently, because the shorter match makes time much more valuable relative to safety.
A county or state side with a lead of 200 on the second evening has roughly two days of playing time left and needs twenty wickets. Declining the follow-on there is a far more expensive choice than it is in a Test, because there is no fifth day to absorb the two sessions of batting. Enforcement rates in four-day cricket have consequently held up better than in Tests, and captains who decline usually do so because of the weather forecast rather than the bowlers.
Bonus points complicate it in leagues that award them. A side that has already collected its available bowling points has one less reason to bat again, while a side short of batting points may prefer a second innings that will not otherwise happen. Those incentives are set out in the guide to the county championship, and they can produce decisions that look eccentric until you know the table.
Where the number came from, and why the option exists at all
The follow-on is one of the oldest provisions in the Laws, and for most of its life it was not a choice.
It entered the Laws in 1835 as a compulsory measure: a side trailing by 100 runs or more in a three-day match had to bat again immediately, and neither captain had any say in it. The purpose was purely practical. Three-day cricket had very little slack in it, and a rule that guaranteed the beaten side batted straight away was a rule that stopped matches expiring unfinished.
The margin was raised to 120 runs in 1894, and in 1900 the Law was rewritten into something close to its present shape. The follow-on became optional, and the required lead went up to 150 runs in a three-day match with 100 for two days and 75 for one. The reasoning recorded at the time is the same reasoning captains give now: a side whose bowlers were spent gained nothing from being forced to bowl again, and compelling it to do so occasionally handed the advantage to the side that had played worse.
The four-tier structure that includes the 200-run figure for matches of five days or more arrived in 1980, when Test cricket had settled at five days and first-class cricket at three or four. That structure is what Law 14.1 still contains.
Two things follow from that history. The first is that the option was created precisely because compulsion produced bad cricket, which makes the modern habit of declining an intended use of the Law rather than a distortion of it. The second is that the numbers were fixed for a game that scored far more slowly than today's, and nobody has revisited them since. A lead of 200 in 1980 represented a much larger share of a typical first innings than it does now.
Day-night Tests move the decision again
Pink-ball cricket has added a variable that the Law never anticipated, and it cuts against declining.
In a day-night Test the difficulty of batting is not spread evenly across the day. The pink ball is at its most dangerous under lights in the evening session, when the seam is visible for longer, the ball keeps its hardness, and the light is neither daylight nor full darkness. That hour is worth more to a bowling side than any other hour in the match.
A captain who declines the follow-on has to think about who bats in it. Batting again himself means his own top order occupies part of that session, and it means the opposition's second innings starts at a time of his choosing rather than immediately. Enforcing means his bowlers get the beaten side in that window while they are still reeling. On several pink-ball surfaces this has been enough to override the workload argument, because a session under lights against a hard ball is a shortcut to ten wickets that no amount of pitch deterioration can match.
The reverse consideration also exists. Bowling long spells under lights on consecutive evenings is demanding in its own way, and pink-ball Tests have a habit of finishing early, which means the time saved by enforcing may not have been needed in the first place.
The World Test Championship changed what a draw is worth
For most of Test history a draw was a neutral outcome, and a captain who protected himself against defeat by declining the follow-on gave up little that anyone was counting.
The championship structure changed that arithmetic by putting a points value on results and ranking sides by the percentage of available points they take. A draw is now a measurable loss of ground rather than an honourable non-event, and the points system and how it is calculated makes that explicit. Over-rate penalties sharpen it further, since a side that spends an extra session in the field to enforce the follow-on has that much more opportunity to fall behind the required rate.
The effect on the follow-on decision is real but modest. A captain in the middle of a championship cycle has a slightly stronger reason to seek the win and a slightly weaker tolerance for the draw a cautious approach can produce. Against that, the same competition raises the cost of losing a fast bowler for the next two Tests, which pushes in the opposite direction. The honest reading is that the championship has raised the stakes on the decision without settling it.
Six things people get wrong about the follow-on
It is not a penalty. Nothing in Law 14 punishes the side that batted badly. It is a discretionary saving of time offered to the side that batted well, and the beaten side has no say in it.
It does not exist in limited-overs cricket. The Law applies only to matches in which each side is scheduled to bat twice, so no one-day international, T20 or hundred-ball match can produce one.
It does not fix the batting order for the rest of the match. If the side following on takes a lead, the enforcing side bats fourth and chases. Sides that follow on and set a target are unusual but entirely normal in Law.
A captain does not have to announce a refusal. Declining requires no notification at all. Sending his own openers out at the change of innings is a complete and final answer.
The lead is not recalculated later. It is the first-innings difference and it is settled the moment the second first innings ends, whatever the scoreboard does afterwards.
Enforcing is not automatically the aggressive choice. A captain who bats again, scores at five an over for a session and a half and then declares may leave himself more overs to bowl than one who enforced and watched the opposition bat through a day.
Reading the decision the moment the tenth wicket falls
Five things tell you which way a captain is going, and most of them are visible from the boundary.
Check the lead against three hundred, not two hundred. The legal threshold is 200 but the behavioural one is considerably higher. A lead in the two hundreds with a day and a half gone usually means the openers are padding up.
Count how long the fielding side has been out there. A first innings that took a day and a half against one that took four sessions is the difference between an exhausted attack and a fresh one, and it moves the decision more reliably than the lead does.
Look at what the pitch has already started doing. Puffs of dust, uneven bounce and balls gripping in the footmarks all argue for batting again and leaving the fourth innings to the opposition. A surface still true on the third morning argues for enforcing.
Read the forecast the way the captain does. A day of rain due on the fifth removes the fourth-innings safety a declining captain is buying, and pushes him back towards enforcing while there is still time to use the advantage.
Watch which bowler is stretching. If the strike bowler has spent the last twenty minutes with a physiotherapist, the follow-on is not being enforced whatever the lead says.
There is a sixth tell, and it comes from the beaten side rather than the winning one. Watch whether its openers put their pads on during the final wicket of the innings. Dressing rooms prepare for the likely outcome, and a batting side that expects to be sent back out will have someone strapping up before the last man is dismissed. If nobody moves, the coaches have already worked out what the opposing captain is going to do, and they are usually right.
The follow-on has become one of the sharpest tests of whether a captain is thinking about this match or about the series, and reading it correctly means knowing both the fixed number in the Law and the much larger number in his head. The companion piece on when a captain closes his own innings covers the other half of the same problem, and there is a good deal more on rules, tactics and the arguments they start in the cricket archive and across the wider blog.
Common questions
What is the follow-on in cricket?
It is the option given to the side that batted first, when it finishes a long way ahead on first innings, to send the opposition straight back in rather than batting again itself. The opposition then bats two innings in succession. It exists only in matches where each side is scheduled to bat twice.
How big does the lead have to be?
In a match scheduled for five days or more the lead must be at least 200 runs. Shorter matches use smaller figures: 150 runs over three or four days, 100 over two days and 75 in a one-day match. The lead is measured on first innings alone.
Is a captain obliged to enforce the follow-on?
No. Law 14 gives him an option, not a duty, and there is no penalty of any kind for declining it. He must tell the opposing captain and the umpires if he intends to use it, and once he has said so he cannot change his mind.
How many teams have won a Test after following on?
Four. England did it at Sydney in 1894 and at Headingley in 1981, India did it at Kolkata in 2001, and New Zealand did it at Wellington in 2023. That is four times in roughly a century and a half of Test cricket.
Why do modern captains decline the follow-on so often?
The usual reasons are bowler workload, the wish to bat on the better surface and leave the worse one for the fourth innings, and higher scoring rates that make it possible to bat again and still have time to win. Enforcement has fallen from around eighty-five per cent through the twentieth century to roughly half of eligible cases.
What happens if the first day is washed out?
Law 14 recalculates the required lead using the days that actually remain from the start of play. A five-day Test that loses its opening day is treated as a match of three or four days, so the margin drops from 200 runs to 150.
Filed under Cricket·test cricket · laws of cricket · first-class cricket · captaincy · rules