Opportunity-Based Projections: Targets, Carries, and Usage Rates

Opportunity-based projections anchor fantasy point estimates not in what a player has done but in what the team is likely to hand them — touches, targets, snaps. Targets in passing games, carries in the run game, and usage rates across positions are the raw material from which projected stats are built. Understanding how these inputs translate into scoring expectations helps explain why two players with similar historical production can carry very different projections heading into the same week.

Definition and scope

At its simplest, an opportunity-based projection starts with a volume estimate and multiplies it by an efficiency rate. A wide receiver expected to see 9 targets in a given game, with a historical catch rate of 67% and 11.2 yards per reception, produces a projected receiving line before a single snap is played. The same logic applies to running backs: a back projected for 18 carries at 4.3 yards per carry generates a rushing yardage baseline that then feeds into standard or PPR scoring calculations.

Targets and carries are not interchangeable concepts. A target is a passing attempt directed at a receiver — it counts regardless of outcome. A carry is a rushing attempt. Usage rate is the broader umbrella: in football, it typically refers to a player's share of team opportunities at their position, whether measured as target share (percentage of team passing attempts directed at one receiver) or carry share (percentage of team rushes given to one back). The snap-count and target share data tracked by analytics platforms pulls directly from official play-by-play logs, which in the NFL context come from Next Gen Stats and Pro Football Reference.

This framework extends across sports. In the NBA, usage rate is formally defined as the percentage of team plays a player uses while on the floor — a metric Basketball-Reference calculates as (FGA + 0.44 × FTA + TOV) / (Team FGA + 0.44 × Team FTA + Team TOV) during the player's minutes.

How it works

Opportunity-based models follow a structured sequence:

1. Establish team-level volume — how many passing attempts, rush attempts, or plays is the offense projected to run? Vegas implied totals and pace-of-play metrics inform this layer (see Vegas lines and fantasy projections).
2. Distribute shares — what percentage of those opportunities belongs to each player? Target share, air yards share, and carry share data from recent weeks, adjusted for injuries and depth chart changes, determine individual allocations.
3. Apply efficiency rates — yards per carry, yards per target, catch rate, touchdown rate. These are regressed toward position baselines to avoid over-weighting small samples (a topic explored further in regression to mean in fantasy).
4. Convert to fantasy points — volume × efficiency × scoring format multipliers. PPR formats weight target share more heavily than non-PPR formats, since each reception carries a full point regardless of yardage.

The model at fantasyprojectionlab.com builds projections through this layered process, treating opportunity estimates as the structural foundation rather than an afterthought.

Common scenarios

Backfield committee splits are where carry-share analysis earns its keep. When two backs split 60/40 on a team projecting for 25 rushing attempts, the math is straightforward — but historical carry share from the prior four weeks often overstates future split stability. Injuries, game script, and red-zone role require separate treatment, because goal-line carries are disproportionately valuable and don't distribute the same way as first-down carries.

Target share volatility after injury is the receiver equivalent. When a team's No. 1 receiver misses a game, that player's historical 28% target share doesn't redistribute evenly to the depth chart. The injury adjustments in projections methodology tracks how target share actually migrates in comparable historical situations — and the answer is almost never uniform.

High-usage efficiency outliers are a third case. A running back posting 6.8 yards per carry over three weeks on 12 carries per game looks dominant, but that carry volume puts the sample at just 36 touches — sample size and projection reliability addresses why efficiency numbers stabilize at different thresholds for different stats.

Decision boundaries

Not every opportunity translates equally. Three distinctions matter most when applying usage-based projections:

• Air yards vs. target count: A receiver with 8 targets averaging 5 air yards each is running short routes and depending on volume. A receiver with 5 targets averaging 18 air yards is a downfield threat where variance is higher but ceiling is larger. Floor and ceiling projections capture this distinction explicitly.
• Snap rate vs. route participation: Total snaps include pass protection assignments and run-blocking packages. Route participation rate — percentage of dropbacks where the receiver ran a route — is the cleaner denominator for target share calculations, especially for tight ends who block heavily.
• Positional usage thresholds: Research tracked by Pro Football Focus and Football Outsiders suggests running back efficiency metrics stabilize around 50 carries, while receiving yards per target needs closer to 70 targets for stabilization. Projections built on smaller samples should carry wider confidence bands (see projection confidence intervals).

The scoring format amplifies all of this. A 30% target share in a PPR league generates different dollar-value implications than the identical share in a standard league — a topic scoring format impact on projections breaks down in detail.