Score confirmation & status badges

A submitted score, whether you typed it in or a player sent it from their phone, moves through a few states before it locks. Those states let everyone see what's recorded and what's still waiting on the other team.

How a score gets confirmed

A court confirms when both teams agree on the score. One side submits from their score link; the other opens their link and submits the same result. Matching entries confirm the court automatically, with no organizer click. Mismatched entries flag a dispute instead. Once confirmed, the court's inputs lock so nothing can be nudged by accident. A Box League works by the sheet rather than the court: one player reports the box's whole sheet and any other box-mate confirms it; the reporter can't.

What the status badges mean

On the player's screen and on your live monitor, each court shows where it stands:

State	What it means
Waiting	No score in yet, or one team has submitted and the court is still waiting on the other team to confirm.
Confirmed	Both teams agree. The score is locked and counts.
Disputed	The two teams submitted different scores. Someone needs to correct it.

A court sits in the waiting state until the other team confirms. The player who submitted sees a note that their score was sent and can still change it; your monitor shows who submitted. Once both teams agree, that player gets a "Score Confirmed" message and the inputs go disabled.

Monitoring submissions live

When you run a session with player phones or headless auto-mixing, you can watch results arrive in real time. The score panel shows each court with its current status (who has submitted, who has confirmed, what's still waiting, and which courts are disputed) and refreshes on its own as scores come in.

When the server is running the rounds, that panel is a read-only live monitor. It shows you exactly what's happening but won't publish or change a round on its own, so it can never clobber what the server is doing. To make a manual change, you take control of the session first. See Headless mode for how that hand-off works.

When a court is entered from two places

The same court often gets reported twice: both teammates submit, a player resubmits a correction, or you type a score while a player is entering the same one. What happens:

• The latest submission wins. A newer entry for the same court replaces the older one, so a correction always supersedes the mistake.
• Matching scores confirm. Conflicting ones get flagged as a dispute. The court is marked disputed rather than PickleFriend guessing which result is right.
• The organizer resolves disputes. A disputed court is your cue to check with the players and enter the agreed score, which confirms it.

You may notice more than one row in a court's history after a correction. That's the record of what was entered; only the most recent, confirmed score feeds your ratings and standings.

When a player's tab is out of date

A player's score link stays open until they navigate away. If the organizer moves to the next round while a player's tab is still showing the previous round, that tab is still on the old round.

Two things can trigger this:

• The tab lost track of the round. If the tab doesn't know which round is current (for example, the page loaded before the mix was published), tapping Submit shows: "Score session has refreshed — pulling the latest round..." The page fetches the current round automatically and the player can then submit normally.
• The tab's round is no longer current. If the tab is on a round that no longer belongs to the active session (for example, the tab was left open across multiple rounds), the server rejects the submission with "Score session has advanced — please refresh and try again." The player refreshes, the page loads the current round, and they submit from there.

Either way, no score lands on the wrong round. The player refreshes and resubmits.

Next

• Player score link for how players get to their court and submit.
• Editing games to fix a score after a court is confirmed.