Test Captaincy: Declarations, the Follow-On and Reviews Guide

Batting first is the default in Test cricket, and the AI knows it. The exception is the classic bowl-first call: a genuinely green, seaming surface with morning moisture. The captain reads this match's prepared pitch, not the venue's reputation, so an unusually grassy Lord's tempts a bowl while a flat road is an almost automatic bat. On a typical surface, bat.

When should a captain close the innings? Mined from thousands of real first innings, the answer surprised us: captains bat far longer than intuition suggests. With real batting still possible, genuine declarations cluster around a 510-520 total regardless of era, and even the aggressive quarter still bat past 390. The AI reflects that: it will not declare a strong first innings early just because it has passed 400. Time pressure on days three and four lowers the bar, and an exposed tail lowers it too, because there is little to gain batting the last pair on.

The third-innings declaration is a different calculation: balance a safe lead against the overs left to bowl the other side out. The AI aims to set a target that would be a hard chase rather than a gettable one, holds out for a genuinely safe lead, and gets more willing to pull out on the final day as time runs short. Test captains do not leave gettable targets, and neither does the AI.

The archive shows why captains are cautious when they set a target. Across the Tests in which the side batting last was set a target and the match produced a result, targets under 150 were reached 95.6% of the time and targets of 150 to 199 76% of the time. From 200 to 249 it was close to even, at 50.4%. From 250 to 299 the chasing side won 40.6% of those matches, from 300 to 349 19.3%, and above 350 just 3.2%.

Only four sides have ever scored 400 or more to win a Test: West Indies' 418 against Australia in Antigua in 2003, South Africa's 414 in Perth in 2008, Australia's 404 at Headingley in 1948 and India's 406 in Port of Spain in 1976, chasing 403. A captain who sets 400 with a day to play is, on the record, almost certain not to lose. The risk is not losing but running out of time to win, which is why the real question in a third-innings declaration is how many overs to leave, not how many runs.

Declarations still backfire. At Adelaide in 2006, England declared their first innings at 551 for six and still lost: Australia replied with 513, then bowled England out for 129 on the final day and chased 168 with time to spare. Declaring had not been the mistake; batting with too little intent on the last day was. The most famous generous declaration came from Garry Sobers at Port of Spain in 1968: he set England 215 in less than three hours, England got them, and it was the only result of the series. In real cricket, a declaration is a bet that your bowlers can take ten wickets in the time you have left them, and it is only as good as the attack that has to win it.

When a side is bowled out far enough behind, the fielding captain can send them straight back in. Modern captains enforce it only about half the time it is available, and the AI starts there, then adjusts for the two things that actually drive the call. Time is the big one: late in the match, with the clock the enemy, it enforces far more often to buy an extra innings of bowling. A tired attack pushes the other way, because enforcing means bowling two long innings back to back with no rest. There is a dedicated guide to the follow-on rule itself.

In the modern era each side gets three unsuccessful reviews per innings, and they are a resource to manage, not spend freely. The AI reviews a strong shout readily and a weak one rarely, guards its last review more jealously, and is a little more willing to gamble a fielding review late in the match when it is hunting a result. Because the on-field umpire in the modern era is fallible in both directions, a review is never a guaranteed wicket, and this is a genuine judgement, the same one you make when the prompt comes to you.

Between decisions, the captain also sets the tempo. Chasing, the AI compares the required rate to a gettable clip and shuts up shop for the draw when the target is out of reach, because nobody slogs at a Test target. In the field it crowds the bat when the tail is in or the batting side is blocking for a draw, and sits back to squeeze when defending a small fourth-innings total.

Take the armband yourself in The Follow-On, or study how real captains handled these calls across 150 years in the Test archive.

• MCC Laws of Cricket, Law 15: Declaration and forfeiture; Law 14: The follow-on
• CricArcade Test match archive: 2,537 Tests, 1877 to March 2024
• Figures compiled from the official match scorecards in CricArcade's archive

• The Follow-On Rule, Explained: What the follow-on is, when a captain can enforce it, and how the margin has changed since cricket's first Test in 1877.
• How CricArcade Decides a Single Delivery: Batter, bowler, match situation, conditions: what goes into every delivery in CricArcade, and why the same match state always gives you the same match, verifiably.
• How a Test Pitch Plays: Green tops, dustbowls and roads: 60-plus real venues, per-match pitch preparation, wear over five days, the new ball and the sessions in The Follow-On.
• The Six Eras of Test Cricket: From the three-day Golden Age to the DRS era: six periods of Test cricket, each calibrated to the real match record, and two findings that surprised us.
• Play The Follow-On, or browse every guide.