TRC Tournament Scheduler

Select a block to see its full match rundown.

Utilisation by lane

Pool match length — sets every age group

Knockout match length — sets every age group

Add an age group

Removing a group deletes its placement, team names and fees.

Presets — each adds only what is missing

Name the teams in each pool. Names appear on the board, in the match rundown and in every export. Leave a slot blank and it keeps its pool code. Knockout fixtures stay as progression labels — W QF1 v W QF2 — because who plays is not known until results are in.

Auto-arrange

These pack the board by longest block first. It balances the lanes but knows nothing about heat, age or which games you want as showpieces — a starting point, not an answer.

Days

A day’s number is its position here. Removing one renumbers the days after it, and whatever is scheduled on those days moves with the renumbering.

Add a day

Pitches

Each pitch becomes a lane on both days. Give pitches at the same ground the same venue — exports group by venue, and the board keeps them as separate lanes.

Add a pitch

Start over

Timing

Doors open

Doors close

Turnaround between games

Snap increment

Gap wanted between pools and knockout

Changeover — same pitch layout

Changeover — different pitch layout

These apply to every age group. Match lengths, squad sizes and formats are set per age group on the Age groups tab.

Ranking

Entry fee per team — sets every age group

Or edit one age group in the table below.

What each club pays

Running costs

Enter rates and the counts come from the schedule, so the shape of the day is priced in — running four games at once needs four referees on the whistle, not two. Leave these at zero and the tab stays a revenue sheet.

Files

The .md reads as a document and still imports — the full config travels in a fenced JSON block at the end of it. Either file can be mailed or dropped in a chat and opened here.

Saved versions

The board autosaves as you work, but only ever holds one state. Save a named version when you have something worth keeping, and come back to it after experimenting. Versions live in this browser — use a file to move them between machines.

Export for Tournify

Tournify imports teams by pasting, has no schedule import and no API, so these are paste blocks and working sheets rather than a file it can swallow. The two tools are complementary: this one decides the shape, Tournify runs the day — its planner cannot take scheduling constraints such as minimum rest, which is exactly what this works out.

The handover page is the one to work from — every step in order, teams with a copy button per division, and the fixture list grouped the way you will drag it. It prints cleanly if you would rather have it on paper next to the laptop. The two text exports are there if you want the raw data in a spreadsheet.