Most local tournament disputes aren’t about the cricket. They’re about the schedule, the rules, and who is really ahead in the table. Settle these things before the first ball and the whole event runs more smoothly. This guide works through the decisions in order, with free tools for each step.
1. Choose the format to fit your ground time
Start with how many matches you can realistically play. A round-robin, where everyone plays everyone, is the fairest format, but the number of matches grows fast: n × (n − 1) ÷ 2.
| Format for 8 teams | Matches |
|---|---|
| Single round-robin + final | 28 + 1 = 29 |
| Two groups of 4 (round-robin) + semi-finals + final | 12 + 2 + 1 = 15 |
| Straight knockout | 7 |
For a weekend event with one ground, two groups plus knockouts is usually the right balance: every team gets at least three games, and the event still finishes on time.
2. Fix the match length
For time-limited local events, 6, 8, 10 or 12 overs per side are common. Allow about 4 minutes per over plus changeovers when planning. A 10-over match usually needs around 90 minutes, slot to slot.
3. Write the rules down before day one
Put these in a one-page rules sheet and share it in the captains’ WhatsApp group:
- Points: the usual system is 2 for a win and 1 each for a tie or no result.
- Tie-breakers, in order: for example points, then wins, then net run rate, then head-to-head.
- Tied matches: shared points, or a super over?
- Bad weather: the simplest fair rule is to reduce overs equally for both sides. If the second innings can’t start, it’s a no result.
- Walkovers and late arrivals: how long do you wait, and how many points does the team that turned up get?
- Player eligibility and bowling limits: for example, a maximum of 2 overs per bowler in an 8-over game.
4. Make a fair schedule
Use the fixture generator. It uses the circle method, so no team plays twice in one round, and with an odd number of teams each gets exactly one bye. Add the start date to get a dated list, then download it as a CSV for Excel or Google Sheets.
Tip: if some teams can only play at certain times, reorder the team list and regenerate until the early rounds suit them.
5. Record scores properly
For each match, write down runs and overs for both innings, and whether the side was all out. You need all of these to work out NRR later. “Team A won by 20 runs” isn’t enough information.
6. Keep the points table live
After each match day, enter the results in the points table maker. It sorts teams by points, wins and NRR, applies the all-out rule, and saves the results in your browser for next time. Share the printed or CSV table after every round so captains can check their own figures.
7. The final round: tell teams what they need
When places are still open, teams will ask what they need to do. The NRR qualification calculator answers exactly that, for example “win by 27 runs, or chase it within 17.2 overs.” Sharing this in advance heads off arguments afterwards.
Quick checklist
- Format chosen to fit ground time.
- Overs per side and bowling limits agreed.
- Rules sheet shared with captains, including tie-breakers.
- Fixtures published.
- Scorer briefed to record runs, overs and all-outs.
- Points table updated after every match day.
New to NRR? Read Net run rate explained.
Written by Basant Upadhyay. Every figure in this guide was worked out with the calculators on this site. Last reviewed September 2026.
