Event Day Contingency

Tournaments expose a contingency state machine alongside the normal play state. A tournament director can transition into paused, partially-cancelled or fully-cancelled with a documented reason code (weather, venue, force majeure), and every transition snapshots the current state — completed rounds, played matches, partial scores — into an immutable resume point. The state is persisted server-side so a hardware failure on the scoring tablet does not destroy progress; restarting the next morning reloads the snapshot and the tournament continues from the exact match it stopped at.

No-show handling runs as a draw-recompute service. When the registration cutoff passes, the director marks no-shows; the draw engine re-balances pools, walkovers are awarded with the right ranking weight (or with no weight, configurable per competition level), and the affected players get a generated notification explaining the bracket change. Court unavailability (a flooded terrain, a damaged piste) flows into the same scheduler — the court is taken out of the available pool, in-flight matches reassign to free terrains and the schedule recalculates with minimum disruption to start times.

Partial-results handling preserves what was played. If two of three planned rounds finish before cancellation, the system can publish those rounds as official results, award partial ranking points pro-rated by the configured policy, and trigger refund processing for the cancelled portion. Refunds and credits route through the finance subsystem with a reason code (event-cancellation), respecting the federation's refund policy — full refund, registration-fee retention, store credit. Emergency communication uses a one-button broadcast that fans out by email, SMS and push to every registered participant in the participant roster, with localised templates per language and an audit-logged delivery receipt for compliance and post-mortem review.