Days, fields, and the schedule window
The Venues step defines the tournament's playing surface: how many days it runs, the daily time window matches may occupy, and which fields exist on each day.
The schedule window
A single-row configuration sets:
- Number of days (capped by your plan's per-tournament limit where one applies).
- Earliest match start and latest match end - the daily window.
- Grid interval - 10, 30, or 60 minutes; the granularity of the painted grid and of drops on the schedule board.
Shrinking the day count or window warns before dropping painted periods that fall outside the new bounds.
Fields
Add fields to each day from the tenant's field list, grouped into per-location columns (with a "No location" column). A field is schedulable only on days where it is assigned - removing it from a day clears its painted periods there. Fields can carry an optional turnaround time: idle minutes kept free between consecutive matches for changeovers or resurfacing.
Fields can also live only in this tournament: New field for this tournament creates a locationless tournament-local field in the "This tournament only" column - handy when you will never reuse the venue. It assigns to days, paints, and carries transition time like any workspace field, and Save to workspace copies it into your Locations records for later tournaments.
Days
Day cards rename inline on click and keep their own field columns and painted grids. League-style play spread over matchdays uses Copy setup on a day card to stamp fields and painted cells onto other days - day names and dates stay untouched.
Painting shortcuts
Manual painting is not the only way to a valid grid: Fill day under a field's column header paints that field's whole day for all selected categories at equal priority, Fill all days next to a selected field does the same on every day (assigning the field where needed), and the first-run Use all field time banner fills every field on every day in one click. Each replaces painted cells in its scope after a confirmation.
Validation requires at least one day, one field per day, and one painted category cell before generation can run.
The capacity estimate renders in hours (minutes in parentheses) and appears both beside the schedule configuration and under the day-grid heading, so it is visible before and while painting.
League matchdays
When a category format contains a round-robin stage (including the round robin inside a group stage), a collapsed League matchdays (optional) panel appears between the schedule window and the day grids - it opens on its own once a mapping exists. Each stage card lists the round count its current entrants will generate and a mapping table: one row per matchday with an optional name, the rounds it hosts, and the tournament days it may be placed on. A match bound to a matchday can only be scheduled on that matchday's days. Auto-assign fills the table with one round per day in order; an empty mapping leaves the stage's matches free across all days.
The collapsible Season calendar form stamps the whole weekly calendar in one step: first matchday date, number of matchdays, and weeks between them. It creates days named "Matchday 1", "Matchday 2", ... on that cadence using the configured daily window - paint one matchday's fields and use a day card's Copy setup to replicate it across the season.