Start with the rules you will publish
Write these down before you invite a single team:
- Overs per side and the maximum per bowler.
- Ball type (leather, tennis, tape) and whether the match uses a cap for each bowler.
- Whether DLS applies, and which tool the league will use.
- How a tie is decided: super over, bowl-out, or shared points.
- How points are awarded for wins, ties, no-results and walkovers.
- Who can protest a result, by when, and what evidence counts.
If it is not written, it will be invented in week four, usually by the captain who is losing.
Build the fixture around the ground
Count the grounds and the match slots first. A round-robin of eight clubs needs seven rounds if each club plays each other once, and more if you want a return fixture. Work out how many weekends you have, how many games a ground can hold, and where the rain-off dates go.
Put a reserve date into every week. A tournament that cannot absorb one wash-out will be rearranged in a panic, and the panic is where the errors happen.
Choose the format
- Round robin: every team plays every other. Fair, and the table decides the winner. Needs more fixtures.
- Groups and knockouts: two or more groups, then a semi-final and final. Shorter, but a team can be knocked out after one bad afternoon.
- Single knockout: the quickest format. Use it only when time is short.
Pick one, write it down, and do not change it halfway.
Name the scorers
Every match needs a scorer whose name is recorded on the scorecard. One scorer with a live book beats three people filming the square. If the league wants two scorers, name both and agree who signs the final book.
On match day
Publish the scorecard link in the group before the toss. Arrive early enough to agree the playing conditions with both captains, check the pitch and the boundaries, and confirm the umpires. Note the start time. If the start is delayed, write the time of the first ball.
After the match
Lock the result. If you allow edits, log who changed what and when. Points tables die when a captain can quietly edit a no-ball. Publish the table after every round, not only at the end, so people can see the arithmetic.
Settle disputes with the book
When a captain disputes a score, the book is the evidence. Check the disputed ball against the scorer's record and the umpire's account. Decide the dispute by the written rule, not by which captain is louder.
Common mistakes
- No written playing conditions, so every decision is a fresh argument.
- Fixtures that clash with a ground's other bookings.
- A points table that uses different rules for different groups.
- No plan for rain, so the final is rushed.
Citations
Club practice. Pair your rules with the MCC Laws for anything the playing conditions do not cover.
Match questions
Questions scorers actually ask
- 01 How many overs should a club tournament use?
- Whatever the ground and the time allow, but it must be fixed before the first fixture. T20 (20 overs) is the most common club format because it fits one afternoon.
- 02 How do I handle a wash-out in a round robin?
- Decide in advance: a rained-off match is a no-result with a point each, or the fixture is replayed on a reserve date. Write the rule into the playing conditions.
- 03 Do I need a DLS tool?
- Only if rain is likely to shorten matches and you want fair targets. Name the official tool in the playing conditions so nobody has to guess.
- 04 How do I stop a table dispute?
- Publish the table after each round with the scorecards linked, and keep the edit log. Most disputes disappear when the arithmetic is visible.
