No projection this week
Philip doesn't have a projection right now — either his team is on a bye, the week's slate hasn't been simulated yet, or he isn't in a position to draw usage. His game log and the usage read below are the real record either way, and this page picks him back up as soon as there's a game to simulate.
How much he's on the field
Philip has averaged 97% of his team's snaps across 3 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. Opportunity is the first thing the model reads and the last thing it gives up on — production without snaps is noise, and snaps without production usually corrects.
What kind of quarterback he is
Philip has completed 58 of 92 (63%) for 544 yards, 4 touchdowns and 3 interceptions — 5.9 yards an attempt. 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 3 games
Over that stretch Philip has 543 total yards. In a sport with seventeen games, a five-game window is closer to an anecdote than a trend — which is why usage, not this, anchors the number.
How the model reads him
The number on Philip is a share of a simulated game. First the matchup: possessions, field position, how each offense is likely to move. Then his slice of it, set by usage rather than by reputation. How those pieces are weighted is ours and gets re-tuned against results; the output is published and graded, which is the half you can check.
What we'd flag
Football's sample sizes are brutal — seventeen games a season means a "trend" is often four data points. Injuries and game script move usage more than talent does week to week, and a blowout can erase a starter's second half. For Philip specifically, Philip has only 3 games in our log, so every rate on this page is fragile.
