Docs/Organizers

Advanced tutorial

Control complex tournaments without losing the audit trail

Use advanced Manager tools deliberately: staged formats, schedule changes, offline replay, exports, and auditable exceptions.

Advanced 13 min read Source verified

Model the format before you publish it

The released Event Wizard supports singles, doubles, and mixed doubles; age-group presets or custom groups; reusable formats; a stage preview; scale guidance; and a custom Format Composer. Use the preview to make progression understandable before you publish. Rich V2 stage workspaces may be present behind a feature flag, so this guide does not assume they are part of the default release.

  • Name every stage so participants can recognize it.
  • Set the format and advancement intent before registration closes.
  • Publish a draw only after checking its field and seeding inputs.
  • Use the activity and audit surfaces for deliberate, reviewable corrections.

Change table assignments with containment

  1. 01

    Identify the smallest affected set

    A table delay rarely requires rebuilding the entire day. Start with the match, table, or session that is actually blocked.

  2. 02

    Use the released assignment path

    Assign tables from the Live console and keep the change to the affected match or table. The richer V2 delay and auto-schedule controls are disabled in the default release.

  3. 03

    Validate again

    Re-run the supported schedule publication checks and update participant-facing information when required.

  4. 04

    Communicate the delta

    Tell players, coaches, and parents what changed, what did not, and where the authoritative schedule now lives.

Treat offline writes as a queue, not a second truth

Manager includes connectivity monitoring, a durable offline write queue, replay handling, and conflict or stale-state UI. Queue coverage is deliberately narrow: match result, team-rubber result, team walkover, entry check-in, seeding publish, and draw perform/publish/swap actions. Tournament creation, imports, scheduling, and arbitrary edits are not promised offline.

Create a defensible closeout package

  • Use federation export or OTRF export when a governing body expects a specific shape.
  • Use the OTRF v0.3 JSON export when an interoperable tournament record is required.
  • Retain draw audit, activity feed, unified audit log, and export audit history for contested decisions.
  • Archive the tournament only after the final result and export review.