This week
Cam is on the road against WSH. We project 44.9 rushing yards, 17.9 receiving yards on 3.1 targets. 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
Across 12 games, Cam has been on the field for 57% of his team's snaps. That's a rotational-to-starter share. It's the number most likely to move his projection week to week, because a swing of ten points of snap share moves everything downstream with it. The model weighs this above efficiency for a simple reason: snap share predicts next week better than last week's yardage does.
What kind of back he is
Cam has 169 carries for 645 yards (3.8 a carry) and 6 rushing touchdowns. He's also seen 41 targets for 274 yards — pass-game work is what separates a back who plays on third down from one who leaves the field, and it's worth more to a projection than the same yardage on the ground. Running-back yardage swings hard on the blocking in front of him, which is why the model weighs opportunity — carries and targets — above efficiency.
His last 5 games
Over that stretch Cam has 332 total yards. Five games is a small sample in any sport and a tiny one in football, where a team plays seventeen times a year — so recent form informs the projection without overriding the usage underneath it.
How the model reads him
Every projection here is built the same way for Cam as for a starter on a contender — simulate the game, then apportion it by role. No manual adjustments, no gut calls on who's due. The weighting behind it is proprietary and re-tuned on real outcomes; everything it produces is public and graded against the box score.
What we'd flag
Three things to carry. The season is seventeen games, so most trends here are small samples wearing a confident number. Game script rewrites usage — a team trailing throws, a team ahead runs. And injury news lands after we publish.