The conflict comments you already collect should block the kickoff
Long conflict lists, shared coaches, fields that close at dusk. Blackouts from the import stay hard; rematches cap at two unless the grid is stuck.
- No setup fee
- No long-term contract
- Pay only when you export
What usually goes wrong
The soccer weekends we hear about break in the same places. None of them are fixed by retyping the grid.
- Conflict comments in the registration file never make it onto the grid
- Two teams with the same coach kick off at the same time on different fields
- A third rematch lands in three consecutive weeks because the grid was full
What to run instead
Same auto-schedule underneath. These are the first moves for this kind of weekend.
- 1
Parse the conflict comments you already collect
Blackout dates, Sunday-afternoon bans, and play windows in the registration comments — “cannot play Sunday afternoons,” “1pm to 6pm,” “11/14-15 no games” — become hard constraints, not a sidebar someone has to remember.
- 2
Coach groups and rematch caps
Linked teams share a coach; conflicts are honored first, and a coach lock keeps that hard. Pairs preferably meet at most twice; a third rematch is a last resort and never three weeks in a row. Hail Mary may allow a third meeting among leftovers — never a fourth.
- 3
Public schedule for families
One public schedule link for the season. Scores and standings update when you enter them — no new attachment every Sunday night. League weeks use the same on-the-hour engine; a dedicated outdoor-soccer tournament format is not a separate engine yet.
Other playbooks
Run more than one sport? The grid is the same.
Auto-schedule this playbook on the courts you already booked
Import last season's file, generate against your courts or fields, and see what is left before you send a single link. You only pay when you export.