Commissioner Managing Waiver Priority: How to Set Up and Manage Waiver Wire Rules
Why the waiver priority system is one of the most consequential competitive rules in fantasy: every manager who starts a player who gets injured needs access to the waiver wire; every manager who wants to stream an opponent-specific defense or backup RB relies on the waiver wire; the system that determines who gets first claim on waiver wire players affects competitive balance throughout the season; the wrong waiver system creates incentives (intentional losing to gain priority) that damage the league experience for everyone.
Managing Waiver Priority
The two waiver systems:
The systems: (1) traditional waiver priority (reverse standings order): managers are assigned a priority number (1 = last priority, 12 = first priority in a 12-team league); the priority order is set at the start of the season (inverse of draft order or random) and resets each week (the manager who uses their claim drops to last priority); this system rewards managers who are losing (they gain priority each week they don’t use a claim) and creates the “waiver priority as currency” dynamic; it is the most traditional system; (2) FAAB (Free Agent Acquisition Budget) blind bidding: each manager starts with a season-long budget (commonly $100 or $200); to claim a waiver player, a manager bids some portion of their budget blindly; the manager who bids the most wins the player; ties are broken by the season-long reverse standings order; FAAB eliminates the “intentional losing for waiver priority” incentive and creates a second resource layer (budget management) alongside roster management; FAAB is the more skill-testing system and is recommended for competitive leagues.
The waiver processing rules:
The logistics: (1) waiver wire processing window: most leagues process waivers once per week (Tuesday morning) in the standard configuration; some leagues process multiple times per week (Monday night, Tuesday morning, Wednesday morning) to allow faster acquisition of players injured or newly available; specify the processing schedule explicitly in the constitution; (2) the continuous waiver versus batch processing distinction: batch processing handles all claims simultaneously during a single processing window; continuous (or rolling) waivers process claims in real time but can create different opportunities for managers who check the app at different times; batch processing is more fair for managers with different time availability; (3) free agency (no waivers): after the initial waiver period clears (often 2 days), unclaimed players become free agents that can be added by any manager on a first-come, first-served basis without spending budget; free agency speed strongly favors managers who monitor the app in real time; (4) connect waiver priority to paid waiver management — FAAB is a form of paid waivers (spending a limited budget); the paid waiver guide covers FAAB budget strategy and commissioner management in detail.
Commissioner management of waiver disputes:
The disputes: (1) the most common waiver dispute: a manager claims they submitted a waiver bid before the deadline but the platform shows the bid as after the deadline; resolve by requesting the platform’s timestamp log (most platforms provide this); do not override platform timestamps without documented evidence of a system error; (2) the priority-order transparency requirement: post the current waiver priority order in the league’s shared channel at the start of each week; managers should never be surprised by their waiver priority standing; (3) the FAAB balance display: ensure all managers can see all other managers’ FAAB remaining budgets at all times; FAAB bid strategy depends on knowing how much competitors have remaining; opacity in FAAB balances reduces the strategic quality of the bidding system; (4) pair waiver priority management with constitution vote processes — changes to the waiver system mid-season require a constitution vote with supermajority approval; waiver system changes affect competitive balance and require broad consensus.
Worked Example: Priority Confusion
A manager thinks they had the first claim, but the platform shows another manager higher in priority after last week’s successful claim. If the league has a written rolling-priority rule, the commissioner should apply the platform order and explain how it changed.
The best prevention is a weekly visible priority list or FAAB balance display. Managers may still dislike the result, but they should not be surprised by the mechanics.
Common mistake: changing waiver priority because a result feels unfair. Waiver systems must be mechanical or they lose credibility.
Waiver Priority Table
| System | Best use |
|---|---|
| Rolling priority | Simple leagues |
| Weekly reset | Leagues prioritizing parity |
| FAAB | Competitive leagues |
| Continuous waivers | Deep leagues with active managers |
Changing Waiver Rules
Waiver rules should almost never change midseason. Managers draft, budget, and manage roster depth based on the acquisition system in place. If the league wants to move from priority to FAAB, put it to an offseason vote and implement it before the draft.
If a platform setting is discovered to be wrong, the commissioner should compare the platform to the written rules and restore the intended setup when possible. Communicate the correction clearly so managers understand whether it was a rule change or a settings fix.
Waiver rules should also cover dropped players. Some leagues place dropped players on waivers for a fixed period; others make them immediately available. That setting can decide major disputes after accidental drops or late-week injury news, so it belongs in the same written waiver policy.
For how waiver priority management connects to the commissioner toolkit, see our paid waivers guide and constitution vote guide. Start at the commissioner hub for all resources.