Route Participation: The Stat Between Snaps and Targets

Route participation is the percentage of his team’s dropbacks on which a player ran a pass route: routes run ÷ team dropbacks. If an offense drops back 38 times and a tight end runs 19 routes, his route participation is 50% — regardless of how many snaps he played.

It is the stat that sits between snap share and target share, and it is the one that catches the errors the other two make. A player cannot be targeted on a play where he was not running a route, so route participation is the real denominator for everything a pass-catcher does.

The usage funnel

Usage analysis is a funnel with four stages. Each one narrows the one before it, each one is controlled by someone different, and each one gets noisier as you move right.

The discipline is to work left to right and never skip a stage. Almost every bad usage read comes from jumping from stage one to stage four — seeing a big snap count and a bad box score and concluding a player is being wasted, when in fact he never ran a route.

Snap share is the widest filter and the most available. Route participation is the first one that costs you something to get, and the first one that is genuinely diagnostic for pass-catchers.

Why it matters most for tight ends and slot receivers

Wide receivers split out wide are running a route on nearly every dropback by default — there is not much else for them to do. Their snap share and route participation track each other closely, and checking both is mostly redundant.

Tight ends are the opposite. The position is two jobs wearing one number. An in-line tight end is a sixth offensive lineman on run plays and a pass protector on a meaningful share of dropbacks. He accumulates snaps at a rate that looks like a full-time starter because he is a full-time starter — at a job that produces no fantasy points.

Rotational and slot receivers have a milder version of the same problem. A slot receiver who only plays in three-wide personnel might post a 55% snap share that is nearly all passing downs, in which case his route participation will be far higher than his snap share and he is more valuable than he looks. The distortion runs both ways, which is what makes it worth measuring rather than guessing.

Running backs get the same treatment from the other direction. A back at 60% snaps who runs a route on 15% of dropbacks is an early-down runner with no receiving floor. A back at 40% snaps who runs a route on 55% of dropbacks is a passing-down specialist and a much better play in PPR formats. Neither of those facts is visible in the snap count, which is one reason backfield committees are so hard to read from box scores.

Phantom snap counts

A phantom snap count is a snap share that describes presence rather than participation. The three common versions:

• The blocking tight end. 85–90% snap share, 40–50% route participation. He is on the field because the offense runs heavy personnel, and his routes are mostly play-action leak-outs and check-downs.
• The decoy receiver. A quality blocker on the perimeter who plays every snap in an offense that runs a lot. His routes are there, but his target rate on them is tiny because the scheme uses him to occupy a safety.
• The two-minute-only back. A back whose share is inflated by hurry-up drives at the end of halves — a lot of snaps, all in situations that will not repeat at that rate.

Targets per route run

TPRR — targets per route run — is targets ÷ routes run. It answers a narrower and more useful question than target share: when this player runs a route, how often does the quarterback throw to him?

Target share is contaminated by playing time. A receiver can post a low target share simply because he was on the field for 60% of dropbacks, which is a coaching decision, not a statement about how the offense sees him. TPRR strips that out.

These are heuristics in common use, not fixed lines:

Yards per route run is the same idea applied to production: receiving yards ÷ routes run. It blends role and efficiency into one number and is the standard way to compare receivers across wildly different snap counts. Use TPRR to ask about opportunity and YPRR to ask about what he did with it.

The pairing that matters is TPRR against route volume. High TPRR on few routes is a player who would be productive if given the field — a genuine breakout candidate if the role opens. Low TPRR on many routes is a player who is on the field for reasons that have nothing to do with the passing game, and his snap count will keep flattering him all season.

Where the data comes from

Being honest about this matters. Snaps and targets are counted from the official record of each game. Routes are not. Route participation is produced by charting services whose analysts review every play and record who ran a route and who stayed in to block.

Three consequences:

1. It is not free. Most route and TPRR data sits behind an analytics subscription. Snap counts and targets are everywhere; routes are not.
2. Providers disagree. The edge cases are genuinely ambiguous — a back who chips an edge rusher and releases into the flat, a tight end who runs two steps and settles into protection. Different charting rules produce different numbers.
3. Do not mix sources. Pick one provider and compare within it. A 4-point gap between two players from the same source is meaningful; a 4-point gap between two sources is noise.

Worked example: two tight ends, same snap share

Both play for offenses that ran 62 plays and dropped back 36 times. Both posted an 80% snap share — about 50 snaps each. From the snap count alone they are the same player.

Read that table carefully, because it contains the trap and the escape from it.

Tight End A is a genuine pass-catcher. He is in the route on nearly every dropback, and his 31 routes give him roughly double the chances of B. His TPRR is fine but unspectacular — he is not the first read, he is the volume guy. If his offense throws more, he scores more. He is startable and he is safe.

Tight End B posts the higher TPRR, and this is where people go wrong. That 18.8% looks like the better rate, and in isolation it is — the quarterback likes him when he runs. But he runs on fewer than half of dropbacks because he is blocking on the rest. Sixteen routes a game is a hard ceiling. Unless his route participation moves, his TPRR advantage cannot overcome a 15-route deficit.

The useful conclusion: A is the better play now; B is the better watchlist name. If B’s route participation climbs from 45% toward 70% — because the offense changes personnel groupings, or the tight end ahead of him gets hurt — his existing target rate suggests the production will follow immediately. That is a role change worth pre-positioning for, and it is invisible in snap counts.

Using it to break a waiver tie

The most common in-season application: two pass-catchers are available, you have one roster spot, and their box scores look similar. Work the funnel.

1. Snap share trend, three weeks. Anyone moving down is out. Direction beats level.
2. Route participation. The higher number wins by default, and the gap needs to be substantial — 10 points or more — before it decides anything.
3. Routes run per game in raw terms. Percentages of a slow offense are smaller than they look. Multiply by dropbacks.
4. TPRR. Among players with comparable route volume, this breaks the tie. It is the closest thing to a measure of how much the quarterback trusts a player.
5. Red-zone routes. A player who leaves the field inside the 20 has a capped ceiling regardless of everything above. Red-zone usage is a separate signal and should be checked separately.
6. Vacated opportunity. If someone ahead of him is out, tomorrow’s routes will not look like last week’s.

Steps 1 through 4 are ordered deliberately — earlier steps are more reliable and cheaper to check. That ordering is the backbone of usage-based waiver wire decisions and it fits inside the wider usage-based fantasy process you run every week.

One caveat that gets missed: route participation is a share of dropbacks, so it inherits the volatility of how often a team drops back. A blowout loss inflates dropbacks and can drag a starter’s route percentage down while his raw route count goes up. Read three-week trends, check the raw counts alongside the percentages, and treat any single game as a suggestion. The definitions for every stage of the funnel are collected in the NFL usage stats glossary if you want the short versions in one place, and target share is the next stage down the funnel once routes check out.