Few things in cricket create more confusion -- and controversy -- than rain interruptions. When bad weather shortens a limited-overs match, the Duckworth-Lewis-Stern (DLS) method is used to calculate revised targets and determine a fair result. This guide explains how DLS works in plain language, traces its history, and walks through real examples so you'll never be caught confused when the commentator says "Team X is 12 runs ahead on DLS."
The DLS method is a mathematical formula used to set revised targets in rain-affected limited-overs cricket matches (ODIs and T20Is). It was designed to replace cruder methods (like the "most productive overs" system) that often produced absurdly unfair targets.
The core idea: a team's batting potential depends on two resources -- the number of overs remaining and the number of wickets in hand. DLS quantifies these resources as percentages and adjusts the target proportionally when overs are lost to rain.
Before 1997, cricket used various crude methods to handle rain. The most infamous was the "most productive overs" method, which produced the farcical 1992 World Cup semi-final target: South Africa needed 22 runs from 13 balls, rain came, and after the recalculation they needed 21 runs from just 1 ball. The cricketing world demanded a better system.
Frank Duckworth and Tony Lewis, two English statisticians, developed a resource-based model that the ICC adopted in 1999 as the official rain rule for international cricket. Their method used published tables that showed the percentage of resources remaining for any combination of overs and wickets.
After both original creators retired, Professor Steven Stern took over maintenance and introduced the "DLS" update. The key change was switching from a fixed table (Standard Edition) to a continuously updated model (Professional Edition) that accounts for modern scoring trends. T20 run rates have increased dramatically since 2003, and the Professional Edition adjusts its resource percentages accordingly.
At the start of an innings, a team has 100% of its resources (all overs, all wickets). As overs are bowled and wickets fall, resources are consumed. If no rain occurs and a team is all out or uses all overs, resources reach 0%.
Key insight: losing a wicket costs more resources when many overs remain (because that batter would have faced more balls). Conversely, losing an over matters less when several wickets have already fallen (because the remaining batters are lower-order and would contribute fewer runs anyway).
DLS uses a parameter called G50 -- the average score expected in a 50-over innings with all resources intact. For men's ODIs, G50 was around 245 in the original model and has been adjusted upward over time to reflect modern scoring (currently closer to 260). For T20s, a corresponding G20 value is used.
The basic formula (simplified) is:
Revised Target = Team 1's Score x (Team 2's Resources / Team 1's Resources) + 1
If Team 2 has fewer resources than Team 1 (e.g., Team 2 has fewer overs to bat), the target is reduced proportionally. If Team 2 has more resources (e.g., rain during Team 1's innings reduced their overs), the target is increased.
Suppose in an ODI, Team A bats first and scores 280 in 50 overs (100% resources used). Rain arrives during the innings break, and Team B's innings is reduced to 40 overs.
From the DLS tables, a team with 40 overs and 10 wickets has approximately 89.3% of its resources. Using the formula:
Revised Target = 280 x (89.3 / 100) + 1 = 250.04, rounded to 251
Team B would need 251 to win from 40 overs.
During a rain-interrupted chase, broadcasters display a par score -- the score Team B needs at the current point to be level with Team A if rain ends the match immediately. If Team B is above par, they win; below par, they lose; at par, it's a tie.
This is what commentators mean when they say "Team B is 15 runs ahead on DLS." Follow the par score in real time on SportGodAI's live match pages, where our AI also factors rain probability into its win predictions.
While DLS is far superior to its predecessors, it has known limitations:
DLS applies to T20 matches as well, but with adjusted resource tables that reflect the shorter format. Because T20 scoring rates are much higher and more volatile, even small resource differences translate to significant run changes. The ICC requires a minimum of 5 overs per side for a valid T20 result under DLS.
The DLS method isn't perfect, but it's the most mathematically sound system cricket has produced for handling rain interruptions. Understanding resources, par scores, and the basic formula will make rain-affected matches far less confusing. The next time clouds gather, check SportGodAI's predictions -- our models incorporate weather data and DLS scenarios to give you the most accurate win probabilities available.
Try Sport God AI live
Live scores, AI predictions, and fantasy — free during IPL 2026.