
The follow-on rule, and why captains stopped enforcing it
Once a lead of 200 runs in a Test used to mean an automatic decision. It doesn't anymore, and the reasoning tells you a lot about modern captaincy.
What the rule actually says
In a Test match, if the side batting first builds a big enough first-innings lead (the threshold depends on match length, and is smaller in a rain-shortened game), it can force the opposition to bat again immediately instead of taking its own turn to bat. The idea is to punish a side that's been badly outplayed by denying it the rest between innings and pressing the advantage while conditions and momentum still favor the leading side.
Why it fell out of favor
Enforcing the follow-on means the leading side has to bowl two long innings back to back with no break in between, on pitches that generally get more helpful for batting as a Test goes on and more taxing on tired bowlers. Several high-profile Tests where a team enforced the follow-on, only for the opposition to bat long enough in their second innings to set a target the leading side then failed to chase, made captains far more cautious about the decision.
The modern default
Most captains now bat again instead, even with a big lead, to rest the bowling attack, extend the overall lead further with the bat, and set a target rather than chase one. Enforcing the follow-on still happens, but it's treated as a situational call — pitch condition, weather forecast, bowler fitness — rather than the near-automatic decision it once was.


