The Duckworth–Lewis (D/L) method is a mathematical formulation designed to calculate the target score for the team batting second in a limited overs cricket match interrupted by weather or other circumstances. It is generally accepted to be the most accurate method of setting a target score. The D/L method was devised by two English statisticians, Frank Duckworth and Tony Lewis. After their retirements Professor Steven Stern became the custodian of the method. In November 2014, it was renamed the Duckworth–Lewis–Stern method (or D/L/S method).
The basic principle is that each team in a limited-overs match has two resources available with which to score runs: wickets remaining, and overs to play. Where overs are lost, setting an adjusted target for the team batting second is not as simple as reducing the run target proportionally to the loss in overs, because a team with ten wickets in hand and 25 overs to bat can be expected to play more aggressively than if they had ten wickets and a full 50 overs, for example, and can consequently achieve a higher run rate. The Duckworth–Lewis method is an attempt to set a statistically fair target for the second team's innings, based on the score achieved by the first team, taking their wickets lost and overs played into account.
- 1 History and creation
- 2 Theory
- 3 Examples
- 4 Use and updates
- 5 Target score calculations
- 6 Example Standard Edition Target score calculations
- 6.1 Reduced target: Team 1's innings completed; Team 2's innings delayed (i.e. resources lost at the start of the innings)
- 6.2 Reduced target: Team 1's innings completed; Team 2's innings cut short (i.e. resources lost at the end of the innings)
- 6.3 Reduced target: Team 1's innings completed; Team 2's innings interrupted (i.e. resources lost in the middle of the innings)
- 6.4 Increased target: Team 1's innings cut short (i.e. resources lost at the end of the innings); Team 2's innings completed
- 6.5 Increased target: Multiple interruptions in Team 1's innings (i.e. resources lost in the middle of the innings); Team 2's innings completed
- 7 In-game strategy
- 8 Other uses
- 9 Criticism
- 10 Cultural influence
- 11 References
- 12 Further reading
- 13 External links
History and creation
Various different methods had been used previously to resolve rain-affected cricket games. The most common were the average run-rate method, and the most productive overs method.
The average run-rate method had been replaced in the early 1990s by the most productive overs method, developed by Australians after a 1989 World Series final between Australia and the West Indies. Chasing Australia's 226/4 off 38 overs, the West Indies needed 180 off 31.2 overs. Rain stopped play for one hour and 25 minutes, and under the average run-rate method, the revised target was 61 runs off the 11.2 overs that remained. The West Indies won the match and the competition with 4.4 overs remaining and eight wickets in hand. Australian fans booed this unsatisfactory conclusion, which was criticised by the media and Australia's captain. In this match, the D/L method would have increased the West Indies' target to 232 to take into account a two-hour rain delay during Australia's innings, and then revised the target to 139 after the second interruption.
The D/L method was devised by two British statisticians, Frank Duckworth and Tony Lewis, as a result of the outcome to the semi-final in the 1992 Cricket World Cup between England and South Africa, where the most productive overs method was used. Rain stopped play for 12 minutes with South Africa needing 22 runs from 13 balls chasing England's 252/6 off 45 overs. The revised target left South Africa needing 21 runs from one ball, which was a reduction of only one run compared to a reduction of two overs, and a preposterous target given that the maximum score from one ball is generally six runs.
The D/L method avoids this flaw: in this match, the revised D/L target would have left South Africa four to tie or five to win from the final ball.
The earlier methods had flaws that were easily exploitable. The average run-rate method took no account of how many wickets were lost by the team batting second, but simply reflected how quickly they were scoring when the match was interrupted. So, if a team felt a rain stoppage was likely, they could attempt to force the scoring rate without regard for the corresponding highly likely loss of wickets, skewing the comparison with the first team. The most productive overs method also took no account of wickets lost by the team batting second, and effectively penalized the team batting second for good bowling, by ignoring their best overs in setting the revised target.
Duckworth said, "I recall hearing Christopher Martin-Jenkins on radio saying 'surely someone, somewhere could come up with something better' and I soon realised that it was a mathematical problem that required a mathematical solution."
Duckworth and Lewis's method was first used in international cricket in the 1996–97 Zimbabwe versus England One Day International series in the second match. Zimbabwe won the match by seven runs. The D/L method was formally adopted by the International Cricket Council in 1999 as the standard method of calculating target scores in rain-shortened one-day matches.
The essence of the D/L method is 'resources'. Each team is taken to have two 'resources' to use to make as many runs as possible: the number of overs they have to receive; and the number of wickets they have in hand. At any point in any innings, a team's ability to score more runs depends on the combination of these two resources. Looking at historical scores, there is a very close correspondence between the availability of these resources and a team's final score, a correspondence which D/L exploits.
Using a published table or computer which gives the percentage of these combined resources remaining for any number of overs (or, more accurately, balls) left and wickets lost, the target score can be adjusted up or down to reflect the loss of resources to one or both teams when a match is shortened one or more times. The two teams' resource percentages are found, and used to calculate a 'par score' for the second team that is usually a fractional number of runs. The target score is this number rounded up to the next integer, and the score to tie (also called the par score), is this number rounded down to the preceding integer. If the second team reaches or passes the target score, then they have won the match. If the match ends when the second team has exactly met (but not passed) the par score then the match is a tie. If the second team fail to reach the par score then they have lost.
In the version of D/L most commonly in use in international and first-class matches (the 'Professional Edition'), the target for the team batting second ('Team 2') is adjusted up or down from the total the team batting first ('Team 1') scored, in proportion to the two teams' resources (combination of overs and wickets available), i.e.
If, as usually occurs, this 'par score' is a non-integer number of runs, then Team 2's target to win is this number rounded up to the next integer, and the score to tie (also called the par score), is this number rounded down to the preceding integer. For example, if a rain delay means that Team 2 only has 90% of the resources that were available to Team 1, and Team 1 scored 254, then 254 × 90% = 228.6, so Team 2's target is 229, and the score to tie is 228. The actual resource values used in the Professional Edition are not publicly available, so a computer must be used which has the software loaded.
If it's a 50-over match and Team 1 completed its innings uninterrupted, then they had 100% resource available to them, so the formula simplifies to:
Summary of impact on Team 2's target
- If there is a delay before the first innings starts, so that the numbers of overs in the two innings are reduced (but still the same as each other), then D/L will make no change to the target score. This is because both sides will be in the same position of having the same number of overs and 10 wickets available, and they will know this throughout their innings, thus having the same amount of resource available.
- Team 2's target score is first calculated once Team 1's innings has finished.
- If there were interruption(s) during Team 1's innings, or Team 1's innings was cut short, so the numbers of overs in the two innings are reduced (but still the same as each other), then (in the Professional Edition) D/L will adjust Team 2's target score as described above.
- The adjustment to Team 2's target after interruptions in Team 1's innings is often an increase, implying that Team 2 has more resource available than Team 1 had.
- Although both teams have 10 wickets and the same (reduced) number of overs available, an increase is fair as, for some of their innings, Team 1 thought they would have more overs available than they actually ended up having.
- If Team 1 had known that their innings was going to be shorter, they would have batted less conservatively, and scored more runs at the expense of more wickets. They saved some wicket resource to use up in the overs that ended up being cancelled, which Team 2 doesn't need to do, therefore Team 2 has more resource to use in the same number of overs. Therefore, increasing Team 2's target score compensates Team 1 for the denial of some of the overs they thought they would get to bat.
- If there are interruption(s) to Team 2's innings, either before it starts, during, or it's cut short, then D/L will reduce Team 2's target score from the initial target set at the end of Team 1's innings, in proportion to the reduction in Team 2's resources. If there are multiple interruptions in the second innings, the target will be adjusted downwards each time.
- If there are interruptions which both increase and decrease the target score, then the net effect on the target could be either an increase or decrease, depending on which interruptions were bigger.
Stoppage in first innings
In the 4th India – England ODI in the 2008 series, the first innings was interrupted by rain on two occasions, resulting in the match being reduced to 22 overs each. India (batting first) made 166/4. England's target was set by the D/L method at 198 from 22 overs. As England knew they had only 22 overs the expectation is that they will be able to score more runs from those overs than India had from their (interrupted) innings. England made 178/8 from 22 overs, and so the match was listed as "India won by 19 runs (D/L method)".
During the fifth ODI between India and South Africa in January 2011, rain halted play twice during the first innings. The match was reduced to 46 overs each and South Africa scored 250/9. The D/L method was applied which adjusted India's target to 268. As the number of overs was reduced during South Africa's innings, this method takes into account what South Africa are likely to have scored if they'd known throughout their innings that it would only be 46 overs long.
On 3 December 2014, Sri Lanka played England and batted first, but play was interrupted when Sri Lanka had scored 6/1 from 2 overs. At the restart both innings were reduced to 35 overs, and Sri Lanka finished on 242/8. England's target was set by D/L at 236 from 35 overs. Although Sri Lanka had less resource remaining to them after the interruption than England would have for their whole innings (about 7% less), they'd used up so much resource before the interruption (2 overs and 1 wicket, about 8%), that the total resource used by Sri Lanka was still slightly more than England would have available, hence the slightly decreased target for England.
Stoppage in second innings
A simple example of the D/L method being applied was the first ODI between India and Pakistan in their 2006 ODI series. India batted first, and were all out for 328. Pakistan, batting second, were 311/7 when bad light stopped play after the 47th over. Pakistan's target, had the match continued, was 18 runs in 18 balls, with three wickets in hand. Considering the overall scoring rate throughout the match, this is a target most teams would be favoured to achieve. And indeed, application of the D/L method resulted in a retrospective target score of 305 (or par score of 304) at the end of the 47th over, with the result therefore officially listed as "Pakistan won by 7 runs (D/L Method)".
The D/L method was used in the group stage match between Sri Lanka and Zimbabwe at the 20/20 World Cup in 2010. Sri Lanka scored 173/7 in 20 overs batting first, and in reply Zimbabwe were 4/0 from 1 over when rain interrupted play. At the restart Zimbabwe's target was reduced to 108 from 12 overs, but rain stopped the match when they had scored 29/1 from 5 overs. The retrospective D/L target from 5 overs was a further reduction to 44, or a par score of 43, and hence Sri Lanka won the match by 14 runs.
An example of a D/L tied match was the ODI between England and India on 11 September 2011. This match was frequently interrupted by rain in the final overs, and a ball-by-ball calculation of the Duckworth–Lewis 'par' score played a key role in tactical decisions during those overs. At one point, India were leading under D/L during one rain delay, and would have won if play had not resumed. At a second rain interval, England, who had scored some quick runs (knowing they needed to get ahead in D/L terms) would correspondingly have won if play had not resumed. Play was finally called off with just 7 balls of the match remaining and England's score equal to the Duckworth–Lewis 'par' score, therefore resulting in a tie.
This example does show how crucial (and difficult) the decisions of the umpires can be, in assessing when rain is heavy enough to justify ceasing play. If the umpires of that match had halted play one ball earlier, England would have been ahead on D/L, and so would have won the match. Equally, if play had stopped one ball later, India could have won the match with a dot ball – indicating how finely-tuned D/L calculations can be in such situations.
Stoppages in both innings
During the 2012/13 KFC Big Bash League, D/L was used in the 2nd semi-final played between the Melbourne Stars and the Perth Scorchers. After rain delayed the start of the match, it interrupted Melbourne's innings when they had scored 159/1 off 15.2 overs, and both innings were reduced by 2 overs to 18, and Melbourne finished on 183/2. After a further rain delay reduced Perth's innings to 17 overs, Perth returned to the field to face 13 overs, with a revised target of 139. Perth won the game by 8 wickets with a boundary off the final ball.
Use and updates
The published table that underpins the D/L method is regularly updated, using source data from more recent matches.
For 50-over matches decided by D/L, each team must face at least 20 overs for the result to be valid. For Twenty20 games decided by D/L, each side must face at least five overs. These minimum limits do not apply to innings where a team is bowled out or reaches its target early.
If the conditions prevent a match from reaching this minimum length, it is declared a no result.
Until 2003, a single version of D/L was in use. This used a single published reference table of total resource percentages remaining for all possible combinations of overs and wickets, and some simple mathematical calculations, and was relatively transparent and straightforward to implement. However, it had a known flaw in how it handled very high first innings scores (350+).
In 2002 the resource percentages were revised, following an extensive analysis of limited overs matches, there was a change to the "G50" for ODIs. (G50 is the average score expected from the team batting first in an uninterrupted 50 overs-per-innings match.) G50 was changed to 235 for ODIs. These changes came into effect on 1 September 2002. As of 2014, these resource percentages are the ones still in use in the Standard Edition, though G50 has subsequently changed.
The tables show how the percentages were in 1999 and 2001, and what they were changed to in 2002. Mostly they were reduced.
From the 1999 Cricket World Cup match in Bristol between India and Kenya, Tony Lewis noticed that there was an inherent weakness in the formula used at the time that would give a noticeable advantage to the side chasing a total in excess of 350. A correction was built into the formula and the software, but was not fully adopted by users until 2004. One-day matches were achieving significantly higher scores than in previous decades, affecting the historical relationship between resources and runs.
The second version uses more sophisticated statistical modelling, but does not use a single table of resource percentages. Instead, the percentages also vary with score, so a computer is required. Therefore, it loses some of the previous advantages of transparency and simplicity.
The original version was named the Standard Edition, and the new version was named the Professional Edition. Tony Lewis said, 'We were then [at the time of the 2003 Cricket World Cup Final] using what is now known as the Standard Edition. [...] Australia got 359 and that showed up the flaws and straightaway the next edition was introduced which handled high scores much better. The par score for India is likely to be much higher now.'
Duckworth and Lewis wrote, 'When the side batting first score at or below the average for top level cricket..., the results of applying the Professional Edition are generally similar to those from the Standard Edition. For higher scoring matches, the results start to diverge and the difference increases the higher the first innings total. In effect there is now a different table of resource percentages for every total score in the Team 1 innings.' The Professional Edition has been in use in all international one-day cricket matches since early 2004.
The decision on which edition should be used is for the cricket authority which runs the particular competition. The ICC Playing Handbook requires the use of the Professional Edition for internationals. This also applies to most countries’ national competitions. At lower levels of the game, where use of a computer cannot always be guaranteed, the Standard Edition is used.
In June 2009, it was reported that the D/L method would be reviewed for the Twenty20 format after its appropriateness was questioned in the quickest version of the game. Lewis was quoted admitting that "Certainly, people have suggested that we need to look very carefully and see whether in fact the numbers in our formula are totally appropriate for the Twenty20 game."
For the 2015 World Cup, the ICC implemented the Duckworth–Lewis–Stern formula, which included work by the new custodian of the method, Professor Steven Stern, from the Department of Statistics at Queensland University of Technology. These changes recognised that teams need to start out with a higher scoring rate when chasing high targets rather than keep wickets in hand.
Target score calculations
Using the notation of the ICC Playing Handbook, the team that bats first is called Team 1, their final score is called S, the total resources available to Team 1 for their innings is called R1, the team that bats second is called Team 2, and the total resources available to Team 2 for their innings is called R2.
|Overs remaining||Wickets in hand|
Step 1. Find the batting resources available to each team
After each reduction in overs, the new total batting resources available to the two teams are found, using figures for the total amount of batting resources remaining for any combination of overs and wickets. While the process for converting these resources remaining figures into total resource available figures is the same in the two Editions, this can be done manually in the Standard Edition, as the resource remaining figures are published in a reference table. However, the resource remaining figures used in the Professional Edition are not publicly available, so a computer must be used which has the software loaded.
- If a team loses resource at the start of an innings (left hand image below), then this is simple. For example, if the first 20 overs of an innings are lost, then 30 overs and 10 wickets are remaining, which is 75.1% in the Standard Edition, so this is the resource available.
- If a team loses resource at the end of its innings (centre image below), then the resource that was available to that team is found by taking the resources it had at the start, and subtracting the resources remaining at the point the innings was ended. For example, if a team starts with 50 overs and 10 wickets (100% of its resources), but its innings is ended with 20 overs and 8 wickets remaining (52.4% of its resources), then the resources it actually used is 100% − 52.4% = 47.6%.
- If a team loses resource in the middle of its innings (right hand image below), then the resource that was available to that team is found by taking the resources it had at the start, and subtracting the resources remaining at the point the innings was interrupted (to give the resources used in the first period of the innings), then adding on the resource remaining at the restart. For example, if a team starts with 50 overs and 10 wickets (100% of its resources), but is interrupted when it still has 40 overs and 8 wickets remaining (77.8% of its resources), and restarted when it has 20 overs and 8 wickets remaining (52.4% of its resources), then the resources it actually used is 100% − 77.8% + 52.4% = 74.6%. Another way of looking at this is to say it lost the resources available between 40 overs and 8 wickets (77.8%) and 20 overs and 8 wickets (52.4%), i.e. 77.8% − 52.4% = 25.4%, so its total resource available was 100% − 25.4% = 74.6%.
These are just the different ways of having one interruption. With multiple interruptions possible, it may seem like finding the total resource percentage requires a different calculation for each different scenario. However, the formula is actually the same each time − it's just that different scenarios, with more or less interruptions and restarts, need to use more or less of the same formula. The total resources available to a team are given by:
which can alternatively be written as:
Each time there's an interruption or a restart after an interruption, the resource remaining percentages at those times (obtained from a reference table for the Standard Edition, or from a computer for the Professional Edition) can be entered into the formula, with the rest left blank. Note that a delay at the start of an innings counts as the 1st interruption.
Step 2. Convert the two teams' batting resources into Team 2's target score
- If R2 < R1, reduce Team 2's target score in proportion to the reduction in total resources, i.e. S × R2/R1.
- If R2 = R1, no adjustment to Team 2's target score is needed.
- If R2 > R1, increase Team 2's target score by the extra runs that could be expected to be scored on average with the extra total resource, i.e. S + G50 × (R2 – R1)/100, where G50 is the average 50-over total. Team 2's target score is not simply increased in proportion to the increase in total resources, i.e. S × R2/R1, as this 'could lead to some unrealistically high targets if Team 1 had achieved an early high rate of scoring [in the powerplay overs] and rain caused a drastic reduction in the overs for the match.' Instead, D/L Standard Edition requires average performance for Team 2's additional resource over Team 1.
G50 is the average score expected from the team batting first in an uninterrupted 50 overs-per-innings match. This will vary with the level of competition and over time. The annual ICC Playing Handbook gives the values of G50 to be used each year when the D/L Standard Edition is applied:
|Period||Matches involving ICC full member nations||Matches between teams that play first-class cricket||Under-19 internationals||Under-15 internationals||Matches between ICC associate member nations||Women’s ODIs|
|1999 − 31 Aug 2002 ||225||?|
|1 Sep 2002 − 2006 ||235|
Duckworth and Lewis write, 'We accept that the value of G50, perhaps, should be different for each country, or even for each ground, and there is no reason why any cricket authority may not choose the value it believes to be the most appropriate. In fact it would be possible for the two captains to agree a value of G50 before the start of each match, taking account of all relevant factors. However, we do not believe that something that is only invoked if rain interferes with the game should impose itself on every game in this way. In any case, it should be realised that the value of G50 usually has very little effect on the revised target. If 250 were used, for instance, instead of 235, it is unlikely that the target would be more than two or three runs different.'
- If R2 < R1, reduce Team 2's target score in proportion to the reduction in total resources, i.e. S × R2/R1.
- If R2 = R1, no adjustment to Team 2's target score is needed.
- If R2 > R1, increase Team 2's target score in proportion to the increase in total resources, i.e. S × R2/R1. The problem of early high scoring rates potentially producing anomalously high targets has been overcome in the Professional Edition, which is essentially 'a different table of resource percentages for every total score in the Team 1 innings.' Therefore, Team 2's target score can be simply increased in proportion to the increase in total resources when R2 > R1, and there is no G50.
Example Standard Edition Target score calculations
As the resource percentages used in the Professional Edition are not publicly available, it is difficult to give examples of the D/L calculation for the Professional Edition. Therefore, examples are given from when the Standard Edition was widely used, which was up to early 2004.
Reduced target: Team 1's innings completed; Team 2's innings delayed (i.e. resources lost at the start of the innings)
|Overs remaining||Wickets in hand|
On 18 May 2003, Lancashire played Hampshire in the National League. Rain before play reduced the match to 30 overs each. Lancashire batted first and scored 231–4 from their 30 overs. Before Hampshire began their innings, it was further reduced to 28 overs.
|Total resources available to Lancashire (R1)||30 overs and 10 wickets||75.1%|
|Total resources available to Hampshire (R2)||28 overs and 10 wickets||71.8%|
|Hampshire's par score||231 x R2/R1 = 231 x 71.8/75.1||220.850 runs|
Hampshire's target was therefore 221 to win (in 28 overs), or 220 to tie. They were all out for 150, giving Lancashire victory by 220 − 150 = 70 runs.
If Hampshire's target had been set by the average run rate method (simply in proportion to the reduction in overs), their par score would have been 231 x 28/30 = 215.6, giving 216 to win or 215 to tie. While this would have kept the required run rate the same as Lancashire achieved (7.7 runs per over), this would have given an unfair advantage to Hampshire as it's easier to achieve and maintain a run rate for a shorter period. Increasing Hampshire's target from 216 overcomes this flaw.
As Lancashire's innings was interrupted once (before it started), and then re-started, their resource can be found from the general formula above as follows (Hampshire's is similar): Total resources = 100% − Resources remaining at 1st interruption + Resources remaining at 1st restart = 100% − 100% + 75.1% = 75.1%.
Reduced target: Team 1's innings completed; Team 2's innings cut short (i.e. resources lost at the end of the innings)
|Overs remaining||Wickets in hand|
On 3 March 2003, Sri Lanka played South Africa in the 2003 Cricket World Cup Pool B. Sri Lanka batted first and scored 268–9 from their 50 overs. Chasing a target of 269, South Africa had reached 229–6 from 45 overs when play was abandoned.
|Total resources available to Sri Lanka (R1)||50 overs and 10 wickets||100.0%|
|Total resources available to South Africa at the start of their innings||50 overs and 10 wickets||100.0%|
|Total resources remaining to South Africa when play abandoned||5 overs and 4 wickets||14.3%|
|Total resources available to South Africa (R2)||100.0% − 14.3%||85.7%|
|South Africa's par score||268 × R2/R1 = 268 × 85.7/100.0||229.676 runs|
Therefore, South Africa's retrospective target from their 45 overs was 230 runs to win, or 229 to tie. In the event, as they had scored exactly 229, the match was declared a tie.
South Africa scored no runs off the very last ball. If play had been abandoned without that ball having been bowled, the resource available to South Africa at the abandonment would have been 14.7%, giving them a par score of 228.6, and hence victory.
As South Africa's innings was interrupted once (and not re-started), their resource is given by the general formula above as follows: Total resources available = 100% − Resources remaining at 1st interruption = 100% − 14.3% = 85.7%.
Reduced target: Team 1's innings completed; Team 2's innings interrupted (i.e. resources lost in the middle of the innings)
On 16 February 2003, New South Wales played South Australia in the ING Cup. New South Wales batted first and scored 273 all out (from 49.4 overs). Chasing a target of 274, rain interrupted play when South Australia had reached 70–2 from 19 overs, and at the restart their innings was reduced to 36 overs (i.e. 17 remaining).
|Total resources available to New South Wales (R1)||50 overs and 10 wickets||100.0%|
|Total resources available to South Australia at the start of their innings||50 overs and 10 wickets||100.0%|
|Total resources remaining to South Australia at the interruption||31 overs and 8 wickets||68.6%|
|Total resources remaining to South Australia at the restart||17 overs and 8 wickets||46.7%|
|Total resources lost to South Australia by the interruption||68.6% − 46.7%||21.9%|
|Total resources available to South Australia (R2)||100.0% − 21.9%||78.1%|
|South Australia's par score||273 × R2/R1 = 273 × 78.1/100.0||213.213 runs|
South Australia's new target was therefore 214 to win (in 36 overs), or 213 to tie. In the event, they were all out for 174, so New South Wales won by 213 − 174 = 39 runs.
As South Australia's innings was interrupted once and re-started once, their resource is given by the general formula above as follows: Total resources available = 100% − Resources remaining at 1st interruption + Resources remaining at 1st restart = 100% − 68.6% + 46.7% = 78.1%.
Increased target: Team 1's innings cut short (i.e. resources lost at the end of the innings); Team 2's innings completed
On 25 January 2001, West Indies played Zimbabwe. West Indies batted first and had reached 235–6 from 47 overs (of a scheduled 50) when rain halted play for two hours. At the restart, both innings were reduced to 47 overs, i.e. West Indies' innings was closed immediately, and Zimbabwe began their innings.
|Total resources available to West Indies at the start of their innings||50 overs and 10 wickets||100.0%|
|Total resources remaining to West Indies when innings was closed||3 overs and 4 wickets||10.2%|
|Total resources available to West Indies (R1)||100.0% − 10.2%||89.8%|
|Total resources available to Zimbabwe (R2)||47 overs and 10 wickets||97.4%|
|Zimbabwe's par score||235 + G50 × (R2 − R1)/100 = 235 + 225 × (97 − 89.8)/100||252.100 runs|
Zimbabwe's target was therefore 253 to win (in 47 overs), or 252 to tie. It is fair that their target was increased, even though they had the same number of overs to bat as West Indies, as West Indies would have batted more aggressively in their last few overs, and scored more runs, if they had known that their innings would be cut short at 47 overs. Zimbabwe were all out for 175, giving West Indies victory by 252 − 175 = 77 runs.
These resource percentages are the ones which were in use back in 2001, before the 2002 revision, and so do not match the currently used percentages for the Standard Edition, which are slightly different. Also, the formula for Zimbabwe's par score comes from the Standard Edition of D/L, which was used at the time. Currently the Professional Edition is used, which has a different formula when R2>R1. The formula required Zimbabwe to match West Indies' performance with their overlapping 89.8% of resource (i.e. score 235 runs), and achieve average performance with their extra 97.4% − 89.8% = 7.6% of resource (i.e. score 7.6% of G50 (225 at the time) = 17.1 runs).
As West Indies' innings was interrupted once (and not re-started), their resource is given by the general formula above as follows: Total resources available = 100% − Resources remaining at 1st interruption = 100% − 10.2% = 89.8%.
Increased target: Multiple interruptions in Team 1's innings (i.e. resources lost in the middle of the innings); Team 2's innings completed
- Rain stopped play when they had reached 109–2 from 25 overs (i.e. 22 remaining). At the restart both innings were reduced to 44 overs (i.e. 19 remaining for Australia).
- Rain stopped play again when Australia had reached 123–2 from 28 overs (i.e. 16 remaining), and at the restart both innings were reduced further to 36 overs (i.e. 8 remaining for Australia).
Australia finished on 170–2 from their 36 overs.
|Total resources available to Australia at the start of their innings||47 overs and 10 wickets||97.1%|
|Total resources remaining to Australia at interruption||22 overs and 8 wickets||55.8%|
|Total resources remaining to Australia at restart||19 overs and 8 wickets||50.5%|
|Total resources lost by interruption||55.8% − 50.5%||5.3%|
|Total resources remaining to Australia at interruption||16 overs and 8 wickets||44.7%|
|Total resources remaining to Australia at restart||8 overs and 8 wickets||25.5%|
|Total resources lost by interruption||44.7% − 25.5%||19.2%|
|Total resources available to Australia (R1)||97.1% − 5.3% − 19.2%||72.6%|
|Total resources available to Netherlands (R2)||36 overs and 10 wickets||84.1%|
|Netherlands' par score||170 + G50 × (R2 − R1)/100 = 170 + 235 × (84.1 − 72.6)/100||197.025 runs|
The Netherlands' target was therefore 198 to win (in 36 overs), or 197 to tie. It is fair that their target was increased, even though they had the same number of overs to bat as Australia, as Australia would have batted less conservatively in their first 28 overs, and scored more runs at the expense of more wickets, if they had known that their innings would only be 36 overs long. Increasing the Netherlands' target score neutralizes the injustice done to Australia when they were denied some of the overs to bat they thought they would get. The Netherlands were all out for 122, giving Australia victory by 197 − 122 = 75 runs.
This formula for Netherlands' par score comes from the Standard Edition of D/L, which was used at the time. Currently the Professional Edition is used, which has a different formula when R2>R1. The formula required Netherlands to match Australia's performance with their overlapping 72.6% of resource (i.e. score 170 runs), and achieve average performance with their extra 84.1% − 72.6% = 11.5% of resource (i.e. score 11.5% of G50 (235 at the time) = 27.025 runs).
After the match there were reports in the media that Australia had batted conservatively in their final 8 overs after the final re-start, to avoid losing wickets rather than maximising their numbers of runs, in belief that this would further increase the Netherlands' par score. However, if this is true, this belief was mistaken, in the same way that conserving wickets rather than maximising runs in the final 8 overs of a full 50-over innings would be a mistake. At that point the amount of resource available to each team was fixed (as long as there were no further rain interruptions), so the only undetermined number in the formula for Netherlands' par score was Australia's final score, so they should have tried to maximise this.
As Australia's innings was interrupted three times (once before it started) and re-started three times, their resource is given by the general formula above as follows:
Total resources available = 100% − Resources remaining at 1st interruption + Resources remaining at 1st restart − Resources remaining at 2nd interruption + Resources remaining at 2nd restart − Resources remaining at 3rd interruption + Resources remaining at 3rd restart = 100% − 100% + 97.1% − 55.8% + 50.5% − 44.7% + 25.5% = 72.6%.
During Team 1's innings
Strategy for Team 1
During Team 1's innings, the target score calculations (as described above), have not yet been made.
The objective of the team batting first is to maximise the target score which will be calculated for the team batting second, which (in the Professional Edition) will be determined by the formula:
For these three terms:
- Team 1's score: Team 1 will always increase Team 2's target by increasing their own score.
- At the start of Team 2's innings, Team 2's resources will be 10 wickets and the number of overs available, and Team 1 cannot affect this.
- Team 1's resources are given by:
If there will not be any future interruptions to Team 1's innings, then the amount of resource available to them is now fixed (whether there have been interruptions so far or not), so the only thing Team 1 can do to increase Team 2's target is increase their own score, ignoring how many wickets they lose (as in a normal unaffected match).
However, if there will be future interruptions to Team 1's innings, then an alternative strategy to scoring more runs is minimising the amount of resource they use before the coming interruption (i.e. preserving wickets). While the best overall strategy is obviously to both score more runs and preserve resources, if a choice has to be made between the two, sometimes preserving wickets at the expense of scoring runs ('conservative' batting) is a more effective way of increasing Team 2's target, and sometimes the reverse ('aggressive' batting) is true.
|Overs remaining||Wickets in hand|
For example, suppose Team 1 has been batting without interruptions, but thinks the innings will be cut short at 40 overs, i.e. with 10 overs left. (Then Team 2 will have 40 overs to bat, so Team 2's resource will be 89.3%.) Team 1 thinks by batting conservatively it can reach 200–6, or by batting aggressively it can reach 220–8:
|Runs Team 1 thinks it can score||200||220|
|Wickets Team 1 thinks it will have in hand||4||2|
|Resource remaining to Team 1 at cut-off||22.8%||11.4%|
|Resource used by Team 1||100% − 22.8% = 77.2%||100% − 11.4% = 88.6%|
|Team 2's par score||200 x 89.3% / 77.2%
= 231.35 runs
|220 x 89.3% / 88.6%
= 221.74 runs
Therefore, in this case, the conservative strategy achieves a higher target for Team 2.
|Overs remaining||Wickets in hand|
However, suppose instead that the difference between the two strategies is scoring 200–2 or 220–4:
|Runs Team 1 thinks it can score||200||220|
|Wickets Team 1 thinks it will have in hand||8||6|
|Resource remaining to Team 1 at cut-off||30.8%||28.3%|
|Resource used by Team 1||100% − 30.8% = 69.2%||100% − 28.3% = 71.7%|
|Team 2's par score||200 x 89.3% / 69.2%
= 258.09 runs
|220 x 89.3% / 71.7%
= 274.00 runs
In this case, the aggressive strategy is better.
Therefore, the best batting strategy for Team 1 ahead of a coming interruption isn't always the same, but varies with the facts of the match situation to date (runs scored, wickets lost, overs used, and whether there have been interruptions), and also with the opinions about what will happen with each strategy (how many further runs will be scored, further wickets will be lost, and further overs will be used? How likely are the coming interruptions, when will they happen, and how long will they last – will Team 1's innings be re-started?).
This example shows just two possible batting strategies, but in reality there could be a range of others, e.g. 'neutral', 'semi-aggressive', 'super-aggressive', or timewasting to minimise the amount of resource used by slowing the over rate. Finding which strategy is the best can only be found by inputting the facts and one's opinions into the calculations and seeing what emerges.
Of course, a chosen strategy may backfire. For example, if Team 1 chooses to bat conservatively, Team 2 may see this and decide to attack (rather than focus on saving runs), and Team 1 may both fail to score many more runs and lose wickets.
Note also that if there have already been interruptions to Team 1's innings, the calculation of total resource they use will be more complicated than this example.
Strategy for Team 2
During Team 1's innings, Team 2's objective is to minimise the target score they will be set. This is achieved by minimising Team 1's score, or (as above), if there will be future interruptions to Team 1's innings, alternatively by maximising the resource used by Team 1 (i.e. wickets lost or overs bowled) before that happens. Team 2 can vary their bowling strategy (between conservative and aggressive) to try and achieve either of these objectives, so this means doing the same calculations as above, inputting their opinions of future runs conceded, wickets taken and overs bowled in each bowling strategy, to see which one is best.
Also, Team 2 can encourage Team 1 to bat particularly conservatively or aggressively (e.g. through field settings).
During Team 2's innings
A target (from a given number of overs) is set for Team 2 at the start of its innings. If there will not be any future interruptions, then both sides can play to a finish in the normal way. However, if there are likely to be interruptions to Team 2's innings, then Team 2 will aim to keep itself ahead of the D/L par score, and Team 1 will aim to keep them behind it. This is because, if a match is abandoned before the given number of overs is complete, Team 2 is declared the winner if they're ahead of the par score, and Team 1 is declared the winner if Team 2 are behind the par score. A tie is declared if Team 2 are exactly on the par score. (This is provided a minimum number of overs has been bowled in Team 2's innings.)
The par score increases with every ball bowled and every wicket lost, as the amount of resource used increases. As an example, in the 2003 Cricket World Cup Final Australia batted first and scored 359 from 50 overs. As Australia completed their 50 overs, their total resources used R1=100%, so India's par score throughout their innings was: 359 x R2/100%, where R2 is the amount of resource used to that point. After 9 overs India were 57-1, and 41 overs and 9 wickets remaining equates to 85.3% of resources, so 100% − 85.3% = 14.7% had been used. India's par score after 9 overs was therefore 359 x 14.7%/100% = 52.773, which is rounded down to 52.
During the six balls of the 10th over India scored 0, 0, 0, 1 (from a no ball), loss of wicket, 0. At the start of the over India were ahead of the par score, but the loss of the wicket caused their par score to jump from 55 to 79, which put them behind the par score.
|Overs used||1 wicket lost||2 wickets lost||India's actual score|
|Resources remaining||Resources used (R2)||D/L par score||Resources remaining||Resources used (R2)||D/L par score|
There are uses of the D/L method other than finding the current official final target score for the team batting second in a match that has already been reduced by the weather.
Ball-by-ball par score
During the second team's innings, the number of runs a chasing side would expect to have scored on average with this number of overs used and wickets lost, if they were going to successfully match the first team's score, called the D/L par score, may be shown on a computer printout, the scoreboard and/or TV alongside the actual score, and updated after every ball. This can happen in matches which look like they're about to be shortened by the weather, and so D/L is about to be brought into play, or even in matches completely unaffected by the weather. This is:
- To help spectators and players understand whether the chasing side are doing better or worse than they would need to do on average to reach the target score.
- The score the batting team's score would be compared to determine which side had won, if the match had to be abandoned right then. It is the par score which is displayed, i.e. the score to tie. The target, to win, score is one run more than this. South Africa exited the 2003 World Cup after a resulting a draw with Sri Lanka by mistakenly believing the par score on the printout was the target score.
Net run rate calculation
It has been suggested that when a side batting second successfully completes the run chase, the D/L method could be used to predict how many runs they would have scored with a full innings (i.e. 50 overs in a One Day International), and use this prediction in the net run rate calculation.
This suggestion is in response to the criticisms of NRR that it doesn't take into account wickets lost, and that it unfairly penalizes teams which bat second and win, as those innings are shorter and therefore have less weight in the NRR calculation than other innings which go the full distance.
The D/L method has been criticized on the grounds that wickets are a much more heavily weighted resource than overs, leading to the suggestion that if teams are chasing big targets, and there is the prospect of rain, a winning strategy could be to not lose wickets and score at what would seem to be a "losing" rate (e.g. if the required rate was 6.1, it could be enough to score at 4.75 an over for the first 20–25 overs). The 2015 update to D/L/S recognised this weakness and changed the rate at which teams needed to score at the start of the second innings in response to a large first innings.
Another criticism is that the D/L method does not account for changes in proportion of the innings for which field restrictions are in place compared to a completed match.
More common informal criticism from cricket fans and journalists of the D/L method is that it is unduly complex and can be misunderstood. For example, in a one-day match against England on 20 March 2009, the West Indies coach (John Dyson) called his players in for bad light, believing that his team would win by one run under the D/L method, but not realizing that the loss of a wicket with the last ball had altered the Duckworth–Lewis score. In fact Javagal Srinath, the match referee, confirmed that the West Indies were two runs short of their target, giving the victory to England.
Concerns have been raised as to its suitability for Twenty20 matches, where a high scoring over can drastically alter the situation of the game and variability of the run-rate is higher over matches with a shorter number of overs.
- "A Decade of Duckworth–Lewis". BBC. 1 January 2007. Retrieved 2009-03-21.
- "Introducing Duckworth–Lewis–Stern method". Cricbuzz. 12 February 2015. Retrieved 2015-03-30.
- Duckworth/Lewis. "The D/L method: answers to frequently asked questions". ESPN Cricinfo. Retrieved 5 January 2017.
- 3rd Final, 1988/89 Benson and Hedges World Series Cup
- "22 off one ball – A farcical rain rule leaves everyone bewildered", from Cricinfo.
- "Stump the Bearded Wonder", Bill Frindall explains how D/L would apply to 1992 WC semi-final
- Scorecard of the 2nd ODI between England and Zimbabwe, 1 January 1997, from Cricinfo.
- Data Analysis Australia's detailed mathematical analysis of the Duckworth–Lewis Method daa.com.au.
- espncricinfo D/L FAQ's Q15
- Scorecard for the rain-affected 4th ODI between India and England on 23 November 2008, from Cricinfo.
- Sri Lanka v England Scorecard
- Pakistan v India Scorecard, 6 Feb 2006
- Perth v Melbourne scorecard
- Perth v Melbourne report
- Duckworth/Lewis Method of Re-calculating the Target Score in an Interrupted Match
- The Duckworth-Lewis Method (2002) from Cricinfo.
- The Duckworth-Lewis Method (1999) from Cricinfo.
- The Duckworth-Lewis Method (2001) from Cricinfo.
- Rain affected rules from Cricinfo.
- Tony Lewis, of Duckworth-Lewis, Interview: Journalists denigrate system by publishing 'rubbish' without understanding 27 August 2013
- espncricinfo D/L FAQ's Q13
- espncricinfo D/L FAQ's Q14
- ICC Playing Handbook
- ICC Playing Handbook 2013/14 Section 6
- espncricinfo D/L FAQ's Q1
- Duckworth–Lewis to review their formula for T20 matches Archived 10 October 2012 at the Wayback Machine.
- "Duckworth-Lewis method in new avatar for World Cup". ESPNcricinfo. Retrieved 7 July 2016.
- espncricinfo D/L FAQ's Q4
- The dummy's guide to Duckworth-Lewis
- ICC Playing Handbook 2006-07
- espncricinfo D/L FAQ's Q6
- Over by over
- Ball-by-ball description from espncricinfo
- South Africa left to lick wounds (BBC)
- Being Duckworth-Lewis: cricket's weather-break mathematicians (The Guardian)
- Bhogle, Srinivas, The Duck worth/Lewis Factor, Rediff.com.
- Booth, Shane, quoted in For a Fair Formula, The Hindu.
- Varma, Amit, Simple and subjective? Or complex and objective?[permanent dead link], ESPNcricinfo
- Charlie Brooker, AV campaigners have created a stupidity whirlpool that engulfs any loose molecules of logic, dismisses the claim of the simplicity by citing the method's formula, The Guardian, 25 April 2011. Retrieved 2011-04-28
- The anomalous contraction of the Duckworth–Lewis method
- BBC news interview with The Duckworth Lewis Method
- Interview with band
- Duckworth, FC & Lewis, AJ "Your Comprehensive Guide to The Duckworth Lewis Method for Resetting Targets in One-day Cricket", Acumen Books, 2004. ISBN 0-9548718-0-4
- Duckworth, F "A Role for Statistics in International Cricket" Teaching Statistics, (June 2001) Volume 23, No. 2 pp 38–44
- Duckworth, FC & Lewis, AJ "A fair method for resetting the target in interrupted one-day cricket matches" Journal of the Operational Research Society, (Mar 1998) Volume 49, No. 3 pp 220–227 JSTOR 3010471
- ICC's D/L method FAQ
- Cricinfo's D/L method FAQ
- ICC's D/L method (standard edition) table of resource percentages
- Cricinfo's explanation of the D/L method
- BBC Sport's explanation of the D/L method
- Web based Calculator for the Standard Edition of the Duckworth Lewis method
- Calculator for the Stern Edition of the D/L method
- Alternatives to D/L