Game Script and Score Projections: How They Shape Start/Sit Outcomes
Game script — the predicted or unfolding narrative of how a football game's score differential will develop — is one of the most powerful and underappreciated forces in fantasy football start/sit decisions. Score projections set the stage before kickoff; game script rewrites the script in real time. Together, they determine which players touch the ball, how often, and in what situations — which means they determine fantasy outcomes more directly than almost any other variable.
Definition and Scope
Game script refers to the sequence of in-game situations that teams face based on the score at any given moment. A team leading by 17 points in the third quarter is running a different offense than one trailing by the same margin — and those two offenses produce wildly different fantasy outputs from the same roster.
Score projections, closely related, are the pregame implied totals set by oddsmakers that estimate how many points each team is expected to score. These figures, published by sportsbooks and aggregated at resources like the Las Vegas Totals at Action Network and ESPN's Vegas Lines, encode collective market knowledge about team strength, matchup, weather, and injury status. A team with an implied score above 27 points is operating in meaningfully different fantasy territory than one implied at 18.
The scope of this concept touches every position. It shapes RB usage, pass volume, WR target distribution, TE involvement, and even the relevance of the DST start/sit strategy. No position is immune to its influence, though the effects differ by role in ways that matter for lineup construction.
How It Works
The mechanism is straightforward: offensive play-calling adjusts to score differential, and those adjustments create predictable patterns in fantasy-relevant statistics.
When a team is trailing, the offense shifts toward passing — because the clock becomes an enemy that only incomplete passes can stop. Pass attempts per game spike, as do air yards, targets to boundary receivers, and overall volume for pass-catchers. Running backs in trailing offenses often see their rushing attempts collapse by 30–40% in the second half compared to their projected workload (a pattern documented in Pro Football Reference game logs across back-to-back seasons).
When a team is leading, the inverse takes hold. The run game dominates. Ball-carriers accumulate carries, and touches lean toward short, time-consuming routes over downfield shots. The lead-protecting team's top RB becomes a near-certain candidate for high-volume work, while that same team's WR1 may spend critical fourth-quarter snaps standing on the sideline.
Score projections create pregame expectations. A game with a total of 48 or higher is categorized in the industry as a "shootout game," and these games statistically produce more passing yards and more fantasy points at the skill positions — particularly WR and TE — than games with totals below 40. The Vegas Lines and Game Totals page covers how to extract these numbers from sportsbook data and apply them to lineup decisions.
Common Scenarios
Four situations come up repeatedly in real lineup decisions:
-
Heavy favorite with a blowout script — A team favored by 10+ points is projected to lead for most of the game. The lead-back benefits from volume; WRs on that team may see fewer targets as the offense shifts to run-heavy play-calling. On the opposing team, the trailing offense typically becomes a passing machine, elevating WRs and pass-catching backs in PPR formats.
-
High-total shootout — Both teams are expected to score freely. This scenario benefits pass-catchers on both rosters. WRs and TEs see elevated target floors because neither team will be content to drain the clock — scores are too close and climbing too fast.
-
Low-total grinder — Totals below 40 signal bad weather, strong defensive matchups, or slow offensive pace. Running backs gain relative value; boom-week targets for WRs become less likely. This is where weather impact on start/sit and game totals converge into one suppressed-scoring environment.
-
In-game script reversal — A team favored by 7 that falls behind by 14 at halftime has just become the trailing team regardless of pregame projections. Real-time scoring changes the math entirely, and daily fantasy players adjust lineups accordingly (daily fantasy start/sit strategy accounts for this in a way redraft leagues cannot).
Decision Boundaries
The practical line between "start" and "sit" based on game script comes down to position and projected role within the offense.
Running backs represent the starkest binary: a lead-back on a heavy favorite in a low-total game is among the highest-floor starts in fantasy. That same player, in a game where his team projects to trail for three quarters, becomes a risk — not because of talent, but because of situation. A backup or pass-catching back on the trailing team can leapfrog a consensus RB1 in value for a given week.
Wide receivers and tight ends tilt toward high-total games and trailing-team scripts. Deploying WRs into low-total games against elite defenses, expecting full target volume, is one of the most common start/sit mistakes in fantasy.
The comparison that crystallizes the concept: the same WR2 in a 52-point projected total is a different player than in a 37-point total — same ability, same matchup on paper, different expected touches. Game script and score projections are the difference between those two numbers, and between a week-winning lineup and a frustrating near-miss.
For a fuller look at how these projections fit alongside snap counts, target share, and injury reports inside a structured decision process, the start/sit decision framework synthesizes all these inputs into a repeatable weekly approach. The home page also connects these topics across the full landscape of start/sit analysis.