Docs/Reference

Operational guidance

Best practices that scale from a club night to a major event

Simple habits that make the connected workflow reliable for every role.

Reference 8 min read Source verified

Keep one source of truth per kind of decision

Keep one source of truth per kind of decision
DecisionAuthoritative surface
Tournament structure and lifecycleManager Desktop
Participant-facing draw and schedulePublished Portal tournament page
Table device assignmentManager Desktop Table devices
Table's current queuePaired Manager Mobile Table mode
Certified resultManager Desktop live/result workflow
Governance trailManager audit and export history

Make changes in the smallest safe scope

  • Correct the specific entry, seed, match, table, or schedule block that is wrong.
  • Re-run validation after structural changes.
  • Republish participant-facing information when its meaning changed.
  • Record a reason for unusual draw, schedule, or result corrections.
  • Avoid parallel offline writers during a venue network outage.

Communicate in participant language

  • Say which tournament and event you are referring to.
  • State the local time and table, not only 'your next match'.
  • Explain whether a change is proposed, saved, or published.
  • Point people back to Portal instead of creating an unofficial schedule document.
  • Tell families what to do when a verification code, payment, or private-access check fails.

Rehearse the seams

Most tournament failures happen between surfaces, not inside a single form. Before a major event, rehearse a player registration, a check-in, a draw and schedule publish, a match result, a reconnect, a dispute correction, and the required export. Rehearse Table mode pairing only when the V2 Manager shell is enabled for that deployment.