How Session Finalization Avoids Partial Rating Changes
Imagine that four players finish a session and their ratings change, but the history page shows no explanation. The organiser presses Finalize again. Now the ratings move twice.
That is the dangerous failure mode in any results system: not a loud failure, but a half-finished publication that looks safe to repeat.
ServeLeague treats finalization as one trusted publication step. A session should not say Results Posted until its rating changes and rating history agree. Two administrators cannot complete the same session at once, and a failed attempt leaves the session available for a safe retry.
Some secondary work, such as preparing later notifications, can still produce a warning. The important promise is specific: the core rating record is not presented as final while its essential pieces disagree.
Only a locked session can enter finalization
Finalization starts from Under Review, the user-facing label for the Locked state. Draft and Live sessions are rejected. Already-finalized sessions are rejected too.
That boundary stops ordinary player score submission before calculations begin. It gives the administrator a stable set of recorded matches to inspect through the finalization preview, including separate projected Singles, Doubles, and Merit changes.
Some competition formats add stronger completeness checks. A graded session cannot finalize with ungenerated matchups or missing scheduled results. Super N rounds must have a valid bracket and complete required matches. Team leagues can expose incomplete-matchup information and require the administrator to acknowledge proceeding with partial recorded results.
The principle is consistent: find known gaps while the session is still open to review, not after ratings have been published.
The next risk is simultaneous action by two administrators.
Two browser tabs can submit the same action. A slow mobile connection can encourage a second tap. Two administrators can act at nearly the same moment.
ServeLeague allows only one finalization attempt to hold the session at a time. A second attempt is stopped or discovers that the first has already completed.
This prevents a double tap, a slow connection or two open browser tabs from applying the same session twice. If the important work fails, the session remains Under Review and the administrator can retry rather than being left with a misleading published state.
The lifecycle context is explained in Inside the Session State Machine.
The new rating keeps its explanation
Players should never see a new current rating without the match-by-match history that explains how it moved. The platform saves those two views of the same event together.
That protects three common questions:
- “Why did my number change?”
- “Did this session count twice?”
- “Can the club retry after a failure without moving everybody again?”
If an earlier attempt left incomplete session work, the platform rebuilds from the trustworthy rating history before trying again. The retry replaces that session’s contribution rather than stacking another copy on top.
This is why the history is operationally important, not decorative. It is both the explanation shown to players and the record needed to restore a consistent starting point.
Finalization does more than ratings. Depending on the competition and results, it can also update weekly summaries, recognise achievements, refresh saved standings, recalculate team scores, create team-order suggestions and prepare notifications.
Not every follow-up has the same consequence. The platform separates failures that make the session unsafe to publish from failures that can be reported as follow-up warnings.
Critical failures keep the session Under Review. A retry reconstructs the dependable pre-session position and repeats the work without counting the session twice.
Other failures can be non-fatal. A later summary, saved view or message may need another attempt even though the rating and history are sound. The administrator should see that warning rather than receiving a false claim that every secondary effect completed perfectly.
That distinction matters. “No half-updated ratings” applies to the rating and history save. Claiming that every follow-up action shares the same guarantee would be false.
Results Posted is the public boundary
The important work runs while the session is still Under Review. Only after it succeeds does the platform mark the session as Results Posted and close live PIN entry.
That ordering matters because rating-aware standings and player histories treat posted sessions as settled. The public label is therefore more than a badge. It tells readers that the competition record has crossed from review into published history.
Messages about the completed session are prepared after that transition so they can include the posted results rather than an older ladder.
For clubs, the practical rule remains simple: use the preview, resolve disputes, then finalize once. The Understanding Your Rating tutorial explains what players see after that point.
The organiser still owns the review
Safe finalization does not make pre-publication review optional. It protects the act of publishing, but it cannot decide whether a handwritten score was transposed or whether the wrong doubles partner was selected.
Before pressing Finalize:
- Confirm all expected matches are present.
- Resolve protests and unusual outcomes.
- Check the projected rating changes.
- Make sure another administrator is not already completing the session.
- Treat any warning after completion as a real follow-up item.
This complements the rating rules described in Why Two Wins Can Produce Different Rating Changes. Correct arithmetic and trustworthy publication are separate responsibilities.
The practical difference is easy to state: the platform does not treat finalization as “change the status and hope the rest finishes.” It keeps the rating and its history aligned, prevents simultaneous completion, and makes the core work safe to retry. For a club, that means one publication step can remain the moment everyone agrees the reviewed session became official.