Duckworth-Lewis-Stern Method Explained: How DLS Works
Rain stops play, the covers come on, and half the crowd starts doing mental arithmetic while the other half argues about whether the chasing team is now ahead or behind. The system that settles those arguments is the Duckworth-Lewis-Stern method, better known as DLS. It is the mathematical rulebook that converts an interrupted match into a fair contest, producing a revised target that reflects exactly how many overs and wickets each side has left.
The method is easy to misunderstand and even easier to distrust, especially when a team appears to lose a match despite scoring the same number of runs as its opponent. The logic behind it, however, is straightforward once the core idea clicks into place: the two teams are competing for resources, and resources mean overs and wickets together, not runs alone.
Why a simple run-rate comparison was never enough
Before DLS existed, rain-hit matches were settled with crude adjustments. The most notorious of them, used in the 1992 World Cup semi-final between England and South Africa, asked South Africa to score 22 runs from 13 balls, then revised the target to 21 from one ball after two overs were lost to rain — an absurd outcome that showed the world something better was needed.
The flaw in run-rate-based rules was that they treated all overs as equal. In reality, a chasing side’s resources are not linear. The first overs are cheap in wickets but modest in scoring; the final overs are explosive but risky. Losing overs from the end of an innings, where the scoring rate is highest, costs a team far more than losing overs from the start. A fair rule needed to capture that shape of an innings, not just its average.
The core idea: resources, not run rates
The method’s inventors, statisticians Frank Duckworth and Tony Lewis, built their system around a single concept: every match situation can be measured by the resources still available to the batting side. Those resources are a blend of overs remaining and wickets in hand, mapped onto a curve that reflects real scoring patterns.
- Overs remaining — the deliveries left to face, weighted so that the final overs are worth more than the early ones.
- Wickets in hand — the freedom to attack; a side with ten wickets can take risks that a side with three cannot.
- The resource curve — the mathematical model that converts any combination of overs and wickets into a percentage of the total resources a full 50-over innings with ten wickets would provide.
When play is interrupted, the target is recalculated as a proportion: the chasing team’s par score is the first team’s total multiplied by the ratio of resources the chaser had available compared with the side batting first. If the second team ends exactly on that par score, the match is a tie; above it, a win; below it, a loss.
A worked example that makes the numbers click
Concrete numbers beat abstract formulas, so here is a simplified illustration of the method in action. Suppose Team One scores 280 in its full 50 overs, using 100% of its resources. Team Two, in reply, has 30 overs left with ten wickets in hand when rain wipes out the rest of the match. A resource table tells us that 30 overs and ten wickets represent about 75.1% of the total available resources. The par score is therefore 280 × 75.1% ≈ 210. If Team Two has 215 when the rain returns, it wins; 210 would be a tie; 208 would be a loss.
Notice what the method quietly achieved: it recognised that losing 20 overs from the end of a chase is a much heavier blow than a run-rate calculation would suggest, because those were the overs where Team Two planned to score fastest. That is the entire genius of the system in one example.
How targets change mid-chase: par scores in practice
Modern broadcasts show a “par score” line throughout a rain-affected chase, and many followers find it the most confusing part of the system. It becomes simple once you understand what the number means: the par score is what the chasing side would need to have at this exact moment to end up level if the match were abandoned right now. Chasing teams compare their score to this line ball by ball.
- Above the par score — the chasing side is currently ahead; if rain ends the match now, it wins.
- On the par score — the match would be declared a tie.
- Below the par score — the chasing side is behind, even if it is comfortably matching the original run rate.
This running comparison is why commentary often says a team is “ahead of the DLS par score” long before any decision is announced. The par line itself climbs steeply as the innings enters its final overs, because each remaining delivery is worth more, which is also why teams that look safe with ten overs left can suddenly find themselves behind after a single interruption.
The Stern update and why the numbers keep shifting
The original formula, designed in the 1990s, served cricket well but relied on scoring patterns from a slower era. As T20 batting reshaped one-day cricket and teams began treating the first ten overs as a launchpad rather than a warm-up, the model’s assumptions aged. Steven Stern, an Australian statistician, led a comprehensive revision in the mid-2010s that recalibrated the resource tables to reflect modern scoring rates, particularly the more aggressive use of the powerplay and the final overs.
The update, renamed D/L to DLS in recognition of his work, changed targets in high-scoring matches noticeably. Under the old tables, a team chasing 350 might have been set an easier revised target than under the current model; the Stern revision widened the gap between first-innings totals in high-scoring games, making the method fairer in an era where 350 is no longer an extraordinary score.
How DLS handles different kinds of interruptions
Not every rain break arrives at the same moment, and the method responds differently depending on when the match loses overs. The scenarios below cover the situations that cause the most confusion among spectators.
| Scenario | What happens to the target | Typical effect |
|---|---|---|
| Overs lost before the chase begins | Target recalculated for the reduced overs | Usually a reduction, sometimes slight |
| Interruption during the chase | Par score adjusted on the spot | Target can rise or fall depending on wickets lost |
| Both innings shortened equally | Resources adjusted for both sides | Often little or no change |
| Chase abandoned before the minimum overs | Match declared if par position is decisive | Result based on current standings |
The third and fourth rows explain the outcomes that surprise people most. If both teams lose the same number of overs, the target barely moves, because the contest has been distorted evenly. And if the match is abandoned during the first innings or very early in the second, the rules require a minimum number of overs to constitute a game — typically twenty in one-day cricket — below which no result can be determined at all.
Why teams sometimes seem to lose while winning
The most famous criticism of DLS comes from matches where a team’s supporters cannot understand why a healthy score was not enough. The answer almost always lies in wickets. A chasing side that is 150 for 1 in the 30th over has a very different future from one that is 150 for 6, even though the scores are identical, because the second team has far fewer resources left to convert remaining overs into runs.
This is also why captains think in terms of DLS position rather than the raw asking rate during interrupted chases. A smart batting side recalculates its risk appetite after every stoppage: if it is above par, it can afford to consolidate; if below, it must accelerate even into conditions it cannot see. Coaches prepare for this by drilling the resource percentages into their players, because a single miscalculation of when to push can swing the match more than any spell of bowling.
What DLS cannot do
For all its sophistication, the method has boundaries that critics keep pointing at, and knowing them makes the system easier to accept.
- It cannot measure conditions — a pitch that turned vicious or a ball that began swinging counts for nothing; the formula sees only overs and wickets.
- It assumes average scoring patterns — a team built around a slow anchor and a brilliant finisher may be undervalued by a model built on generic curves.
- It cannot predict collapses — the par score assumes the chasing side uses its remaining resources rationally, which T20 cricket regularly disproves.
None of these limitations invalidates the method; they simply mark the edge between mathematics and the chaos that makes cricket worth watching. Every competing proposal has traded away one of these weaknesses only to create a worse one, usually by rewarding defensive batting or ignoring the value of wickets.
From confusion to confidence
Once you accept that runs, overs and wickets form a single bundle of resources, the entire system stops feeling like sorcery. The next time rain interrupts a match, watch the par score rather than the required run rate, remember that the line steepens sharply toward the end of the innings, and notice how the chasing team’s tactics change the moment it crosses the threshold from behind to ahead. The method is not perfect, but it took cricket from the farce of 1992 to a system that, nearly every time it is used, produces a result both teams can live with.
