Setting a Target: How Batting Teams Decide When to Declare or Accelerate
How batting teams set and calculate winning targets across formats — the logic behind Test declarations, the acceleration phase in ODI second innings, the T20 benchmark scores that constitute a 'good' target, how a first-innings lead translates to a declaration target, and the DLS context that affects limited-overs target revision. What factors a captain weighs when deciding whether to declare in Tests or how hard to push in the final overs of a limited-overs innings.
Test Declarations: Setting an Achievable Impossible
A Test match declaration is one of cricket's most complex tactical decisions. The captain must balance two competing needs: set a target large enough that the opposition cannot realistically score it in the remaining time, while also having enough time remaining to bowl the opposition out. A declaration that leaves the opposition with 150 overs to score 350 runs on a good pitch is dangerous — the chasing team may do it. A declaration leaving 60 overs to score 400 runs on a deteriorating pitch is safer but risks a draw if wickets don't fall. The optimal declaration considers: pitch condition (how much it's deteriorating), weather forecast (rain reduces bowling time), opposition batting depth (can they bat 10 wickets out for 60 overs on a bad pitch?), and the run-rate required (is 4 per over realistic on this surface?).
The Second Innings Lead Calculation
When a team leads on first innings in Tests, their second-innings runs add to that lead to create the target. If Team A scored 350 and Team B scored 250 (a 100-run lead for A), and Team A scores 200 in their second innings, Team B needs 301 runs to win (100 + 200 + 1). Captains calculating when to declare track the 'overall lead' in real time — they're setting the target the opposition must chase, not just selecting a second-innings total. The historic rule of thumb for Test declarations: on day 5 of a 5-day Test with deteriorating pitch conditions, 280-320 runs in 65-70 overs is considered a 'competitive declaration' — enough to be challenging but not unachievable, creating genuine match tension.
ODI and T20 Benchmark Scores
In ODIs, a batting team that bats first tries to set a target large enough to be genuinely challenging. Historical win rates by target bracket: Teams posting 250-275 in ODIs win approximately 55% of the time; teams posting 300-320 win approximately 65% of the time; teams posting 330+ win approximately 70-75% of the time. In T20Is, the equivalent benchmarks: 150-160 wins approximately 55% of the time (borderline competitive); 170-180 wins approximately 65%; 190+ wins approximately 70%. These are historical averages and vary significantly by pitch condition, venue, and opposition bowling strength. The 'par score' concept — what a batting team 'should' score on a given surface — is used by commentators and analysts to contextualise whether a posting is above or below conditions-adjusted expectation.
Frequently asked questions
What is a 'par score' and how is it calculated?
A par score is the estimated total a batting team should score given the match conditions (pitch, weather, ground dimensions, opposition bowling). Par scores are used in two contexts: as a planning benchmark for batting teams setting targets, and in revised DLS targets after weather interruptions. Analysts calculate par scores using historical data from similar conditions — a flat batting pitch at a small venue in dry weather might have a par score of 170 in T20, while a green pitch at a large venue in overcast conditions might have a par score of 140. Par scores are not official statistics but are widely used in broadcast analysis. The DLS method uses mathematically derived par scores specific to overs remaining and wickets lost, creating a formal definition of what 'par' represents at any point in a rain-affected innings.
How does a team decide whether to bat conservatively or accelerate in the final overs?
The decision to accelerate vs conserve in ODI batting depends on the pitch state and wickets in hand. A team with 5 wickets remaining after 40 overs and 180 on the board has the luxury to attack: they can send wickets to accelerate in the final 10 overs, knowing they still have depth. A team with 7 wickets down after 40 overs and 180 on the board must be more conservative — losing another wicket exposes tail-enders who cannot score quickly, meaning the final 10 overs might yield only 50-60 runs. The fundamental principle: wickets in hand buy acceleration options. A batsman on 80 who has been in for 90 balls with 5 overs to go has a strong case to attack; one who arrived at the crease 10 balls ago with 5 overs remaining should play conservatively first.
What factors influence whether a Test match ends in a win vs a draw?
Test match outcomes are determined by three interacting factors: runs available (how large a target), time available (how many overs remain), and pitch conditions (how difficult batting has become). A large target with many overs on a flat pitch favours the chasing team. A modest target with few overs on a disintegrating fifth-day pitch favours the bowling team. The classic 'impossible chase that succeeds' scenario (e.g. Headingley 1981, Edgbaston 2005) occurs when the chasing team's batting is of sufficient quality to overcome a combination of difficult conditions, moderate time pressure, and a target that is theoretically beyond what the conditions 'should' allow. Such outcomes become famous precisely because they exceed what probability and conditions predicted.