Step 1
Create the League and map the season stops
Leagues are the multi-stop branch of Team Competitions. Create the league once, then define the season through a list of stops that can each carry their own date, venue context, participating teams, and operational setup.
- Set the league name, season start, timezone, and overall venue context.
- Add stops in order and keep naming consistent with Stop 1, Stop 2, and so on.
- Remember that one stop can contain multiple matches per team in larger leagues.
- Plan the season before generating any matches so standings and progression stay easier to manage.
League schedule
Season start: Apr 4, 2026
Current stop: Stop 2
Format path: Round Robin → Knockout
Stop 1
Mar 19, 2026 • Round Robin
CourtX | Oakville
Stop 2
Apr 9, 2026 • Round Robin
CourtX | Burlington
Stop 3
May 2, 2026 • Knockout
TBD venue
League Settings
Controls standings scope, pool logic, and later-stage progression.
Shared across the league unless you override at match level later.
Copied into each generated league match.
Placeholder for future league rollout.
Step 2
Set league rules and the shared match template
League settings do two jobs: they define the overall competition model and they provide the template that each generated match starts from. Settings are split into independent edit sections so you can change one area without reopening the full configuration.
- Use league format for pools, qualifiers, and stop-level progression choices.
- Use roster rules for match roster size, gender logic, age logic, and player-usage limits.
- Use match format for game slots, scoring, tiebreakers, and court behavior.
- League monetization remains intentionally deferred while event-first payments lead the rollout.
Step 3
Add players, teams, and captains for the full season
League rosters live longer than event rosters, so the setup phase matters even more. Add the competition players first, then build teams and assign captains who will help run stop-by-stop operations.
- Captains are assigned from the league player pool.
- Open team rosters can absorb changes across the season when your rules allow it.
- League roster changes are controlled by the between-round window rather than an event-day lock.
- Quick Setup remains useful for building realistic test data.
Stop 2
Court 1 • next: Team 1 vs Team 4
Court 2 • next: Team 2 vs Team 3
Court 3 • open
Court 4 • open
Stop 1
Courts: 1, 2
Step 4
Run each stop with match generation and per-stop court ops
League operations happen stop by stop. Generate matches for the active stop, run those matches, then let standings and queue logic inform what comes next. Court management is global at league level, but each stop owns its own court names and counts.
- Use the Schedule tab for stop planning and stage generation.
- Use the Courts tab for live operational court review and updates.
- Current stop appears first in Courts; completed stops move to the bottom and can collapse.
- Queued and scheduled matches continue to sync as teams and courts become available.
Step 5
Track cumulative standings and seed later stages with confidence
Standings are one of the biggest reasons to use a league instead of isolated events. Ladders keeps both stop context and full-league context visible so the organizer can make progression decisions from verified data.
- Review overall league standings to monitor season-long performance.
- Review stop-specific outputs when each venue or stop needs its own local story.
- Use standings for deterministic knockout qualification and seeding.
- When round robin feeds knockout, standings become the bridge between phases.
| Team | MP | W% | PD |
|---|---|---|---|
| Pickle Blues | 8 | 75 | +41 |
| Midnight Mavericks | 8 | 63 | +18 |
| Oakville Aces | 8 | 50 | +4 |
Knockout preview
Seed 1: Pickle Blues
Seed 2: Midnight Mavericks
Seed 3: Oakville Aces
Seed 4: Lakeshore Spin
Season summary
Stops completed: 3
Final format: Round Robin → Knockout
Champion: Pickle Blues
Highlights
MVP: Anna Leigh Waters
MVT: Ben Johns + Anna Leigh Waters
Top pairing trend: 83% game win rate
AI insights
Spot streaks, strong stop-to-stop adjustments, standout pairings, and late-season momentum before publishing the final league story.
Step 6
Close the league with results, context, and insight
Once the season is complete, the Overview tab becomes the final control point. This is where league organizers confirm standings, review the champion context, and preserve the season as a finished record.
- Use final league standings as the primary results view.
- Keep stop summaries available when you need to explain how the season unfolded.
- Use AI insights to add narrative context to the data, not to replace the standings.
- Archive the league as a historical reference once the final stage is complete.
Good habits
A few habits that make leagues easier to govern
- Keep stop naming, stop ordering, and venue naming consistent.
- Use the Schedule surface for planning and the Courts surface for live operations.
- Review standings after every stop, not only at the end of the season.
- Let captains handle their side where possible so the organizer can focus on league-level flow.
- Use the Overview and Standings tabs together when preparing the next stage.
Related pages