> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcuemanager.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Player self-scoring

> Let players record frame winners from their own phones, with the front desk approving only what they disagree about.

Normally every frame is recorded by staff — a winner button on the table card, or an answer to the camera's "who won on table 3?" dialog. **Player self-scoring** hands the first tap to the players instead: they scan the [QR on their table](/player-app/player-app), tap who won the frame, and the front desk only gets involved when something is wrong.

Frames are money in CueManager — the loser of a frame pays for it — so a player's tap does not bill anything on its own. It creates a **frame result waiting to be confirmed**, and only something else agreeing with it turns that into a real, billed frame.

<Note>
  Self-scoring is **off** until you switch it on, and it never applies to snooker. See [Where it applies](#where-it-applies).
</Note>

## Turning it on

<Steps>
  <Step title="Open the branch">
    Management → **Branches**, then edit the branch.
  </Step>

  <Step title="Find Player self-scoring">
    Tick **Let players record their own frames**.
  </Step>

  <Step title="Set the confirmation window">
    How long the other side has to confirm before the frame counts automatically. The default is **90 seconds**; anything from 5 seconds to an hour is allowed.
  </Step>

  <Step title="Save the branch">
    Players at that branch see winner buttons on their phones from the next frame onwards.
  </Step>
</Steps>

A shorter window means less waiting and less chance a player walks off before confirming; a longer one gives the other side more room to object. Ninety seconds suits most clubs.

## Where it applies

A player only gets winner buttons when **all** of this is true:

| Condition                                          | Why                                                                                   |
| -------------------------------------------------- | ------------------------------------------------------------------------------------- |
| The branch has self-scoring switched on            | It is off by default                                                                  |
| The session has not been switched off individually | See [the per-game switch](#switching-it-off-for-one-game)                             |
| The session is still running                       | Finished games are closed to changes                                                  |
| The session is billed **per frame**                | Games on the clock have no frame results to record                                    |
| The game is **8-ball or 9-ball**, not snooker      | The snooker marker decides when a frame ends and records the result itself            |
| The player is in the game                          | They hold one of the player spots, having claimed it or been picked at the front desk |
| The player scanned that table's QR                 | Proof they are actually at the table                                                  |

When one of these is not met, the phone says why in plain words — "This club records frames at the front desk", "This game is billed by time, so frames are not recorded" — instead of just hiding the buttons.

## What happens when a player taps a winner

The player picks a side under the score. Their phone shows **Recorded: … won** with a countdown, and the other side's phone asks **Is that right?**

Nothing has been billed yet. That result now waits for one of four things:

<Steps>
  <Step title="The other side confirms">
    Only the **opposing** side can confirm — never the submitter, and in doubles never their own partner. A confirmation records the frame immediately.
  </Step>

  <Step title="The camera vouches for it">
    If a table camera has just seen a frame end on that table and nobody has answered its alert, the countdown is cut to at most **20 seconds**. The camera proves that *a frame ended*, never *who won*, so the other side still gets a chance to object — a short one.
  </Step>

  <Step title="The countdown runs out">
    With nobody objecting, the frame is recorded automatically once the branch's confirmation window has passed.
  </Step>

  <Step title="Staff decide it">
    The front desk can approve it, record it for the other side instead, or reject it outright. See [what the front desk sees](#what-the-front-desk-sees).
  </Step>
</Steps>

Either player can tap **No, that's wrong** — which stops the countdown and puts it in front of the front desk — and the player who submitted it can undo their own mis-tap the same way.

Once recorded, the frame is an ordinary frame: it charges the loser, at double the rate in doubles, exactly as if staff had tapped the button. Nothing about [billing](/concepts/how-billing-works), receipts, or checkout changes.

<Note>
  Only one frame result can be waiting at a time on a given table. If both players tap at once, the second one is told the frame is already waiting and can simply confirm it.
</Note>

## What the front desk sees

Staff do not have to watch for any of this — the exceptions come to them.

**On the active session panel.** A game with a result waiting shows a chip: who the player says won, and a countdown to when it will count. Two buttons sit next to it:

* **Approve** — record the frame now instead of waiting out the window.
* **… won** — record it for the *other* side instead, when the players got it round the wrong way.

**Anywhere in the app.** A disputed result opens a dialog on every till in the branch, the same way a camera alert does. It shows who claimed what, asks **Who actually won it?**, and offers **Reject** for a frame that never finished at all — rejecting records nothing.

If the same player has already had frames counted in this game with nobody confirming them, the dialog says so. That is the pattern worth looking at before the bill lands.

**Frames staff record themselves always win.** If the front desk records the frame from the table card while a player's result is still waiting, the player's result is dropped rather than billed a second time, and staff are told that the game has already moved on.

## Switching it off for one game

The active session panel has a **Player scoring on / off** toggle. Use it when one table needs the front desk to take over — an argument, a phone that keeps mis-tapping, a guest playing on a member's spot — without changing the setting for the whole club. Turning it off stops the next result; a result already waiting still resolves.

## The limits that keep it honest

Self-scoring is a customer-facing write path, so it carries deliberate bounds:

| Limit                                               | What it does                                                                                                                              |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **One waiting result per game**                     | A table cannot queue up frames                                                                                                            |
| **45 seconds between results from the same player** | Comfortably below the fastest real rack, so honest players never meet it — a phone tapping its way through a session meets it immediately |
| **Three contested claims per player per game**      | After three of a player's results end disputed or rejected, they are sent to the front desk for the rest of that game                     |
| **Warning after two unconfirmed frames**            | Frames that counted purely because the clock ran out are flagged for staff on the dispute dialog                                          |
| **Only the opposing side may confirm**              | A partner waving frames through would make the whole thing a formality                                                                    |

None of this stops staff from recording a frame the ordinary way at any moment.

## Fixing a frame that was already recorded

The confirmation window is the correction period, but it is not the last word. A frame that was recorded wrongly — by a player or by staff — can be struck off the bill with **Correct a frame** on a running session. See [Correcting a frame](/sessions/running-a-session#correcting-a-frame).

## Related pages

* [The player app](/player-app/player-app) — QR stickers, member sign-in, and claiming a spot
* [Running a session](/sessions/running-a-session) — the staff side of frame recording
* [How billing works](/concepts/how-billing-works) — loser-pays frame pricing
* [Club leaderboard](/player-app/leaderboard) — where the recorded frames end up