Tournament scheduling guides
Practical guides for organizers - every format, field calculation and league workflow, linked to free generators you can try without an account.
Tournament formats
How each format works, how many matches it produces, and when to pick it.
-
What is a round robin tournament?
A round robin is a tournament format where every team plays every other team exactly once. Instead of eliminating anyone, it keeps the whole field playing until the last round and crowns the champion at the top of a standings table. Because every team faces the same opponents under the same rules, a round robin produces the fairest ranking a format can deliver - which is why it underpins league seasons, tournament group stages and small one-day events. The trade-off is volume: the fixture count grows quickly with the field, so round robins shine when you have the time and fields to play them.
-
Round robin vs single elimination
These are the two most common tournament formats, and they solve opposite problems. A round robin maximizes fairness and guaranteed games by having every team meet every other team; a single-elimination bracket maximizes speed by sending half the field home each round. Choosing between them is really choosing what your event is for - a trustworthy ranking of the whole field, or a dramatic champion decided in the shortest possible time. This guide compares the two on match count, fairness, player experience and logistics, then shows the hybrid format most one-day events actually pick.
-
How many games are in a round robin?
The short answer is "n(n-1)/2" matches for "n" teams - 3 matches for 3 teams, 28 for 8, 120 for 16. Each team plays "n - 1" games, and the schedule takes "n - 1" rounds when "n" is even or "n" rounds when it is odd. That single formula drives most of your planning: it sets how long the day runs, how many fields you need, and whether a full round robin is realistic at all. This guide derives the numbers, lists every count from 3 to 32 teams, and shows how to turn match counts into hours on the field.
-
Group stage and knockout, explained
Groups plus knockout is the two-phase format behind most of the world's best-known tournaments: the field splits into small groups that each play a round robin, then the best finishers from every group advance to a single-elimination playoff that decides the champion. The format exists because the two pure alternatives force an awkward choice - a full round robin is fair but slow, a straight bracket is fast but harsh - so this structure takes the guaranteed games of the first and the climactic finish of the second, and fits both into a single day of field time.
-
Double elimination, explained
A double-elimination bracket gives every team a second life: you are only out after two losses. Teams that lose in the main draw drop into a parallel losers bracket that runs alongside it, and the survivors of the two sides meet in a grand final - which occasionally needs a deciding reset match. The format exists for competitions where a single bad game should not end a campaign: it keeps the speed and drama of a knockout while forgiving one off day, at the cost of roughly double the matches and a structure that takes a moment to explain.
-
The Swiss system, explained
The Swiss system is a tournament format that ranks a large field in a handful of rounds without eliminating anyone. Every round, the scheduler pairs teams with equal or near-equal records - winners play winners, losers play losers - so the standings sort themselves by strength as the day goes on. After about "ceil(log2 n)" rounds, often with one extra added for comfort, the top of the table produces a convincing champion. It is the standard format in chess and card games and a strong option anywhere a full round robin is too long but an early knockout is too harsh.
-
Scheduling an odd number of teams
An odd-sized field cannot split into pairs, so every round of an odd-team round robin leaves one team idle - a bye. Handled casually, byes feel unfair ("why do they get the rest?"), but handled properly they are the cleanest possible solution: the circle method treats the bye as an extra ghost team, and the rotation then guarantees every team rests exactly once while still meeting all real opponents. This guide shows how the method works, walks a 7-team schedule round by round, and covers the fairness details organizers ask about most.
Planning a tournament
From headcount to kickoff: fields, timing, rest, referees and the checklist.
-
How to schedule a tournament
Scheduling a tournament means answering five questions in order: which format you will play, how many matches that format creates, how many fields and hours you have, who referees each game, and how much rest every team gets between matches. Get those five right and publishing the schedule is the easy part. This guide walks through the whole flow end to end with a running example - 8 teams, 2 fields, 20-minute matches - and links to a deeper guide for each step.
-
How many fields do you need?
The number of fields your tournament needs comes down to one equation: total matches x slot length, divided by the hours you have, tells you how many games must run in parallel - and that is your field count. This guide shows the arithmetic with real numbers, explains what "slot length" really includes, and covers the cases where the formula needs adjusting.
-
How long will the tournament take?
A tournament's running time is match count x slot length, divided by the number of fields - plus the overheads everyone forgets: check-in, breaks between matches, finals ceremonies and the inevitable slippage. This guide walks through the maths with concrete numbers and points you at a calculator that does it for you.
-
Rest time between matches
Fair rest is the difference between a schedule that merely fits the day and one that is actually equitable: a team playing three matches in a row while its opponent rested for an hour is competing at a real disadvantage. This guide covers how much rest teams need, how to enforce it in the schedule, and the trade-offs when rest windows fight against a tight finish time.
-
Assigning referees fairly
Referee assignment is a scheduling problem of its own: every match needs a referee, no referee should cover a game they have a stake in, and the workload has to spread evenly enough that nobody spends the day whistle in hand while others rest. This guide covers the three assignment models, the fairness rules that apply to all of them, and how to keep the refereeing plan from collapsing when the schedule shifts.
-
Tournament day checklist
Tournament day rewards preparation and punishes improvisation. Everything below is organised by when it happens - the week before, the morning of, during play, and after the final - so you can work top to bottom. It assumes a typical one-day event like 8 teams, 2 fields and 20-minute matches, but the same shape holds for anything up to a full weekend.
-
Seeding a tournament
Seeding is placing stronger entrants in the bracket or groups so they meet later rather than in round one - it keeps early matches competitive, rewards the ranking teams earned before the event, and produces semifinals that feel like semifinals. This guide covers where seeds come from, how to place them with the serpentine method, and how byes work when your entry count is not a power of two.
Running a league
Fixture lists, home-and-away balance, postponements and standings.
-
How to create a league schedule
A league schedule is a fixture list that covers an entire season: every pairing, every matchday, every venue decision, written down before the first kickoff. Done well, it gives each team the same number of games, a fair split of home and away dates, and a calendar that players, referees, and field managers can plan around for months. This guide walks through the full process - choosing the format, counting the matchdays, mapping them to real dates, and assigning home and away - using a 10-team league as the running example. If you want the arithmetic handled for you, the "league schedule generator" (/tools/league-schedule-generator) produces a complete fixture list from a team count in a few seconds.
-
Home and away balance
Home advantage is real in nearly every sport - familiar field, no travel, more fans. A league fixture list that gives one team eleven home games and another seven has tilted the competition before a ball is kicked. Home and away balance is the discipline of spreading venue advantage evenly across the season: equal counts, alternating patterns, and two-legged ties that mirror each other. This guide explains how the balance works mechanically, where it typically breaks, and how to check a schedule before you publish it. If you are still assembling the fixture list itself, start with "how to create a league schedule" (/guides/leagues/how-to-create-a-league-schedule) and come back.
-
Handling postponements and rescheduling
No league season survives contact with reality unchanged. Pitches flood, referees fall ill, a club's cup run eats a league weekend, a venue double-books. The question is never whether games will be postponed - it is whether your season can absorb them. A schedule with built-in slack and a written rescheduling policy turns postponements from season-ending crises into routine admin. This guide covers the policy decisions to make before round one, the practical options for slotting make-up games, and how to move an entire matchday without breaking the rest of the calendar. The scheduling side of a resilient season starts in "how to create a league schedule" (/guides/leagues/how-to-create-a-league-schedule).
-
Season standings and tiebreakers
A league table converts nine months of results into a single number per team - points - and when two teams finish level, tiebreakers decide who takes the title, the promotion spot, or the last playoff berth. The table looks simple, but the choices underneath it - how many points a win is worth, and in what order ties break - shape how teams play all season. This guide explains the common points systems, the standard tiebreak orders, and the worked examples that expose the edge cases, so you can write rules your league never has to litigate. For the fixture list the table is built on, see "how to create a league schedule" (/guides/leagues/how-to-create-a-league-schedule).
Choosing software
Objective comparisons - and when a spreadsheet is enough.
-
Tournament scheduling software compared
Ten tools organisers actually shortlist, one table, nine criteria - verified against each vendor's own public pages on 14 November 2026, including our own row.
-
Spreadsheet vs dedicated tournament scheduler
Most tournaments start life in a spreadsheet, and many should stay there. This guide maps the honest boundary: where a sheet is genuinely sufficient, and the four places it predictably breaks - conflicts, reschedules, publishing, and staff constraints.
Put it into practice
Build your first schedule in minutes - every feature is free.
Create a free workspace