Tournament Organizer studio
Run a tournament end to end
The Tournament Organizer studio covers the entire life of an event: creating it, reviewing registrations, publishing groups, scheduling matches, releasing rooms, running results, and closing it out.
Every state transition described here is enforced by the backend, so a control that is hidden on screen is never the only thing standing between someone and a rule.
# Tournament Organizer overview
The overview reports the organizer totals for tournaments, registrations, and teams, with the managed events listed underneath so the busiest events are never more than one click away.
# Managed tournaments
Managed tournaments is the working list. Each event shows its status chip and only the actions that are available at that stage, so an event that has already started does not offer to be re-scheduled.
# Create tournament
Creation is progressive. The stage tabs move through basic information, format, rules, schedule, and publication, so a long form is never presented all at once and nothing is lost when you step back.
Capacity is restricted to the supported bracket sizes, and the scoring rules chosen here become the rules the results engine and the ladder both use.
A tournament stays a draft until it is published. Drafts are not listed in the explorer and cannot be entered.
# Edit tournament
Editing reopens the same stages for an existing event, with the current values already in place. Changes that would move a published schedule or rule set are recorded as audited actions rather than applied silently.
# Registration review
Registration review is the approval queue. Each entry arrives with its eligibility result, lineup snapshot, and payment state, and only an eligible entry can be approved.
Approving is capacity-safe and transactional. Rejecting or withdrawing an entry releases the slot it held.
# Managed groups
Managed groups is where the grouped stage is built and published. Rounds and groups are shown as chips with their team slots underneath, so balance can be checked before anything goes live.
Groups are balanced, invited teams are accounted for, and the same round advances the same number of qualifiers from every group.
A two-party group swap is agreed by both teams before it is applied, and the history of the swap is kept.
# Review qualification
Qualification review repairs a grouped round whose source results changed after advancement. It shows a current preview of what would change and requires a written reason before anything is applied.
A repair keeps group identifiers, unchanged entries, slots, publication, and the schedule. Entries that are still valid are never replaced, and protected downstream play is left untouched.
Repair requires Tournament Organizer ownership, a Tournament Director assignment, or administrator authority, and the preview version must still be current.
# Match schedule and rooms
Matches holds the schedule for every round. Scheduling can be generated automatically or set by hand, and each match carries its own room credentials and optional livestream link.
Credentials are released according to the configured opening rule, including the five-minute wait after the previous match completes where that rule applies.
Normal editing of a match locks once it has started; from that point changes go through the result and dispute flows instead.
# Results engine
The results engine is where match results are entered and finalised. Bulk entry covers a whole round at once, and an individual row can be corrected later with a required reason.
Final standings are published only once results are completed and approved, and a first-round bottom-four demotion is calculated from the finalised tie-break order.
Every change to a published score keeps an append-only revision, and the public results page shows a sanitised correction history.
# Organizer management
Staff are assigned per tournament. A Tournament Director, Results Manager, Moderator, or Support member sees only the events and the actions their role allows, which keeps least privilege practical to apply.
# Reserved slots
Reserved slots hold capacity for invited or reserved teams before registration opens to everyone. An assigned slot occupies capacity; a pending application does not.
Reserved and invited teams are counted when balanced groups are planned, so a published group is never planned against a field that cannot fill it.
# Global Toppers opportunities
Global Toppers opportunities are announced by an administrator and accepted or declined by eligible organizers. Only the first valid acceptance assigns the event, so two organizers can never both be given it.
Team entry to a Global Toppers event is always free, and an allocated qualification rank is immutable even if the team later drops in the ladder.
The event cannot start until every slot is allocated and the organizer platform-fee proof has been approved.
# Communication centre
The communication centre mirrors the player inbox for organizer activity: registration decisions, staff changes, qualification repairs, and payment outcomes all land in the same filtered list.
# Pages CMS
The Pages CMS lets an organizer publish informational pages for their own audience, with a page library holding everything already written and published.
# Media library
The media library holds uploaded assets alongside the built-in platform artwork. An upload is validated by its actual bytes, size, and decoded dimensions before it is stored under a random name.
Supported images are re-encoded to WebP on the way in, so an upload cannot smuggle a different format into the library.