Duckworth-Lewis-Stern (DLS) Method Explained: Rain Rules in Cricket
How the Duckworth-Lewis-Stern method works in cricket — the mathematical system that recalculates target scores when rain interrupts limited-overs matches, why it replaced the old average run-rate method, and why the DLS calculation can feel counter-intuitive.
The Duckworth-Lewis-Stern (DLS) method is the mathematical system used in limited-overs cricket (ODIs and T20Is) to recalculate target scores when rain or other interruptions reduce the number of overs available. It replaced the older 'average run-rate' method in 1999 and has been the ICC's official rain rule method since. When overs are lost to rain, the DLS method adjusts the target score so that the team batting second has an equivalent challenge to the team batting first.
Why the Old Method Was Unfair
The pre-DLS 'average run-rate' method (which simply divided the first team's total by overs faced, then multiplied by overs available for the second team) was demonstrably unfair: it didn't account for the different value of remaining overs. If rain fell while the first team was 200/1 after 30 overs and the match was reduced to 25 overs per side for the second team, the target was simply adjusted by proportional overs — but the second team had 10 wickets in hand for 25 overs, a very different challenge from 200/1 after 30. The most notorious example was the 1992 World Cup semi-final: South Africa needed 22 from 13 balls, rain came, and the old method reset the target to 22 from 1 ball — an impossible equation created by a mathematically crude system.
The DLS Logic: Resources
DLS measures batting 'resources' — the combination of wickets remaining and overs remaining that a team has available to score runs. A team with 10 wickets in hand and 20 overs remaining has more resources than a team with 5 wickets in hand and 20 overs remaining; a team with 10 wickets and 5 overs has fewer resources than a team with 10 wickets and 20 overs. The DLS tables quantify the percentage of total resources that correspond to every combination of wickets and overs, and the target adjustment is based on the proportion of resources each team has available compared to what the first team used.
Counter-Intuitive DLS Results
DLS targets can seem unfair when rain interrupts the second team's innings: if Team B is batting and rain stops play when they are behind the DLS par score, they lose (even if they had wickets in hand and might have caught up). If rain helps the fielding team (reducing overs when the batting team was struggling), the DLS calculation accounts for this differently from when rain helps the batting team. Fans who try to apply simple proportional logic (we've scored X from Y overs, we need Z in W overs) frequently find the DLS number doesn't match their mental arithmetic — because DLS accounts for wickets-in-hand and the exponential value of later overs that simple proportion does not.
T20I DLS Applications
DLS in T20I cricket has been particularly controversial — the shorter format means smaller adjustments have larger proportional impact, and matches can be decided on DLS before enough overs are bowled for the match to have a feel of completion. The ICC minimum overs requirement for a T20I result (typically 5 overs per side in the most extreme weather interruptions) can produce results from very small samples that frustrate players and fans. But DLS in these truncated conditions still produces fairer outcomes than the average run-rate method's cruder arithmetic.
Frequently asked questions
What is the Duckworth-Lewis-Stern (DLS) method?
A mathematical system that recalculates target scores in limited-overs cricket when rain or interruptions reduce overs. It replaced the average run-rate method in 1999 and is the ICC's official rain rule. DLS accounts for both overs remaining AND wickets in hand — not just overs — which is what makes it fairer than simple proportion.
Why was the old rain rule replaced by DLS?
The old average run-rate method was demonstrably unfair — most notoriously in the 1992 World Cup semi-final, where South Africa needed 22 from 13 balls, rain came, and the old system reset the target to 22 from 1 ball. It failed because it didn't account for wickets remaining, treating 20 overs with 1 wicket the same as 20 overs with 10 wickets.
Why do DLS targets sometimes seem wrong?
Because DLS uses exponential mathematical functions to measure 'batting resources' (overs × wickets-in-hand) rather than simple proportion. Fans applying mental arithmetic (X runs in Y overs) get a different number because they aren't accounting for the changing value of wickets-in-hand as overs reduce. DLS is genuinely more accurate, but more complex than proportion allows.
