When rain interrupts a limited-overs cricket match, the Duckworth-Lewis-Stern method helps officials set a fair revised target by comparing the resources available to both teams. This guide explains resources, par scores, shortened chases, interruption scenarios, and a practical checklist for following a rain-affected live cricket match.
Overview
The Duckworth-Lewis-Stern method, commonly called DLS, is used when weather reduces the time available in a one-day or T20 match. Instead of treating every lost over as an identical loss, it considers two central resources: overs remaining and wickets in hand.
The logic is straightforward. A batting team with many overs left and most of its wickets available has more scoring potential than a team with only a few overs left or several wickets already lost. DLS uses established resource values and an approved calculation system to compare those situations. The result may be a revised target for the chasing team, a par score used to judge the result of an interrupted innings, or a decision that too little play remains for a fair contest.
DLS is not a simple deduction of runs for every over lost. The same number of overs can have a different effect depending on when the interruption occurs and how many wickets have fallen. A stoppage early in an innings may remove a large block of potential scoring time, while a stoppage near the end may affect fewer remaining resources. Similarly, losing wickets reduces the batting side's available resource because fewer wickets remain to support an attacking chase.
The official target depends on the competition's playing conditions and the calculation made by the appointed officials. A scorecard or live cricket match centre may show a revised target, current par score, required rate, and number of overs remaining, but these displays should be read alongside the official announcement.
For background on reading the underlying figures, see How to Read a Cricket Scorecard and Ball-by-Ball Commentary. It can help you identify the innings score, overs completed, wickets lost, and the exact point at which play stopped.
Checklist by scenario
Scenario 1: Rain interrupts the first innings
- Record the scheduled overs and the number of overs available when play resumes.
- Note the batting team's score and wickets at the interruption.
- Check whether the first innings will continue or be completed under a shortened limit.
- Confirm the new maximum overs for both innings, rather than assuming the chasing side simply receives the same number of overs already bowled.
- Wait for the official revised target before judging the chase.
If the first innings is shortened, the batting side may have fewer resources than originally expected. The revised target is then set using the resources available to each innings under the match regulations.
Scenario 2: Rain interrupts the chase
- Write down the chasing team's score, wickets lost, and overs completed when play stops.
- Record the overs remaining before and after the interruption.
- Check whether the chase will resume with the same target and fewer overs, or whether the target will be recalculated.
- Look for the official par score at the interruption point.
- Compare the chasing team's score with par only after confirming the relevant over and wicket position.
When play stops during a chase, the par score can indicate which team is ahead at that moment. If the chasing side is above par, it may be considered ahead if the match cannot resume, subject to the competition's rules. Being below par does not necessarily mean the match is over; the officials may restore enough overs for a revised chase.
Scenario 3: The match loses several blocks of play
- Track every interruption separately, including when it began and when play resumed.
- Record the score and wickets at each break.
- Note any change to the innings length announced by officials.
- Check whether the match has reached the minimum number of overs required for a result.
- Use the latest official target, not an earlier target displayed during a previous phase of the match.
Multiple interruptions can lead to more than one revision. A target shown before a further delay may become obsolete once additional overs are removed.
Worked example: the resource comparison
The following is an illustrative example, not an official match calculation. Assume Team A scores 240 in a completed innings. Due to weather, Team B is judged to have 75% of the resources available to Team A's innings. If Team A used 100% of its available resources and Team B has 75%, a simplified resource comparison would produce a proportional scoring figure of 180 runs before the target-setting adjustment. The target would normally be one run higher than the par score used for the chase.
| Item | Illustrative value | What it means |
|---|---|---|
| Team A score | 240 | The first innings total used as the starting reference |
| Team A resources | 100% | Assumed full innings resource |
| Team B resources | 75% | Reduced overs and/or wicket resources after rain |
| Illustrative par score | 180 | A simplified proportional comparison only |
| Illustrative target | 181 | One run above the par score |
Real DLS calculations use detailed resource tables or authorised software, and the result may not match a simple percentage multiplication. Treat examples like this as a way to understand the principle, not as a substitute for the official target.
What to double-check
Resources are more than overs
Two innings with the same number of overs remaining may not have the same resource value. Wickets in hand matter because a team can generally take more risks when it has more batters available. This is why a chase at 8 wickets down is assessed differently from a chase at 2 wickets down, even if both teams have the same overs left.
Par score is not always the target
A par score describes the score expected to represent an even position at a particular stage. The target is the score the chasing team must reach to win, usually one run above the relevant par score. A live scorecard may display both figures, so check the labels carefully.
Overs notation can cause confusion
In cricket, 17.4 overs means 17 overs and four legal balls, not 17.4 decimal overs. When recording a rain delay, note the exact overs and balls completed. Misreading this notation can lead to an incorrect estimate of the remaining resources.
Competition regulations still apply
Different competitions can have different minimum-over requirements, reserve-day arrangements, abandonment rules, or procedures for a tied result. DLS provides the target calculation, but the playing conditions determine whether a result is possible and how the match is formally decided.
For reliable context during a match, compare the official scorecard, ball-by-ball commentary, and competition update. The guide to finding today's cricket matches and start times can also help you verify the scheduled format and venue before following a weather-affected fixture.
Common mistakes
- Subtracting a fixed number of runs per over: DLS measures changing resources, so there is no universal run deduction for each lost over.
- Ignoring wickets: The score alone does not describe the chasing team's resource position.
- Using an old target: A second interruption may trigger another revision.
- Confusing a projected score with a DLS target: A projected score is an estimate of scoring pace; DLS is an official resource-based calculation.
- Assuming the first innings score is automatically protected: The revised target reflects the resources available to both sides, not simply the original total.
- Relying on unofficial graphics: Social posts and broadcast overlays can lag behind an official update. Confirm the target when play resumes.
DLS also should not be used as a fantasy cricket prediction tool by itself. A revised target changes expected run rates and match dynamics, but player selection still depends on roles, batting position, bowling allocation, and confirmed team news. For a broader process, see the fantasy cricket team-building guide.
When to revisit
Return to this checklist whenever rain interrupts a limited-overs match, particularly before interpreting a live cricket score, placing weight on a match prediction, or assessing a team's position in a tournament. Recheck the guide at the start of each major season or tournament because playing conditions, calculation tools, and competition procedures can change.
On match day, save these five details in order: the scheduled overs, score at the interruption, wickets lost, overs remaining after the delay, and the officially announced revised target. Then compare the scorecard with the latest ground or competition update. If the target changes again, replace the earlier figure rather than trying to combine both calculations.
This process keeps rain-affected match analysis grounded in the information that actually controls the result. The final authority is always the match officials and the competition's published playing conditions.
