Step 1
Create the Event and confirm the rule set
Start from the Teams hub and create an Event. In Ladders, Events are the single-day branch of Team Competitions. After creation, you land directly in settings so the structure can be confirmed before anyone is added.
- Choose the event date, venue, roster size, and join PIN.
- Define the competition format: round robin, knockout, or a combination.
- Define roster rules: size, gender rules, age rules, thresholds, and max games per player.
- Define the match template: default game count, scoring, tiebreaker behavior, and court management.
- Expand the monetization plan when the event is paid and choose how seats are covered.
Competition format
Choose whether the event runs as round robin only, knockout only, or a mixed format such as round robin into knockout.
Roster rules
Control roster size, match roster size, gender rule, age rule, age threshold, and max games per player in a match.
Match format
Control game count, per-game disciplines, scoring system, tiebreaker behavior, and whether court management is active.
Competition Settings
Controls the overall event structure.
Validates who can be selected and how often.
Defines the copied template used for generated matches.
Optional, collapsed by default during creation.
Settings behavior
Each section is edited independently from the Settings tab or app bar shortcut.
Once the first match is completed, these edit cards are replaced by a locked summary view.
Step 2
Add players and fix missing eligibility early
In the Players tab, search existing users and add them to the competition. This happens before team assignment. Each competition keeps its own player snapshot, including the age and gender fields used later for roster and lineup validation.
- Use the add-player action to search the user base and add several players in one session.
- Review the missing eligibility badge immediately after import.
- Use Edit eligibility to set age and gender if the profile is incomplete.
- Review join requests in the same screen when player access is enabled later.
Step 3
Build teams, captains, and rosters
Once the competition player pool is ready, create teams manually or use Quick Setup. Ladders respects roster rules during team assembly, and the first seeded player becomes captain by default.
- Captains are chosen from already-added competition players.
- Managers can edit team rosters before play begins.
- Players already committed to another team do not appear in the selection list.
- Roster chips show each player’s gender color and age so validation is visible at a glance.
Ladders schedules the first available matches, then promotes queued matches automatically as teams and courts free up.
Step 4
Generate matches and let courts do the heavy lifting
From the Matches tab, generate the event schedule. When court management is enabled, you first define the event courts, then choose a start time, courts per match, and average match duration during generation.
- Only the first set of playable matches starts as Scheduled.
- Any match blocked by team availability stays Queued.
- Court assignments happen when a match becomes scheduled, preventing double allocation.
- Managers can still create a manual match if an exception is needed.
Step 5
Run the match, lock lineups, then record verified scores
Open any match card to move from roster selection into game-by-game operations. Match rosters are submitted per team first, then each game lineup is set according to its gender and age rules. Once a score is entered, that lineup locks.
- Matches move through Queued → Scheduled → In Progress → Completed.
- Lineups follow the round-flip rule so one side does not always reveal first.
- Duplicate player use in the same round is blocked.
- Score entry enforces the configured format: no ties in a game, target score, and win-by margin.
- If match ties are not allowed, the organizer can add a tiebreaker or settle based on total points where appropriate.
Details
In ProgressRound 1
Date: Mar 19, 2026
Scoring: Rally to 15, win by 2
Courts: 1, 2
Games scored: 3/4
Round 1
Anna Leigh Waters • Ben Johns
Catherine Parenteau • Tyson McGuffin
Anna Bright • Lea Jansen
Jessie Irvine • Rachel Rohrabacher
Round 2
Ben Johns • JW Johnson
Tyson McGuffin • Collin Johns
MVP
Anna Leigh Waters
MVT
Anna Leigh Waters + Ben Johns
Team standings
| Team | MP | W% | PD |
|---|---|---|---|
| Pickle Blues | 4 | 75 | +24 |
| Midnight Mavericks | 4 | 50 | +3 |
| Oakville Aces | 4 | 50 | -1 |
AI insights
Spot streaks, standout pairings, score patterns, and momentum shifts once enough match data is available.
Step 6
Review standings, then close the event cleanly
After the generated matches are finished, the Overview tab becomes the closeout screen. This is where organizers review standings, confirm summary data, and use End Competition when the event is ready to be finalized.
- Team standings rank by win percentage, not raw wins.
- Player standings highlight the event MVP.
- Pairing standings highlight the most valuable team combination.
- Once the event is ended, editing is locked and the Results view becomes the natural summary destination.
Good habits
A few organizer habits that make events smoother
- Verify eligibility before team creation if any age or gender rules exist.
- Use court management for any event where multiple courts run in parallel.
- Generate matches only after teams are final, because format edits lock once live play begins.
- Encourage captains to review match rosters before the first start call.
- Use the built-in checklist from the Overview help button for live event pacing.
Related pages