Rain interruptions have always been cricket's most contentious logistical problem. A five-day Test can absorb significant weather delays through reserve days and extended playing hours, but in limited-overs cricket — particularly T20 — a 20-minute rain delay can alter an entire match. The sport spent decades applying crude solutions before statisticians Frank Duckworth and Tony Lewis produced a mathematically defensible answer in 1997. Their method, later refined by Steven Stern and renamed Duckworth-Lewis-Stern (DLS), is now the official ICC standard for revising targets in interrupted limited-overs matches.
Why Cricket Needs a Rain Rule
The intuitive solution to rain interruptions is simple proportion: if Team 2 loses five overs out of twenty, reduce their target by 25%. This is the "pro-rata" method, and it is deeply unfair in almost every realistic scenario.
Consider why: a team batting first distributes risk across all 20 overs, losing wickets steadily and accelerating in the final overs when the fielding restrictions end. A team chasing 160 in 20 overs plays entirely differently from a team chasing 120 in 15 overs — the required run rate jumps from 8.0 to 8.0 nominally, but the fielding side has not lost the equivalent "resource" of five overs worth of defensive bowling. The chasing side has lost high-value scoring overs without a proportional reduction in the target.
The core insight of DLS is that a team's run-scoring potential is determined by two resources simultaneously: overs remaining and wickets in hand. Removing overs from a chase is far more damaging when a team has fewer wickets remaining (less margin for error) than when they have ten. Pro-rata ignores this interaction entirely.
The "Resources" Concept: Overs × Wickets
DLS uses a precalculated resource table. Every combination of overs remaining and wickets in hand represents a percentage of the team's total scoring resource. The table is derived from historical scoring patterns across thousands of international matches.
A simplified illustration (not the exact DLS table):
| Overs Remaining | 0 Wickets Lost | 3 Wickets Lost | 6 Wickets Lost | 9 Wickets Lost |
|---|---|---|---|---|
| 20 | 100.0% | 75.1% | 49.0% | 18.4% |
| 15 | 85.1% | 64.3% | 42.4% | 16.2% |
| 10 | 66.5% | 50.1% | 33.5% | 12.8% |
| 5 | 40.0% | 31.6% | 21.5% | 8.6% |
| 0 | 0% | 0% | 0% | 0% |
The full DLS table has values for every over and wicket combination. Importantly, the relationship is non-linear: losing overs late in an innings (when a team has few wickets and is in acceleration mode) is more damaging than losing overs early.
How DLS Recalculates a Target
When Team 2's innings is interrupted, the calculation follows this structure:
If Team 1 completed their full innings without interruption:
Team 2's Par Score = Team 1's Score × (Team 2's Resources% / 100)
Revised Target = Par Score + 1
If Team 1's innings was also interrupted:
The "G50" value (the average score expected from a full 50 or 20-over innings, updated annually by the ICC) enters the calculation. The formula adjusts for the fact that both teams had reduced resources, and the side with more resources should have an appropriately scaled advantage.
The Professional Edition (PE) of DLS — used in all international matches — also applies a non-linear adjustment for very high first-innings totals, since teams that score substantially above the G50 benchmark tend to do so more efficiently than low-scoring teams.
Worked Example: T20 Match Interrupted at 10 Overs
Setup:
- Team 1 scores 160 runs in 20 overs (no interruption)
- Team 2 begins their chase; rain stops play after Team 2 has faced 10 overs, scoring 75 runs for 2 wickets lost
- Umpires reduce the remaining innings to zero — the match is called off
Determine resources used:
At the start of Team 2's innings: 20 overs remaining, 0 wickets lost = 100% resources.
After 10 overs with 2 wickets lost: 10 overs remaining, 2 wickets lost = (using illustrative table values) approximately 60.5% resources remaining.
Resources used by Team 2 = 100% − 60.5% = 39.5%
But since rain stopped play and no more overs are possible, Team 2 has only used 39.5% of their resources.
Calculate par score:
Team 2 Par Score = Team 1 Score × (Team 2 Resources% / Team 1 Resources%)
= 160 × (39.5% / 100%)
= 160 × 0.395
= 63.2
Rounded to 63. Team 2 scored 75, which is above the par score of 63, so Team 2 wins by DLS method.
Had the match been reduced rather than abandoned — say, Team 2 gets 15 overs instead of 20 — the revised target would have been: 160 × (Team 2 resources for 15 overs, 0 wickets) / 100% = 160 × 85.1% ≈ 136 runs, meaning Team 2 needs 137 to win.
Famous DLS Controversies
DLS has been the center of significant controversy in high-stakes matches, primarily because its outputs are counterintuitive to casual viewers.
2019 Women's ICC T20 World Cup Final (Australia vs India): Rain interrupted the match after Australia batted. The DLS target set for India was widely debated, with critics arguing the par score was set too high given the conditions under which the match was being played and the match was already interrupted before India batted.
2016 World T20 Final (West Indies vs England): A rain delay altered over allocations mid-match, and the DLS recalculation produced a revised target that West Indies ultimately chased down off the final ball in one of cricket's most dramatic finishes. The application of DLS was correct but contributed to the chaotic finish.
Various ODI tournaments: Critics have long noted that DLS can disadvantage the chasing team in low-scoring matches on difficult pitches, because the resource table was initially calibrated on higher-scoring matches. Stern's 2004 revision and ongoing updates have partially addressed this, but the perception persists.
DLS vs VJD: The Competing Methods
The VJD method, developed by Indian mathematician V. Jayadevan, offers an alternative mathematical framework for revised targets. It uses two separate resource curves — one for normal scoring and one for accelerated scoring — and handles multiple interruptions somewhat differently.
| Feature | DLS | VJD |
|---|---|---|
| Developer | Duckworth, Lewis, Stern (UK) | V. Jayadevan (India) |
| Official ICC use | Yes (all international matches) | No (ICC does not recognize for internationals) |
| Domestic use | Most countries follow ICC | Used in some Kerala and Indian domestic fixtures |
| Handling of low-scoring matches | Improved post-Stern revision | Claims better calibration for sub-par totals |
| Transparency | Published formula framework; PE table undisclosed | Openly published curves |
| Multiple interruptions | Handled via iterative resource subtraction | Handled via separate curve calculations |
The ICC has reviewed VJD periodically and has not adopted it, citing DLS's extensive validation record across international conditions. Supporters of VJD argue it handles specific edge cases — particularly low-scoring matches on turning tracks — more equitably. The debate reflects a genuine statistical challenge: no single resource table can perfectly capture the run-scoring dynamics of every combination of pitch, conditions, team strength, and match situation.
DLS will remain imperfect by definition. It is a statistical model applied to a human sport with enormous situational variability. What it provides is consistency, transparency in its framework (if not its exact tables), and decades of validation data — which is considerably more than its predecessors ever offered.