This week
Baker is on the road against CIN. We project 271.9 passing yards, 27.4 rushing yards. The number comes out of a drive-level simulation of the game rather than a season average — it asks how many possessions his side is likely to get, what they do with them, and how much of that flows through him.
How much he's on the field
97% — that's Baker's average snap share over 20 games. That's a full-time role. Snap share at this level is the most stable input we have — it changes slowly, and it survives a bad game in a way that yardage never does. This is the number to check first on any football page. Everything else here is downstream of it.
What kind of quarterback he is
Baker has completed 406 of 625 (65%) for 4458 yards, 35 touchdowns and 12 interceptions — 7.1 yards an attempt. He's also run for 475 yards, which matters more than it looks: rushing production is the most reliable floor a quarterback has, because it doesn't depend on anyone catching anything. Yards per attempt is the number to watch: completion percentage rewards checkdowns, and a quarterback can complete 70% of his passes without ever threatening anybody.
His last 5 games
Over that stretch Baker has 1232 total yards. A handful of games is thin evidence in a seventeen-game season. It nudges the projection; it doesn't drive it.
How the model reads him
Baker's projection starts with the game, not with him. We simulate the matchup drive by drive — how many possessions each side gets, how far they travel, how often they score — and then ask what share of that flows through him given his role. That ordering matters: a productive player on a team that runs 55 plays a game has a lower ceiling than a lesser one on a team that runs 70.
What we'd flag
Read this knowing the limits. A seventeen-game season makes every rate noisy; game script can invert a player's usage inside one afternoon; and depth-chart changes often surface too late to be in the projection.