State reference
Tournament lifecycle reference
The implemented twelve-state tournament path and the operational meaning of each transition.
Canonical state sequence
| State | What it means | Typical next action |
|---|---|---|
| DRAFT | Organizer-only structure is still changing | Publish |
| PUBLISHED | Public context may exist; entries are not yet accepted | Open registration |
| REGISTRATION_OPEN | Entries can be collected | Close registration |
| REGISTRATION_CLOSED | Entry field is stable for preparation | Start check-in or seeding |
| CHECK_IN | Arrival status is being reconciled | Start seeding |
| SEEDING | Seeds and placements are being prepared | Publish draw |
| DRAW_PUBLISHED | Competitive placement is visible | Publish schedule |
| SCHEDULED | Sessions and tables are ready | Start |
| IN_PROGRESS | Live match operations are active | Complete |
| COMPLETED | Competition play is finished | Archive |
| ARCHIVED | Event is retained as a closed record | None |
| CANCELLED | Tournament was cancelled | None |
Transition rules that prevent surprises
- Publish before opening registration.
- Close registration before seeding from a final field.
- Use Check-in when the event's check-in mode requires it; auto paths can proceed from registration close to seeding.
- Publish the draw before the schedule.
- Start only after a published schedule is operationally ready.
- Complete only after live results and progression are reconciled.
- Cancel and archive are terminal decisions; treat them as governance actions, not navigation shortcuts.
Lifecycle is not the same as access
A tournament's state tells you where it is operationally. Its access tier determines who can see it. Portal supports public, unlisted, and private behavior, with private reads protected by signed-in membership-aware checks.