No projection this week
Storm 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
Across 11 games, Storm has been on the field for 58% 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 defensive back he is
Storm has 30 tackles across 11 games — 2.7 a game. Tackle volume is a strange stat for a defensive back: the best coverage players sometimes post the fewest, because nothing is thrown their way. A rising tackle count can mean he's playing well in run support or that receivers are catching the ball in front of him, and the box score can't tell you which.
His last 5 games
Over that stretch Storm has 15 tackles. 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 Storm 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.