Scoreline Hub
Cricket Football Tennis IPL FIFA Wimbledon Athletics Basketball
AboutContactPrivacy Policy

How Rain Rules Turn A Match Into A Target Number

ADVERTISEMENT

When rain shortens a limited-overs match, the revised target is calculated rather than negotiated. The calculation rests on a model of what a batting side still has available to it.

Why a simple proportion fails

Scaling a target by overs alone assumes runs accumulate evenly, which they do not. A side chasing at eight an over for the last five overs is not scoring at its innings average.

It also ignores wickets entirely. A team with nine wickets in hand and a team with two are in completely different positions even with identical overs remaining.

Any usable method therefore has to combine both. The overs left and the wickets left are the two things that determine how aggressively a side can bat from here.

The idea of a scoring resource

Rain rules treat overs and wickets together as a single quantity: the capacity a side still has to score. Losing overs and losing wickets both consume it, at different rates.

The relationship is not linear. Early wickets cost proportionally more capacity than late ones, because they constrain how the entire remaining innings can be played.

An interruption is then handled by comparing capacity available to each side. If the chasing side has less than the setting side had, its target is reduced by the same proportion.

Why revised targets look strange

A team five wickets down often receives a smaller reduction than a team none down after the same interruption. The model has already priced their lost wickets as consumed capacity.

Targets can also rise per over even as the total falls. Fewer overs with wickets intact means a higher required rate, which is the model's assessment rather than a penalty.

Spectators reading the revised total as a punishment or reward are misreading it. It is an arithmetic restatement of a position that already existed before the rain arrived.

What the scorers actually do

The calculation is performed by the official scorers, not by the umpires or the broadcaster, and the result is communicated to the players through the umpires.

Because the model is tabulated, the same inputs always produce the same output. Two scorers working independently should arrive at an identical figure, which is the check that it was done correctly.

Every interruption is timestamped and logged, because the calculation depends on exactly when play stopped and resumed. The log becomes part of the match record alongside the scorecard.

Where the model's assumptions show

Any resource model is calibrated on historical scoring patterns, and scoring patterns change. Batting sides now attack more freely in phases where earlier calibrations assumed consolidation.

Governing bodies revise the tables periodically for this reason. A method left uncalibrated slowly drifts away from the game it is supposed to describe.

That drift is invisible to spectators, who see only a number appear on a screen. The number carries assumptions about how cricket is played, and those assumptions have an expiry date.

A batter with one gear is still worth picking

The phrase you hear in selection meetings is that a player is one-dimensional. It is said as a criticism. I have never fully understood why, given that the format is short enough that a team only needs a handful of dimensions in total and can distribute them across eleven bodies.

Consider the batter who can only hit down the ground and only against pace. He is useless in the middle overs against two spinners on a turning surface. He is also, in the right six deliveries, the most valuable player on the field, because the thing he does badly never comes up and the thing he does well comes up repeatedly.

The counter is obvious and it is about flexibility. If a wicket falls at the wrong moment, a specialist walks into a situation he cannot handle, and you have burned a slot. That is real. But it is a scheduling problem, not a talent problem, and scheduling problems have solutions that talent problems do not.

What actually happens is worse than either. Sides pick a squad full of players who are competent in every phase and outstanding in none, then wonder why they keep posting adequate totals and losing to somebody who had one man go berserk for four overs. Competence across the board is a way of guaranteeing you are never the reason a match turns.

I would rather carry two narrow players and accept that in a third of matches one of them is dead weight. The distribution of outcomes matters more than the average, because you do not get half a trophy for finishing consistently mid-table in a knockout competition.

There is a coaching dimension to this that gets ignored. Telling a specialist to broaden his game usually makes him worse at the thing he was picked for, because the technique that lets a player hit a length ball over long-on is not the technique that lets him work it into the leg side. They fight each other. He ends up in the middle, hitting neither shot with conviction, and within a season he is a squad player.

Leave him alone. Let him be strange.

The best selections I have watched were not the most complete cricketers on the list. They were the ones whose weakness the captain had a plan to hide.