Rain Reduction in Limited-Overs Cricket: How Shortened Matches Work
Rain interruptions in limited-overs cricket frequently shorten the number of overs available, requiring target recalculation using the DLS method. This article explains how rain reductions work in practice, how the DLS method determines revised targets, and what strategic adjustments batting and fielding teams make when rain reduces a match.
How Rain Reduces a Match
Limited-overs cricket matches (ODIs and T20Is) have a minimum over threshold for a result to be possible — in T20Is, 10 overs per side; in ODIs, 20 overs per side. If rain prevents either team from batting their full allocation, the match may be shortened. Two scenarios: pre-match rain reduction (both teams agree to reduce the match to a set number of overs before play begins — e.g., reducing a 50-over ODI to 35 overs per side); and mid-match rain interruption (rain arrives after the first innings has begun or the first innings is complete, requiring recalculation of the target for the second innings using DLS). The timing of the rain determines which scenario applies and how the DLS calculation is structured.
How DLS Revises Targets
The DLS method (Duckworth-Lewis-Stern) revises targets based on the concept of 'resources' — a combined measure of overs remaining and wickets in hand. A team's resources determine how many runs they can be expected to score from the remaining match. If the second innings is interrupted by rain, the DLS calculation determines what the second team's revised target is — based on how many resources they have remaining versus how many resources the first team had when they scored their total. The key principle: if the first team scored their runs with 10 wickets and 50 overs, and the second team then loses 5 overs to rain after 20 overs, the DLS target reflects the relative resource disadvantage of the reduced second innings. This means the target is not simply a proportional reduction of the first innings score.
Strategic Adjustments for Rain-Affected Matches
Strategic adjustments when rain is likely or confirmed: batting first teams in rain-risk conditions try to front-load scoring (scoring quickly in the early overs to ensure a high total even if the innings is later curtailed); they also try to lose fewer wickets early (because DLS is more favourable to teams that have more wickets remaining when rain arrives). Fielding teams in rain-affected matches may adopt more aggressive field placements (accepting some boundary risk to take wickets — fewer wickets in hand reduces the opposing team's DLS resources). During a mid-innings rain break, the DLS calculation is performed by the match referee and the revised target is presented to both teams before play resumes — the fielding team must know what target they are defending.
Frequently asked questions
What is the 'par score' in a rain-affected match?
The 'par score' is the DLS-calculated total that, at any given point in the second innings, represents the equivalent position to the first team at the same point in their innings. If rain arrives and the match is decided without resumption, the second team wins if they are at or above the par score (for their current over and wickets). During rain delays, television broadcasts display the current par score and update it based on the match situation. The par score is useful not only for rain-day adjudication — it also provides a real-time 'are we winning?' indicator for the batting team throughout a chase, showing whether they are ahead of or behind the DLS-calculated match-winning position.
Can a team deliberately score slowly to exploit DLS in their favour?
The strategic implications of DLS do create incentive effects on batting approach. In practice: if a team is batting first and rain is forecasted, they may push the scoring rate hard in early overs (to maximise their total before potential interruption, since DLS gives more weight to early-innings scoring when interruption occurs in later overs). If a team is batting second, early rain that reduces overs can favour a low-wicket-loss approach (teams with wickets in hand have higher DLS resources, so preserving wickets during a rain-threatened phase is strategically valuable). Whether teams explicitly 'game' DLS by scoring slowly or quickly based on rain forecasts is contested — most captains prefer to play normally and accept DLS outcomes as external.
Is there a minimum number of overs for an ODI result to be valid?
Yes — in ODIs, each team must face a minimum of 20 overs for a result to be declared. If the first team is bowled out before 20 overs in the first innings, the match continues normally regardless. If the second innings cannot reach 20 overs due to persistent rain, the match is declared a 'no result' or abandoned — no winner is declared. In T20 Internationals, the minimum is 10 overs per side. Below these thresholds, even a DLS calculation cannot provide a valid result — the ICC determined that very short matches (under 20 overs for an ODI; under 10 for a T20I) provide insufficient data for a fair DLS-adjusted result. Tournament rules may specify different procedures (coin toss, group-stage record) for determining who advances if no result is possible.