Fantasy Football Anti-Tanking Rules: How Commissioners Handle Intentional Losing
Tanking in fantasy football damages league integrity in ways that ripple beyond the manager doing it. A team that benches starters to lose games artificially changes the standings for every other team they play — and managers who lose to an intentionally weakened lineup have legitimate grievances.
Anti-Tanking Quick Reference
| Situation | Commissioner action | Mistake to avoid |
|---|---|---|
| Manager benches healthy starter for no clear reason | Direct message first: “Is everything okay with your team?” | Immediately accusing tanking without evidence |
| Manager starts player on bye intentionally | Confirm intent; if pattern exists, cite anti-tanking clause | One bad lineup decision ≠ tanking; need evidence of system |
| Manager trading away starters after elimination | Evaluate whether trades are reasonable returns; post publicly if not | Blocking legitimate roster rebuilding — managers are allowed to trade |
| Manager stops logging in entirely | Zombie-team protocol: contact directly, then replace if no response | Leaving a zombie team to auto-set for weeks; damages everyone |
| No anti-tanking rule exists | Do not create rules mid-season — cite fairness principle, document, write rule for next season | Mid-season rule creation is itself an integrity violation |
What Tanking Actually Is
Explicit tanking vs. giving up. The most important distinction for commissioners is between explicit tanking and a manager who has simply given up. These look similar from the outside but require very different responses.
Explicit tanking: A manager deliberately sets a suboptimal lineup to lose — benching a healthy WR1 for an injured backup, starting a player on a bye week intentionally, or trading away starters for mid-round picks after being eliminated.
Giving up: A manager who is eliminated from playoff contention and simply stops engaging — auto-sets lineups, stops making moves. This creates a competitive integrity problem but is not the same as deliberate manipulation.
The key test: is the manager making decisions designed to lose, or are they simply not making decisions?
Why Anti-Tanking Rules Are Important
The competitive ripple effect. When Team A tanks to get a worse record, they face Team B next week. Team B beats an intentionally weakened lineup and gets a win they may not have earned against a full-effort team. Meanwhile, Team C — who played Team A the week before and lost — has a record that does not reflect this imbalance. The manager doing the tanking is not just affecting their own season — they are changing the competitive landscape for every team in the league.
The keeper/dynasty compounding. In keeper or dynasty leagues, the tanking problem is amplified. A manager who tanks to get a worse record picks earlier in the dynasty rookie draft, acquiring assets that provide value for years. The cost is a few losses in a season where the team was already eliminated — the benefit is multi-year draft capital.
Anti-Tanking Policies
Lineup lock notification. The simplest policy: require managers to set their lineups by a stated deadline or the commissioner contacts them directly. If a manager fails to set a lineup, the commissioner sets the optimal lineup for that week from their available players. This is preventive, not punitive — it catches the passive case (manager who stopped engaging) and requires no judgment call on intent.
Side pot for total points. Adding a total points tiebreaker or prize creates an incentive to score every week regardless of win-loss position. A manager who is eliminated from the playoff race but competing for the highest total points prize has a reason to field their best lineup.
The zombie-team problem. A manager who genuinely abandons the league mid-season — stops logging in entirely, misses multiple weeks of waiver claims — should be replaced. Follow your replacement manager process.
Explicit prohibition in the constitution. Include an anti-tanking clause: “Intentionally setting a lineup to minimize your score is a violation of league rules and subject to commissioner review.” This gives you the rule to cite if you need to intervene.
Handling Suspected Tanking
Gather evidence before acting. A manager who benches one player for a surprising reason has not necessarily tanked. Evaluate: is there a plausible legitimate reason for the lineup choice? Before accusing someone of tanking, confirm the decision pattern is systematic and inexplicable.
The conversation first. In most cases, a direct message to the manager is the right first step. “I noticed you benched Amon-Ra St. Brown this week — is everything okay with your team?” This addresses both the passive-giving-up case and gives a manager a chance to correct course before it becomes a formal issue.
Ruling publicly when needed. If a manager is clearly tanking — trading away a playoff-contending roster for picks, starting players on byes — announce the investigation to the full league with your reasoning. The ruling gains legitimacy when it is transparent.
For the broader league constitution framework that should include anti-tanking rules, see: How to Write a Fantasy Football League Constitution: What to Include and Why It Matters. For how to handle the related problem of managers going inactive during the season, see: Fantasy Football League Engagement: How Commissioners Keep Managers Active All Season.