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.
Keep one source of truth per kind of decision
| Decision | Authoritative surface |
|---|---|
| Tournament structure and lifecycle | Manager Desktop |
| Participant-facing draw and schedule | Published Portal tournament page |
| Table device assignment | Manager Desktop Table devices |
| Table's current queue | Paired Manager Mobile Table mode |
| Certified result | Manager Desktop live/result workflow |
| Governance trail | Manager 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.