Fantasy Projections vs. Rankings: Understanding the Difference
Projections and rankings are the two most common outputs in fantasy sports analysis, and they're often treated as interchangeable — which is how managers end up making decisions on incomplete information. They measure different things, operate through different mechanisms, and answer different questions. Knowing which tool fits which decision separates disciplined roster management from gut-feel guessing dressed up as strategy.
Definition and scope
A projection is a quantified forecast: Patrick Mahomes throws for 287 yards and 2.4 touchdowns in a given week. It arrives as a number — or a range of numbers — that estimates a player's expected statistical output in a defined time frame. That number flows directly from a model that ingests inputs like target share, snap counts, opponent defensive rankings, weather, and Vegas implied totals. The projection models used in fantasy analysis weight those inputs differently depending on sport, position, and scoring format.
A ranking is a relative ordering. It answers the question "who is better than whom?" without specifying by how much. The difference matters enormously. Two wide receivers ranked 12th and 13th might have projected point totals of 14.2 and 14.1 — essentially a coin flip. Or the gap between ranks 5 and 6 might be 4 full points, a chasm large enough to alter lineup decisions in a GPP tournament. Rankings compress all of that variance into a single ordinal list.
The scope of each tool also differs. Projections are typically sport- and scoring-format-sensitive — a scoring format's impact on projections is substantial enough that a tight end might jump 8 ranks between standard and PPR formats while his raw yardage projection stays identical. Rankings can be consensus (averaged across multiple analysts) or model-driven, but they always describe a population of players relative to each other, not a player relative to his own expected output.
How it works
Projection systems start with historical data — per-game stat lines, usage rates, target distributions — and apply regression analysis or machine learning to estimate future performance. The output is a point estimate, sometimes accompanied by a confidence interval that reflects the model's uncertainty. Projection confidence intervals are often underreported in fantasy coverage, which understates how much randomness lives inside even a well-built forecast.
Rankings are derived from projections in one of two ways:
- Direct conversion — players are sorted by their projected point totals for a given week or season, producing a projection-based rank. The 1st-ranked player simply has the highest projected score.
- Analyst judgment overlays — a human analyst starts with projection-derived ranks and adjusts for factors the model underweights: injury trajectory not yet reflected in snap-count data, a contract year motivation signal, or a head coach's stated intent to feature a specific back in the red zone.
The second method is where rankings and projections diverge in practice. An analyst might rank a running back 8th overall despite a projection that places him 14th, because of a matchup or usage signal the model hasn't fully priced in. That delta — the spread between projection rank and consensus rank — is itself an analytical signal. Comparing projection systems side by side often reveals where consensus has drifted from model output and why.
Common scenarios
Draft preparation: Preseason rankings dominate draft boards, but applying projections to draft strategy reveals value gaps the ordinal list obscures. A running back ranked 22nd with a projected 195 total points is a better pick at pick 24 than a receiver ranked 18th with a projected 188 points — rankings alone would suggest otherwise.
Waiver wire decisions: Week-to-week projections drive waiver wire decisions because the relevant question is absolute output, not relative rank. If a handcuff running back is projected for 14.8 points in a given week because the starter is out, his ranking among all backs is secondary to whether 14.8 points fills a roster need.
Trade evaluation: Rankings create the negotiating language ("I'm trading a top-12 receiver for a top-8 tight end"), but trade value and projection data — specifically rest-of-season projected totals — determine whether that trade has positive expected value. The ranking is the shorthand; the projection is the math.
DFS lineup construction: In daily fantasy, lineup optimization with projections depends almost entirely on raw projection numbers and their associated ceilings, because tournament scoring rewards upside over average expected value. Rankings are nearly useless in this context — a player ranked 7th at his position with a high ceiling and a favorable matchup can be a better tournament play than the player ranked 1st with a capped upside.
Decision boundaries
The rule of thumb is cleaner than it might appear: use projections when the decision requires a quantity, use rankings when it requires a comparison.
Deciding between two quarterbacks for a start/sit decision? The projection numbers answer that directly — the player projected for 22.4 points starts over the one projected for 19.1, all else equal. Deciding where to draft a player relative to his positional peers? Rankings provide the navigational structure.
The failure mode worth watching is rank anchoring — treating a player's rank as meaningful when the underlying projection difference is within the model's margin of error. At the /index level of any fantasy analysis operation, the distinction between these two tools is foundational: projections quantify, rankings organize. Both are necessary. Neither is sufficient without the other.