Build the fixture list once, then move what needs moving

Generate a full round-robin schedule for a league from its team list — the app pairs every team using the circle method, inserts a bye when the team count is odd, and writes the fixtures and matches in a single transaction.

League-admin action only (LEAGUE_ADMIN / SUPER_ADMIN / PLATFORM_SUPPORT, or a club role holding the LEAGUE_MANAGE_SCHEDULE capability — backend/src/handlers/standingsHandler.ts:310). Requires an active season (backend/src/services/scheduleService.ts:227) and at least two non-deleted teams (backend/src/services/scheduleService.ts:214). An archived league is read-only, so a closed season's schedule cannot be regenerated.

Choose a single or a double round-robin; the double pass replays every pairing with home and away swapped.

The API accepts one or two passes only — a triple round-robin is rejected by the request schema.

Cap the schedule so each team plays at most a chosen number of games instead of the full round-robin.

Implemented by truncating whole rounds, so with an odd team count the byes still fall where the rotation puts them.

Run a whole tournament day in one calendar block: every generated match gets its own start time spaced by a slot length you set, with an optional break inserted after a chosen match.

Admin-only route (frontend/src/app/router/router.tsx:768). The round-robin/pool-play half is free; the knockout step of the Tournament Day Builder calls the paid, module-gated knockout generator. Slot spacing is a fixed interval (45 minutes unless you change it) — it does not read court rental hours or venue availability, so nothing checks that the day fits inside the hours you booked.

If you try to schedule or move a match into a window where one of the two teams is already playing, the app blocks the save and names the clashing fixture.

It is a soft block: an authorized league admin can force the booking through by re-sending with an override flag (backend/src/handlers/matchHandler.ts:1059). Bulk generation never blocks — it returns the overlaps as warnings instead (backend/src/services/scheduleConflictService.ts:288).

Scheduling a match into a window when the same venue is already hosting one raises a conflict that must be acknowledged before it saves.

The server-side check compares the venue only — it does not consider which court within the venue, so two matches on different courts of the same venue are reported as a venue conflict. Court-level precision exists only as an advisory banner in the browser's schedule manager (frontend/src/pages/app/schedulerConflicts.ts:78), which never blocks a save.

Conflict detection sizes the slot from the sport being played — derived from the league's period or half length where the sport has a clock, and from the sport's own declared typical match length where it does not — plus a handover buffer, with a per-league slot-length override that wins over both.

Match end times are not stored; the check assumes the proposed match and the existing one occupy the same length block.

Leagues that intentionally stack fixtures can force a booking through the conflict check, so the detector never traps an operator who knows what they are doing.

Available to any caller already authorized to write the schedule; there is no separate approval step or audit-specific role for the override.

When you generate a batch of fixtures, the app checks the whole plan against existing matches before writing anything and reports the overlaps it found.

Warning only — generation never blocks. It compares against pre-existing matches; overlaps inside the batch itself are not reported, because whole rounds are deliberately scheduled at the same time for multi-court venues. Venue conflicts are not part of this check either — the generators never assign a venue.

Create one-off matches by hand with a date, time, venue and court number, then move, postpone or cancel any match from the schedule manager.

Admin surface — the schedule manager route is restricted to SUPER_ADMIN, PLATFORM_SUPPORT and LEAGUE_ADMIN (frontend/src/app/router/router.tsx:812); a custom club role holding LEAGUE_MANAGE_SCHEDULE can move matches via the API. Cancel is a status change, not a delete — the row stays on the schedule and can be moved back to SCHEDULED or POSTPONED (backend/src/handlers/matchHandler.ts:1302). Deleting it is a separate action.

Keep a venue list per league with a structured address, capacity, amenities and notes, and attach a venue to any match.

Venue details are operator-facing and require tenant read access to list (backend/src/handlers/venuesHandler.ts:238).

Split a venue into named courts or surfaces, and add, rename, delete or reorder them as the building changes.

Court names are a venue-configuration surface; assigning a court to a match is a manual choice in the match dialog, not an automatic allocation.

Rounds are spaced by exact intervals in UTC, so a season that crosses a daylight-saving change does not slide its start times.

The trade-off is explicit: fixtures keep the exact interval rather than tracking local wall-clock time across a DST change.

Generate a separate round-robin inside each pool, so a group stage schedules pool by pool.

Creating a pool is gated on the paid TOURNAMENT_POOLS module (backend/src/handlers/divisionHandler.ts:237), which is a PRO-tier, per-league opt-in that ships disabled by default (backend/prisma/seed.ts:95). Divisions that are not pools are ungated.

Every public league gets a fan page with a Schedule tab showing its fixtures, readable without an account.

Requires the league to be public and active or completed (backend/src/handlers/standingsHandler.ts:42); signed-in followers of an unlisted league can also read it. Draft leagues stay private, and the tab hides when the Scheduling module is switched off for that league (frontend/src/pages/fan/LeagueFanPage.tsx:69).

Subscribe to a league, team, venue or single match as a calendar feed and open it in Apple Calendar, Outlook or Thunderbird.

A private league's feed inherits the league's access gate. Each league feed returns a sliding window of matches around today, and is capped at a maximum number of events per feed (backend/src/handlers/calendarFeedHandler.ts:283).