Control complex tournaments without losing the audit trail

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.

• ✓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

   Move one match, or refill a block

   On the Schedule tab, tap a placed match to arm it, then tap an empty slot to move it or another match to swap them — the grid checks the move against the players first, and a blocked slot names the clash: a shared entry already playing in an overlapping window, or one landing inside the fifteen-minute rest gap. To refill a whole session block, use Auto-schedule — it runs once the tournament has a session block to fill, and otherwise tells you why it cannot. The cascading +15 min delay control remains disabled.

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 and a durable offline write queue. Queued writes replay automatically when connectivity returns, and a queued submit is confirmed to the operator with a queued-will-submit-when-online notice. The queue depth and connection state are visible in the macOS menu-bar tray. There is no conflict-resolution sheet and no queue-inspection list in the current shell. Writes that succeed replay and clear on their own, but a write the server rejects as a conflict is not resolved for you: it stays in the queue and holds the tray’s queued count above zero until the underlying disagreement is settled at the desk. A queued count that will not fall is the signal to look for it. 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

• Run the federation export from the Export tab: pick the event, then the governing body and the file shape you need. The export is blocked until every result in scope is certified, which is deliberate.
• Take a full tournament backup before archiving. It captures the whole live state — entries, draws, schedule, and results — as one file.
• OTRF v0.3 is still a real output shape, but there is no button for it in the current Manager build. Ask for it through the API if a governing body requires that specific record.
• Retain the seeding, draw, and export audit trails for contested decisions — those three are what the audit surfaces cover.
• Archive the tournament only after the final result and export review.