Fantasy Football Commissioner Player Adds: How to Handle Player Addition Disputes and Issues
The dispute resolution first step: before making any correction, verify what the platform’s transaction log shows — not what the manager claims should have happened. Platform transaction logs are the authoritative record of what was submitted, when, and at what bid or priority. Most “dispute” situations are resolved by reviewing the log with the manager and showing them exactly what their submission contained.
Player Add Dispute Quick Reference
| Dispute type | Root cause | Resolution | Mistake to avoid |
|---|---|---|---|
| Wrong player claimed | Manager selected wrong player from the platform interface — their mistake, not a platform error | Review transaction log; define in league constitution whether commissioner correction is available for manager-error wrong-player claims | Correcting every wrong-player claim regardless of cause — a platform error is correctable; manager interface error is their responsibility |
| FAAB bid amount dispute | Manager claims they submitted a higher bid than recorded — almost never a platform error | Review transaction log timestamp against bid recorded; FAAB bids are recorded at submission with timestamp | Overriding recorded FAAB bids without clear evidence of platform error — reversing manager-submitted bids based on their claim undermines the blind bid system |
| Claim priority dispute | Manager believes their priority was higher than applied — misunderstands how weekly reset works | Explain the priority reset system; show the priority standings at the time the claim processed | Assuming the manager is correct about their priority without verifying against the platform log — priority disputes are almost always misunderstandings |
| Processing timing dispute | Manager submitted before the deadline but claim did not process | Check the submission timestamp against the platform’s waiver processing window; some platforms process at specific times, not continuously | Promising to investigate without checking the timestamp first — the timestamp resolves 90% of timing disputes instantly |
| Drop-add dispute | Manager dropped a player who was claimed by another team; original manager claims they made an error | Define in constitution whether drop reversals are available — most leagues do not allow it to prevent gaming the waiver system | Reversing drops on request without a constitution provision — establishes precedent that all accidental drops can be reversed |
| Platform error: confirmed | Platform transaction log shows different result than what manager submitted, confirmed by platform support | Contact platform support; request reversal; apply the correction once confirmed | Unilaterally reversing a claim without platform confirmation — only confirmed platform errors warrant commissioner correction |
Common Player Add Dispute Types
Wrong player claimed. A manager submits a waiver claim on Player A but intended to claim Player B — they selected the wrong player from the platform interface. Most platforms do not reverse this error after processing because it was a manager mistake, not a platform error. Define in your league constitution whether commissioner correction is available for documented wrong-player claims.
Bid amount dispute. A manager claims they submitted a higher FAAB bid than what was recorded. This is almost never a platform error — FAAB bids are recorded at submission time with a timestamp. Review the transaction log timestamp against the waiver deadline and verify the bid recorded is what was submitted.
Prevention Through Education
Pre-season platform tutorial. Send a brief tutorial on how to submit waiver claims (screenshots of the claim interface) before the first week of the season. Most player add disputes come from managers who misused the platform — not from platform errors or commissioner mistakes.
For how player add disputes connect to commissioner management, see: Commissioner League Rules: How to Write and Enforce Fantasy Football League Rules.