Organizer control room
iMatch Manager Desktop
The macOS-first SwiftUI application for setup, draw and schedule work, live-floor control, results, audit, and export.
Enter the correct operating context
Manager restores a signed-in session, loads the operator's organizations, and requires an organization selection before the operator workspace appears. The active organization scopes tournament data and actions. An operator without an account can create one and set up an organization from the app itself.
A Next up ribbon sits under the window header on every view. It names the next lifecycle step for this tournament and what is blocking it, so the running order does not have to be carried in someone's head.
The primary app target is macOS 14 or later. The same SwiftUI package also targets iPadOS 17 or later, with Table mode as the focused mobile surface described in the next guide. Every current build opens the same operator shell: a nine-view sidebar of Live, Entries, Events, Schedule, Brackets, Standings, Export, Activity, and Settings, reachable with ⌘1 through ⌘9, with ⌘T to switch tournament and ⌘K for the command palette. The legacy Command Center workflow was retired at runtime on 2026-07-29; no setting returns to it.
Current organizer capabilities
| Phase | Tools visible in the implementation |
|---|---|
| Build | Create a tournament fresh, as a new edition of an existing one, or restored from a backup file; the two-step Event Wizard; age-group presets and a custom format composer; reusable event templates |
| Register | Open and close registration, the public self-registration gate, a venue-wall registration QR, entry and withdrawal handling, bulk add, Check-in desk |
| Seed & draw | Lifecycle-gated seeding, the draw desk, per-stage boards, draw audit, and stage advance |
| Schedule | Venue table inventory per venue, Auto-schedule for a session block, move and swap on the schedule grid, validated publish transition |
| Run | The Live tab in grid, venue, or team-tie mode; call, submit result with a Played/Walkover/Retired/DQ outcome, certify, confirm codes, and digital-scoring provisioning |
| Close | Final standings and awards, federation export, export audit, full tournament backup, archive |
| Resilience | Connectivity monitoring and a narrow durable queue for results, check-in, seeding publish, and draw operations; queued writes replay automatically when the connection returns |
Use modes in lifecycle order
- 01
Setup
Keep structural work in Draft and use templates to reduce rule drift.
- 02
Entries
Close the intake window and reconcile check-in before draw generation.
- 03
Draw
Seed, generate, inspect, adjust, and publish in that order.
- 04
Schedule
Run Auto-schedule for each session block, adjust placements with move and swap, then complete the validated publish.
- 05
Live
Make day-of actions from the Live tab (⌘1) so match state, score, and progression remain connected.
- 06
Review
Read the Activity feed, the per-event audit log, and the Export tab's audit history, then archive from Settings → Lifecycle.
Common mistakes
- Working in the wrong organization after switching between clubs.
- Generating a draw before withdrawals and no-shows are settled.
- Publishing a schedule before inspecting table and player conflicts.
- Typing a fictional numeric score instead of setting the Walkover, Retired, or DQ outcome.
- Repeating a write during a network interruption instead of checking the offline queue.