Cricket Points Tables and Tiebreakers

A cricket points table is not just a leaderboard. It is the public record of rules you chose before the league began and results you entered afterwards. It becomes contentious when either part is vague.

This guide gives you a rule set to publish, a worked table you can audit by hand, and the exact boundary of CricketOrganizer's current table. The live table records result outcomes. It does not collect scorecard runs and overs, so it does not calculate net run rate (NRR).

Publish the points rule before fixtures begin

For a standard league, state the points beside the registration rules and repeat them in the captain's briefing:

This is also CricketOrganizer's current default: a win is worth 2, a loss 0, and a tie or no result gives each team 1.

The table is only the first decision. Publish these six answers before the first match:

1. How many points does each result earn?
2. What counts as a tie, a no result, a forfeit, and an abandoned match?
3. Does a shortened match count, and under which playing conditions?
4. What is the full tiebreak order?
5. Who corrects an entered result, and by when?
6. When does the league table freeze before a knockout draw?

Do not add bonus points or change the tiebreak order once teams have played. A simple rule that every captain can reconstruct beats a complicated rule no one can apply consistently.

Build a four-team table by hand

Suppose a league has four sides: Falcons, Rangers, Tigers and Warriors. Three completed fixtures have these outcomes:

The audit table is then:

For every row, check both equations:

P = W + L + T + NR
Pts = (W × 2) + T + NR

The completed-fixture total is another useful check. Three completed matches should contribute six team appearances. Here, `2 + 2 + 1 + 1 = 6`.

Record each result in CricketOrganizer

The current flow records the outcome, not a ball-by-ball scorecard. To update the visible table:

1. Open the tournament's Matches page.
2. On the fixture row, select Record result. The same control becomes Edit result after a result is saved.
3. Optionally record the toss winner and decision.
4. Under Winner, choose either team, Tied, or No result.
5. For a winning team, enter a positive margin and choose runs or wickets.
6. Select Save result. The fixture is saved as Completed.
7. Open the Points table tab to see the recalculated rows. The public tournament table uses the same derivation.

Choosing Tied saves the result description “Match tied”. Choosing No result saves “No result”. That wording matters in the present implementation: a completed result with no winner is counted as a tie only when its result description contains “tie”. Otherwise it is counted as a no result.

Know what the live table counts

CricketOrganizer builds both the organizer and public tables with `deriveStandings` in `src/utils/standings.ts`. Its behavior is specific:

That last row explains one otherwise puzzling outcome: a fixture can be marked completed yet have no effect if either linked team has been deleted. Treat deleted-team data as a correction task before publishing the final table.

Use the current sort honestly

The live rows sort in this order:

1. More points first.
2. More wins next.
3. Team name last, in alphabetical order.

Team name makes the list stable. It is not a sporting tiebreaker. If two teams finish level on points and wins, the current table will place them alphabetically unless you maintain and publish a separate competition decision.

CricketOrganizer does not show an NRR column or calculate NRR from recorded results. The result dialog captures the winner, margin, toss and result description, but no innings runs or overs. A separate `standingsCalculator.ts` contains NRR arithmetic used by the standalone tool, not by the rendered points table.

If your competition uses NRR, keep a scorecard-based ledger for every included match and calculate it independently with the net run rate calculator. The net run rate guide explains aggregate totals, cricket-over notation and the all-out rule.

Choose a tiebreak order you can prove

For a league that keeps complete scorecards, this is a defensible published order:

1. Points.
2. Wins.
3. NRR across the matches your rules include.
4. Head-to-head, only if every relevant side played the same applicable fixture.
5. A playoff or draw, if a qualification place still cannot be separated.

For a competition using only the current CricketOrganizer result entry, stop after points and wins unless you keep the extra evidence yourself. Do not call NRR automatic, and do not insert it retrospectively from partial scores.

State whether head-to-head comes before or after NRR. A three-way tie can make head-to-head ambiguous, which is why the rule needs to say what happens when it does not produce one clear order.

Audit the table after every round

Use this short reconciliation routine before you share an updated table:

1. Filter the fixture list to completed matches.
2. Compare that count with the results you have actually confirmed.
3. For each team, check `P = W + L + T + NR`.
4. Recalculate points from the published points rule.
5. Check that every completed fixture has two existing teams.
6. Read the tie and no-result descriptions, rather than assuming a blank winner means one or the other.
7. If NRR is in your rules, reconcile runs for, overs faced, runs against and overs bowled from the scorecards before applying the tiebreak.
8. Write a short correction note when a result changes, such as “Match 12 corrected to no result at 18:40”.

The fixture and duration calculator helps you decide the number of league fixtures your table must absorb. Use tournament formats compared to choose that structure, then ground and slot allocation to leave enough time for delayed matches and result checks.

Copy this rule notice into your competition pack

League points: win 2, tie 1 each, no result 1 each, loss 0.
The table ranks teams by points, then wins.
[Add NRR here only if you maintain complete scorecard totals for every included match.]
Any remaining tie is decided by [head-to-head / playoff / draw].
The organizer records and corrects results until [time or round], then freezes the table before the knockout draw.

Replace the bracketed choices before publishing. The cricket fixture generator hub covers the schedule and public-table workflow. The rule notice belongs alongside it, before the first fixture gives anyone a reason to dispute the table.