How to run an NFL survivor pool in 2026

A survivor pool (also called an eliminator or last-man-standing pool) is the simplest football contest there is: every week, each player picks one NFL team to win. Pick a winner, you survive. Pick a loser, you're out. The catch that makes it interesting: you can never pick the same team twice in a season. The last player standing wins the pool.

Simple for players — but if you're the commissioner, there's real work hiding in “simple”: rule decisions to make before Week 1, weekly deadlines to enforce, eliminations to track without mistakes, and an endgame that needs a tie-breaker plan. This guide walks through all of it, in the order you'll face it. We'll use PicksHub as the worked example since that's what we build, but the decisions apply no matter how you run your pool.

1. Decide your rules before anyone joins

Every survivor pool argument in December traces back to a rule that wasn't written down in August. Settle these four before you invite a single player:

Strikes: sudden death or a mulligan?

Classic survivor is one loss and out. Many pools soften that to two strikes (your second loss eliminates you), which keeps more players alive into November and keeps casual players engaged. Bigger pools can afford sudden death; smaller pools often play better with a mulligan. In PicksHub this is one setting (“strikes allowed”) chosen at pool creation.

Missed picks: strike or free pass?

Someone will forget to pick during a bye-week trip. Decide now: does a missed pick count as a loss, or is it quietly excused? Most pools treat a missed pick as a strike — a free pass punishes the players who showed up. Whatever you choose, it must be automatic and non-negotiable, because the person who forgets will be your brother-in-law. PicksHub applies your missed-pick rule automatically the moment the week locks.

Team reuse: the rule that shapes the whole season

“Never pick the same team twice” sounds like one rule but is actually two decisions:

• Winners: once you survive with a team, that team is burned for the rest of your season. This is the core survivor mechanic — nearly every pool uses it.
• Losers: in multi-strike pools, can a player re-pick a team they lost with? Some pools say yes (you didn't “use” the win), some say no (a pick is a pick). Both are defensible — what matters is that the rule is enforced by software, not by someone auditing a spreadsheet in Week 12.

PicksHub supports both variants and blocks illegal picks at selection time, so nobody can accidentally (or “accidentally”) reuse a team.

The endgame: what if nobody survives — or two players do?

Two endings need a plan. If everyone alive loses in the same week, do they all die (and the pool ends in a tie among that week's casualties), or does the week get replayed? And if the season ends with multiple survivors, do they share the title or does a tie-breaker (like total wins) decide it? Write it down before Week 1. PicksHub asks for your tie rule up front and applies it automatically when the pool completes.

2. Set up the pool and invite players

However you host, three logistics questions come up in the first week:

• How do people join? A shareable invite link is the baseline. Decide whether anyone with the link can join (fine for friends-of-friends pools) or whether you want a gate. PicksHub gives you an invite link plus two optional gates: an access code, and manual approval of each join request. For most pools, auto-approve plus an access code is the sweet spot — no bottleneck, but no strangers.
• Multiple entries? Letting players run two or three entries keeps them interested after their first entry dies, and larger pools commonly allow it. Set a per-player cap so one person can't flood the pool.
• Who's actually in? If your members are helping you cover the pool, you need to know who's squared up before kickoff — chasing 300 people through a group chat doesn't scale. PicksHub gives organizers a private activation checklist: every entry starts as “Pending,” members can tap a button to tell you they're all set, and you mark entries Active as they settle up with you — however your group handles that, entirely outside the platform. Each member also gets a short member number (“This is #24”) so messages from a big roster are instantly identifiable.

3. Run the weeks

The commissioner's weekly job is three things, and all three should be automatic:

• Lock picks on time. Decide when picks close: at each week's first kickoff (standard), at each pick's own game time, or at a fixed weekly deadline like Sunday noon. Enforce it by machine — a commissioner manually locking a spreadsheet at 12:59 on Thursday is how pools lose friends. Late picks are the single most common survivor dispute.
• Score accurately. One wrong elimination and trust is gone for the season. PicksHub scores from two independent data feeds that must agree before any result is final — when they disagree, the organizer sees a side-by-side dispute view instead of a silent mistake.
• Keep everyone informed. Pick reminders before lock, results and eliminations after the games. If your hosting does this by email automatically, your group chat stays fun instead of administrative.

A note on strategy your players will appreciate: because teams can't be reused, the best pools aren't won by picking the biggest favorite every week — they're won by saving the best teams for the weeks you'll need them. Watching a rival burn their last good team in October is half the fun.

4. The end of the season

Most pools end before Week 18 — someone becomes the last entry standing and the pool completes. When it goes the distance, your written tie rule from step 1 takes over: co-champions, or a tie-breaker like total wins. Either way, the finale should be automatic: winner determined by the rules everyone agreed to in August, announced to the whole pool, with the full pick history available so anyone can verify it.

Commissioner's checklist

1. Choose strikes (sudden death or two), missed-pick rule, team-reuse variant, and tie rule — in writing.
2. Create the pool and set an access code; decide the multi-entry cap.
3. Send the invite link; track who's squared up as people join.
4. Activate the pool once everyone's in — before Week 1 locks on September 9.
5. Let the software run the weeks: locks, scoring, eliminations, emails.
6. Crown the winner the rules picked, not the one the loudest player argued for.

Week 1 of the 2026 season locks Wednesday, September 9. A pool takes about five minutes to set up, and your invite link can be in the group chat today.