DLS Method Explained: How Rain Decides Cricket Scores

Few things in cricket spark as much living-room argument as a number that appears the moment dark clouds roll in: the revised target. The DLS method — short for Duckworth-Lewis-Stern — is the formula that decides who wins when rain steals overs, and almost everyone who follows Indian cricket has cursed it at least once. Yet the logic underneath is far more sensible than the conspiracy theories suggest. Here is what it actually does, why it works the way it does, and how to read it live so you are never the confused one in the room.

The one idea that makes DLS click

Forget the formula for a second. The whole method rests on a single insight: a batting team has two resources — the overs remaining and the wickets in hand — and these two things together determine how many runs it can still score.

A team with 10 wickets and 50 overs has 100% of its resources. A team with 10 wickets but only 25 overs left does not have 50% — it has more, because fresh batters can attack freely. Conversely, a team that has lost 8 wickets cannot use its remaining overs fully, no matter how many are left.

DLS captures this in a resource table: every combination of overs-left and wickets-lost maps to a percentage of total resources. When rain removes overs, it removes resources, and the target is adjusted to reflect the resources each side genuinely had.

How the revised target is actually calculated

When the team batting second loses overs, the maths is, in plain terms, a ratio. Take the first team's score, look at the resource percentage each side had access to, and scale accordingly. The simplified shape is:

• Team 2's target ≈ Team 1's score × (Team 2's resources ÷ Team 1's resources), then add 1 to win.

If the chasing side has fewer resources than the team that batted first, the target comes down. If — unusually — an interruption leaves it with effectively more usable resources, the target can actually be revised upwards beyond the original score. That counterintuitive bump is exactly why fans accuse the system of bias, when in fact it is just being consistent.

A crucial detail: international matches use the Professional Edition, which runs on licensed software rather than a printed table. The publicly available Standard Edition is simpler and meant for club cricket without computers. The professional version handles very high first-innings totals far better, which matters in the T20 era.

The par score: your real-time scoreboard tool

The most useful thing for a viewer is not the final target — it is the par score flashed on screen during a rain-threatened chase. Par is the score the batting side should be at, for the wickets it has lost, to be exactly level on DLS at that instant.

• If the chasing team is above par when play is abandoned, it wins.
• If it is below par, it loses.
• If it is exactly level, the match is tied under DLS.

This is why captains obsess over wickets in a stop-start chase. Slogging to stay ahead of par while losing wickets is dangerous, because every wicket lost raises the par line — you can be ahead one ball and behind the next without scoring at all.

When DLS even applies

A result cannot be conjured out of a washout. There are minimum-overs floors:

1. In a 50-over ODI, the team batting second must face at least 20 overs for a DLS result.
2. In a T20 international, the floor is 5 overs per side.
3. Below those thresholds, the game is declared a no-result, regardless of how dominant one side looked.

This is why you sometimes see a team cruising at 80 for 1 in a chase and still walking away with nothing — the rain came before the minimum was reached.

Why the old rules were worse — and the 1992 trigger

To appreciate DLS, remember what it replaced. The old Most Productive Overs method simply lopped off a batting side's least productive overs when time was lost — a crude fix that ignored wickets entirely.

It produced one of cricket's most infamous moments. In the 1992 World Cup semi-final, South Africa needed a gettable target off the last over, rain intervened, and they returned to a scoreboard demanding an impossible 22 runs off 1 ball. The absurdity of that revision pushed statisticians Frank Duckworth and Tony Lewis to build something fairer. Their method was adopted by the ICC at the end of the 1990s and became the global standard.

When the pair retired, Australian academic Steven Stern took over as custodian and recalibrated the model for modern scoring rates, where teams routinely post 350-plus and T20 totals balloon. The method was renamed DLS in 2014 to reflect his contribution.

What still trips people up

Three honest criticisms survive, and it is worth knowing them.

First, DLS was built on decades of one-day scoring patterns, so the steepest, most chaotic phases of a T20 chase are the hardest to model — the data is thinner and the variance is huge. Second, the method assumes a team would have continued at a typical trajectory, which can flatter a side that was actually collapsing or punish one poised to explode. Third, the toss and conditions — dew, a deteriorating pitch, fading light — are invisible to the formula, even though they hugely shape a real chase.

None of this makes DLS wrong; it makes it a fair average rather than a perfect prediction. For a problem with no clean answer — how do you finish a game nature interrupted? — a transparent, consistent, wickets-aware model is about as good as it gets.

The takeaway for the next rain delay

Next time the covers come on, ignore the groaning and do three things: check the par score, count the wickets in hand, and remember the minimum-overs rule. If your team is batting second, ahead of par, and past the overs floor, you are in a genuinely strong position — and you will understand the revised target on screen better than the commentators sometimes do. That is the quiet value of knowing how DLS works: it turns a moment of confusion into one of clarity.