How to organize a cricket tournament

Most local cricket tournaments don't fail on the field — they fail in the admin. A format that needs more matches than the ground has daylight for, rosters that arrive on match morning, a points table kept in someone's head. All of it is avoidable with an hour of planning. Here's the whole job, step by step.

Choose a format

The format decides everything downstream: how many matches you'll host, how long the tournament runs, and how much cricket each team gets. There are three formats that cover almost every local tournament:

• Knockout— lose and you're out. Fewest matches, biggest stakes, fits in a weekend. The trade-off: half your teams go home after one game.
• Round-robin league — everyone plays everyone. The fairest format and the most cricket per team, but match counts grow fast.
• Groups then knockout — the World Cup shape. Groups guarantee every team a few matches; the knockout gives you semifinals and a final worth turning up for. The best default for 8 or more teams.

Count the matches before you commit. The math for common tournament sizes:

Knockout is always one less than the number of teams — every match eliminates exactly one team. A round-robin is n×(n−1)/2, which is why a 16-team league (120 matches) is a season, not a tournament. The groups row assumes top two advance: 8 teams as two groups of 4 (12 group matches plus a 3-match knockout), 12 teams as four groups of 3 (12 plus a 7-match knockout), and 16 teams as four groups of 4 (24 plus 7). If you can host about 6 matches a day on one ground, a 16-team groups-and-knockout tournament is roughly five full days — know that before you promise anyone a two-day event. If the league math is too heavy but every team deserves more than one game, groups are the compromise: a 4-team group gives each team three matches before the knockout starts. To see the exact draw for your teams, put their names into the free fixture maker, or read how to make tournament fixtures.

Collect teams and rosters

Open registration at least two weeks out and set a hard deadline a few days before the draw — you can't schedule fixtures around teams that may or may not exist. For each team you need three things: a captain with a working phone number, a full roster (with a couple of substitutes beyond your playing XI), and jersey numbers if you're printing anything.

Get rosters in writing before the tournament starts, not on match morning. Two reasons: it's your only defence against ringers — the "cousin who just happened to turn up" who played district cricket — and it's what makes individual stats meaningful later. Decide your substitution rules now too (can a player who has already played for one team turn out for another? almost always: no) and tell every captain the same answer.

Schedule across days and grounds

Start from your real constraint: match slots. A 10-over match takes about 90 minutes with the innings break; add 30 minutes of buffer for the toss, a late start, and the handover between matches. On a single ground with daylight from 8am to 6pm, that's five, maybe six matches a day. Two grounds doubles it — but only if both are genuinely playable and someone responsible is stationed at each.

Then apply three rules. First, no team plays back-to-back matches — bowlers' bodies and tempers both need the gap. Second, put the matches that matter (semifinals, final) late in the day or on the final day, when the crowd is biggest. Third, publish the schedule before the first ball and treat changes as expensive: every reschedule is ten phone calls and one team that didn't get the message. Leave one spare slot per day for the inevitable overrun or rain delay.

Assign scorers

Every match needs exactly one person whose job is the score — named in advance, not volunteered at the toss. A player on the batting side keeping the book between overs is how you end up with two versions of the total in the last over. Neutral scorers are ideal; at minimum, pick someone who isn't playing in that match.

Brief your scorers before day one on the rules you're actually playing with: what counts as a wide down leg, whether a no-ball gets a free hit, how many overs per bowler, what happens on a tie. Playing with a tennis ball or in a box? The tennis-ball cricket rules and box cricket rulesguides list what to settle. Ten minutes of alignment saves an hour of argument. And agree on the correction protocol: mistakes get fixed the moment they're spotted, announced out loud, never quietly edited after the match.

Share the public link

A tournament feels real when people who aren't at the ground can follow it. Put the fixtures, live scores, and points table somewhere public, and share one link — in the captains' WhatsApp group, the colony group, the office group. One link beats a nightly screenshot of a spreadsheet: it's always current, nobody asks "is this the latest?", and parents and teammates who couldn't make it can check the score from anywhere. Do it from day one, not just for the final. A live page also quietly raises the standard of everything else: teams show up on time for fixtures everyone can see, and scorers are more careful when the scorecard is public.

Keep standings honest

More tournaments are soured by a disputed points table than by anything that happens on the pitch. The fix is boring and completely effective: decide the rules before the first ball, write them down, and share them with every captain. Points per win, draw, and washout. The tiebreaker — for cricket that's net run rate (NRR), so define it and don't hand-wave it; the NRR calculator settles any argument over the sums. What happens if a team forfeits or turns up short.

Then update results the same day, every day. A table that lags behind the cricket invites people to keep their own — and once there are two tables, you have a dispute. When a scoring error surfaces, correct it visibly and tell the affected captains directly. The standings only work if everyone believes them.

Let the software do the admin

Everything above is the organizer's judgement; almost none of it needs to be manual labour. This is what SportsScorer automates: pick any of the three formats and fixtures generate themselves, teams register through a link into an approval queue, captains add players by phone number, each match gets an assigned scorer with ball-by-ball scoring that survives a dropped connection, and the public page — live scores, scorecards, standings with NRR, knockout progression — updates itself with one shareable link. It's free, works on Android and the web, and your spectators need no login at all. Create your tournament and spend match day watching the cricket instead of the spreadsheet.