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. Set the outcome chip — Played, Walkover, Retired, or DQ — when the match did not finish normally, 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
- 01
Mint a code
In the Live tab, open Table devices and create the table pairing code or QR. A code covers one table, lasts fifteen minutes, and can be claimed once.
- 02
Enter Table mode
At the Manager login screen on iPad, choose Table mode, then scan the QR or type the code.
- 03
Confirm the lock
Verify the table name on the paired screen and the assigned queue. Ask the operator to enable Guided Access manually if kiosk behavior is required.
- 04
Watch connection state
Connected is the healthy state. Reconnecting means the heartbeat has gone stale; check network before assuming the queue is current.
- 05
Brief the table official on scoring
Singles, doubles, and mixed matches are scored on the pad and submitted once at the end. A team tie is not scoreable on the pad — route it to the desk.
- 06
Escalate from the table
Use Call operator to flag the control desk. The desk sees a Calling badge and an amber flag on the live grid until it dismisses the raise.
Protect the bracket when something goes wrong
| Situation | Use | Avoid |
|---|---|---|
| Player never arrives | The withdrawal or no-show path, then a Walkover outcome on the result, as policy requires | Entering a fake score |
| Wrong score was submitted | At certification, record the result as not approved — the match stays uncertified and will not advance — then re-submit the corrected result | Advancing later rounds before correction |
| Table device disconnects | Check Reconnecting state and call operator | Assuming its queue is live |
| A table becomes unavailable | Move or swap the affected matches on the Schedule tab and contain the change | Promising a cascading delay tool — the +15 min control is still disabled |
| Network drops | Monitor queued offline writes and replay conflicts | Repeating the same write on multiple machines |
Know what the floor is publishing to the room
Every result you certify is read back on the public tournament page in more detail than a scoreboard: an event card there opens into its draw as a bracket tree, its round-robin brackets as group cards, and each match's score foldable down to the individual games. Keep one device on that page, as a participant sees it, and desk questions arrive already half-answered.
- Check a corrected result on the public page before telling a player it is fixed — the per-game numbers are visible there too.
- Set the real outcome chip — Walkover, Retired, or DQ. Each renders as its own labelled badge on the public result, so an invented numeric score is visible as one.
- Expect questions about the group card's PTS column. It carries the tournament's own published match points when the source publishes them for every row in the group, and otherwise the page's own arithmetic at 2/1/0. The card's footer says which of the two you are reading.
- On a tournament past roughly a thousand matches, spectators may see an honest 'results may be incomplete' note. Answer with the page, not a side list.