The DLS method explained without the maths

Rain interrupts a chase, the target changes, and somebody on the boundary insists the new number is unfair. The Duckworth-Lewis-Stern method is one of the most complained-about things in cricket and one of the least understood, and the underlying idea is genuinely simple even though the arithmetic is not.

Start with the thing DLS is trying to protect. A team batting second knows exactly what it needs, which is an advantage. A team whose innings gets cut short loses overs, which is a disadvantage. If you simply scaled the target by overs remaining, you would ignore the other resource a batting side has: wickets. Ten wickets and five overs is a completely different situation to two wickets and five overs, even though the overs are identical, because the first team can attack every ball and the second cannot.

So DLS treats a batting innings as a stock of two resources, overs and wickets, and works out what percentage of that stock a team has left at any moment. A side that has lost no wickets with most of its overs remaining holds nearly all its resources. A side deep into its innings with one wicket standing holds very few. The revised target is set so that both teams have had the use of a comparable share of resources. That is the whole concept. Everything else is the table that converts a given overs-and-wickets combination into a percentage, which is built from a large historical record of how scoring actually behaves.

This is why the revised targets that feel wrong usually are not. When a chasing side loses overs but still has all its wickets, the target barely drops, and that surprises people. It should not: losing overs when you have every wicket intact costs you less than losing overs when you are seven down, because the wickets let you take more risk in the overs you have left. The method is charging you for what you actually lost.

Where it gets genuinely contentious is at the edges. Very short revised games amplify small differences, because the resource percentages change steeply when few overs remain. A team that was setting up an assault at the death and never got to play it has a legitimate complaint that no formula can capture, since the model works on averages and that team's plan was not average. And the calculation cannot know that the pitch changed under lights, or that dew arrived.

For a tournament played entirely in Barbados in September, this is worth understanding before it matters rather than during a rain delay. The practical points are the ones to hold on to: a match needs a minimum number of overs in the second innings to produce a result at all, the revised target appears on the scoreboard rather than being negotiated, and if a game is abandoned without reaching that minimum it is a no-result. How your particular operator settles a no-result is in their rules, not in the DLS tables, and it is worth reading once in advance.