Fantasy Football Running Back Projections: Backfield Share and Volume
Running back projections live and die on one question: who is actually getting the ball? Backfield share and volume metrics answer that question with more precision than almost any other input in the projection process. This page breaks down how those metrics are defined, how projection models use them to build point estimates, and where the method gets complicated — which it does, frequently and in ways that matter for lineup decisions.
Definition and scope
Backfield share is the proportion of a team's running back touches — carries plus receptions — that a single player accounts for across a defined sample. Volume is the raw count of those opportunities: rushing attempts, targets, and their product in expected points and yards. The two concepts are related but distinct. A running back with a 70% backfield share on a run-heavy team might see 22 carries and 4 targets per game. The same share rate on a pass-heavy team might yield 14 carries and 6 targets — similar share, meaningfully different volume and fantasy value depending on scoring format.
The practical scope of these metrics extends across standard, PPR, and half-PPR formats, each of which weights receptions differently. In full PPR formats, a back receiving 6 targets per game at a 75% catch rate is projecting for roughly 4.5 receptions — worth 4.5 additional points before yardage. That delta is large enough to separate a mid-round asset from a must-start. Scoring format impact on projections covers how those format adjustments cascade through the full projection model.
How it works
Projection systems build backfield share estimates by layering three inputs:
- Historical snap and touch distribution — the baseline touch rate from prior weeks, adjusted for sample size reliability. A back with 4 games of data carries more uncertainty than one with 12. Sample size and projection reliability addresses why early-season numbers warrant wider confidence intervals.
- Team pace and play-count context — a team running 68 plays per game creates more total opportunities than one running 61. The Vegas lines and fantasy projections page explains how implied totals feed into pace and opportunity estimates.
- Game script probability — teams leading by 10 points rush more; teams trailing by 10 pass more. This affects not just the number of carries but whether a committee back's lead-back role is likely to hold through four quarters.
These inputs combine to produce a projected touch total, which is then multiplied by per-touch efficiency assumptions — yards per carry, yards per target, touchdown rate — to generate a final point estimate. The running-back projection methodology page walks through the specific model structure in more detail.
Common scenarios
Three backfield configurations produce the most variation in projection outcomes:
True workhorse — one back with 55%+ snap share and 18+ expected touches per game. These projections are the most stable because they're least sensitive to game-script volatility or committee rotation decisions. Derrick Henry's 2020 season — 378 carries, 2,027 rushing yards — is the canonical example of what a high-volume projection looks like when it hits.
Two-back committee — two running backs splitting carries roughly evenly, often with a role-based split (early-down vs. third-down, or inside runner vs. receiving back). These projections require an assumption about which back captures which touches, and that assumption has a higher error rate. A 55/45 split can shift to 65/35 in a single game without a formal depth chart change.
Handcuff situation — a clear starter with a backup who projects as irrelevant unless the starter is injured. The starter carries a high expected-value projection; the handcuff carries a low base projection with an outsized floor-to-ceiling range depending on injury probability. Floor and ceiling projections covers how models represent that asymmetric variance.
Decision boundaries
The point at which backfield share data changes a roster decision is not arbitrary — it has a threshold logic. A running back crossing from 45% to 55% snap share mid-season crosses a meaningful boundary: below 50%, he is plausibly in a committee; above 55%, he is plausibly the lead back. The projection adjusts not linearly but in step-changes because role definitions shift.
For waiver wire decisions specifically, using projections for waiver wire decisions describes how share data interacts with rest-of-season value. A back who just recorded a 63% snap share in Week 6 but played behind someone else for Weeks 1–5 requires a judgment call: treat the recent game as signal of a role change, or treat the full-season data as the more reliable baseline?
The answer depends on context — injury to the incumbent, coaching statement, or observable game-plan shift — which is why usage rate adjustments in projections exists as a dedicated topic. Volume projections at the running back position are less about raw talent than about organizational decisions that can change with a single press conference.
For a grounding overview of how all these individual metrics fit into a complete projection framework, the Fantasy Projection Lab home is the right starting point before going deeper into position-specific methodology.