This week
Zach is on the road against LV. We project 2.1 tackles, 0.3 sacks. 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
74% — that's Zach's average snap share over 20 games. 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. This is the number to check first on any football page. Everything else here is downstream of it.
What kind of defensive lineman he is
Zach has 8 sacks and 40 tackles across 20 games. Sacks are the stat everyone quotes and the least stable one on this page — they arrive in bunches, they depend on coverage holding up behind him, and a lineman can win every rep for a month without one. Snap count and pressure rate describe a pass rusher far better than a sack total does, which is why his projection moves less on a big game than you'd expect.
His last 5 games
Over that stretch Zach has 12 tackles and 4.5 sacks. 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
Zach'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.