How to Write a Fantasy Football League Constitution: What to Include and Why It Matters
A constitution does not need to be long. It needs to be clear. Every rule that is open to interpretation will eventually be tested, and when it is, having a written answer agreed upon before the season beats deciding in the moment.
League Constitution Quick Reference
| Section | What to cover | Most common mistake |
|---|---|---|
| League format | Number of teams, head-to-head vs. total points, playoff weeks, consolation | Skipping consolation rules; last-place punishment rules that go undocumented |
| Scoring | Every category — PPR value, TD values, bonuses | Leaving unusual settings undocumented; managers find out mid-season |
| Draft rules | Snake vs. auction, draft order method, keeper rules, deadline, auto-pick policy | Keeper rules ambiguous on cost; late submissions not addressed |
| Waiver wire | Type (rolling/FAAB/reverse), processing day, FAAB budget | No document on FAAB amount; disputes about waiver priority |
| Trade rules | Review window, veto mechanism, trade deadline, collusion definition | “Commissioner only” veto with no criteria given — appears biased |
| Tiebreakers | In-season seeding, playoff tiebreaker, multi-team tie resolution | Discovered on the day a tie occurs; any ruling looks biased to the loser |
| Manager conduct | Inactivity policy, collusion consequences, dispute resolution process | Manager replacement rules undocumented until someone quits mid-season |
Why Every League Needs a Written Constitution
Memory is unreliable. “We always do it this way” is not a constitution. Different managers will remember previous decisions differently, and what was decided in year 3 is not always remembered correctly in year 8. A written document eliminates “I thought we agreed” disputes.
Precedent compounds. Every ruling a commissioner makes without written backing becomes a potential precedent for future disputes. A written constitution limits what managers can cite as precedent.
New manager onboarding. When a manager joins your league, a constitution tells them how the league works without requiring the commissioner to explain everything personally.
Core Sections of a League Constitution
League format and structure: Number of teams; head-to-head or total points format; regular season length and playoff format (number of teams, which weeks); consolation bracket rules.
Scoring rules: Document every scoring category your platform uses, including unusual settings (PPR, bonus points for long TDs, TE premium) so managers can verify their understanding against the official record.
Roster requirements: Number of starters at each position; total roster size; bench spots; IR spots; taxi squad (dynasty leagues).
Draft rules: Snake vs. auction; draft order determination method; auto-pick policy (what happens if a manager disconnects); time per pick; keeper rules — how many, which round, eligibility requirements, deadline.
Waiver wire rules: Waiver type (rolling priority, FAAB, reverse standings reset); FAAB budget if applicable; processing day and time; free agent rules after waiver period clears.
Trade rules: Trade review window; veto mechanism (commissioner only, majority vote, or none); trade deadline date; collusion definition and consequences.
Tiebreakers: In-season tiebreakers for playoff seeding; playoff tiebreakers if a game ends in a tie; multi-team tie resolution.
Prize structure: Total dues per manager; how dues are collected and secured; prize breakdown; payout timing.
Manager conduct: Inactive manager policy; anti-collusion policy; dispute resolution process; manager replacement policy.
What to Avoid in a Constitution
Over-specificity for rare scenarios. You cannot anticipate every edge case. Trying to enumerate every possible situation creates a document so long managers do not read it. Write rules that address known recurring situations and give the commissioner clear authority to rule on everything else.
Ambiguous language. “Players must be set by a reasonable time before the game” is not a rule — it is an invitation to argue what “reasonable” means. Use specific, measurable language: “Lineups must be set by 30 minutes prior to their game’s kickoff per the platform lock.”
Retroactive rule changes. A rule cannot be added to resolve a current dispute and applied retroactively to the dispute that prompted it. If a new rule is added mid-season, it takes effect the following week. Document this principle in the constitution itself.
Maintaining the Constitution
Update after every rule change. When the league votes to change a rule, update the constitution immediately. A constitution that is 3 years behind current practice is not a useful document.
Version control. Date every revision — “Last updated: January 2026” — so managers can confirm the document reflects current rules.
Accessible location. Store the constitution somewhere every manager can access: a shared Google Doc, the platform’s league notes, or an email sent to all managers at the start of each season.
For how to handle specific situations covered in the constitution, see: Commissioner Guide: How to Handle Trade Disputes, Vetoes, and Collusion. For the full commissioner playbook covering setup through end of season, see: Commissioner End-of-Season Checklist: How to Close Out the Year and Set Up Next Season.