Fantasy Analytics
Reading Usage for Waiver Decisions
5 min read
TL;DR
The waiver wire rewards acting on role changes before they turn into points. That means reading usage trends, not last week's box score, because everyone can see the box score.
You are competing on timing
Everyone in your league sees the same scoring leaderboard. A player who scored 22 points last week will be claimed by whoever has the highest priority, and the price is set by that visibility.
The advantage available is in players whose role has changed but whose points have not caught up yet. That gap usually lasts a week or two.
What to look for
- A step change in snap share, not a drift. A jump from 30% to 60% in one week is a decision; a slow rise is a trend that others have already seen.
- Route participation rising for a receiver, especially with a teammate injured or struggling.
- Goal-line carries changing hands. Small volume, disproportionate scoring.
- A schedule that is about to soften, which turns an emerging role into visible production.
Two of these together is a much stronger signal than any one alone.
The discipline part
Most waiver claims fail, and that is normal — you are buying lottery tickets on role changes, and most role changes do not stick.
The two habits that matter are to act on process rather than on the last box score, and to drop the claim without ceremony when the usage does not hold up in week two. Being wrong quickly is cheap; being wrong slowly costs you a roster spot for a month.
Keep these
- The edge is in role changes that have not yet become points
- A step change in snap share beats a good box score
- Most claims fail — cut them fast when the usage does not hold
Up next
Which Stats Stabilize First
