Rain can change a cricket match without changing the score already on the board. This guide explains the Duckworth-Lewis-Stern (DLS) method, including how overs remaining, wickets in hand, par scores, revised targets, reserve days, and abandoned-match rules are used to interpret a rain-affected result. The examples are illustrative; the official competition playing conditions and DLS calculation remain the final reference.
Overview
The Duckworth-Lewis-Stern method is a mathematical system used to reset targets when rain or another interruption removes playing time. Its purpose is to give the chasing side a realistic target based on the scoring resources still available to both teams.
Those resources are not simply overs. In limited-overs cricket, a team’s ability to score depends on two linked factors:
- Overs remaining: More available deliveries generally mean more scoring opportunity.
- Wickets in hand: A team with more wickets available can usually attack with less risk than a team close to being bowled out.
DLS treats the combination of overs and wickets as a resource percentage. Official DLS calculations use resource tables or approved software rather than a basic run-rate equation. This matters because a loss of 10 overs is not equally damaging at every stage of an innings. Ten overs lost when a team has nine wickets in hand may have a different effect from ten overs lost when only two wickets remain.
Three terms are especially important:
- Par score: The score considered level for a specific point in a rain-affected match.
- Revised target: The score the chasing team must reach to win, normally one run above the relevant par score.
- Resources: The scoring opportunity represented by the remaining overs and wickets in hand.
When you check a cricket live score after an interruption, do not rely only on the original asking rate. First confirm the revised number of overs, the score at the stoppage, the wickets lost, the revised target, and the competition’s result rules.
How to estimate a DLS revised target
A practical DLS workflow has five steps. The match referee, umpires, or official scoring system will perform the calculation, but this sequence helps you understand the result.
- Record the match state. Note the format, innings, score, wickets lost, overs completed, and scheduled overs per side.
- Identify the interruption. Establish whether rain stopped play during the first innings, between innings, or during the chase. Also check whether play will resume on the same day or after a reserve day.
- Calculate available resources. The official method assesses the resources available before and after the interruption. This combines overs and wickets rather than treating them independently.
- Set the new innings length or target. If both teams have lost playing time before or between innings, the first innings may be shortened and the chasing target recalculated. If the chase is interrupted, the target can be revised according to the resources still available to the chasing team.
- Check the result threshold. If the match cannot resume, the chasing team’s score is compared with the DLS par score for that point. A score above par indicates a win for the chasing side; a score below par indicates that the team defending the target is ahead. The exact result procedure is governed by the competition’s playing conditions.
A commonly shown simplified relationship is:
Revised target ≈ first-innings score × chasing resources available ÷ first-innings resources available, then adjusted to a whole-number target.
This expression is useful for understanding the direction of a calculation, but it is not a substitute for the official DLS table or software. The resource percentages, rounding rules, minimum overs, and match regulations can vary by competition.
| Interruption point | What usually changes | What to check |
|---|---|---|
| During the first innings | The batting side may receive fewer overs, and the second innings may be shortened or assigned a revised target. | Overs available to each side and the first-innings resource position. |
| Between innings | The chasing innings may begin with fewer overs than scheduled, requiring a new target. | First-innings score, revised chase length, and official target. |
| During the second innings | The target or par score may be recalculated using the chasing team’s score, wickets, and resources remaining. | Score at stoppage, wickets lost, overs left, and whether play can resume. |
Inputs and assumptions
To interpret a rain rule correctly, collect the same inputs you would use when reading a detailed match scorecard:
- Format and scheduled overs: A T20 and an ODI do not use the same innings length or interruption expectations.
- Team 1’s score: Include the completed score and wickets lost if the first innings ended early.
- Overs completed and remaining: Confirm the official over count. A partial over is recorded in cricket notation as balls, not a decimal in the ordinary mathematical sense.
- Wickets in hand: This is central to resource assessment. A side at 80 for 2 has a different resource position from one at 80 for 7.
- Interruption length and timing: The available time may determine whether overs are deducted, whether innings are rescheduled, or whether play is abandoned.
- Playing conditions: Minimum overs for a result, reserve-day provisions, tie procedures, and abandonment rules are competition-specific.
Par score and revised target are related but not identical. A revised target is the number required to win before or during the chase. A par score is a reference point at a particular moment. For example, if a chase is stopped permanently, the officials may compare the chasing team’s actual score with the par score at the interruption. If the match resumes, a new target can be issued for the remaining overs instead.
Reserve days add another layer. A reserve day may allow a match to continue or restart under the tournament’s stated conditions, but it does not automatically mean the original schedule, overs, or target will remain unchanged. Check the event’s official regulations before interpreting a result.
Worked examples
Example 1: T20 interruption before the chase
Suppose Team A scores 168 in a scheduled 20-over innings. Rain then reduces Team B’s chase to 14 overs. Team B has all 10 wickets available at the start of the shortened innings.
The target is not normally calculated by multiplying 168 by 14 divided by 20. That would ignore the relationship between overs and wickets. Instead, the official calculation compares Team A’s scoring resources with the resources available to Team B for 14 overs and 10 wickets. The result might be higher or lower than a simple run-rate estimate, depending on the resource values and the competition’s procedure.
For a live match update, the useful information is therefore: “Team B need the official revised target in 14 overs,” not merely “Team B need 118 runs,” unless that number has been confirmed by the match officials or official score system.
Example 2: T20 interruption during the chase
Team A makes 176 in 20 overs. Team B reaches 92 for 2 after 10 overs when rain stops play. If the match can resume, the officials assess the resources Team B had used and the resources still available after the revised overs are set. The target may be recalculated rather than simply reducing 176 by the number of overs lost.
If the match cannot resume, the score of 92 is compared with the DLS par score for the precise stoppage point. A chase can therefore be ahead or behind par even when its current run rate looks strong by ordinary standards. Wickets lost are part of the calculation, so two wickets at the same score can affect the comparison.
Example 3: ODI interruption during the first innings
In an ODI, Team A begins its innings but loses substantial time to rain. The officials may reduce the number of overs available to Team A and set a corresponding chase length for Team B. If Team A scores 245 in its shortened innings, Team B’s target is based on the resources available to each side, not on the original 50-over assumption.
If another interruption occurs during Team B’s chase, the target may be revised again. The correct sequence is to use the latest official target and latest official over allowance. Earlier estimates from television graphics or social media should not be treated as final.
When to recalculate and what to verify
Revisit the DLS position whenever an interruption changes the amount of play available. Recalculation may be needed after a delayed start, a rain break, a second rain break, a change to the reserve-day schedule, or a decision that no further play is possible.
Use this practical checklist during a live cricket match:
- Confirm the official score, wickets, and overs at the stoppage.
- Check whether the innings or match has a minimum-overs requirement.
- Look for the announced number of overs remaining and the official revised target.
- Distinguish the target from the par score shown for the current match state.
- Check the tournament’s reserve-day and abandonment provisions.
- After the match, compare the result with the official scorecard and match report.
For tournament tracking, a rain-affected result can also influence the points table and, where applicable, net run rate or other tie-breakers. Those calculations are controlled by the competition’s regulations, so do not assume that every abandoned or shortened match is treated identically.
For more context, see our guide to reading a cricket scorecard, review how points tables and net run rate work, and use the cricket schedule planning guide when checking reserve-day dates and match timings. This article should be refreshed before each major tournament, or whenever the organiser changes its minimum-overs, reserve-day, or result provisions.