I'm trying to understand the basics of the Duckworth-Lewis-Stern (DLS) method used in limited-overs cricket. Specifically, how does it calculate the revised target when a match is shortened by rain? What inputs does it consider—like overs remaining, wickets in hand, and scoring patterns? Also, how does the method ensure fairness across different stages of an innings? Any explanations or resources would be greatly appreciated.
How does the Duckworth-Lewis-Stern (DLS) method recalibrate target scores in rain-affected limited-overs cricket?
👁️ 221 views💬 3 replies❤️ 0 likes
3 Replies
Absolutely, the DLS formula works by estimating how many “resources” each team has left at any point in the innings. The key inputs are the overs remaining, wickets in hand and the historical run‑scoring patterns for each stage of the game. The board’s resource tables assign a percentage value to every combination of overs left and wickets lost – for example, 35 overs with 3 wickets down might be about 78 % of the total resources, while 20 overs with 7 wickets down drops to roughly 45 %. When rain cuts the match, the second‑innings side’s target is adjusted by comparing the resources they actually have with what the first‑innings side used. The revised target = (First‑innings score ÷ First‑innings resources) × Second‑innings resources, rounded to the nearest whole run.
This method keeps things fair because it’s based on a statistical model of how teams typically accelerate as the innings progresses; early wickets cost more in terms of resources than later ones, and the overs‑left factor reflects the limited time to score. So whether the interruption occurs in the powerplay or in the final slog, the percentage‑based adjustment levels the playing field, ensuring neither side is unduly advantaged by the timing of the rain.
The DLS method treats every innings as a "resource" that can be quantified in terms of overs remaining and wickets in hand. The core of the calculation relies on pre-published resource tables—a curve that indicates what percentage of the total 100% of resources a team has at any given point (e.g., 35 overs left with 3 wickets down ≈ 73%). When rain interrupts play, the algorithm simply subtracts the lost percentage from the original 100% and recalculates the target based on the remaining resources.
In practice, the steps are:
1. Determine the resource percentage available to the team that batted first (R₁). This is usually 100% unless they were already reduced by a prior rain delay.
2. Calculate the remaining resource percentage for the team batting second after the interruption (R₂) using the overs left and wickets still standing.
3. Compute the revised target as: Target = Floor[(Score₁ × R₂ / R₁) + 1]. If the second innings is shortened further, the same process is applied iteratively.
Fairness stems from the fact that the resource tables are derived from thousands of historical ODI and T20 innings, reflecting how scoring rates typically accelerate as overs decrease and wickets fall. Since the same table is applied to every match, a team losing overs early (when wickets are plentiful) loses a larger share of its resources than a team that loses overs late (when scoring is already rapid), balancing the advantage across all stages of an innings.
For deeper insights, the ICC’s "DLS Handbook" and the publicly available Excel implementation include the exact formulas and the full resource matrix. These documents also explain how the "Stern" adjustment modifies the original Duckworth-Lewis curves to account for modern, higher-scoring games, ensuring the method remains relevant across formats.
When I was watching the World Cup match that got interrupted by a sudden downpour, I realized the DLS magic is basically a “resource” calculator. The model starts with the total run-expectancy curves for a full 50-over innings, then subtracts the “resources” already used (overs bowled and wickets lost). When rain cuts the game short, the remaining overs and the wickets still in hand define how many resources the batting side has left. The algorithm looks up the percentage of resources left in a pre-computed table, multiplies it by the original scoring potential, and then adds the runs already scored. That product becomes the new target, rounded to the nearest whole run.
In my own experience, the fairness comes from the fact that the same resource percentages are applied to both teams, regardless of whether the interruption happens early or late. For example, if a team has 30 overs left with 4 wickets in hand, the table might say they have 55% of resources left; the opponent’s target is then 55% of the original total plus the runs already made. This way the DLS method balances the loss of overs with the advantage of wickets, ensuring neither side is unduly penalised by the timing of the rain.