How to Read Fantasy Rankings: Interpreting Tiers, ADP, and Projections

Fantasy rankings are the most referenced tool in the pre-draft process — and, paradoxically, one of the most misread. A raw numbered list, a tiered grid, an ADP figure, and a projection model can all point to the same player and still tell four different stories. Knowing what each layer of information actually measures — and where it stops being useful — is what separates a manager who picks confidently from one who freezes at pick 47.

Definition and Scope

At the most basic level, a fantasy ranking is an ordered list of players sorted by their projected contribution to a fantasy team over a defined period. That definition sounds simple until the variables multiply: projected for which scoring system? Which roster construction? Which week, or which full season? The fantasy rankings glossary breaks down the specific terminology, but the three primary data layers most ranking tools present are tiers, ADP, and projections — and they are not the same thing, even when they largely agree.

Tiers are groupings of players whose projected value is close enough that the order within the group matters less than the group itself. ADP (Average Draft Position) is an empirical measure — the average pick at which a player has been selected across a large sample of real drafts. Projections are forward-looking statistical estimates: expected rushing yards, receptions, home runs, or points scored. The three numbers surrounding any player's name may converge or diverge sharply, and that gap is often the most actionable information on the entire page.

How It Works

Rankings are typically generated through one of two processes: algorithmic projection models or expert consensus aggregation. The consensus rankings explained page covers the aggregation method in depth, but the essential mechanism is that raw statistical projections (expected yards, touchdowns, plate appearances) are converted into estimated fantasy points under a specific scoring system, then sorted.

Tiers overlay that sorted list with a visual or structural signal about cliffs — the points where the expected value drops meaningfully between one player and the next. A tier break after the third wide receiver in a PPR league, for example, signals that the fourth wide receiver available is statistically distinct from the top three, not just one slot lower. Tier-based drafting strategy treats those breaks as decision triggers rather than decoration.

ADP introduces a behavioral dimension. It reflects what real managers are doing in drafts, which frequently diverges from what projection models recommend. A player ranked 18th overall by a projection system but drafted 28th on average represents a rankings vs. ADP gap — a potential value window if the projection model is right, or a warning sign that the broader market sees a risk the model underweights.

Projections themselves come in two structural forms worth distinguishing:

1. Point projections — a single expected fantasy point total (e.g., 280 PPR points over a 17-week season), useful for direct player comparisons.
2. Range projections — a floor, median, and ceiling output, useful for identifying risk profiles. A player with a floor of 180 and ceiling of 420 carries materially different roster implications than one projected at 270 flat.

Common Scenarios

The most frequent situation where ranking misreads cause real damage is the positional anchor fallacy: treating a player's position within a tier as more meaningful than which tier they occupy. Picking the 4th-ranked running back when the 6th-ranked wide receiver is available — because the RB number looks better — ignores that both players may sit in the same tier, making the RB's apparent numerical advantage meaningless.

A second common scenario involves ADP-to-projection mismatches at the format level. ADP data is typically aggregated across draft formats, but PPR vs. standard rankings produce meaningfully different player valuations. A slot receiver's ADP in standard leagues may undervalue that player by 8 to 12 draft positions relative to their PPR-adjusted projection rank. Importing consensus ADP into a PPR league without adjusting is a structural error, not a judgment call.

The preseason vs. in-season rankings distinction matters here too. Projections built before Week 1 carry uncertainty ranges that compress as a season progresses and target share, snap counts, and injury data accumulate.

Decision Boundaries

Three specific conditions signal when ranking data should drive a draft pick and when it should be treated skeptically:

1. When tiers and projections agree but ADP diverges by more than 10 positions, the market is pricing something the model does not capture — an injury concern, a beat reporter note, a coaching scheme change. That delta deserves investigation before drafting, not blind trust in either signal.

2. When projections are nearly identical across 3 or more players at the same position, tier membership and ADP become the primary differentiators. The model has effectively declared those players equivalent; roster construction logic and positional scarcity should break the tie.

3. When a player's floor projection falls below league-average starter threshold, ceiling projections become misleading. A player who scores 38 fantasy points in an optimistic scenario but 90 points at their median is a useful bench asset. A player who scores 38 at their floor and 280 at their ceiling is a boom-or-bust gamble, not a reliable starter.

The full fantasy rankings methodology explains how projection confidence intervals are built, and the homepage provides orientation to the full analytical framework. Advanced metrics in fantasy rankings extends these concepts into efficiency-based inputs that projection models increasingly incorporate.

Reading rankings well is less about trusting the list and more about understanding what each number is actually measuring — and what it is quietly admitting it cannot know.