Pools run smoothly almost every week. The data flows, the leaderboard updates, the math settles. But every commissioner who runs more than a few pools eventually hits an edge case — a golfer withdraws mid-round, the score looks off, an entrant claims a tiebreaker mistake. This guide walks through the disputes and edge cases that come up most often, and the practical steps for resolving them without the room melting down.
Most disputes resolve themselves once you check the source of truth. Mid-round withdrawals, cut-rule penalties, and scoring corrections all have well-defined behaviors. Force-completion and manual overrides exist for the unusual cases.
The principle — check the source before you rule
When a dispute surfaces, the first move is almost never to make a ruling. It is to check the source.
The platform's leaderboard derives every column from a published data feed. If a roster's score looks wrong, the question is whether the underlying score in the data feed matches what the leaderboard shows. In almost every case the answer is yes — the data is correct, and what the entrant remembers from the broadcast is wrong. Pull up the official tournament page for the round in question, find the player, and check the round score. Nine times out of ten the dispute evaporates.
The cases where the data is actually wrong are rare but real. A round score occasionally lands incorrectly in the feed before being corrected; a player's status is misclassified for an hour before the next sync picks up the correction. The platform's ingestion gates catch the worst of this — partial-round strokes are blocked from persistence, and durable-absence detection auto-flips players who disappear from the field for three consecutive syncs. If the leaderboard genuinely diverges from the official scoring, contact us and we will resolve it from the engine side.
Mid-round withdrawals
A golfer on a roster withdraws mid-round. This is the single most common edge case, and the behavior is well-defined.
The platform marks the player as wd once the next data sync confirms it. The status is upgrade-only — once a player is wd, no subsequent sync can flip them back to active unless a commissioner manually corrects it. The roster row showing that player goes inactive: their name renders muted with a WD pill, their score cells render dashed, and their counting status drops.
What happens to the team total depends on the cut rule. In a worst_active pool, the player's missed rounds are filled with the worst score any active golfer in the pool posted that round. In a fixed_penalty pool, the missed rounds get the configured penalty number. In a field_average pool, the missed rounds get the average of active golfers that round.
The full mechanics live in How Scoring Works. For dispute purposes, the rule the commissioner needs to remember is: the platform applies the cut rule automatically. There is no manual step.
Cut-line ambiguity
Round 2 ends. The platform announces a cut. An entrant insists their golfer made the cut and the system has it wrong.
Cut detection follows the published tour rule for the tournament. Most events use 70-and-ties at 36 holes; the platform tracks this per tournament and stores the cut-after-rounds value explicitly so the engine knows when to run cut detection. For the small number of events with non-standard cuts — Signature Events with no cut, the four-round events that cut after Round 3 — the platform's value is the source of truth.
When an entrant disputes a cut classification, three checks in order:
The official tournament page lists who made the cut. Confirm what the tour says.
The platform's cut-sync routine runs once per tournament at R2-official; if the dispute comes in within the first hour of the cut event, the sync may not have completed yet. Wait an hour and re-check.
If both checks confirm the platform has it wrong, contact us. The cut-sync routine writes upgrade-only — once a player is marked cut, the engine will not flip them back without a manual override.
Scoring corrections after a round
The tour occasionally posts a corrected score hours after the round ends. A player was credited with a 71 at posting; the official scorecard reconciles to 72 the next morning. The platform re-reads the data feed on every recalculate-scores tick, which runs every five minutes during active tournaments, and the corrected score propagates automatically. Leaderboard rows update within the next tick after the data feed publishes the correction.
The only manual case is when the tour issues a correction so far after the round that the data feed never picks it up. This is rare — once or twice a season across the majors. In those cases the commissioner cannot fix it themselves; contact us and we will run a manual recalculation against the corrected data.
Tournament-level interruptions
Weather, course conditions, or an act of god occasionally truncate a tournament. The PGA Tour has shortened majors to fifty-four holes; the U.S. Open has been postponed for weather. The platform handles these cases through the same data feed that handles a clean tournament — the tour announces the truncation, the data feed reflects it, and the engine treats the truncated tournament as complete.
For pools, this means:
A four-round pool whose tournament finishes at fifty-four holes scores the final standings off the first three rounds. The cut rule (if applicable) still applies. The team total is the sum of counting golfers' scores across the rounds actually played.
A Weekend Shootout pool whose tournament truncates before Round 4 is played is the unusual case. The Round 3 and Round 4 scoring window collapses. The platform handles this by completing the pool against whatever rounds actually occurred; if only Round 3 played, the team total is the sum of Round 3 counting scores.
A tournament that is fully cancelled flips the pools attached to it through the cancellation path. Entry fees are not handled by the platform, but the commissioner sees a clear "cancelled" state on the pool page and can refund entry fees off-platform if the pool was paid.
Tiebreaker disputes
The tiebreaker resolves the leaderboard at completion. An entrant occasionally insists the resolution is wrong.
Three things to check before responding:
The tiebreaker rule applied is the one snapshotted at lock time. If the commissioner changed the tiebreaker rule mid-pool — which is allowed at Birdie and above until lock — the snapshot is the source of truth, not the current rule shown on the pool page.
The tiebreaker math is documented in Tiebreakers Explained. The cascade walks through best_score_type → best_single → fewest_cuts → earliest_submission if the chosen rule fails to separate the tied entries. If two entrants are still tied after every rule, the leaderboard renders them as a true tie and the payout splits per the default rule.
Cascade outcomes can feel surprising. An entrant who lost on best_single because their best round was a 70 and the other roster's best round was a 69 sometimes argues that the rule favors small differences. It does — that is the design. The rule is a rule; the dispute is about whether the room wants this rule next year, not about whether the engine resolved it correctly this year.
Common questions
An entrant claims they submitted before the lock but the platform says they did not. What do I do?›
Pull up the entry record. The platform stores a submission timestamp on every entry, including draft saves. If the entry shows a submission timestamp before the lock, the entry is valid; the entrant's confusion is about the join versus submit distinction (joining a pool is not the same as submitting a roster). If the entry shows no submission, the entrant did not submit and the lock correctly excluded them. The platform does not retroactively admit late entries except via the Eagle-plus late-entry feature, which has to be configured during setup.
The leaderboard shows a player with a status I do not recognize — DNS or DNF. What does that mean?›
DNS is "did not start" — a player on the roster who was in the field but never teed off in Round 1. DNF is "did not finish" — a player who teed off but withdrew before completing the round in progress. Both are treated as missed-round statuses for cut-rule purposes. The platform shows them as muted pills on the roster row, the same way WD and CUT render.
What happens if a roster has so many cuts and withdrawals that none of the counting golfers played four rounds?›
The team total is computed against whatever counting rounds actually occurred, with the cut-rule penalty applied for missed rounds. In practice, this is an unwinnable position — the penalty stack puts the roster well above the field — but the engine resolves it without erroring. The roster appears on the leaderboard with a high total and a high cut count, and the standings settle accordingly.
For the broader scoring picture, read How Scoring Works. For when payments are part of the dispute, read Managing Payments as a Commissioner. For host setup, read The Commissioner Guide.