Fantasy Projections: How to Use Them and Their Limits

By 4Football Staff · October 30, 2026 · 10 min read

A projection is an educated average, not a prediction of what will happen. Learn how projections are built, how to read ranges, and how to use them without leaning on them too hard.

You open your lineup on Sunday morning and see two numbers next to your flex options: 13.4 and 12.9. The first player is projected for half a point more. Surely that settles it?

It almost never does. A fantasy projection is a useful tool and a frequently misread one. The number does not say what will happen. It says roughly what would happen on average if the same game were played many times under the same conditions. In any single game, the player will almost certainly not score 13.4 points. He might score 4 or 31, and the half-point difference between two players is smaller than the noise in either one.

This guide explains what a projection is, how one is built, why even good ones miss, and how to use them in drafts, lineups, and trades while keeping their limits in mind. It describes how projections work in general rather than recommending any particular source.

What a projection actually is

A fantasy projection is an estimate of a player's statistics for a game or a season, converted into fantasy points using a scoring system. A weekly projection for a receiver might include expected receptions, receiving yards, and touchdowns. Multiply each by the league's scoring values, add them up, and you have a point total.

Two things are worth noticing.

First, the number is a central estimate, a kind of average of the many outcomes that could happen. Football produces a wide range of outcomes: a receiver might catch two passes or ten, and touchdowns are rare events that arrive unpredictably.

Second, the projection depends on the scoring settings. A projection built for a league that awards a point per reception will differ from one built for standard scoring. Always check which settings a projection used. If a source does not say, assume it follows a common default and adjust.

How projections are built

Different services use different methods, and most do not publish the details. The general structure, however, is similar.

1. Start with the team. Analysts estimate how many plays a team will run and how it will split between passing and rushing. A fast-paced offense that likes to throw has more opportunities to give its players than a slow, run-heavy one.
2. Divide the opportunity. Within the team's totals, estimate each player's share of carries, targets, and snaps. This step depends heavily on the depth chart and on injuries.
3. Apply efficiency. Estimate how productive each player will be per carry or per target, using past performance, the opponent, and the player's skill.
4. Estimate touchdowns. Touchdowns are the hardest event to predict, because they are rare and depend on the offense's chances near the goal line. Many projections use a player's share of red zone opportunities and a typical conversion rate. That is the shakiest step in the chain, because a team's goal-line chances vary a great deal from game to game.
5. Convert to points. Apply the scoring system.
6. Adjust for context. Matchup, weather, game environment, and injuries refine the estimate. The odds page lists the market's point spreads and totals, which many analysts treat as a sign of how a game is expected to unfold.

Some sources are built by individual analysts, some by statistical models, and some by combining many projections into a consensus. Each approach has strengths. An analyst can account for a news item that a model has not seen yet. A model can apply the same method to every player without fatigue. A consensus smooths out the quirks of any single source.

The range behind the number

The single number hides a spread. Think of a projection as the center of a range of possible outcomes.

Imagine two hypothetical receivers, each projected for 14 points.

They share a projection but not a profile. A produces something close to 14 most weeks. B has games of 3 and games of 28, and the average comes out to the same place. Which one should you start depends on what you need. If you are a heavy favorite and want a safe score, A is the better choice. If you are an underdog and need a big week to win, B's chance of a huge game is worth more. Some sources publish a floor (a poor but realistic outcome) and a ceiling (a good one) alongside the projection. When you can find them, they add valuable context.

In best ball formats, where only the high scores count, this idea becomes central. Our guide to best ball explains why.

Why projections miss

Even excellent projections miss often. That is not a sign of poor work; it is a consequence of the sport.

Football is high variance

A single game has few plays, a handful of which decide a player's day. One long touchdown can double a receiver's total. One fumble can end a drive that would have produced a score. Because individual outcomes depend on a small number of events, even a perfect forecast of averages cannot predict a single week.

Injuries change everything

An injury to the player himself, a teammate, or the quarterback changes the opportunity for everyone nearby. A projection made on Tuesday may be outdated by Sunday. Check the injury report before every lineup deadline, and note when a projection was last updated.

Role is uncertain

The biggest hidden assumption in any projection is the player's role. A running back who shares carries may be projected for 12 touches, but the coach could give him 20 or 5. A new starter's role has no history. Even for established players, a coach can change his approach from week to week.

Touchdowns are noisy

As noted above, touchdowns are hard to predict. A player with a projected touchdown total of 0.5 will score either zero or one, and the points that follow are large. Projections smooth touchdowns into fractions, which never occur in real games.

Projections can be optimistic

When many players on a team are projected independently, their totals can add up to more than the offense is realistically likely to produce. Each player gets credit for a favorable share of the team's plays, and the shares overlap. If you see projections that give a team's players more yards or touchdowns than the team could plausibly generate, treat them with caution. A quick check is to add up the passing, rushing, and receiving projections for one team and ask whether the total looks realistic.

No source is magic

No service has solved the problem of predicting football. Their methods differ, and no single source is consistently best across all players and weeks. Use projections as one input among several, not as an oracle.

How to use projections well

Compare, do not worship

The most useful way to read projections is relative. The difference between a player projected at 22 and one projected at 10 is meaningful. The difference between 13.4 and 12.9 is not. Treat close projections as ties and use other information to break them.

Look at several sources

When sources agree, you can have a little more confidence. When they disagree sharply, something interesting is happening: perhaps a disputed role, a recent injury, or a different view of the matchup. A big disagreement tells you to investigate before deciding. Check news and depth charts to see which source seems to be better informed.

Use ranges and context for ties

When two players are close, ask these questions:

1. Which one has the more secure role?
2. Which one has the better matchup? Our guide to matchup analysis explains how to judge it.
3. Do you need a safe result or a big one?
4. Are there injury concerns for either player or his quarterback?
5. When does each player's game start, and will you know more by then?

Our start/sit framework puts these steps in order.

Treat preseason projections as a starting point

Season-long projections made before the first game rest on assumptions about roles, health, and performance, and many of those assumptions will fail. A projection for a rookie or a player changing teams has even less to go on. Use them for draft preparation, and expect to update your view as the season reveals who is actually doing what.

Update as information arrives

The best projection is the one that includes the latest news. If a starter is ruled out on Saturday, a backup's projection should rise. If a game is expected to have heavy wind, a passing offense may be adjusted downward. Check that the projection you rely on is current, and look for a time stamp.

Match the projection to your format

Standard, half-point, and full-point reception leagues all rank players differently, and so do leagues with extra points for long plays, tight end premiums, or quarterback bonuses. If a projection does not match your format, adjust, or find one that does. The same player can move several spots depending on how the league scores receptions.

Projections in drafts and trades

Weekly projections get most of the attention, but season-long projections matter in drafts and trades too.

In a draft

A season projection adds up expected weekly output across the schedule, and it is usually converted into a rank. Managers use these ranks to build a draft board. The key is to remember that the numbers rest on the assumptions listed above. A running back projected for a heavy workload is projected that way because analysts expect him to be the lead back. If he is hurt in the second week, or the coach changes course, the projection becomes irrelevant.

A practical response is to group players into tiers instead of treating every rank as exact. If five players are projected within a point or two of each other per game, they are effectively one tier, and the choice among them can come down to risk, age, or injury history. You will rarely be wrong to pick any of them, and you may be wrong to agonize.

In a trade

When you evaluate a trade, season projections can show what a player is expected to provide over the remaining weeks. But "rest of season" projections shift quickly with injuries and role changes. Before accepting a deal, check how the projection treats the player's remaining schedule, whether bye weeks are included, and whether his role has recently changed. A projection built before a teammate's injury may understate a player's value, and one built before a player's own injury may overstate it.

A hypothetical comparison

Say you are choosing between two flex options on a Sunday morning. Player X is projected for 13.4 points and Player Y for 12.9. A check of the surrounding information shows that Player X plays in the late game, faces a strong defense, and shares snaps with a returning teammate. Player Y plays early, has a secure role, and his team is expected to throw more than usual. The half-point gap in the projections is smaller than any of these considerations. Most managers who weigh the context carefully would start Y, or at least regard the choice as a toss-up. The projection did its job by narrowing the field to two players, and the other information made the choice. That division of labor is the right one.

Common misreadings

• "He is projected for 18, so I expect 18." The number is an average. His result is likely to be well above or below it.
• "This source was wrong last week, so it is useless." A single miss tells you almost nothing. Projections should be judged over many cases.
• "The highest projection wins." A tiny edge may be inside the margin of error.
• "A projection is a recommendation." It measures expected points, not whether a player is right for your situation.
• "Season-long projections tell me who to trade for." They can help, but a trade also depends on your needs and your opponent's.
• "I should never go against the projection." Sometimes you have good reasons, such as a fresh injury report or a strong matchup. Projections are advice, not rules.

Building your own sense of the numbers

You do not need to build a model to think like a projector. A few questions from the process above can help you judge any projection.

• What is the player's role, in snaps, carries, and targets?
• How many opportunities does his team create?
• Is the matchup good or bad?
• How much of the number depends on a touchdown?
• What would make the projection wrong?

If you can answer these, you can tell when a projection looks reasonable and when it does not. For an extra dimension, look at efficiency measures such as fantasy points per snap, which help show whether a role is converting to production. Look up player details on our players page and see the fantasy page for more resources.

The short version

• A projection is an average expected outcome, not a forecast of what will happen in one game.
• It is built from team plays, player shares, efficiency, touchdown estimates, and your scoring settings.
• The range around the number (floor and ceiling) matters as much as the number itself.
• Football's variance, injuries, uncertain roles and rare touchdowns make misses normal.
• Compare projections relatively, use several sources, and treat close numbers as ties.
• Update for news before every deadline, and match the projection to your league's format.
• Use projections as one input alongside role, matchup and your own judgment.