Commissioner Guide: How to Set and Enforce a Trade Veto Policy
Nothing creates more fantasy league conflict than trade vetoes. Managers who benefit from blocking trades are incentivized to use the veto process for competitive reasons, not integrity reasons. Without a clear policy, commissioners get trapped between angry managers and damaged league culture.
Veto Policy Quick Reference
| Situation | Right call | Wrong call |
|---|---|---|
| Contender trades RB1 for WR2 + 2 picks | Allow — both sides have plausible rationale | Block because one side “got a bad deal” in your assessment |
| Last-place team trades elite WR for a bench player | Review — contact both managers, ask for rationale; if no sense can be made, consider veto | Allow without review because “managers can make mistakes” — true, but this warrants a check |
| Same two managers trade repeatedly, always in one direction | Review the pattern holistically — individual trades may be defensible; the pattern signals collusion | Evaluate only each individual trade in isolation |
| Manager in a must-win situation sells their best player cheaply | Contact them first and confirm they understand the trade — may be a panic seller, not colluder | Assume collusion without the conversation |
| League manager vote to block a trade | Commissioner-only veto recommended — league votes enable competitive blocking | Allow majority-vote vetoes without a supermajority requirement — encourages competitive blocking |
The Core Problem With Naive Veto Systems
Many leagues use “manager vote” systems where any trade can be blocked if a majority votes against it. This sounds fair but creates structural problems:
- Competitive vetoes: Managers vote against trades that benefit opponents, not because the trade is unfair.
- Chill effect on trading: Managers who know their trades will get scrutinized stop making trades — reducing everyone’s enjoyment.
- Inconsistency: Trades that are objectively similar get treated differently based on which managers are involved.
The goal: A good veto policy blocks actual collusion while letting all good-faith trades go through without interference.
Defining Actual Collusion (vs. Just a Bad Trade)
What collusion looks like:
- A last-place manager sells elite players to a contending team for clear junk (to help a friend or settle a private debt)
- A manager who is eliminated trades away their best players with no plausible fantasy rationale
- A manager who owns two teams in the same league trades between their own teams
- A pattern of trades between two managers where value consistently flows in one direction over a season
What collusion is NOT:
- A trade where one side appears to get less value, but both sides have a rationale
- A rebuilding team selling veterans for picks or youth
- A contending team giving up future picks for a rental player
- Any trade where both managers can explain their reasoning
The test: Can both managers explain why they made this trade in terms that make sense given their team’s situation? If yes — not collusion. If no — review warranted.
Commissioner-Only Veto (Recommended)
The commissioner (and possibly a designated trade review panel of 2–3 managers) has sole authority to veto trades. League managers do not vote.
Pros: eliminates competitive vetoes; faster resolution; more consistent standards. Cons: commissioner must be perceived as neutral and fair; if the commissioner has a conflict of interest, the appearance of bias becomes a problem.
Write the standard into the constitution: “Trades may only be vetoed if they involve: (1) clear evidence of collusion between managers, defined as one side receiving significantly less value than they are giving up with no plausible competitive rationale for the weaker side; or (2) a manager clearly not understanding what they are giving up (commissioner may contact both managers to confirm understanding before ruling). Trades will NOT be vetoed because other managers believe one side got a bad deal. Managers have the right to make mistakes.”
Handling Trade Review Requests
When a manager asks you to review a trade:
- Acknowledge the request and commit to a timeline (24–48 hours)
- Contact both trading managers privately and ask each to explain their rationale
- Evaluate the rationale against the written standard — not against whether you personally think it was a good trade
- Communicate the decision to all parties with a brief explanation
- Do not announce decisions in the group chat unless required — direct messages avoid the pile-on
When you veto: Document your reasoning in writing. Send it to both managers involved and keep a copy. If challenged later, you have a record.
When you allow: A brief message to the requesting manager: “I’ve reviewed the trade. Both managers have provided rationale consistent with their team situations. The trade will proceed.” No lengthy justification needed.
Transparency Practices
Announce the policy before the season. Share the written veto policy with all managers before draft day. Ask for acknowledgment. This reduces mid-season “I didn’t know that was the rule” objections.
Log all trade reviews. Keep a simple log of every trade formally reviewed and the outcome. Share the log with all managers at season end. Transparency about the process builds long-term trust.
Pattern Monitoring: The Repeat-Trader Problem
Any single trade between two close friends may be defensible. The pattern of trades over time is what signals collusion. If Manager A has received significantly more value across 4 trades with Manager B, that warrants holistic review — not just evaluation of each individual transaction.
Monitor and document repeated trade partners. If a pattern of directional value transfer emerges over a full season, that is worth a direct conversation before it becomes a constitution-level problem.
For how to structure the overall league constitution to prevent trade disputes, see: Commissioner Guide: How to Write a Fantasy League Constitution. For how to handle managers who stop participating mid-season, see: Commissioner Guide: Managing Orphan Teams and Non-Participating Managers.