Survivor rules

Remain alive by selecting one winning team each round without selecting the same team twice in the competition. There is nothing to accumulate: the only thing a round produces is whether you are still in it.

• A participant selects exactly one team playing in an eligible round event.
• A team already consumed by that participant cannot be selected again. Each participant has their own used-team history.
• The entire round locks at the earliest eligible event’s authoritative kickoff or observed start, whichever occurs first.
• Before the round lock, the participant may replace the selection with any eligible unused team. The latest server-receipted revision is authoritative.
• No valid pre-lock selection eliminates the participant. Silence is not survival.

If a postponed event remains within the configured round, the locked selection follows it and is scored when the result is final. If the event moves outside the configured round, it is void for that round: the participant survives and the team is not consumed.

The competition ends when any one of these is true:

1. exactly one participant remains alive after a finalized round — that person is champion;
2. no participant remains alive after a finalized round — everyone who was alive entering that round and was eliminated in it is a co-champion; or
3. the configured final round ends with multiple survivors — all remaining survivors are co-champions.

There is no hidden tiebreaker in any of the three cases. The second case is the one informal pools argue about: when the field is wiped out in a single round, this version names the whole wiped-out field as co-champions rather than reaching for a rule invented after the fact.

Ranking the eliminated

Eliminated participants rank by latest elimination round, so lasting longer ranks higher. Participants eliminated in the same round share a rank.

Selections stay private until the round locks, then become visible to the community. Because the round locks as one unit, nobody sees a live selection while the round is still open.

Used-team history and alive-or-eliminated status are visible after each applicable lock. That is deliberate: which teams a rival has burned is part of the game, and it is only knowable once the lock has removed any advantage in knowing it.

1. 01

   A participant selects Harbor City, and Harbor City wins.

   The participant survives, and cannot select Harbor City again in this competition.

2. 02

   Harbor City loses, or the event ends tied.

   The participant is eliminated, and Harbor City is consumed either way.

3. 03

   The selected event is declared a no-contest.

   The participant remains alive and may use Harbor City in a later round.

4. 04

   Every remaining participant loses in Round 8.

   Those participants are Round-8 co-champions and the competition ends.

5. 05

   A selection arrives at the exact round lock timestamp.

   Rejected. The participant is eliminated unless an earlier valid receipt exists.

A corrected official result in Survivor is the heaviest correction in the product. It can revive or eliminate participants, and it can change whether a team was consumed — which changes what was legal to select in every later round.

So the scorer replays the competition in round order from the earliest affected round, because later team eligibility and the competition-end state may both change. It is never a patch applied to the current standings.

The shared append-only correction process applies: originals are preserved; actor, time, reason, evidence, and scope are recorded; the same deterministic scorer reruns; the change appears in the competition’s correction log; and materially affected participants are notified — including anyone whose elimination is reversed or whose survival is not.

Members can flag an apparent issue until 48 hours after a round is finalized, and Clutchhall still fixes an objectively verified error found later. How to report an integrity issue.