Duckworth Lewis Method Explained Rules, Formula, and Scenarios

Cricket fans know that rain and bad weather can wreak havoc on limited-overs matches. In this guide, the Duckworth Lewis Method Explained step by step, covering its purpose, formula, and typical scenarios. It is a mathematical formula used to fairly adjust the target score for the team batting second when a match is interrupted. Often called the D/L method (or DLS – Duckworth-Lewis-Stern – in its modern form), this system ensures that losing overs to rain doesn’t unfairly advantage one team over the other.

A match interrupted by bad light or rain triggers the Duckworth-Lewis (D/L) method to set a new target. The scoreboard at Trent Bridge above shows play stopped due to bad light – in such situations officials would apply the D/L calculations.

Why Was the Duckworth Lewis Method Explained Method Created?

Before Duckworth and Lewis developed their solution in 1997, international cricket used simpler adjustment methods that were often unfair or easily exploited. For example:

• Average Run Rate method: This approach set the target based on the chasing team’s scoring rate at interruption. It ignored wickets lost, so a team could sacrifice wickets to boost their run rate without penalty. This made comparisons with Team 1’s innings misleading.
• Most Productive Overs method: This method dropped the chasing team’s best scoring overs when calculating the revised target, effectively penalizing good batting. It also ignored wickets lost and could advantage Team 2 by ignoring its top overs.
• Both of these methods failed to account for match context and resources. They often altered the balance of the game unfairly whenever rain fell.

To address these flaws, Frank Duckworth and Tony Lewis (English statisticians) devised a new model in 1997. Their goal was to create a statistically fair formula that uses overs remaining and wickets in hand as a combined metric of batting resources. In 1999 the International Cricket Council (ICC) officially adopted the Duckworth-Lewis method for rain-shortened games. It quickly became the standard in limited-overs cricket (ODIs, T20s, and similar formats) whenever weather interruptions occur. The Duckworth-Lewis approach ensures that targets are adjusted based on the true potential each team had with their available resources.

Key Concepts: Overs, Wickets, and Resources

The Duckworth-Lewis method is built on the idea that a batting team’s ability to score runs depends on two resources: the overs remaining and the wickets in hand. Both are finite, and their combination determines how many runs a team can reasonably score. D/L uses pre-calculated tables (or software) that convert any scenario of overs left and wickets lost into a percentage of total scoring resources available.

For example, at the start of a 50-over innings, a team has 100% of its resources (all 50 overs and all 10 wickets). If a rain delay reduces the innings to 25 overs, the resource percentage might drop to about 50% (meaning only half the scoring potential). If the team has also lost wickets when play stops, the resource percentage is even lower. These values come from statistical models of scoring rates.

When resetting a target, the D/L method compares Team 1’s and Team 2’s resources. Team 1’s resources (R1) is the percentage they used, and Team 2’s resources (R2) is the percentage they will have. Then:

• If R2 < R1, Team 2 has fewer resources than Team 1 and the target is reduced proportionally.
• If R2 > R1, Team 2 actually has more resources (often because Team 1’s innings was cut short), and the target is increased to compensate.

This ensures fairness. For instance, if Team 1’s innings is shortened by rain, Team 1 had fewer resources. If Team 2 then bats a full innings, they have a relative advantage (more resources), so D/L will raise the target above Team 1’s score to even things up.

How the Duckworth-Lewis Formula Works

The core formula of D/L adjusts the target based on the ratio of resources. In its simplest form (when Team 1 had a full innings), it is:

Team 2’s par score = Team 1’s score × (Team 2’s resources ÷ Team 1’s resources).

After finding this par score, Team 2 needs one additional run to win; meeting the par score results in a tie.

For example, suppose Team 1 scored 250 runs with 100% resources (full 50 overs). If rain limits Team 2 to just 25 overs (and they have all 10 wickets), and the D/L table says 25 overs equals about 50% resources, then the par score is roughly 250 × (50% ÷ 100%) = 125. In that case, Team 2 would need 126 to win. (If Team 2 scores exactly 125, the match is a tie under D/L rules.)

When Team 1’s innings is shortened by rain, Team 1’s resources R1 drop below 100%. Team 2 might still have full overs (R2 = 100%). In that case R2 > R1, so the formula must increase Team 2’s target above Team 1’s score. The extra runs correspond to Team 1’s lost potential. The official method uses an average scoring rate factor called G50 (for example, around 245 in top-level ODIs) to compute how many runs those extra resources are worth. In practice, the calculation is handled by software or tables, but the principle remains: more resources for Team 2 means a higher target to win.

Calculating Team Resources

To apply the formula, the first step is finding each team’s available resources (R1 and R2) from D/L tables or software:

• R1 (Team 1’s resources): This is typically 100% if Team 1 bats a full innings with no interruptions. If rain cuts their innings short, R1 equals the table value for (overs they actually faced, 10 wickets if none lost).
• R2 (Team 2’s resources): This depends on how many overs Team 2 gets after the interruption and how many wickets they have. If Team 2 also faces rain, officials recalculate R2 after each delay.

Once R1 and R2 are known, the revised target is determined:

• If R2 < R1 (Team 2 has fewer resources), the target is lowered by multiplying Team 1’s score by (R2/R1) and then adding 1 run.
• If R2 > R1 (Team 2 has more resources), the target is increased. Roughly:

Revised target = Team 1’s score + G50 × (R2 – R1) / 100.

This adds the number of runs that would be expected on average from the extra resource percentage (R2 – R1).

Example of a Duckworth-Lewis par score on a live scoreboard. Team 1 scored 204. After a rain delay, Team 2’s adjusted par score is shown as 153. This means Team 2 needs 154 to win (153 would tie) under the revised target.

Step-by-Step Example Calculations

Let’s walk through some simplified examples:

• Scenario 1: Team 2 has fewer overs (Target Reduction)
  1. Team 1 bats first in a 50-over game and scores 280 runs (R1 = 100%).
  2. Rain delays play before Team 2’s innings. The match is reduced so Team 2 can only bat 30 overs. According to D/L tables, 30 overs with 10 wickets is about 65% resources (R2 ≈ 65%).
  3. Calculate par score: 280 × (65% ÷ 100%) = 182 (par). This is the score Team 2 would tie with. Therefore, Team 2 needs 183 to win.
  4. If Team 2 scores exactly 182, it’s a tie; 183 wins. This 183 is the revised target for Team 2 in 30 overs.
• Scenario 2: Team 1’s innings shortened (Target Increase)
  1. In another game, Team 1 bats first but rain cuts their innings to 25 overs instead of 50. They score 180 runs in those 25 overs. (Here R1 might be ~50% for 25 overs and 10 wickets.)
  2. After the break, Team 2 is allowed a full 50 overs (R2 = 100%). Team 2 therefore has 50% more resources than Team 1.
  3. Extra runs = G50 × (R2 – R1) / 100 = 245 × (100% – 50%) = 122.5, rounding to 123.
  4. Revised target = 180 + 123 = 303 to tie, so Team 2 needs 304 to win.

These examples show how the target changes. In practice, match officials use an official D/L (DLS) calculator or charts to do these steps quickly, but the essence is: compare resource percentages and scale the target up or down accordingly.

Common Match Scenarios

Cricket rules define how and when to apply D/L adjustments. Common situations include:

• Delayed start (before Team 1’s innings): If rain delays the start and both teams know the reduced overs from the beginning, no adjustment is needed. Both sides have equal resources from the start, so the target stays the same (just scoring one more run than Team 1’s score to win).
• Interruption during Team 1’s innings (Target increase): If Team 1’s innings is cut short by rain, Team 1 had fewer resources (lower R1). If Team 2 still gets the full quota of overs (higher R2), Team 2’s target will be higher than Team 1’s actual score. The increase compensates for the overs Team 1 didn’t have, making the chase as hard as if Team 1 had batted fully.
• Interruption during Team 2’s innings (Target decrease): If Team 2’s innings is interrupted (losing overs while chasing), Team 2’s resources drop (lower R2). D/L reduces the target in proportion to the lost overs. After each suspension, the par score (and hence remaining target) is recalculated downward. Team 2 is always allowed to score at least as many runs as they already have, so delays don’t penalize them beyond reducing the final target.
• Tie and Par Score: The D/L par score is the number of runs Team 2 needs to tie the match under the revised conditions. One more run than the par score is needed to win. For example, if the par score is 153, then 153 is a tie and 154 wins the game. Some modern scoreboards explicitly display this “par” number for clarity.
• Multiple interruptions: If rain interrupts play multiple times (in either innings), officials recalculate resources after each break. The net effect on the target can include both increases and decreases, depending on how overs are lost. The D/L procedure handles each interruption in turn to arrive at the final target.

In practice, the revised target or par score is usually announced once play resumes (or through live scoring apps). For example, many TV broadcasts and live score systems display the updated D/L target or current par score after every over so that teams and fans can follow exactly how many runs are needed at any point.

Duckworth-Lewis-Stern (DLS): The Updated Method

In November 2014, the method was officially updated and renamed Duckworth-Lewis-Stern (DLS) after Australian statistician Professor Steven Stern took over its custodianship. Stern refined the original tables and formulas using modern scoring data, especially to account for the faster run rates in Twenty20 cricket. Despite the new name, the core concept is unchanged.

Key points about the DLS version:

• Modern data: The DLS tables use recent scoring data so that teams’ current playing styles (like big hitting in T20s) are accurately represented.
• Format-specific tables: DLS provides separate resource tables for different match formats. For example, the resources for a 20-over match differ from a 50-over match. Using the correct table ensures targets stay fair in T20s, ODIs, or even 10-over games.
• ICC mandate: The International Cricket Council requires the use of the DLS method (via approved software) in any official match where overs can be lost. The playing conditions specify that if an innings is interrupted after it starts, the DLS calculator must be used to set the new target. (If computers fail, there are backup procedures, but generally the software does the computation instantly.)
• World Cup usage: The Duckworth-Lewis method was first used in the Cricket World Cup in 2001. By the 2015 World Cup, the revised DLS tables were in place. Today’s major tournaments and leagues all follow DLS for rain rules.
• G50 values: The DLS method uses a parameter called G50 when Team 1’s innings is cut short. The ICC sets G50 = 245 for ODIs between full-member teams (so extra runs are based on an average 245-run innings). For matches between lesser teams, a lower G50 (like 200) may be used. This ensures the target increase reflects the expected scoring level of the match.

Despite the new name, commentators and fans often still say “Duckworth-Lewis.” Both D/L and DLS refer to the same underlying system. The update ensures the method stays accurate as the game evolves, but the goal – a fair target in rain-affected matches – remains the same.

Criticisms and Controversies

The D/L/DLS method is widely accepted, but it has had its critics:

• Complexity and Transparency: Casual fans and some players can find D/L confusing because the adjustments aren’t intuitive without explanation. The revised target often appears suddenly on the scoreboard, and people may not immediately understand why it changed. Historically, the exact formulas and tables were proprietary, which added to the mystery (modern software has alleviated this somewhat).
• Unexpected targets: In very high-scoring games or unusual situations, the D/L-adjusted target can look odd. For example, sometimes the target might seem too easy or too hard compared to the match context. However, statistical analyses show that on average D/L is quite fair. When odd cases happen, it’s usually because the particular scoring patterns differ from the historical average that D/L uses.
• No match specifics: The method is based on historical scoring patterns and does not account for specific match conditions like pitch behavior, team strengths, or weather besides overs lost. Critics note that two games with the same overs/wickets situation might not actually be equally difficult in practice. D/L cannot factor in something like a batting-friendly pitch or an extremely strong batting lineup.
• Need for updates: When the method first came out, it worked well for ODIs but needed tweaks for the higher run rates in T20s. That’s why Stern’s update was necessary. In the future, if scoring trends change (for example, even higher power hitting), further adjustments may be needed.
• Historical examples: Some infamous rain-affected matches highlighted the need for better rules. A famous example is the 1992 World Cup semi-final between England and South Africa, where the target calculation under the old method was widely criticized. Controversies like that motivated cricket boards to adopt a robust mathematical rule like D/L.

Even with these criticisms, almost everyone agrees that D/L is the fairest solution currently available. Alternatives tested in the past (like just using run rates) proved more unsatisfactory. The D/L method is periodically reviewed and updated (as with DLS) to maintain its fairness as the sport evolves.

Key Takeaways

• Purpose: The Duckworth-Lewis Method is used to set a fair revised target in rain-affected limited-overs cricket matches. It’s often called the rain rule.
• Resources-based: It treats overs remaining and wickets in hand as combined resources. Each possible combination of overs/wickets corresponds to a resource percentage.
• Adjusting targets: If the chasing team has fewer resources than the first team, their target is reduced proportionally. If they have more resources (because the first innings was shortened), their target is increased to compensate.
• Par score: The par score is the score that would tie the match. The chasing team must score one more run than the par to win. A scoreboard might show the par or revised target directly.
• Modern DLS: Since 2014 the method has been updated as Duckworth-Lewis-Stern, with refined tables. It is now mandatory in international ODIs and T20s.
• Applicability: The method only applies to one-innings limited-overs games (ODIs, T20s, etc.). It is not used in Test cricket or multi-day matches.
• Predictive fairness: While D/L can be complex, it’s grounded in statistics. Its goal is fairness: each team faces an equally challenging task even if rain intervenes.

In the end, the Duckworth-Lewis (or DLS) method represents the game’s commitment to fairness. Every time rain interrupts play, these calculations ensure that both teams face an equally challenging task, rain or shine. For cricket fans, knowing the basics of D/L makes watching rain-affected games more understandable and fair.

Key Terms and Definitions

• Par score: In D/L, the par score is the number of runs the second team needs to tie the match under the adjusted conditions. One more than the par is needed to win.
• Resources (R1, R2): Percentages representing the batting resources a team has, combining remaining overs and wickets. For example, 100% means a full innings with no interruptions.
• G50: A factor used when Team 1’s innings is shortened. It represents the average 50-over score (e.g. about 245 in ODI cricket) and is used to calculate extra runs for any additional resources.
• Duckworth-Lewis-Stern (DLS): The current name of the method (since 2014) after the latest revision by Professor Steven Stern. Often still called just D/L.
• Software/Calculator: Modern matches use official D/L (DLS) software to compute targets instantly. Traditional paper tables of resource percentages exist only as a backup (for umpires in case of computer failure).
• Live par score: On modern scoreboards or broadcasts, once D/L is in effect, the par score is updated after each ball or over. This lets teams and fans track exactly how many runs are needed to tie or win at any point.
• Limited-overs matches only: Duckworth-Lewis applies only to games where each team has a fixed overs quota (ODIs, T20s, etc.). It is not used in Test cricket or other multi-day formats.

Understanding these terms helps clarify how the method adjusts scores. The combination of resources and average scoring assumptions is what makes the Duckworth-Lewis method a fair “rain rule” solution.

Recommended

• Texas Football Friday Night Lights – The Soul of the Game
• Cricket Fielding Positions Explained A Complete Guide for Beginners 2026
• Duckworth Lewis Method Explained Rules, Formula, and Scenarios
• Iowa High School Cancels Football Season Amid Growing Concerns
• WNBA Safety Nets and the Evolution of Player Support 2026