Duckworth-Lewis-Stern (DLS) Method Guide & Target Adjustments

What the Duckworth-Lewis-Stern method solves

When rain (or bad light) shortens a limited-overs match, a simple “pro-rata” target is unfair — early wickets and unused overs change how many runs a side could still score. The Duckworth-Lewis-Stern (DLS) method adjusts targets using resources remaining: overs left and wickets in hand.

Professional competitions publish official DLS tables. Club and local leagues often adopt a simplified version — always follow your tournament playing conditions.

Resources lost and par score

At any point, a batting side has a percentage of its scoring “resources” left. Losing overs to rain reduces resources; losing wickets also reduces them. The par score is what the chasing side should have at that resource level to be level with the first innings.

• First innings shortened — the team batting second may face a revised overs limit and target
• Second innings interrupted — the target is recalculated from resources used so far
• Multiple stoppages — each interruption updates remaining resources again

Manual DLS math is error-prone under time pressure. Agree who owns the official table before the toss.

Shortened innings rules for local leagues

Many gully and club events set a minimum overs threshold (e.g. 5 overs per side) before a result can be declared. Below that, the match may be abandoned as no-result. Write the rule in the tournament sheet so captains are not arguing mid-rain delay.

• Minimum overs for a result
• Whether DLS or a simple run-rate target is used
• Who recalculates and announces the new target

Why STUMPED removes the manual grind

Automated scoring keeps the full ball-by-ball record on device. When play resumes, you still have exact overs, wickets, and totals — so organisers can apply DLS (or house rules) from clean data instead of reconstructing an innings from memory.