Define the goal and scale first
Double round-robin: how many rounds is easier when simple rules are combined with a realistic time plan. Start by defining participant count, available courts or stations, tie-breaking rules and the required finish time. Pairings should be generated only after those constraints are clear, otherwise the entire event may need to be rebuilt after the first round.
TurniejTo performs calculations locally in the browser. Player data is not uploaded to a server, and a complete project can be backed up as JSON. This guide presents a practical workflow and highlights the decisions that most often cause avoidable problems.
An informal eight-player event needs a different plan than a full-day competition with thirty-two teams. Write down the start time, the latest acceptable final, the number of venues and a realistic match duration. Add a buffer for changeovers, recording scores and unexpected delays.
Choose the format according to the goal. Knockout is fast and dramatic, round robin gives everyone more play, and groups followed by playoffs combine both approaches. Double elimination reduces the effect of one unlucky loss but adds more matches.
Prepare participants and rules
Use consistent participant names and check for duplicates. Mark seeded players before the draw. When entrants come from several clubs, schools or departments, consider keeping them apart in the opening round or distributing them across group pots.
The rules should explain points, draws, tie-break order, walkovers, lateness and disqualification. Decide who confirms each score and what happens when an error is discovered after a later round has already started.
Build a schedule with buffers
Do not place matches back to back without considering progression. The same player may advance and require rest before the next round. The schedule should include bracket dependencies, venue changeover time and the possibility of a longer match.
For multiple venues, use clear labels such as Court 1, Court 2 or Table A. TurniejTo can generate the timetable automatically and mark conditional matches whose participants will only become known after earlier results.
Record results in one place
Enter a score immediately after the match. In knockout formats, confirming the score advances the winner automatically. In a league, points, score difference and rank update at once. When a mistake occurs, use the undo or clear-result action rather than editing several later pairings manually.
For a projector or television, use display mode. The operator retains the editing panel while participants see a clear schedule, standings and upcoming matches.
Back up the project and prepare exports
Even with local saving enabled, download a JSON backup before the event. Create another backup after the group stage and before the finals. The file restores the entire project on another device without retyping results.
Export the bracket as SVG or PNG, the schedule as CSV and the full report as PDF. For online sharing, use the standalone HTML export, which contains no editing controls and does not update automatically.
Common mistakes
- Leaving no recovery time between consecutive matches.
- Choosing tie-break rules only after a tie appears.
- Running a draw without marking seeded participants first.
- Keeping no project backup and relying on a single browser tab.
- Placing ads, notices or unrelated controls next to score fields.
The best tournament plan is simple, transparent and achievable within the available hours. Run a rehearsal with sample names and test scores before the real event.
Practical example
Assume that “Double round-robin: how many rounds” concerns an event with sixteen participants, two venues and four hours of playing time. The organizer first records every entrant and then chooses a format that fits the available window. A single-elimination bracket needs fifteen matches, while four groups of four followed by quarterfinals give each participant more guaranteed play.
With twenty-minute matches and five minutes for changeovers, one venue can handle roughly two matches per hour. Two venues can run four matches in parallel only when no participant is required in both places. Minimum recovery time should be entered into the schedule generator before the draw is finalized.
After creating the project, enter two sample scores, verify progression and test the undo action. This short rehearsal exposes incorrect scoring rules, unrealistic breaks and unclear venue names before participants see the timetable.
Organizer checklist
Before publishing the schedule, confirm each of the following:
- the participant list is complete and contains no accidental duplicates;
- seeds and draw pots were marked before randomization;
- rules explain draws, walkovers, lateness and disqualification;
- match duration includes real play and changeover time;
- no participant is required at two venues simultaneously;
- later rounds contain enough recovery time;
- the operator knows who confirms results and how to undo one;
- a JSON backup exists before the first match;
- printouts and display mode are readable from a distance;
- participants know where the current schedule will be shown.
A checklist does not replace formal rules, but it prevents small omissions from becoming major delays. Review it the day before the event and again immediately before the opening round.
After the tournament
After the final, confirm the last score, verify the champion and final ranking, then download both a PDF report and a JSON backup. PDF is convenient for archives and print, while JSON preserves the complete editable structure. A standalone HTML file or PNG image can be prepared for participants.
Remove private organizer notes from anything intended for public distribution. If the project contains children’s full names or other personal information, share it only under the event’s privacy rules. The local TurniejTo copy can be deleted from Settings after the selected exports have been stored safely.
Practical questions
Can a result be changed after progression?
Yes. The application warns that dependent later results may be cleared so the bracket cannot remain in an inconsistent state.
Can the same project be used on another computer?
Yes, export JSON and import the file on the other device. IndexedDB saving does not synchronize automatically.
Is an internet connection required?
After the application has been loaded once, core tournament management can work offline. Advertising and the central project list may be unavailable.