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.
Fantasy production rate by snap share (vs. players under 50%)
Source: Fantasy Rankings Authority, target share and snap count research
Once the volume boxes are checked, weight the quality of the touches. A carry from the opponent's two-yard line and a screen pass in space are worth multiples of a first-quarter run into a stacked box, which is why red-zone touches and targets inside the 10 deserve their own glance on Monday. Two backs can split a backfield evenly while one of them quietly owns every goal-line snap — and that back will outscore his timeshare partner all season on identical touch counts.
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.
Usage Means Different Things by Position
The three numbers are not equally informative everywhere, and treating them as one metric is where beginners go wrong. For running backs, the number that matters most is simply touches, and specifically whether he is on the field on third down — a back with fifteen carries and no receiving work has a lower ceiling and a much lower floor than one with twelve carries and four targets, because the second back keeps scoring when his team falls behind.
For receivers, snap share is close to a solvency test rather than a ranking: almost every full-time receiver clears it, so it tells you who is employed, not who is good. Target share is the number that separates them. For tight ends the useful question is different again — how often he runs a route instead of staying in to block, because a tight end who blocks on half his snaps has a snap share that flatters him badly.
And for quarterbacks, usage in this sense barely applies. He plays every snap by definition, so the equivalent question is his rushing volume, which is the single largest swing factor in quarterback scoring and has nothing to do with the passing game at all.
What Usage Does Not Tell You
Usage is the best available predictor, which is not the same as a good one, and it is worth being clear about its limits. It does not tell you how efficient a player is — two backs with identical carries can differ by two yards a carry, and that gap is real even if it is less stable than volume. It does not tell you about touchdowns, which depend on how often his offense reaches the red zone at all. And it says nothing about game script: a back whose volume comes from playing with a lead has a role that quietly disappears when his team starts losing.
The honest summary is that usage tells you the size of a player's opportunity and almost nothing about what he will do with it. That is still the most valuable thing you can know in September, because opportunity is stable and results are not — but it is a floor under your judgment rather than a replacement for it.
The Five-Minute Weekly Check
None of this needs to be a research project. Once a week, after the games, do the same short pass:
- •For every player you start: did his snap share hold? A drop of more than about ten points is worth an explanation before you start him again.
- •For every bench player: did anyone's snap share climb two weeks running? That is your own roster telling you something before the waiver wire notices.
- •For the wire: who saw real volume in a game nobody watched? A back who quietly took twelve carries in a blowout is more interesting than a receiver who caught one long touchdown.
- •For anyone who just got hurt on another team: whose usage is about to change because of it? That is the claim you want in before Tuesday night.
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.