iPad table companion
iMatch Manager Mobile: Table mode
Pair an iPad to one tournament table, work its queue, score the match point by point, and call the control desk.
Current scope
Manager Mobile in this guide is the Table mode built into the shared Manager SwiftUI app for iPadOS. It is a focused kiosk-style companion, not the full desktop organizer workspace and not the participant iMatch app.
The iPad side covers device pairing, persistent enrollment, a table-locked queue, heartbeat-based connection state, a Call operator action, and point-by-point scoring for singles, doubles, and mixed events. The operator-side Table devices sheet is part of the default Manager shell — there is no release flag to confirm before planning Table mode.
Team ties are the exception: a team match cannot be scored on the pad. Its Start match button stays disabled and names the reason, because a tie is scored as a series of sub-matches rather than as one scoreline.
Pair a table device
- 01Manager Desktop
Open Table devices
An organizer opens the Live tab in Manager Desktop and uses Table devices to mint a code or QR for a specific tournament table.
- 02Manager Desktop
Read the code's limits
A pairing code is nine characters shown as XXX-XXX-XXX, is valid for fifteen minutes, and can be claimed once. Mint a fresh code rather than reusing one.
- 03Manager Mobile
Open Table mode
On the iPad login screen, choose Table mode. This bypasses the operator sign-in flow for the table device.
- 04Manager Mobile
Scan or type
Scan the QR with the iPad camera or type the pairing code, then choose Pair.
- 05Manager Mobile
Verify the table
The paired screen names the table it is locked to and shows only that table's assigned queue. The label is shortened from the table's own name — a table named Table 3 reads T3.
- 06Manager Mobile
Enable kiosk protection
If desired, the operator manually enables iPad Guided Access. The app cannot turn Guided Access on by itself.
Operate the queue
| Signal | Meaning | Action |
|---|---|---|
| Connected | Heartbeat is current | Use the displayed queue |
| Connecting… | Initial connection is being established | Wait briefly before escalating |
| Reconnecting… | Heartbeat is stale or the app resumed | Check venue network and confirm at the desk |
| Now-highlighted row | The derived current match for this table | Confirm participants and physical table |
| Start match | The now-row is a singles, doubles, or mixed match | Begin scoring when both players are at the table |
| Start match, disabled | The now-row is a team tie, or the format has not loaded yet | Score a team tie at the desk, not on the pad |
| Call operator | The table needs desk intervention | Use it instead of leaving the table unattended |
Score the match
- 01Manager Mobile
Confirm the serve
Set who serves first. For doubles and mixed, the pad tracks the four-player serve and receive rotation for you.
- 02Manager Mobile
Score point by point
Tap to award each point. The pad shows the serve indicator and badges the moments that matter — deuce, game point, and match point.
- 03Manager Mobile
Correct a mistake
Undo steps the score back one point. Use it immediately rather than reconstructing the score later.
- 04Manager Mobile
Record what happens away from the rally
Timeouts, lets, and yellow or yellow-red cards are recorded from the pad alongside the score.
- 05Manager Mobile
Confirm and submit
At the end of the match the pad shows the completed result for review. Confirm & submit sends it once; the desk then certifies it.
Outcome One authoritative result at the desk, awaiting certification
Recover safely
- A valid device enrollment is stored securely and restored on launch.
- A match interrupted mid-score is restored at the exact score when the pad comes back.
- A result that could not be submitted because the network was down is kept on the device and sent when the connection returns.
- A revoked or unauthorized pad returns to the pairing screen instead of revealing the operator workspace.
- Use Not this iPad? Exit Table mode only when the device should leave its table-device role.
- If a code fails, ask the operator to verify or mint a new code; the app intentionally does not disclose whether a code was expired, already claimed, revoked, or malformed.