Few things are more frustrating in cricket than a rain-shortened match decided by a number you do not fully understand. The Duckworth-Lewis-Stern method — DLS to most fans — has been a source of confusion, controversy, and occasionally injustice since its introduction. We break it down here so you can follow what is happening when the skies open up mid-match.
Why DLS Exists
The simplest approach to a rain-shortened chase would be to subtract the runs scored from the target and reduce overs proportionally. But that method ignores something critical: wickets in hand. A team that has lost 4 wickets chasing 180 in 18 overs is in a fundamentally different position than one that has lost 0 wickets facing the same total. DLS attempts to account for both balls remaining and wickets in hand — the two resources a batting side has at its disposal.
The method uses pre-calculated resource percentage tables that assign a numerical value to every possible combination of overs remaining and wickets lost. When rain interrupts play, the Match Referee calculates how much of each team's resources were available, then adjusts the target accordingly. The system is rigid by design: it removes subjectivity, but it also produces outcomes that feel unintuitive when you watch them unfold in real time.
How DLS Actually Works in Practice
Here is the core logic: a team starting their innings with 20 overs and 10 wickets has 100% of their resources. If rain reduces their innings to 18 overs, they now have approximately 95% of their resources (the exact number depends on when the interruption happens and how many wickets are down). The revised target is then calculated by adjusting the original target proportionally to the resources available. If Team A scored 200 using 100% of their resources, and Team B has only 95% of resources available, the formula gives Team B a revised target of around 190.
The complexity increases when the interruption happens mid-innings. If Team B has already scored 80 runs in 10 overs and lost 2 wickets, and rain then reduces their remaining overs from 10 to 6, DLS recalculates what percentage of resources they had at the interruption and what percentage they have after the reduction. The revised target accounts for runs already scored and resources consumed. This is where the method feels most opaque — the target can shift by 15+ runs after a single rain break, and it is not always obvious why.
IPL 2026: When DLS Decided Matches
Three IPL 2026 league-stage matches were affected by rain interruptions significant enough to trigger DLS revisions. The most controversial was Match 38, where Mumbai Indians were chasing 182 against Rajasthan Royals at Wankhede. Rain reduced the chase from 20 overs to 16 overs after MI had scored 92 for 3 in 11 overs. The revised target became 164 — a reduction of 18 runs. MI won by 4 wickets with 3 balls remaining, but the vocal criticism from Rajasthan's captain centered on the perception that MI had been "gifted" 18 runs. In reality, DLS judged that the overs lost were more valuable to the chasing side than the runs they had already scored, which is consistent with the method's logic even if it feels harsh to the bowling side.
The second notable case was Match 47, where Delhi Capitals were chasing 176 against Chennai Super Kings. Rain delayed the start of DC's innings, and when play resumed, they faced a revised target of 151 in 16 overs — a 25-run reduction. DC chased it down with 7 balls to spare. The controversy here was not the target calculation, but the fact that CSK had scored 176 in full 20 overs on a pitch that had not been affected by rain, while DC benefitted from a shortened chase on the same surface. DLS does not account for pitch conditions changing due to rain — it assumes the resources are equivalent, which is not always true in practice.
The Playoff Exception
IPL 2026 introduced a reserve day for the final, which meant DLS was only a fallback if the match could not be completed across two days. The final between RCB and Gujarat Titans went to the reserve day after rain washed out play on the scheduled date, and the full 20-over match was completed without DLS intervention. This was the first time since 2021 that an IPL final had a reserve day provision, and it worked exactly as intended — fans got a complete match, and DLS controversy was avoided.
Common Misconceptions
The biggest misconception about DLS is that it adjusts the target based on run rate. It does not. The method is entirely resource-based: it calculates what percentage of the innings' total scoring potential remains, then adjusts the target to match. A team chasing 200 in 20 overs is not given a revised target based on "10 runs per over" — they are given a target based on how much of their batting resources (overs plus wickets) they still have available.
The second misconception is that DLS favors the team batting second. In reality, the method is neutral — it adjusts the target based on resource loss, not team preference. What creates the perception of bias is that rain interruptions during a chase are far more visible and emotionally charged than interruptions during the first innings. When a target drops from 190 to 175 after rain, it feels like a gift to the chasing side, even though the calculation is mathematically consistent with the resource tables.
Fantasy and Betting Implications
For Dream11, rain-affected matches are nightmares. If a match is reduced to under 10 overs per side, most fantasy platforms void the contest entirely and refund entries. For matches reduced to 10–15 overs per side, the scoring dynamics shift heavily toward explosive openers and death bowlers — middle-order batsmen and powerplay bowlers see reduced involvement, which means their fantasy value drops. Our advice: if rain is forecast and the match is likely to be shortened, stack your Dream11 team with openers who bat in the top 3 and bowlers who bowl the final overs. Avoid middle-order anchors and spinners who rely on middle-overs economy.