Why That Rain Target Looks Wrong: The DLS Method, Made Simple

Rain rolls in, the covers come on, and the giant screen flashes a new number that makes no sense. The team that was cruising now needs more, or the side that looked dead is suddenly ahead. Welcome to the most misunderstood piece of cricket arithmetic going: the Duckworth-Lewis-Stern (DLS) method. It decides who wins when the weather refuses to cooperate, and almost nobody in the stands can explain it. By the end of this you will.

With the monsoon parked over much of India through the back half of the year, and limited-overs cricket crammed into that window, DLS is not an exotic edge case. It's the difference between a trophy and a tantrum.

The one idea that makes DLS click

Forget the formula for a second. The whole system rests on a single, sane idea: a batting team begins an innings with two resources — the balls it has left to face, and the wickets it has in hand. A side starting a 50-over innings holds 300 balls and 10 wickets, which the method treats as 100% of its resources.

Every delivery bowled and every wicket lost chips that percentage down. Crucially, the two don't drain at the same speed. Lose early wickets and your remaining resources collapse, because batters in the hut can't use the overs that are left. Keep wickets and you stay rich in resource even deep into the innings. That asymmetry is exactly why a simple run-rate calculation is unfair, and why the old methods were junk.

How a revised target is actually built

When rain steals overs, DLS compares the resources each team truly had available, not the runs they scored. The reference point everyone learns is the core ratio:

• Work out the resource percentage the first team had.
• Work out the resource percentage the chasing team will have after the interruption.
• Scale the first team's score by the ratio of those two numbers.

In plain terms: revised target = Team 1's score × (Team 2's resources ÷ Team 1's resources), then add a run. If the chasing side ends up with fewer resources than the side that batted first, the target drops. If they have more — which happens when overs are cut before they bat, letting them swing from the start — the target can climb above the original total. That second case is the one that enrages fans, and it's the one that's mathematically correct.

The par score, and why you should watch it

The most useful number for a live viewer isn't the final target at all. It's the par score. At any moment in a chase, par is the total the batting side needs to be level with for rain to declare them the winner. Sit one run above par when the umpires walk off for good, and the match is yours. Sit one run below, and you've lost a game you were still playing.

This is why you'll see a captain suddenly tear into a bowler when clouds gather, even with wickets in hand. The team isn't chasing the final target anymore — it's racing to climb above the par line before the next shower lands. Smart sides keep a constant eye on that figure. Casual viewers watch the asking rate; sharp ones watch par.

A 1992 disaster that forced the maths

To see why DLS exists, rewind to the 1992 World Cup semi-final. South Africa, chasing England, needed a gettable target with a couple of balls to spare when rain interrupted. Under the crude "most productive overs" rule then in use, the break wiped out overs but barely touched the target. South Africa came back needing an impossible 22 runs off one ball. It was absurd, it was unfair, and it humiliated the sport on its biggest stage.

That fiasco is the reason two English statisticians, Frank Duckworth and Tony Lewis, built a model that respected wickets in hand as well as overs. It was first used internationally in the late 1990s and adopted as the official ICC method soon after. Years later, Australian academic Steven Stern refined it to cope with the higher scores of modern Twenty20 and one-day cricket, and the method picked up his initial. Hence three names for one rain rule.

Standard versus Professional: the two editions

Not every DLS calculation is run the same way, and this trips people up.

• The Standard Edition uses a single published resource table. It's transparent enough to run with a printout and a calculator, which is why you'll still meet it in club and lower-league cricket where laptops aren't guaranteed.
• The Professional Edition uses licensed computer software and a more complex model that adjusts better for very high first-innings totals. All top-level international and franchise matches use this version, operated by an accredited match official.

The difference matters most when a team has posted a huge score. The Standard table can misbehave at the extremes, while the Professional Edition handles a 250-plus T20 total without producing a silly target. So in the IPL or an international, you're seeing the Professional Edition, even though the broadcast just says "DLS."

What DLS still can't do

For all its elegance, the method is a model, and models simplify. DLS knows how many balls and wickets you had. It does not know that the pitch was a minefield, that dew was about to make the ball a bar of soap, or that a set batter was three overs from going berserk. It assumes an average scoring shape, then bends that average to the interruption.

That's why you'll occasionally see a result that feels harsh even when the arithmetic is flawless. The maths is fair on average; a single match is not an average. There's also the genuine quirk that batting second can become an advantage once overs are slashed early, because the chasers get certainty the first innings never had.

None of this means the system is broken. It means it's doing an honestly hard job — turning an unfinished game into a fair result — better than anything cricket used before it.

Reading the next rain delay like you know something

Next time the covers come on, ignore the groaning crowd and do three things. Find the par score on the graphic and check whether the batting side is above or below it. Notice how many wickets are standing, because that, more than the run rate, is driving the resource percentage. And remember that a target which jumps upward after a delay isn't a glitch — it's the method correcting for an advantage the chasers just received.

Do that, and you'll be the one person in your group who can explain why the screen says what it says. The weather will still ruin matches. At least now it won't confuse you.