Projections vs. Rankings: Understanding the Difference in Fantasy
Projections and rankings are the two most fundamental outputs in fantasy sports analysis, and they are not the same thing — even though platforms frequently present them side by side as if they were interchangeable. One is a numerical forecast; the other is a prioritized order. Confusing them is one of the most quietly costly mistakes a fantasy manager can make, especially during draft season when every pick compounds on the previous one.
Definition and Scope
A projection is a point estimate — a specific predicted output for a player over a game, week, or season. A running back might be projected for 78 rushing yards, 2 receptions, and 0.7 touchdowns in a given week. Multiply those by the relevant scoring multipliers and the result is a projected fantasy point total — something like 14.3 points in a standard PPR format.
A ranking is a relative ordering of players — usually within a position, sometimes across positions. It answers a different question entirely: not "how much will this player score?" but "who is more valuable than whom?" Rankings are downstream of projections but are not identical to them. Two analysts can share nearly identical projections and still disagree sharply on rankings, because rankings also incorporate risk, positional scarcity, roster construction context, and the specific scoring settings of a given league.
This distinction matters most in draft strategy, where managers often anchor too hard on projected point totals without accounting for the uncertainty baked into those numbers.
How It Works
Projections are built from underlying statistical inputs — historical performance, snap counts, target share, strength of schedule, and increasingly, machine learning models trained on play-level data. Platforms like FantasyPros and The Athletic aggregate projections from dozens of analysts and publish consensus numbers. The consensus approach reduces individual analyst bias, though it also tends to regress toward the mean and underestimate breakout or bust scenarios.
Rankings translate those projections into decision-relevant order through a structured process:
- Generate base projections — assign expected statistical lines to each player across a full season or specific week.
- Apply scoring settings — convert statistical projections into fantasy point totals using league-specific multipliers (PPR adds 1 point per reception, for example, which meaningfully re-orders receivers relative to non-PPR formats).
- Adjust for positional scarcity — a tight end projected for 120 fantasy points ranks higher than a wide receiver projected for the same total if elite tight end production is rare and the drop-off to the next tier is steep. This concept is formalized as value over replacement player, or VORP.
- Layer in variance and risk — a player with high injury history or uncertain role may project for 180 points but rank lower than a player projecting 165 points with a stable workload. Bust risk assessment is embedded in the ranking, not the projection.
- Account for positional context — quarterback rankings in a standard 1-QB league look dramatically different from rankings in a superflex format, even if the underlying projections are identical.
Common Scenarios
Draft Day: A wide receiver ranks 12th overall but is projected for only 220 fantasy points, while a running back ranks 14th but projects for 240 points. The rankings are not wrong — they account for the fact that finding 220-point wideouts in rounds 5 through 8 is feasible, while finding 240-point running backs after round 4 is substantially harder. Drafting by raw projection here produces a suboptimal roster.
Start/Sit Decisions: Start/sit decisions are almost purely projection-driven. The relevant question in any given week is "who scores more?" — not "who is more valuable in the abstract?" A WR3 projected for 14 points should start over a WR1 projected for 9 points, regardless of their seasonal rankings. Mixing the tools here is a classic mistake.
Waiver Wire: Waiver wire strategy blends both. A handcuff running back may project for only 8 points this week but rank as the most important available pickup because of long-term positional value if the starter goes down.
Decision Boundaries
The clearest rule is to match the tool to the time horizon. Projections govern in-season, week-by-week decisions where the goal is point maximization in a discrete matchup. Rankings govern drafts and long-term roster construction, where relative value and opportunity cost determine outcomes.
A practical framework for choosing between them:
- Single-week decisions → use projections, adjusted for matchup quality using matchup analysis strategy
- Draft pick decisions → use rankings, adjusted for league scoring via scoring system analysis
- Trade evaluation → use both: projections estimate what a player will contribute this season; rankings establish what that player costs to replace
- Waiver priority decisions → use rankings for long-term roster shape, projections for immediate streaming needs via streaming strategies
The broader fantasy analytics tools landscape has made both projections and rankings more accessible and more granular than they were a decade ago. The tradeoff is that the volume of data can obscure the fundamental question: which tool answers the decision actually on the table? Getting that mapping right — projection for point maximization, ranking for relative value — is what separates managers who treat fantasy as informed decision-making from those who just sort by the first column they see.
The full strategic framework that connects these tools to draft and in-season decisions is laid out on the fantasy strategy guide homepage.