Round Robin Schedule Generator

Everyone meets everyone. Generate rounds, handle byes, and print the fixtures.

One list becomes a complete fixture schedule

Enter between two and thirty-two teams or players, one per line, then choose Generate fixtures. A single round robin gives every participant exactly one match against every other participant. You can print the resulting rounds, save them as a PDF through your browser, or download a CSV for your own spreadsheet. Nothing in this process books a venue, sends invitations, or uploads the names.

The initial order is used as entered unless you select Shuffle starting order. Shuffling uses the same browser-based randomness as the site's other tools. It changes which match appears in which round, not the guarantee that every pair meets. If two participants have the same name, add initials or another short identifier rather than leaving the schedule ambiguous. Names are limited to forty-eight characters to keep the printed fixtures readable.

How rounds and byes work

With an even number of participants, a single round robin has one fewer round than participants. Six teams therefore produce five rounds, three matches per round, and fifteen matches in total. No participant appears twice in the same round. The schedule uses a rotation method: one position stays fixed while the remaining positions rotate, creating a different set of pairs each round.

With an odd number, the generator temporarily adds an empty position. Whoever is paired with that position receives a bye rather than a match against an imaginary team. Five players produce five rounds, two matches in each round, and one bye for every player across the schedule. A bye is a scheduled rest, not a loss or an automatically awarded win; decide your competition's scoring rules separately.

Select Play twice to append a second leg with each fixture's home and away labels reversed. This doubles the number of matches and rounds. For five teams, it also gives every team two byes across both legs. In the single-leg version, home and away are organizational labels, not a guarantee of perfectly balanced travel, court position, or competitive advantage.

Turn rounds into an event plan

A round is a grouping of non-conflicting matches, not a clock time. If you have enough courts, tables, or stations, its matches can happen together. With fewer venues, divide the round into time slots yourself and leave room for changeovers, breaks, and overruns. The generator does not know court availability, referee assignments, travel constraints, or how long a match will take.

For a small classroom event, the printed version can be sufficient: put the round sheets where everyone can see them and record results by hand. For a club tournament, download the CSV and add columns for venue, start time, scores, and officials. Keep the original participant names consistent as you edit. The CSV includes explicit bye rows so rests are not lost when you move the schedule into a spreadsheet.

If you need groups before fixtures, use the random team generator first, then give each resulting team a short name here. If you only need a presentation order, the list shuffler is simpler than generating every possible pair. Choosing the smallest tool that answers the actual question makes the final plan easier to explain.

Printing, changes and privacy

Generate and inspect the fixture count before printing a large event. Thirty-two teams produce 496 matches in a single leg, so even a correct schedule may be much larger than your available event time. Print preview hides the input controls and explanatory material, keeping the fixture rounds. Browser paper size, scaling, margins, and optional headers can affect pagination; check the preview before sending many pages to a printer.

Editing the names or options clears the previous results and disables printing and export until you generate again. This prevents an old schedule from looking as if it reflects a changed participant list. There is no account or saved history, so download the CSV or PDF if you need to keep the result. Anyone who receives that file can read its participant names; use team labels rather than sensitive personal details when sharing publicly.

Questions