Create sports and divisions
Structure your event so players can find the right bracket in two clicks.
Create sports and divisions
Sports and divisions are the skeleton of your event. Players pick a sport, then pick a division, then pay. If this structure is clean, signup is painless. If it isn't, you'll spend the next month answering emails.
Sports
A sport is the activity (Ultimate, Dodgeball, 5k Fun Run). Under Events -> [your event] -> Sports, click Add sport and set:
- Name — what players will see
- Competition date — which day this sport runs (for multi-day events)
- Roster limit and minimum — used for team-required sports
- Team required? — on for team sports, off for individual events like 5ks
- Hat tournament? — on if you'll auto-assign teams from individual signups
- SOTG enabled? — on for Ultimate; off for most other sports
- Custom questions — sport-specific questions like "experience level" or "preferred position"
Divisions
A division is the bracket inside a sport (Try-Hard, Fun, U15, Grandmaster). Click Add division under the sport and set:
- Name — again, how players talk about it
- Age min / max — optional. Computed against the registrant's DOB on the sport's competition date. Age max blocks registration; age min warns the player and requires confirmation.
- Capacity — optional soft cap. When a division hits capacity, new signups are pushed to the waitlist.
A sensible order
Drag divisions to reorder. Players read top-to-bottom, so put the most popular divisions first. For Ultimate events, many organizers lead with Fun and Try-Hard at the top and age-restricted divisions below.
Pricing
Pricing tiers live one level up (on the event). You can target a tier at a specific sport or division by setting its scope — that's how you run "Early Bird Ultimate only" while keeping 5k at one flat price all year.
Editing after opening
You can rename sports and divisions, change age brackets, and reorder at any time — even after registration opens. You can't delete a division that already has registrants, because that would orphan their payments. Close it instead: set the capacity to its current count and it disappears from the public signup flow.
Was this helpful?
