No projection this week
Trey 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.
A specialist's page is a short one
Trey is a specialist, and this page reflects that honestly. Kicking and punting production depends almost entirely on how often his offense stalls in range — situations he doesn't control and a drive simulation prices better than any per-game average. What's below is the real record: the games he appeared in and what he did in them.
How the model reads him
Trey'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.