DLS par score vs target: how to read a rain-affected chase

A DLS par score and a revised target answer different questions. The target tells the chasing team what it needs to win under a revised innings allocation. A par score is the comparison used at a particular stopping point if the chase cannot resume and the conditions allow a result.

Before reading a rain graphic, identify its label and timestamp. A number captured before the next ball or wicket is not automatically the number that decides a later abandonment.

Read the label before doing arithmetic

The ICC Men’s T20 World Cup 2026 conditions describe a revised target as a whole-number winning total, with one fewer producing a tie. For a qualifying chase that ends prematurely, they compare the score at suspension with DLS par: equality is a tie, and the difference determines the run margin.

Minimum-overs requirements and other result conditions depend on the event and stage. Do not apply one tournament’s threshold to every limited-overs match.

Worked example: an official par of 103

These are invented numbers, not a calculation of a real match. Assume the official DLS par supplied at the stopping point is 103, the innings will not resume, and all conditions for declaring a result have been met.

• A chasing score of 104 is one above par: the chasing team wins by one run under DLS.
• A score of 103 equals par: the match is tied under that comparison.
• A score of 102 is one below par: the chasing team loses by one run under DLS.

The useful calculation here is the difference from a supplied official par. It does not show how to derive that par from overs, wickets or a first-innings total. Do not reuse 103 at a different stopping point just because the same teams are playing.

Worked example: a revised winning target of 121

Now imagine a different scoreboard that explicitly says revised target: 121. If the chasing team is on 94, it needs 27 more runs to reach that winning total. Under the assumed revised-innings conditions, finishing on 120 would be a tie, rather than a successful chase.

Keep this example separate from the previous one. The number 121 is a winning target for the revised allocation; 103 was a par supplied at a particular interruption. Comparing the two without their labels creates a disagreement that exists only in the notes.

Make a rain-delay record you can check later

1. Write the competition, stage and innings.
2. Record runs, wickets and the exact ball count when play stopped.
3. Copy the graphic’s label as well as its number.
4. Record whether play is expected to resume or has been abandoned.
5. Wait for the official revised target or result before treating the worksheet as final.

A useful habit is to leave an empty “later update” column. If play resumes and another wicket falls, enter a new row. Replacing the previous row hides why an earlier screenshot no longer matches the final announcement.

Why a run-rate shortcut does not settle it

A simple runs-per-over comparison leaves out the DLS treatment of resources and interruptions. A personal spreadsheet can organise the announced values; it should not present an improvised formula as the official DLS engine.

There is a separate table question after the match: how its result affects the tournament’s net run rate calculation. NRR ranks teams under the competition’s conditions. It is not the same number as the par used to decide a rain-affected chase.