Average draft position is a price tag, not a scouting report. It tells you what the room is charging. A projection tells you what a model expects. The useful part is the disagreement, but only when both sides are tied to real rows. This dated module does not declare an ADP snapshot source, so it will not freeze player names, round labels, or model deltas in prose and pretend they are still current. The live fantasy rankings and draft kit are where the current board belongs.
Price and rank answer different questions
A ranking asks who projects better. ADP asks who the room is taking first. Those are cousins, not twins. A useful value tier groups players whose expected role looks similar, then compares the cost of entering that group. The cheap end of a tier is interesting. The expensive end needs a reason. The player can be excellent and still be a bad purchase when the room has already charged for every pleasant outcome.
That is the whole discipline. Do not turn a small rank difference into a sermon. First ask whether the projection is driven by stable work: routes, targets, carries, snaps, and a role the player can keep. Then ask whether ADP is reacting to the same evidence or merely repeating a familiar name. Our model-versus-consensus guide covers that audit in more detail.
What the stored player-week charts can show
The chart below reads the configured weekly player stats fields for targets and PPR output. It can show how production spreads across different volumes. It cannot, by itself, prove that a current draft slot is cheap or expensive because this module does not attach a current ADP row to the chart. Treat it as context for why role matters, not as a receipt for a live draft recommendation.
The second chart reads stored receiving-yard peaks from the same player-week dataset. Peaks explain why draft rooms fall in love. They do not establish a repeatable baseline. A highlight can move a player up a board faster than a quiet role change, which is exactly why value work starts with workload and ends with price.
Build tiers before the room starts moving
Start with your scoring format and sort players by projected role. Put close profiles together instead of forcing a fake gap between adjacent names. Then mark the first player in each group whose market price is meaningfully cheaper than the rest. That is the spot where patience earns something. If every player in the group costs roughly the same, there is no edge to celebrate. Pick the fit you prefer and move on.
Keep a separate note for fragile projections. A back who needs every goal-line touch, a receiver who needs unsustainably perfect deep balls, or a quarterback whose value rests on a role that has not been confirmed should not share a tier with a player whose workload is already visible. The exact labels matter less than the distinction between bankable opportunity and a story that still needs proof.
How to act when the model and market split
- Read the cause before the gap. A difference driven by role deserves more attention than one driven by a thin efficiency input.
- Check the timestamp. Draft markets move quickly. A stale ADP snapshot can manufacture an edge that no longer exists.
- Respect the tier. Reaching within a group is a preference. Reaching past a comparable group is paying extra for a name.
- Leave room to be wrong. A projection is an estimate, not a hall pass to ignore camp news, injuries, or league settings.
The practical win is not finding a magic sleeper. It is refusing to pay premium prices for ordinary uncertainty. Use the live board for the current numbers, the ADP value-tier framework for the structure, and your league settings for the final call. A clean draft sheet should make overpayment feel obvious before the clock starts yelling at you.
