Opportunity Comes Before Production
Every fantasy point starts the same way: a player was on the field, and the ball came near him. That's why usage data — snap counts, target share, touch counts — is the foundation of every serious projection system. A player cannot score on plays he doesn't participate in, so volume metrics capture the opportunity layer that sits underneath talent, matchups, and luck. Market-share statistics like snap share and target share are, as FantasyData puts it, the foundation of any potential fantasy production. Box scores tell you what happened; usage tells you what was likely to happen — and what's likely to happen again.
The Three Numbers That Matter
- •Snap share: the percentage of his team's offensive plays a player was on the field for. This is the gatekeeper stat — nothing else matters if a player isn't playing.
- •Target share: the percentage of his team's pass attempts thrown his way. The single most predictive stat for receiver scoring, especially in PPR formats.
- •Touches (carries + receptions) for running backs: raw workload, which translates to fantasy points more directly at RB than at any other position.
The thresholds are well established in the analytics community. Research compiled by Fantasy Rankings Authority shows players at 70%+ of offensive snaps produce fantasy points at roughly twice the rate of same-position players under 50%, and that a target share below 10% almost never supports bankable receiver production regardless of snap rate. For running backs the profile question is different: a back handling 60% of backfield snaps while drawing even a 12% target share is a three-down workhorse — the profile that commands weekly-starter treatment.
One Week Is Noise. Three Weeks Is a Role.
The most common usage mistake is overreacting to a single game. Snap distributions fluctuate for boring reasons: blowout scripts, packages, a veteran being rested. Analysts generally want three to four consecutive weeks of elevated usage — something like 80%+ snaps with a 20%+ target share — before treating a shift as structural rather than situational. The exception is the explicit role change: when a starter is hurt or traded, his backup's next-game usage isn't speculative, it's scheduled. Those are the situations where acting on one week of data (or zero weeks — just the injury news) is correct.
Where to Find the Data
You don't need a paid database. Snap counts are published after every game — Fantasy Alarm maintains weekly snap count pages, and most major outlets run a Monday usage column (Yahoo's weekly usage report is a good example) that pre-digests the trends. Ten minutes on Monday reading one usage report will surface every meaningful role change from the weekend — which is exactly the list of players about to appear in Tuesday night's waiver claims.
How This Connects to Waivers
Usage data is the confirmation layer of waiver strategy. Projection systems ingest this data too — which is why a sustained usage climb shows up as a rising weekly projection, and a sudden role change shows up as a projection spike. When you get an alert that a player's projection jumped, usage is the "why" underneath it, and checking it takes one minute: did his snaps and targets actually move, or did one long touchdown inflate the number? Role change means bid; box-score fluke means pass. That single check will save you more FAAB over a season than any bidding trick.