The Target Reset: When Rain Changes a Run Chase
When rain interrupts a limited-overs match during the second innings, the Duckworth-Lewis-Stern (DLS) method recalculates the target — sometimes drastically changing the match dynamics. This article explains how rain during a chase creates a target reset and what it means for both teams.
How Rain During a Chase Changes the Target
When rain interrupts a run chase in progress (the batting team is already batting and has faced some overs), the DLS method recalculates the required score based on: how many overs remain (reduced by the lost overs); how many wickets the batting team has lost (wickets remaining affect the 'resources' available); and the batting team's current score. The revised target is calculated from the DLS 'resources table' — comparing the batting team's resources remaining (overs × wicket combination) before and after the rain interruption. If the batting team had more resources remaining than the fielding team had in their equivalent position at the same score, the target may reduce; if fewer resources, the target may increase. The result is the DLS Par Score — the score the batting team needs to have equalled or passed when rain stops play permanently.
Match-Winning Scenarios from Target Resets
Target resets create specific match-winning and match-losing scenarios: a team that is behind the DLS par score when rain stops play loses the match — even if they felt they were 'in the game' and had wickets in hand; a team that is exactly on the DLS par score when rain stops play wins by 0 runs (or ties in some DLS interpretations); and a team that accelerates their scoring specifically because they know the DLS par score gives them a target to aim for can win through rain interruptions that would have otherwise been neutral (they score the required runs before the rain returns). The DLS par score at any given moment is publicly available during broadcasts — allowing viewers and batsmen to know exactly what score is needed to have won if rain stops play.
Strategic Response to the Reset
Batting teams facing potential DLS resets during a chase make specific tactical adjustments: when rain seems likely (dark clouds, wet outfield), the batting team may accelerate regardless of early risk — getting ahead of the DLS par score before rain stops play; when rain has already stopped and the revised target is known, the batting team recalibrates their required rate for the remaining overs; and when a rain interruption gives a batting team a significantly reduced DLS target, the bowling team must immediately react to the new match dynamics — a previously comfortable bowling position can become suddenly desperate if DLS dramatically reduces the target. The fielding team also responds: if the DLS reduction gives the batting team a much lower target, the bowling captain must immediately seek wickets rather than containment.
Frequently asked questions
Can a team lose on DLS even if they are scoring at a higher rate than the opposition?
Yes — DLS results can appear counterintuitive to raw run-rate comparisons: a team scoring at a higher run rate than the opposition's first innings rate can still lose on DLS if they've lost more wickets than the DLS resource table expects at their score and overs stage. The DLS method considers both runs and wickets simultaneously — a team that is 150/8 after 30 overs while chasing 200 in 50 overs may be 'ahead on run rate' (5 per over required, currently scoring at 5 per over) but 'behind on DLS' (8 wickets lost means minimal remaining resources — the DLS par score would require more than 150 at this wicket-and-over combination because the remaining resources can't deliver the remaining target reliably). The DLS par score accounts for the actual probability of completing the target given the remaining wickets and overs — not just the current run rate.
What happens if rain stops the match completely without a result?
If rain stops a match without sufficient play for a DLS result (typically a minimum of 20 overs completed in the second innings is required for a result in 50-over ODIs), the match is declared a 'no result' — neither team wins or loses. In tournament contexts, no-result matches are typically split points (each team receives half a point); in bilateral series, the match may be replayed on a reserve day if available. No-results are more common in matches with poor pre-match weather assessment — if the match was always unlikely to complete 20 overs in the second innings due to weather, it arguably shouldn't have started. The ICC's match-management protocols allow officials to delay the start of play based on weather forecasts — reducing (but not eliminating) no-result occurrences.
How does the DLS reset affect specific batting positions in the chase?
DLS resets affect batting positions differently depending on the timing: if rain interrupts early in the chase (only 10 overs bowled), the reset primarily affects the run rate required for the remaining overs — the captain can adjust which batsmen to promote based on the new rate requirement; if rain interrupts when a dangerous batsman is at the crease approaching a DLS par landmark, the batting captain may specifically instruct aggressive scoring to reach DLS safety before rain stops play — different from normal match-pacing; and if the DLS reset creates a significantly reduced target with many wickets in hand, lower-order batsmen who had not expected to bat may suddenly be required (if the top order scored rapidly and many fell in the process of reaching the DLS target aggressively). The DLS adjustment creates real-time batting lineup decisions that are additional to the normal match-situation lineup choices.