Docs/Organizers

Intermediate tutorial

Operate the tournament floor

A practical runbook for check-in, live matches, table devices, results, and the exceptions that consume desk time.

Intermediate 11 min read Source verified

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

  1. 01

    Assign

    Confirm the table and the two entries on the live match card.

  2. 02

    Call

    Call the match only when the floor can receive it. This keeps Portal-facing expectations and physical operations aligned.

  3. 03

    Start

    Move the match into progress when the players are present and the table is ready.

  4. 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.

  5. 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

  1. 01

    Confirm availability

    Verify that this Manager deployment enables the V2 shell. Its Table devices sheet is required for the operator side of pairing.

  2. 02

    Mint a code

    In the feature-gated Manager live area, open Table devices and create the table pairing code or QR.

  3. 03

    Enter Table mode

    At the Manager login screen on iPad, choose Table mode, then scan the QR or type the code.

  4. 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.

  5. 05

    Watch connection state

    Connected is the healthy state. Reconnecting means the heartbeat has gone stale; check network before assuming the queue is current.

  6. 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

Protect the bracket when something goes wrong
SituationUseAvoid
Player never arrivesNo-show, withdrawal, walkover, or forfeit flow as policy requiresEntering a fake score
Wrong score was submittedDisputed Scores and the result correction/certification pathAdvancing later rounds before correction
Table device disconnectsCheck Reconnecting state and call operatorAssuming its queue is live
A table becomes unavailableUse the released table-assignment controls and contain the changePromising a rich reschedule tool that is not enabled in the default release
Network dropsMonitor queued offline writes and replay conflictsRepeating the same write on multiple machines