This is a worked example — a 12-team tournament, drawn, scored and part-way through its knockout. Change anything and it becomes yours.
One name per line. A comma after the name is read as the club or school, which the draw can then keep apart.
No teams yet. Add a few, or paste a list.
Club is optional: teams sharing one are kept in different groups where the draw allows.
Suggested group splits
Tiebreakers, in order
Applied top down when two teams finish level on points. A criterion that separates only some of a tied group restarts the chain on whoever is still level.
The code makes the draw reproducible. Write it down and anyone can re-run the same draw and get the same groups — which is what makes a random draw auditable rather than something people have to take on trust.
Nobody has entered yet.
Same rule as the tournament draw: the digits come from the code, so anyone can re-run it and get this grid. Assign the squares first, draw the digits after — that order is the whole point, and the tool holds you to it. The code is generated for you and locks the moment the first square is taken, so the commitment below cannot be changed once people have paid in.
Final score
Type the right answer once it is known and the leaderboard updates. A question with no answer yet is not scored.
Prize split
Works out who is owed what, from a buy-in you state. It sets no odds and no money passes through this page.
On the ground
Figures are exact, not estimates — every format here has an exact count, calculated rather than sampled. Court time assumes every court runs every slot, which is the best case; a real day has gaps.
A full-size event runs to twenty pages nobody reads, so the printed document is whatever you tick here — nothing more.
Built by Steven Turgeon, IT and cybersecurity consultant in Ottawa. This one is here because every bracket generator will happily tell you to run a 144-team round robin and none of them mention it is 10,296 matches. Knowing the cost before you commit is the whole job.