Commissioner: How to Set Up Your Waiver Wire (FAAB vs. Priority vs. Standard)
Waiver wire settings determine whether in-season roster management rewards strategy, patience, and fair access or simply rewards whoever is awake when news breaks. A good commissioner chooses the waiver system before the season, explains it clearly, and removes avoidable loopholes.
Waiver System Comparison and Selection Guide
| System | How it works | Competitive balance | Complexity | Best for |
|---|---|---|---|---|
| Waiver priority | Teams pick in reverse priority order; used picks move to the bottom | Low — early claims can lock one team at the bottom all season | Low | Casual leagues, beginners, leagues that prioritize simplicity |
| Rolling / FCFS | First come, first served — fastest click wins after waivers clear | Very low — rewards phone monitoring at 4am, not strategy | Very low | Not recommended for most leagues |
| FAAB | Blind bids; highest bid wins; budget depletes over the season | High — every claim is a strategic decision with real cost | Medium | Competitive leagues, experienced managers, leagues that want in-season management to matter |
For competitive leagues: Use FAAB. It’s the most skill-expressive, fairest, and most engaging waiver system. The learning curve is manageable after one season.
For casual/beginner leagues: Use waiver priority. Simpler to explain, no budget management required.
For any league: Avoid rolling/FCFS. It rewards availability (who’s watching their phone at midnight) over decision-making. No competitive value.
FAAB Configuration Details
Budget amount:
- $100 budget: Most common. Each dollar = ~1% of budget — easy to express bids (“bid $22 on the RB2”). Standard for most leagues.
- $1,000 budget: More granularity; allows bids like “$125” without committing a quarter of your total budget. Some experienced leagues prefer this.
Both work. Pick one and stay consistent across seasons.
Carry-over vs. reset:
- Carry-over (dynasty leagues): Unused FAAB rolls over year-to-year. Creates long-term financial strategy — managers who save FAAB can dominate future waiver periods.
- Reset (redraft leagues): Each season starts fresh. Simpler. Any unspent budget at the end of the season is lost.
Claim period:
- Weekly (recommended): All bids submitted for Tuesday morning processing. Waivers clear simultaneously, all claims resolved at once. Predictable and fair.
- Continual: Teams can bid anytime; waivers clear at 24-hour intervals. More responsive to mid-week injuries but adds complexity and requires more technical setup.
Start with weekly claim periods. You can always switch to continual if the league wants more responsiveness.
Setting Waivers on Each Platform
ESPN: Settings → League Settings → Waivers. Options include Continual Rolling List, Move-to-Last-After-Claim (traditional priority), or FAAB. Set budget in the same menu.
Sleeper: Settings → Waivers → Waiver Type. Full FAAB support. Budget amount, claim window, and bid privacy all configurable.
Yahoo: Settings → Waivers. Yahoo supports FAAB and priority. Note: Yahoo’s default is “rolling claims” — which is NOT FAAB. Explicitly switch to FAAB if desired; the default will confuse managers who expect blind bids.
The One Setting That Trips Up Most Leagues
Waiver claim timing — set “immediate waivers” if your platform supports it.
Post-game waivers (default on most platforms): Players who played Sunday are on waivers until Tuesday night. Players who played Thursday (TNF) are on waivers until Saturday.
Immediate waivers: A player goes to waivers immediately when dropped, rather than becoming a free agent who anyone can grab instantly.
Platforms that allow players to be dropped and immediately picked back up before waivers process create an exploit — a manager can drop a player Monday night and re-add them before anyone else can claim them. Immediate waivers prevents this.
Check your platform’s settings and enable immediate waivers. This one setting prevents a category of disputes entirely.
Worked Example
Imagine a competitive league using first-come, first-served waivers after games. A starting running back is injured during a late game, and one manager happens to be online first. That manager gets the backup for free while the rest of the league had no realistic chance. The setting rewarded availability, not strategy.
Now imagine the same league using FAAB with a Tuesday claim run. Every manager can evaluate the injury, decide how much of the budget to spend, and submit a blind bid. The winner still gains the player, but the process is fair and strategic.
For a casual family league, waiver priority may still be fine because simplicity matters. For a competitive league, FAAB is usually the best default because it gives every manager a shot at every player while forcing real budget decisions.
Common mistake: leaving platform defaults untouched. Defaults often optimize for simplicity, not fairness; commissioners should intentionally choose waivers, claim timing, and drop rules.
For broader league settings during setup, see: Commissioner: How to Set Up and Run Your Fantasy Draft. For handling waiver disputes when managers believe a claim was processed incorrectly, see: Commissioner: How to Handle Trade Disputes and Complaints.