Rain Interruptions: How Teams Adjust Strategy Mid-Match
How rain stoppages change the tactical landscape of cricket matches — why the fielding team and batting team respond differently to interruptions, what the DLS recalculation means for target setting, and how teams prepare batting/bowling tactics that account for potential rain.
Why Rain Changes Everything
Rain interruptions do not simply pause a match — they fundamentally alter its parameters. In limited-overs cricket (ODIs and T20Is), a rain reduction triggers the Duckworth-Lewis-Stern (DLS) system, which recalculates the target based on the resources (overs and wickets) remaining. This means a team that was comfortably winning before rain may find themselves facing a dramatically different target, or a team chasing a large total may suddenly need fewer runs with no wickets lost.
The key insight: rain does not affect both teams equally in all situations. If a team batting first is interrupted, their innings is shortened, reducing their total. If the team batting second faces rain, the DLS target is recalculated and may be more or less favourable than the straightforward run-rate suggests. The side that understands DLS mathematics — and plans their batting and bowling around its implications — has a significant tactical advantage.
Batting First: Banking Wickets vs Scoring Rate
When a team is batting first in conditions where rain is likely, the DLS-aware strategy is to protect wickets more than normal in the early overs — specifically, to keep wickets in hand so that if overs are reduced, the team has the resources to accelerate aggressively with a full batting lineup. The DLS 'resource table' assigns a higher value to wickets in hand: a team that is 100/0 after 20 overs when rain arrives is in a far better DLS position than a team that is 140/5, even though the second team has more runs.
In rain-prone conditions (English summer cricket, some Caribbean T20 tournaments), the optimal batting-first strategy may be to accept a slightly lower run rate in exchange for minimal wicket loss in the first half of the innings. India's approach in several 2019 World Cup games reflected this: in overcast, rain-likely conditions at English grounds, their top order was instructed to bat deeper into the innings before attacking, prioritising wicket preservation over quick early runs.
Bowling First: The DLS Advantage
Captains who win the toss in overcast, rain-likely conditions often prefer to field first — partly because overcast conditions aid swing bowling, but also because of DLS asymmetry. If the team batting first is interrupted (their innings is shortened), the DLS system typically reduces their total. When the team batting second then chases, they have fewer runs to get. But if the team batting second is interrupted while chasing, the DLS target calculation often favours the batting side less when the chasing team has lost wickets — it can set a target that is harder than the situation suggests.
The 1992 World Cup semi-final between England and South Africa became the most famous rain-interruption controversy: South Africa needed 22 runs from 13 balls when rain arrived; when play resumed, the rain-rule calculation (which was not DLS but an earlier inferior method) reduced their target to 21 runs from 1 ball — an impossible task. The incident directly led to the development and adoption of the Duckworth-Lewis method.
Reading the Rain: Tactical Acceleration Before Rain
Experienced batsmen track weather forecasts during play and adjust their approach when rain appears imminent. The logic: if rain is coming in 8 overs and the scoring rate has been reasonable, it may be better to increase the scoring rate immediately (accepting some risk of wicket loss) because a rain stoppage will reset the over count without affecting wickets already taken. Conversely, if the team batting second has a comfortable position and rain appears likely, they may deliberately play conservatively to wait for rain — knowing the DLS recalculation may hand them the match.
Test Cricket and Rain
In Test cricket, rain does not trigger DLS — there is no revised target system. Instead, lost time is added to the match if possible (play may extend to 6pm instead of 5:30pm, for example), and if insufficient overs are bowled across the match, the match is drawn. This creates its own tactical dynamics: a team ahead in a Test match (in runs or wickets) when rain arrives is incentivised to play slowly, knowing any further time lost makes a draw more likely and protects their position. The team behind is incentivised to play aggressively to accelerate an unlikely win before rain ends the match.
The 20-over minimum rule in Test cricket: for a result to be possible on the final day, at least 20 overs must be bowled. This creates tactical situations where a chasing team deliberately wastes overs (or takes them slowly) to bring the 20-over threshold into play, making a draw the safer outcome than risking defeat. Batsmen who block indefinitely are not doing nothing — in rain conditions, time is their most valuable resource.
Frequently asked questions
What is the DLS method in simple terms?
DLS (Duckworth-Lewis-Stern) is a mathematical system for recalculating targets in rain-interrupted limited-overs matches. It assigns a 'resource percentage' to each combination of overs remaining and wickets in hand, then uses those percentages to recalculate a fair target based on the resources each team had when playing. A team that loses overs while batting first gets a scaled-down total; a team chasing gets a target adjusted to their remaining resources.
What happens if a match is abandoned due to rain with no result?
In group stage matches, a no-result typically means both teams share the points (usually one point each in World Cup format). In knockout matches, a reserve day is scheduled — if no play is possible on the reserve day either, the team higher in the group stage standings advances. If no group-stage precedent exists, shared advancement or a coin toss may determine the winner, though the ICC specifies the exact mechanism in tournament regulations.
Can a team benefit strategically from the DLS calculation?
Yes — DLS can occasionally produce results that seem counterintuitive. The most common example: a team chasing a large total that has lots of wickets in hand when rain arrives may receive a target that is lower than expected from their current run rate, because DLS values unexplored batting resources highly. This is by design — the system attempts to account for the scoring capacity that was not yet used.
