Collect everything first
A wrong input costs more than anything else. The questions come before the solving.
How it works
Four stages. Each one builds on the last.
The method comes from a real season of 16 teams across 6 venues. SeasonSolve writes it down so any program can repeat it.
-
1
Venues
Every court, field and hour you can use, and what each one costs.
- Name each venue exactly as it appears in your team platform, so exports never fail on a typo.
- Courts, dividers and side baskets. Which rims lower to 8 or 9 feet.
- Hours for each weekday, hours that change in January, closed dates and limited-hours dates.
- Time that’s reserved for something else, like an outside trainer.
- How the venue bills: by the hour used, by the hour held, by the week, or free.
You confirm a heat map of open courts and fields before moving on.
-
2
Teams
Every team’s needs, limits, partners and preferences.
- Practices per week in each part of the season, and how long they run.
- Nights that never work, the latest a young team can finish, game nights.
- Equipment and space, like rim height or field size, which rule some venues in or out.
- Who must share, who may share, who shouldn’t, and how.
- Coaches with more than one team, so their practices never collide.
A feasibility check flags anything impossible, in plain English, before solving.
-
3
Solve and review
SeasonSolve fits the puzzle and a separate checker confirms it.
- The repeating week is solved first, period by period, with A/B weeks if you need them.
- Dates are layered on top: blackouts cancel practices (and flag them), make-ups and holds are added.
- Every change asks its scope: this one date, holiday weeks only, this period, or the whole season.
- An independent checker tests every rule against every practice. If it disagrees, nothing ships.
You review one page with the season summary, each week, and anything still to be decided.
-
4
Publish and maintain
Export once, then change carefully.
- Export to leading youth sports management platforms with exact names, one line per team per practice. Export and upload into TeamSnap and GameChanger are already proven.
- After that, changes go out in numbered batches: an import file for additions and a checklist for deletions.
- The public schedule is compared against the plan, event by event, on demand or on a schedule.
Families see the schedule you meant to publish.
The habits behind it
What made the first season work.
Rules you can read
Every rule lives in a plain file you can read and change, not hidden in code.
Ranked trade-offs
Hard rules never break. Soft rules carry a rank you can see in plain English and reorder.
Week first, then dates
A one-night change is a one-night edit. The season is never re-solved for a single date.
Two checks
The solver and a separate checker must agree before anything is published.
Verify what families see
The published schedule is checked against the plan, including changes made outside the tool.
See it with your own venues.
Stage 1 is ready today. Enter your venues and see your real court time on a heat map.