DLS Method Explained: How Rain Reshapes Limited-Overs Cricket Targets
How the Duckworth-Lewis-Stern (DLS) method works in rain-affected limited-overs cricket — why a simple pro-rata calculation is insufficient, the concept of 'resources' (overs and wickets) that DLS models, how the DLS table produces revised targets, why teams can go from winning to losing (or vice versa) when rain stops play, the 1992 World Cup rain rule controversy that DLS was designed to replace, and common DLS scenarios and their outcomes.
Why Pro-Rata Doesn't Work
The simplest approach to a rain interruption in a limited-overs match is pro-rata: if a team scored 200 from 40 overs and the game is reduced to 30 overs, the target becomes 200 × (30/40) = 150. The problem: this ignores that scoring rates accelerate dramatically in the final overs of an innings. A team scoring 200 from 40 overs likely scored 120 in the first 25 overs and 80 in the last 15 (as wickets in hand allow free hitting). If the second team only needs 30 overs to bat, they face those 30 overs with all 10 wickets — they are not bound by the cautious early overs that produced the slower scoring in the first half of the first team's innings. A 150 target from 30 overs with 10 wickets available is significantly easier than 200 from 40 with the same wickets — pro-rata systematically underestimates the advantage of the batting side in reduced-overs scenarios.
Resources: Overs and Wickets
The DLS method (developed by statisticians Frank Duckworth and Tony Lewis, later updated by Steven Stern) models each team's 'resources' — the combined value of remaining overs and wickets in hand. At the start of an innings, a team has 100% of their resources (all overs available and all wickets in hand). As overs are used and wickets fall, resources diminish. The key insight is that resources decline non-linearly — losing a wicket early (when many overs remain) costs more resources than losing the same wicket late; using overs when wickets are plentiful is less costly than using overs when few wickets remain. The DLS table (a resource table) maps every combination of overs remaining and wickets in hand to a percentage of total resources. A revised target is calculated by comparing how many resources each team had available for their innings.
Common DLS Scenarios
Interruption during the first innings: if rain stops the first innings after, say, 30 overs and play resumes for 40 overs per side, the DLS target for the second team is calculated based on first innings resources used vs second innings resources available — the second team's 40-over target reflects what the first team would likely have scored with 40-over resources. Interruption during the second innings: if the chasing team is interrupted, the DLS method calculates what their revised target is given remaining resources — the target may increase if the interruption has left them fewer overs to score with more wickets in hand (resources lost were overs rather than wickets). If rain reduces the second team's innings significantly, the target can sometimes mean a team in a losing position suddenly wins — because the target was already met when DLS is applied to their current score.
Frequently asked questions
Can a team use DLS to their strategic advantage?
Teams in the field can attempt to influence whether DLS helps them by deliberately slowing over rates to use up time and invite rain interruptions when behind — this is theoretically possible but punishable by over-rate penalties. More legitimately, when weather looks threatening, a batting team might choose to attack more aggressively than usual to build a large score early, knowing that a DLS calculation based on a higher score with early wickets will produce a larger revised target. Similarly, a chasing team who suspects interruption might prefer to have wickets in hand rather than overs — losing wickets early reduces resources more per DLS's model, so protecting wickets under a potential DLS scenario has higher value than normal.
What is the minimum number of overs for a DLS result to be valid?
The minimum number of overs to constitute a valid DLS result varies by tournament rules. In ICC-sanctioned ODIs, a match requires a minimum of 20 overs per side for a result. In T20Is, the minimum is 5 overs per side. Below these thresholds, the match is either abandoned (no result) or continues to be rescheduled if the tournament structure allows. The minimum requirement exists because DLS calculations become increasingly unreliable with very small samples — a team's score after 3 overs is dominated by chance (the quality of the opening partnership in those specific 3 overs) rather than their genuine batting quality, and a DLS target based on 3 overs of play would not be a fair comparison.
Has the DLS method ever produced controversial outcomes?
Yes — DLS is better than all predecessor systems but is not universally loved. Several instances of DLS targets being perceived as too easy or too hard have produced controversy: when a team batting first gets all-out quickly and the first innings ends with many overs unbowled (the second team faces a DLS target based on a full-resources comparison, which can be lower than expected). The most structural criticism of DLS is that it was calibrated on historical scoring data — as scoring rates in ODIs have increased dramatically (from 4.5 runs/over average in the 1990s to 5.5+ today), some analysts argue the DLS model's underlying resource table needs updating to reflect modern hitting ability. Steven Stern's 2014 updates addressed some of this, but the debate about whether DLS correctly models very high-scoring conditions continues.