Intermediate tutorial
Operate the tournament floor
A practical runbook for check-in, live matches, table devices, results, and the exceptions that consume desk time.
Open the desk before the doors
- Confirm the active organization and tournament before touching live data.
- Check connectivity and inspect any queued offline writes or conflicts.
- Open Check-in Desk and reconcile withdrawals or no-shows.
- Confirm table labels match the schedule and physical venue signs.
- Keep the public Portal page open on a separate device as a participant sees it.
Use the same loop for every match
- 01
Assign
Confirm the table and the two entries on the live match card.
- 02
Call
Call the match only when the floor can receive it. This keeps Portal-facing expectations and physical operations aligned.
- 03
Start
Move the match into progress when the players are present and the table is ready.
- 04
Capture
Submit the result with the correct winner and game scores. Use walkover or forfeit controls when those outcomes apply instead of inventing a numeric score.
- 05
Certify
Certify the result after review so downstream progression is based on a controlled outcome.
Deploy a Table mode iPad when the V2 shell is enabled
- 01
Confirm availability
Verify that this Manager deployment enables the V2 shell. Its Table devices sheet is required for the operator side of pairing.
- 02
Mint a code
In the feature-gated Manager live area, open Table devices and create the table pairing code or QR.
- 03
Enter Table mode
At the Manager login screen on iPad, choose Table mode, then scan the QR or type the code.
- 04
Confirm the lock
Verify the large Locked to table label and the assigned queue. Ask the operator to enable Guided Access manually if kiosk behavior is required.
- 05
Watch connection state
Connected is the healthy state. Reconnecting means the heartbeat has gone stale; check network before assuming the queue is current.
- 06
Escalate from the table
Use Call operator to flag the control desk. Continue score capture through the supported desktop/scorer process, because Table mode scoring is not yet enabled.
Protect the bracket when something goes wrong
| Situation | Use | Avoid |
|---|---|---|
| Player never arrives | No-show, withdrawal, walkover, or forfeit flow as policy requires | Entering a fake score |
| Wrong score was submitted | Disputed Scores and the result correction/certification path | Advancing later rounds before correction |
| Table device disconnects | Check Reconnecting state and call operator | Assuming its queue is live |
| A table becomes unavailable | Use the released table-assignment controls and contain the change | Promising a rich reschedule tool that is not enabled in the default release |
| Network drops | Monitor queued offline writes and replay conflicts | Repeating the same write on multiple machines |