Recreational League Scheduling: A Fixture List That Stays Right Through Every Rerun

A fall round where one closed field moves five games

A community league schedules its season in rounds. Each fixture needs a field that is open on the date, a referee crew that is free, and a date that is not on either team's blackout list. The policy sets the order: fixtures are walked from the first id to the last, each takes the earliest field and date that satisfies every rule, and anything that cannot be placed is marked unscheduled.

The fixtures live in a Notion database, the league calendar that families subscribe to is in Google Calendar, the policy, field table and round dates are in Google Drive, team managers write in by email, and the referee assignor and fields coordinator post in Slack. When a field closes after a wet week, a quick fix moves the fixtures on that field and leaves the knock-on clashes for someone to find on Saturday morning.

Who works in the room

Scheduling for the league happens in one Kylon room, mostly in the evenings when the volunteers are free. Anything about where and when a fixture plays goes to Myco, the room's default agent. Ada owns the draft check and the replies to teams, and reads from the same Notion records Myco writes, so a reply never quotes a figure the records do not hold. After each approved rerun, Myco mentions Ada with the fixtures that changed, and Ada checks them against any open team threads.

The round, rerun by rerun

Each rerun walks the whole round again under the policy's rerun clause, with every earlier notice still in force. Nothing reaches Notion, the calendar or a team until the league scheduler approves.

Why every notice reruns the whole round

A closed field does not only move its own fixtures. Each moved fixture takes a slot a later fixture would have used, and that fixture moves in turn. Rerunning the full walk in id order, with every notice still in force, is how the result matches what the policy would have produced from the start. Myco reports each rerun as the list of fixtures whose field, date or status changed, and nothing else.

The calendar follows the same discipline. When a fixture moves, its old event is deleted and a new one created once the scheduler approves the run, so families never see two times for one game. A fixture that becomes unscheduled loses its event and gets nothing in its place until a later run finds it a slot.

What the checks catch

• A rerun that drops an earlier notice and reopens a field that is still closed
• A clash that appears two fixtures later, after a moved fixture takes another one's slot
• A calendar showing a fixture twice, or still showing one that is now unscheduled
• A scheduled fixture missing from the coordinator's draft entirely
• A second reply on a team thread that already has its answer

What stays with people

• Approving every run before Notion and the calendar change
• Sending replies to team managers, which Ada drafts
• Deciding with the fields coordinator whether a closure is for a weekend or the rest of the round
• Posting the final round to the league

Integrations in this workflow

Kylon is not league management software and it does not replace the registration tool a league may use. The volunteers keep their records, calendar and inboxes, and the room holds the coordination that used to live in long email chains.

• Gmail
• Google Calendar
• Google Drive
• Notion
• Slack

• Notion holds every fixture with its field, date and status
• Google Calendar is the league calendar families subscribe to, changed only after an approved run
• Google Drive keeps the scheduling policy, the field table, the round dates and the coordinator's draft
• Gmail is where team managers ask about fixtures, answered through drafts a person sends
• Slack is where the referee assignor and fields coordinator post their notices

Where to start

Start with one round. Connect the Notion fixtures database and the league calendar, and write one rule into the room guidelines: every notice triggers a full rerun with all earlier notices still in force, and the league scheduler approves the result before families see it.

“A closure that moves one game moves the next one too, and the rerun finds it before Saturday.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.