Duckworth-Lewis-Stern Method Explained: Rain-Affected Targets, Par Scores and Revised Cricket Chases
DLS MethodRain DelaysCricket RulesMatch AnalysisPar Score

Duckworth-Lewis-Stern Method Explained: Rain-Affected Targets, Par Scores and Revised Cricket Chases

CCricbuzz News Editorial Desk
2026-11-16
7 min read

Learn how DLS changes rain-affected cricket targets, how par scores work, and what to track during interrupted ODI and T20 chases.

When rain interrupts a cricket match, the Duckworth-Lewis-Stern method changes the chase according to the resources available to the batting side. This guide explains how revised targets, par scores, lost overs and reduced-innings results work, so you can read a rain-affected scorecard or live cricket updates with greater confidence.

Overview

The Duckworth-Lewis-Stern method, usually shortened to DLS, is a calculation system used to reset targets in limited-overs cricket after interruptions such as rain, bad light or other delays. It is designed to account for two resources: wickets remaining and overs available.

In a normal chase, the second team has a fixed target and a known number of overs. After a delay, that balance may change. The chasing team might lose overs but retain all its wickets, or it might resume with fewer overs after already losing several wickets. DLS attempts to reflect the scoring opportunity still available rather than simply reducing the target in proportion to overs lost.

The official revised target is produced using approved DLS tables or software and the playing conditions for the competition. A quick mental calculation can help explain the principle, but it should not be treated as an official result. Tournament regulations also determine the minimum number of overs required for a result, the procedure for reserve days and what happens if another interruption occurs.

The most useful distinction is this: the revised target is the score required to win, while the par score is the score that represents a tie at a particular point in the innings. In most limited-overs applications, the target is one run higher than the relevant par score.

What to track

1. The original innings and target

Start with the first innings score, the number of overs scheduled and the target originally set. For example, if Team A scores 250 in a 50-over match, Team B normally needs 251. Record whether the first innings was completed or also affected by rain.

2. Overs lost and overs remaining

Note the scheduled overs, the number completed before an interruption and the revised overs available when play resumes. A reduction before the chase begins is different from a reduction during the chase. If both innings are affected, the calculation must consider the resources used by each side, not only the final number of overs.

3. Wickets lost

Wickets are a major part of the resource calculation. A team with ten wickets in hand generally has more scoring potential than a team with five wickets down, even if both have the same number of deliveries remaining. This is why a simple “original target divided by original overs” approach can produce an unfair result.

4. The official revised target and par score

Follow the target shown by the umpires, match centre or official scorecard. If the target is 181, the chasing side wins by reaching 181; a score of 180 is normally the par score for the completed contest. During the innings, broadcasters may also display a changing par score. That figure tells you whether the batting side is currently ahead of, level with or behind the DLS position.

5. The match status

Separate a DLS result from a no-result. A match can have an adjusted target and still be abandoned if the minimum conditions for a result are not met. For a broader explanation of abandoned games and reduced overs, see our guide to cricket no-result rules.

SituationWhat to checkWhy it matters
Rain before the chaseRevised overs and official targetThe innings may begin with a new target
Rain during the chaseScore, wickets, balls completed and new targetThe target may change after resources are lost
Rain late in the inningsPar score at the interruption pointThe result may be decided from the score at that moment
Repeated interruptionsLatest target and overs remainingEach restart can produce a new calculation

How the DLS workflow works

The practical workflow is easier to follow than the underlying mathematical tables:

  1. Establish the first-innings resources. The calculation considers the overs and wickets available to the team that batted first.
  2. Measure the resources available to the chasing side. This includes the reduced overs and wickets remaining when play is scheduled to resume.
  3. Compare the two resource levels. If the chasing team has fewer resources, its target will usually be lower than the original target. If the first innings lost resources while the chase retains relatively more, the adjustment may be smaller or work in the other direction.
  4. Apply the competition’s approved DLS calculation. The match officials or authorised scoring system produce the official number.
  5. Display the target and par score. The chase continues against the latest target, not the target shown before the interruption.

Consider a clearly hypothetical illustration. Team A makes 250 in a completed 50-over innings. Rain then limits Team B to 30 overs. An official DLS calculation might set a target of 201, depending on the resource assumptions in force. In that illustration, 200 is the par score and 201 wins the match. The numbers are only an example of how the terminology works; they are not a universal conversion from 50 overs to 30 overs.

A second illustration shows why wickets matter. Suppose Team B is 120 for 2 after 20 overs when rain stops play, and the restart leaves 10 overs available. The revised target is not calculated only from 10 overs at the current run rate. The official calculation also recognises that two wickets have been lost and that eight wickets remain. A team at 120 for 8 would have a different resource position and could receive a different par assessment.

Format comparison: ODIs and T20s

FeatureInterrupted ODIInterrupted T20
Scheduled innings lengthUsually longer, giving more scope for staged reductionsShorter, so each lost over has a larger practical effect
Typical information to monitorOvers lost, wickets, revised target and minimum oversEvery over, wicket and restart target is especially important
Interpretation of parUseful across a longer chase with changing resourcesCan shift quickly because a few overs represent a large share of the innings
Key cautionDo not assume a proportional reduction from 50 oversDo not assume the original required run rate remains relevant

The same DLS principles apply across formats, but competition playing conditions can differ. Always prioritise the official match centre and umpire announcement over a fan-made calculator or an old screenshot.

How to interpret changes

If the revised target falls, that does not automatically mean the chasing team has gained an advantage. It has also lost time and therefore scoring opportunities. The meaningful comparison is between the new target, wickets in hand, balls remaining and the current par score.

When a live score shows the batting side above par, it is ahead of the score expected for a tie at that point. Below par means it is behind that benchmark. Being above par is not the same as being certain to win: a side can lose quickly, and the final result still depends on the official target and the number of overs left.

For match analysis, record four snapshots: the score at the interruption, wickets down, overs remaining and official revised target. This creates a reliable explanation for readers following ball-by-ball commentary. For related context, use our cricket scorecard guide and check the confirmed playing XI and squad news before assessing team strength.

Cadence and checkpoints

DLS is not a statistic that needs a monthly update in the same way as a points table. It should be checked whenever a match is interrupted and whenever the competition’s playing conditions are published or revised. Before a major ODI or T20 tournament, confirm the current competition rules, minimum overs requirements and the official method used for target calculations.

During a rain delay, revisit the article at three checkpoints: when the interruption begins, when officials announce the restart conditions and immediately after the revised target appears. If another delay occurs, repeat the process because the target or par score may change again.

When to revisit and what to do next

Return to this guide whenever a live score shows “DLS target,” “par score,” “revised target” or “resources.” Then use this short checklist:

  1. Write down the original score and target.
  2. Confirm how many overs the chasing side will receive.
  3. Record the score and wickets at the latest interruption.
  4. Use the official target announced by the match officials or authorised scorecard.
  5. Compare the current score with the displayed par score, while noting balls and wickets remaining.
  6. Check whether the match has reached the competition’s minimum overs for a result.

This approach keeps rain-affected cricket analysis precise. It avoids guessing from run rate alone and helps readers understand why a target changed, what par means and whether the match is heading toward a result or a no-result.

Related Topics

#DLS Method#Rain Delays#Cricket Rules#Match Analysis#Par Score
C

Cricbuzz News Editorial Desk

Senior Cricket Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.