FanIQ

The Draft Desk

Volume Is King. For Running Backs.

The most repeated rule in fantasy football is true, decisively, at exactly one position. At receiver it points the other way, and almost nobody says so.

"Volume is king" is the closest thing fantasy football has to a commandment. Chase touches, not talent. Opportunity over efficiency. It gets repeated in every draft guide, and it is genuinely one of the more useful things anyone tells a new player.

It is also, on the evidence, a running back rule that got promoted to a universal law somewhere along the way.

What first-half production predicts about rest-of-season PPR points per game

PositionPlayer-seasonsVolume (touches/gm)Efficiency (yards/touch)
Running back1,202r = 0.537r = 0.235
Wide receiver261r = 0.086r = 0.279
Tight end32r = 0.115r = 0.316

Correlation with points per game from week 9 onward. Higher is more predictive.

For running backs it is not close. How often a back touched the ball in the first half of a season predicts his rest-of-season scoring more than twice as well as how many yards he averaged when he did. If you know a back is getting eighteen touches a game, you know most of what matters. Whether he is averaging 4.1 or 4.8 yards a pop is a detail.

For receivers the ordering reverses. Efficiency carries more predictive weight than raw target volume, and volume on its own barely predicts anything at all.

Same league, same seasons, same method. At one position volume wins 0.537 to 0.235. At the next it loses 0.086 to 0.279.

Why the positions behave differently

The second table explains most of it.

How stable each trait is from the first half of a season to the second

PositionVolume stabilityEfficiency stability
Running backr = 0.694r = 0.429
Wide receiverr = 0.279r = 0.504
Tight endr = 0.294r = 0.540

Tight end sample is small (32 seasons clear the touch threshold) and should be read as suggestive only.

A running back's workload is a decision a coaching staff makes and then keeps making. It is announced weekly, it changes slowly, and it is the most stable thing about him. His efficiency, meanwhile, swings on blocking, box counts, and a few broken tackles a month. So the stable input is volume, and the stable input is the one that predicts.

A receiver's target count is much noisier, because it depends on coverage, game script, and what a quarterback decides in three seconds. But his yards per target is comparatively steady, because it encodes something closer to actual ability: separation, catch radius, what he does after the catch, and the role he occupies in the route tree. The stable input at receiver is efficiency, and again the stable input is the one that predicts.

Stated generally, the rule is not "volume beats efficiency." It is "whichever trait is more stable at a position is the one worth projecting." At running back that happens to be volume, which is where the commandment came from.

The caveat, stated plainly

The receiver sample here is 261 player-seasons against 1,202 for backs, and that gap is not an accident. Requiring 40 touches in the first half of a season is easy for a starting running back and hard for a receiver, since receivers accumulate touches only through catches. So this receiver group is already filtered down to high-volume, established starters.

That filtering matters, and it cuts against the finding: restricting the sample to receivers who all catch a lot of passes compresses the range of volume, and compressed range mechanically depresses a correlation. Some of the weak 0.086 is that artifact rather than a fact about football. The reading is that volume matters less at receiver than the conventional wisdom implies, not that it is irrelevant. If you are choosing between two receivers with genuinely different target loads, the target load still counts.

We are showing you the caveat because the alternative is quoting a number we know is flattering. The direction of the effect is solid and reproduces across eras. The exact magnitude at receiver is not.

Why pooling the positions gives the wrong answer

One methodological note, because it is the trap that catches everyone including us on the first pass. If you run this correlation across all skill players at once, efficiency appears to beat volume everywhere. That result is an illusion: running backs average around four yards a touch and receivers around eleven, so "yards per touch" across a mixed pool is mostly just measuring which position a player plays. Split by position and the confound disappears and the real pattern shows up. Any analysis of this question that does not separate the positions is reporting an artifact.

How to draft with it

For backs, buy the job. A projected workhorse on a mediocre offense will usually beat a committee back in a great one, and the efficiency arguments people make in August are largely noise. For receivers, buy the player. Target share matters, but the receiver who is genuinely better at getting open and finishing plays holds his value through the role changes that wreck volume-based projections.

The laws behind this

Each one is a single claim, checked season by season against the same record this piece runs on.

Related reading

FanIQ runs this kind of query against the full play-by-play record for any player, team, or coach you ask about, in plain English.

Get FanIQ free
How we got this1,495 player-seasons from 1999 through 2025 in which a running back, receiver, or tight end recorded at least 40 touches in each half of the season and played at least four games in each half. Correlations are computed separately within each position, because pooling them produces a badly confounded answer (see the note at the end). Touches are carries plus receptions.

One law a week, in your inbox

A single rule from the library with the seasons behind it. Nothing else.