Rules
How league standings work in local cricket: points, NRR, tie-breakers, and how to explain them to captains without drama.
By CricMatch Editorial · Updated 2026-08-17 · ~681 words
In knockout cricket, one bad day ends your campaign. In league cricket, mathematics decide who advances—and captains will scrutinize every decimal. Publishing a transparent points policy before the first match prevents semi-final heartbreak from turning into a rules fight.
A common local setup awards 2 points for a win, 1 point each for a tie or no-result, and 0 for a loss. Some tournaments award a bonus point for large margins. Whatever you choose, print it on the rule sheet and on your tournament page.
Equal points are inevitable. Define ordered tie-breakers: head-to-head result, net run rate, higher wickets taken, or coin toss as last resort. Head-to-head is intuitive; NRR is fairer across unbalanced groups.
Net run rate (NRR) roughly compares how fast your team scores versus how fast it concedes. A simplified view: (runs scored / overs faced) minus (runs conceded / overs bowled). Tournament software applies precise overs fractions (for example 12.3 overs = 12 + 3/6).
If a team is all out before using full overs, many competitions still count the full allotment for the batting side’s overs faced—check your playing conditions. That detail alone changes who qualifies.
Suppose Team A scored 160 in 20 overs and later chased 140 in 18 overs across two completed games, while conceding totals that average slower. Organizers should not calculate NRR by hand under pressure on final league night. Use a system that updates standings after every completed match and show the table publicly.
CricMatch tournament views help organizers keep points and leaderboards consistent so fans and captains see the same ranking.
Update the table the same evening a match finishes. Explain qualification scenarios (“Team B must win and improve NRR by X”) only from verified numbers. Avoid speculative WhatsApp forwards that invent scenarios.
For rain-hit events, decide in advance whether abandoned games give split points and how reduced overs affect NRR. Put those decisions in writing.
Net run rate is (runs scored / overs faced) minus (runs conceded / overs bowled), across the league, with abandoned-game caveats your sheet should name. If Team A scored 150 in 20 and 160 in 20, they scored 310 in 40 overs (7.75). If they conceded 140 in 20 and 170 in 20, they conceded 310 in 40 (7.75). NRR is zero. That is why “we won big once” may not save you if you also leaked a chase.
When an innings is all out, many competitions still charge the full overs for the batting side’s rate. Confirm that with your association sheet. Getting this wrong on the last league morning is how a semi-finalist is announced and then un-announced.
Same column order, same rounding, same timestamp. If you screenshot a spreadsheet at 11pm and a live table at 8am with different decimals, captains will not trust either. One public table, updated after every completed match, is the whole product.
Write the tie-break order under the table: points, then NRR, then head-to-head, then coin — or whatever you chose — so arguments have a page to point at.
If a team does not arrive, your sheet should say whether they lose the points, whether NRR is hit with a fictional 20-over total, or whether the game is void. Inventing a 200-run penalty on the last morning is how a lawsuit-shaped email arrives, even in amateur cricket.
Washouts that constitute a match (some overs bowled) need a written NRR treatment. Washouts with no toss usually share points and skip NRR. Write both.
The public table should show played, won, lost, no-result, points, NRR. If you hide NRR until the last week, you will be accused of cooking it.