← Back to Blog

It is the last round of the group stage. Four teams can still go through, two will. Somebody's cousin has done the maths on the back of a scoresheet and announced that a win is enough. Somebody else has done different maths and says you need to win by forty. Both of them are confident. At least one of them is wrong.

This is how to actually work it out.

Step one: maximum possible points

Qualification is decided on points first, and everything else is a tiebreak. This sounds obvious and it is where most bad reasoning starts, because people jump straight to net run rate when the points question has not been settled.

So begin properly. For every team still in contention, work out their maximum possible points: what they have now, plus two for every match they have left.

Now compare. If your maximum possible points is lower than the current points of enough teams above you, you are out, and no amount of run rate changes it. If your current points is higher than the maximum possible points of everyone below the cut, you are through, and you can stop reading.

Most of the time neither is true, and you are somewhere in the middle. That is when the interesting part starts.

Step two: the other results in the last round

Here is the most common mistake, and it is not a maths error. It is a framing error.

People ask "what do we need to do?" as though their result is the only one that matters. But in the last round, the other matches are happening at the same time. Your qualification usually depends on a combination: you win and a particular other team loses. Or you win by enough that it does not matter what they do.

So the honest answer to "what do we need" is often not a single instruction. It is a set of scenarios:

• Win, and you are through regardless.
• Win, and you are through unless team C wins by more than 60.
• Lose, and you need team C to lose as well, and by a margin bigger than yours.

Any tool or person that gives you one sentence when the situation genuinely has three branches is simplifying in a way that will eventually be wrong at the worst moment.

Step three: net run rate as the tiebreak

When teams finish level on points, net run rate usually separates them. We have written about how NRR works in full, but the one-line version: it is your scoring rate across the whole tournament minus the rate scored against you, all runs over all overs, not an average of per-match figures.

Two consequences matter for qualification.

It is cumulative, so a single game moves it less than people think. If you have played five matches, the sixth is one sixth of the sum. A captain being told to "win by 80 to fix the run rate" is often being asked to do something arithmetically impossible.

Being bowled out counts as the full quota. If you are all out for 90 in 14 overs chasing 20, your run rate is calculated over 20 overs, not 14. This is the single most misunderstood rule in the whole system, and it means a heavy collapse damages NRR far more than a narrow loss.

How many runs to win by, or how many overs to chase in

The question a captain actually wants answered is not "what is our NRR". It is "what do I do at the toss".

Two shapes, depending on whether you bat first.

Batting first: you need a target, and then a margin. The instruction becomes "score X, and win by at least Y runs". Working out Y means asking what total for the opposition would leave your cumulative NRR above the team you are racing.

Chasing: the instruction is an over count. "Chase 141 within 16.2 overs." This is the version that changes how a game is played, because it turns a comfortable chase into a controlled sprint, and it is why you sometimes see a side still attacking with the match already won.

Both calculations need the same inputs: your runs and overs so far, the rival's runs and overs so far, what they are likely to do in their own last match, and the length of the game you are about to play.

Why match length breaks qualification maths

That last input deserves a paragraph of its own, because we got it wrong.

Until recently, Skipper's qualification scenarios assumed a twenty-over match when working out the answers. For a T20 tournament that is fine. For the many local competitions that are not twenty overs, it was not.

A fifteen-over tournament was being told to chase 120 in 18.2 overs. That is a longer chase than the entire match allows. The instruction was not merely wrong, it was impossible, and it was delivered with the same confidence as a correct one.

It now reads the tournament's own overs. Where a tournament genuinely has not recorded them, it asks the organiser rather than guessing. And for formats where net run rate does not apply, like two innings a side, it says so rather than producing a number.

We mention it because it is a useful warning about qualification maths in general: the answer is only as good as its assumptions about the format, and those assumptions are usually invisible. If somebody hands you a required run rate, it is worth knowing what match length they used to get it.

Working out qualification at the ground

All of the above is doable by hand. It is also fiddly, dependent on numbers from other matches happening right now, and being attempted by people who are also trying to run a cricket match.

Which is why Skipper builds it into the points table. Tap any team and it spells out what they need: whether a win is enough, what the required margin is, or the precise over count for a chase. It accounts for the other results still to come rather than pretending yours is the only match, and it uses your tournament's real format.

The point is not to remove the argument. Arguing about qualification is half the pleasure of a group stage. The point is that the argument should be about whether to bat first, not about whose arithmetic is right.

Qualification questions people ask

How is qualification decided in a cricket group stage?

On points first. Compare each team's maximum possible points, which is their current points plus two for every match still to play. Only when teams finish level on points does net run rate separate them.

How do I calculate what net run rate my team needs?

Take your runs and overs across the whole tournament, and the rival's, then work out what result moves your cumulative figure above theirs. It is one running sum over the season, not an average of per-match rates, so a single game moves it less than people expect.

Does being bowled out affect net run rate?

Yes, and severely. If you are all out inside your overs, your run rate is still calculated over the full quota rather than the overs you actually faced. A heavy collapse damages NRR far more than a narrow loss.

What overs are used to work out a required chase?

Your tournament's own match length. A qualification answer calculated against the wrong format is worse than no answer: a 15-over competition told to chase in 18.2 overs has been given an impossible instruction.

Does net run rate apply to two-innings matches?

No. Net run rate is a limited-overs tiebreak. For two innings a side or multi-day cricket it does not apply, and any tool producing a number for those formats is inventing one.