Rain interrupts a limited-overs match, overs are lost, and a revised target appears on the screen that looks nothing like a simple pro-rata calculation. The reason is that the method treats overs and wickets as two separate resources.
The Duckworth-Lewis method, now applied in its Stern revision, is the standard means of resetting targets in rain-affected limited-overs cricket, and it is far more logical than its reputation suggests.
This guide explains the resource concept, how the calculation works, what it gets right and where it is still criticised.
The Resource Concept
Everything follows from one idea.
A batting side begins with two resources.
Those resources are overs remaining and wickets in hand.
Both are consumed as an innings progresses.
Together they determine how many runs a side can expect to score.
Every combination has a resource percentage value.
Targets are adjusted in proportion to resources available.
Why a Simple Average Does Not Work
| Scenario | Naive pro-rata target | Why it fails |
|---|---|---|
| Overs cut with no wickets lost | Proportional reduction | Understates the chasing advantage |
| Overs cut after heavy wicket loss | Proportional reduction | Sets an impossible target |
| Interruption early in an innings | Proportional reduction | Ignores the batting side’s intact wickets |
| Interruption near the end | Proportional reduction | Ignores acceleration already underway |
| Both innings shortened | Equal reduction | Teams planned for different lengths |
| Rain only in the chase | Run-rate scaling | Heavily favours the chasing side |
The old run-rate methods failed in exactly these cases, which is why a system accounting for wickets in hand became necessary.
How the Calculation Runs
The mechanics are systematic.
Resource percentages are read from a published table.
The team batting first has a starting resource value.
Interruptions reduce the resources actually used.
The chasing side’s available resources are calculated the same way.
The ratio of the two determines the adjustment.
The revised target is the first innings score scaled by that ratio.
What the Method Accounts For
- Overs lost before an innings begins
- Overs lost during either innings
- Wickets already fallen at the moment of interruption
- Multiple separate interruptions in one match
- An innings being terminated early
- Matches reduced before the toss
- Scoring patterns typical of the format
- Higher scoring rates in modern limited-overs cricket
The last point explains the Stern revision, which recalibrated the tables after scoring rates rose well beyond what the original model assumed.
Common Criticisms
The method attracts regular complaint.
Targets can appear counter-intuitive to viewers.
The calculation is not transparent in real time.
Teams with wickets in hand are sometimes seen as rewarded.
Very short revised matches produce volatile targets.
Aggressive batting approaches are not fully modelled.
Supporters rarely have access to the resource tables.
Resource Values in Practice
| Situation | Overs left | Wickets left | Resource level |
|---|---|---|---|
| Innings start | Full allocation | Ten | Maximum |
| Early interruption | Most remaining | Nine or ten | High |
| Mid-innings collapse | Half remaining | Three or four | Low |
| Steady mid-innings | Half remaining | Eight | Moderate |
| Late interruption | Few remaining | Several | Low |
| Final over | One | Any | Minimal |
Comparing the third and fourth rows shows the point of the whole system, since identical overs remaining produce very different resource values depending on wickets in hand.
That single distinction is what earlier run-rate methods could not capture, and it is the reason revised targets so often surprise viewers who are only watching the overs.
Worked Example in Principle
A simplified case makes the logic clearer.
Team batting first completes a full innings.
Rain removes a block of overs from the chase.
The chasing side therefore has fewer resources available.
Its target is scaled down by the resource ratio.
If wickets have already fallen, the reduction is smaller.
The final figure is rounded and a par score is published.
Frequently Asked Questions
Why do targets sometimes rise?
Because a shortened chase uses fewer resources, so the target scales up to remain equivalent.
Is it used in Twenty20 cricket?
Yes, with resource tables calibrated to the scoring patterns of the shorter format.
What does the Stern revision change?
It recalibrated the resource values to reflect substantially higher modern scoring rates.
Can a match be decided with very few overs?
A minimum number of overs must be bowled to each side for a result to stand.
The Short Version
The Duckworth-Lewis method treats overs remaining and wickets in hand as combined resources, assigns each combination a percentage value, and scales the target by the ratio of resources available to each side. The Stern revision updated those values for modern scoring rates.
Why It Replaced Earlier Systems
Previous methods ignored wickets entirely, producing results that regularly handed matches to one side through pure arithmetic rather than anything that happened on the field.
Accounting for wickets in hand made revised targets defensible, which is why the method survived every attempt to replace it.
The Par Score
Broadcasts display a running par figure.
It shows what the chasing side should have scored at that moment.
Being ahead of par means winning if rain ends the match.
The figure updates after every wicket.
It also changes with every over bowled.
Captains manage risk directly against that number.
It is the most practically useful output of the whole system.
How Teams Use It Tactically
Awareness of the method shapes decisions.
Sides preserve wickets when rain is forecast.
Batting aggression is tempered to stay above par.
Captains may delay bowling changes before an expected break.
Fielding sides push for wickets to raise the par figure.
Dressing rooms track the calculation continuously.
Analysts provide live projections to the captain.
Ignorance of the method has cost teams matches outright.
Minimum Overs Requirements
Not every shortened match produces a result.
A minimum number of overs must be bowled to each side.
Shorter formats require proportionally fewer.
Below that threshold the match is abandoned.
Tournament rules may add reserve days instead.
Knockout matches often carry different provisions.
Officials manage the cut-off times closely.
The Stern Revision
The update addressed a genuine weakness.
Original tables reflected scoring patterns of an earlier era.
Totals rose substantially as the formats developed.
High first-innings scores were being under-adjusted.
The revision recalibrated resource values upward.
It also improved handling of very high totals.
Periodic recalibration is now an accepted part of the system.
The underlying resource principle was left unchanged.
Alternatives That Were Tried
Several other systems preceded or competed with it.
Average run rate scaling was the earliest approach.
Most productive overs methods removed a side’s weakest overs.
Both produced notorious and indefensible targets.
A proposed alternative used projected score curves.
None handled wickets as convincingly.
The resource model has outlasted every rival.
Where It Is Applied
Use of the method is near universal.
International one-day and Twenty20 matches.
Major domestic limited-overs competitions.
Franchise leagues across multiple countries.
Women’s international and domestic cricket.
Associate-level international fixtures.
Club cricket sometimes uses simplified versions.
Multi-day cricket does not use it at all.
Why Targets Sometimes Look Harsh
The most common complaint has a clear explanation.
A side batting first plans for a full innings.
It holds wickets back for a late acceleration.
Rain in the second innings removes that phase for the chaser.
The chasing side keeps its wickets but loses the overs.
Its resource loss is therefore smaller than the overs suggest.
The target falls by less than viewers expect.
Why Targets Sometimes Look Generous
The reverse situation occurs just as often.
A chasing side loses early wickets before the break.
Its remaining resources are already heavily depleted.
Removing overs then costs it relatively little.
The revised target drops substantially.
Fielding sides find this outcome frustrating.
Both reactions come from the same consistent calculation.
The method does not favour either side systematically.
Transparency and Public Understanding
Communication has lagged behind the mathematics.
Resource tables are published but rarely explained.
Broadcasters show the par score without the reasoning.
Commentators often describe the result as mysterious.
Simple explanatory graphics would help considerably.
Several boards have begun publishing worked examples.
Understanding has improved slowly over the years.
Scheduling and Weather Planning
Administrators plan around interruptions deliberately.
Reserve days are scheduled for major knockout matches.
Extra time is built into daily playing conditions.
Covers and drainage reduce the frequency of lost overs.
Start times may be moved to avoid forecast rain.
Floodlights allow play to continue later than before.
These measures reduce reliance on the method.
They do not remove the need for it entirely.
Effects on Tournament Outcomes
Revised targets regularly shape competitions.
Group-stage qualification has turned on single results.
Net run rate calculations incorporate adjusted scores.
Knockout matches have been decided with reduced overs.
Teams prepare specifically for rain-affected scenarios.
Selection may favour all-rounders in wet conditions.
The method therefore influences squad building indirectly.
How To Follow It as a Viewer
A few habits make interruptions easier to read.
Watch the par score rather than the original target.
Note wickets in hand as the key variable.
Expect targets to fall less than the overs lost suggest.
Remember that early wickets reduce the chasing resource sharply.
Check the minimum overs requirement for the format.
Treat the published figure as arithmetic, not judgement.
Most of the controversy disappears once the resource idea is understood.
A Closing Assessment
The method is one of the few genuinely successful imports of statistical modelling into the laws of a sport.
It replaced systems that produced results nobody could defend, and it has survived decades of scrutiny with its core principle intact.
Its weaknesses are mostly presentational rather than mathematical, because the reasoning is opaque at exactly the moment supporters most want an explanation.
Periodic recalibration has kept it aligned with how the formats are actually played.
No alternative has come close to displacing it, and none appears likely to.
Understanding the resource concept is all that stands between a confused viewer and a perfectly logical revised target.
That gap between the model and its presentation is worth closing.
Boards publish the tables but assume nobody will read them.
Broadcasters show a number without the two inputs behind it.
A simple on-screen display of resources used would explain most results instantly.
Several analytics providers already produce exactly that graphic.
Wider adoption would reduce the annual round of complaints considerably.
The mathematics is not the problem and never really was.
For players, the practical implications are more immediate than for anyone watching.
A batting side aware of the par score plays the situation rather than the scoreboard.
Preserving a wicket can be worth more than six runs when rain is approaching.
Fielding captains attack harder in the overs before a forecast break.
Both behaviours are rational responses to the resource model.
Teams that drill these scenarios handle interruptions far better.
Those that do not tend to find out the hard way.
That hard lesson has been delivered in several high-profile tournaments.
Sides have been eliminated while believing themselves comfortably ahead.
Others have won matches by blocking out an over to stay above par.
Those outcomes look like luck and are usually preparation.
Dressing rooms now treat the calculation as basic match awareness.
Analysts relay the par figure continuously throughout a chase.
It has become as routine as checking the required run rate.
Its longevity is the clearest measure of how well the original idea was constructed.
Few statistical models survive thirty years in competitive sport without replacement.
Fewer still are applied in finals watched by hundreds of millions.
The resource framework has absorbed two format revolutions without structural change.
Recalibration has been enough each time.
That is an unusually strong record for any piece of sporting regulation.
Cricket spent decades producing rain results that embarrassed the sport.
It now produces results that are merely misunderstood.
That is a substantial improvement, and an easy one to build on.
A little more explanation on screen would finish the job entirely.
Until then, the resource table remains the most important document in cricket that almost nobody has read.
Reading it once is enough to make every revised target in the sport make sense.
That is a rare return on an afternoon spent with a page of percentages.
Most supporters will never do it, and the method will keep working regardless.