Commissioner Guide: How to Write Fantasy Football League Rules That Prevent Disputes
Most commissioner disputes come from one source: a situation arose that nobody thought about in advance. The fix is a rules document that covers the obvious situations before they happen. A good rules document doesn’t need to be long — it needs to be complete and clear.
Required Sections Quick Reference
| Section | What to cover | Specificity needed | Common mistake |
|---|---|---|---|
| League format | Teams, starting lineup, roster size, scoring format, waiver type, trade deadline | List exact starting lineup slots (QB/RB/RB/WR/WR/WR/TE/FLEX/K/DST) | “We use PPR” — specify exact point values for every scoring category |
| Schedule and playoffs | Regular season length, playoff team count, seeding method, playoff format | Include consolation bracket rules if applicable | Leaving playoff seeding ambiguous when two teams finish tied on record |
| Waivers and transactions | Waiver priority, FAAB rules, trade deadline, IR rules | FAAB: starting budget, bid timing, minimum bid; IR: how many spots, what qualifies | Leaving IR qualification rules vague — becomes a dispute when a questionable player is stashed |
| Trade policy | Approval process, veto rules, collusion policy, abandoned team policy | Define veto threshold (7/12 managers) and timing (48-hour window) | “Trades may be reviewed” — by whom? By when? How is a decision made? Write it explicitly |
| Lineup rules | Lock timing, injured starter policy, forgotten lineup policy, playoff-specific rules | Write “no exceptions” when you mean it — ambiguous language invites exception requests | Leaving the injured starter policy vague guarantees a dispute in Week 4 |
| Dues and payouts | Entry fee, deadline, payout structure, payment method, non-payment policy | Specify exact amounts and exact dates | Leaving payout structure ambiguous; managers should be able to calculate their prize before the season |
| Commissioner authority | What commissioner decides unilaterally vs. league vote; conflict of interest policy | Address what happens when the commissioner is involved in a disputed trade | Not addressing conflict of interest; managers have no recourse if the commissioner rules on their own dispute |
Why You Need Written Rules
Verbal agreements don’t work in fantasy leagues. When a dispute arises in Week 8, the commissioner’s memory of “what we decided in August” conflicts with the manager’s memory, and suddenly you have an argument about what was agreed rather than about the rule itself.
Written rules serve two purposes:
- They prevent disputes by establishing expectations in advance
- They resolve disputes by providing a neutral reference point
Writing Style
Be specific, not general. “Trades may be reviewed” is useless. Write: “All trades are final unless a majority vote of 7/12 managers vetoes within 48 hours of the trade being processed.”
Address edge cases explicitly. The situations that cause disputes aren’t the obvious ones — they’re the weird ones. What happens if a game is cancelled? What if a player is dropped and re-added within the same week? Address common edge cases in writing.
Write “no exceptions” when you mean it. If your policy is that forgotten lineups play autopick with no adjustment, write: “Lineups lock at kickoff time per individual player. No lineup changes will be made by the commissioner under any circumstances after lock.” Ambiguous language invites exception requests.
Maintaining the Rules Document
Review annually. Before each season, review the rules with the full league. Propose any changes during the off-season voting period. Update the document before the season starts.
Share publicly. The rules document should be accessible to every manager at any time — not just the commissioner. A pinned message in your group chat or a shared Google Doc works well.
When Rules Don’t Cover a Situation
Despite your best efforts, something will happen that isn’t in the rules. When it does:
- State clearly that this situation isn’t covered
- Propose a resolution and the reasoning behind it
- If it’s significant, take a league vote
- After resolving it, add the situation and its resolution to the rules document
The goal is never to be right in the moment — it’s to build a rules document that prevents the same situation from happening again.
Worked Example
Imagine a manager forgets to move an injured player out of the lineup before a Thursday kickoff, then asks the commissioner to substitute a bench player after lock. If the rules document says “no lineup changes after individual player lock under any circumstances,” the answer is simple. If the rules only say “commissioner may fix obvious mistakes,” the league now has a judgment dispute.
The same issue appears with trade reviews. A rule that says “trades may be reviewed” invites arguments about timing, voters, and standards. A rule that says “trades stand unless collusion is found, with a 48-hour commissioner review window” gives everyone a process before emotions enter.
Common mistake: writing rules that sound fair but leave the actual decision unclear. A useful rule tells managers who decides, when they decide, and what standard they use.
For the lineup-specific rules that are most often disputed, see: Commissioner Guide: Setting Clear Lineup Rules — Locks, Deadlines, and Edge Cases. For the trade policy rules that generate the most commissioner headaches, see: Commissioner Guide: How to Handle Trade Disputes and Protests.