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

Fixtures placed on fields and dates, rerun when a field closes.

What it solves: Fixtures are placed on fields and dates under the league’s scheduling policy in one Kylon room, and the whole round is rerun when a field closes, referee availability changes or a blackout date moves. Agents propose and the league scheduler approves each run.

How it runs

  1. First walk Every fixture is placed on the earliest valid field and date, or marked unscheduled Who decides: The scheduler approves before Notion and the calendar change
  2. Draft check The coordinator’s draft is checked fixture by fixture, including scheduled fixtures missing from it Who decides: The scheduler sends corrections to the coordinator
  3. Field closure The full round is rerun with the closed field removed Who decides: The fields coordinator confirms dates and the scheduler approves
  4. Referee batch The full round is rerun with the new availability and the closure still in force Who decides: The referee assignor confirms and the scheduler approves
  5. Blackout swap The full round is rerun with the swapped dates and both earlier notices in force Who decides: The scheduler approves
  6. Team questions Each team that asked gets one reply with its fixture’s field and date from current records Who decides: The scheduler sends each reply
  7. Close-out Fixtures per field and the unscheduled list are read from current records Who decides: The scheduler posts the final round

Tools it connects

  • 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.
  • Notion: Holds every fixture with its field, date and status.
  • Gmail (optional): Is where team managers ask about fixtures, answered through drafts a person sends.
  • Slack (optional): Is where the referee assignor and fields coordinator post their notices.

Set-up prompt

Paste this into Kylon, or start it in one click below.

Set up our recreational league scheduling desk in this Room. Take it one step at a time and wait for my OK before you move on.

1. Connect Google Calendar, Google Drive and Notion first, since the first run needs them. Tell me which ones still need connecting. Gmail and Slack can wait until a step uses them.
2. Ask me who works this desk: the league scheduler, the referee assignor and the fields coordinator. Help me invite them to this Room.
3. Build a Fixtures App with Fixture, Field, Date and Status columns, one record per fixture. Pull the current fixtures from our Notion database.
4. Walk every fixture against the field table, round dates and referee availability in Google Drive and Slack. Propose a field, date and status for each, and show me any that land unscheduled.
5. Check the coordinator's draft in Google Drive fixture by fixture. Flag any scheduled fixture missing from it, and draft one reply per open team thread in Gmail from the current records only.
6. Hold every reply and every write to Notion and Google Calendar until the league scheduler approves each run and sends each reply personally.
7. Write into this Room's guideline: every notice triggers a full rerun with all earlier notices still in force, and the league scheduler approves before Notion, the calendar or any team thread changes.
8. After one clean round, offer to turn the full rerun walk into an Automation.

Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.

Start in Kylon · Full page on kylon.io