Yards after contact is a blocking stat too
Yards after contact arrived as the answer to a real problem. Yards per carry was obviously contaminated by blocking, so the charting services built a stat that started the clock at the moment a defender touched the ball carrier. Everything before that was the line’s work; everything after was the back’s. It is a clean idea, it sounds like an isolation of individual skill, and it now anchors draft profiles, contract arguments, and every February conversation about which back is worth paying. The trouble is that the dividing line the stat depends on is drawn by a person watching film, and where the line falls is itself determined by the blocking it was invented to remove.
Contact is a judgment, not an event
There is no sensor in a jersey deciding when contact occurs. A charter watches the play and marks a frame. That sounds trivial until you list the cases: a linebacker’s fingertips grazing a shoulder pad as the back accelerates past; a safety who arrives with an arm but no leverage; a defensive lineman engaged with a guard whose hand catches the runner in traffic; a back running through a pile where the contact is with his own center. Different services resolve these differently, and some resolve them differently across seasons as their guidelines are revised. That is why the same back can carry two meaningfully different yards-after-contact figures on two reputable sites in the same week, and why year-over-year comparisons within one provider are safer than comparisons across providers.
Where the contact happens decides the number
The deeper problem is not the frame. It is the field position of the frame. Two backs each gain six yards after contact. The first was hit two yards behind the line of scrimmage by an unblocked edge defender and dragged the pile to a four-yard gain. The second was untouched to the second level, met by a backpedaling safety with a running start advantage the wrong way, and turned a good block into eleven. The stat scores them identically. It cannot distinguish them, because it deliberately discarded the information that would — namely, how far the offensive line got the runner before anyone arrived.
And that distance is not random with respect to the runner. Backs on good lines meet defenders later, in space, against smaller and less leveraged tacklers. Backs on bad lines meet defenders early, in traffic, against linemen. Contact at the second level is easier to break and yields more yards when broken. So the stat built to strip out blocking still carries blocking, only now it carries it invisibly, through the quality of the contact it starts measuring at.
Two different skills wearing one number
Yards after contact bundles at least two abilities that have little to do with each other. One is elusiveness: making a defender miss after the initial touch, which is a matter of balance, vision, and change of direction. The other is contact balance and raw power: staying upright through a wrap, falling forward, moving a pile. A 210-pound back who spins out of arm tackles and a 235-pound back who runs through them can post the same figure by opposite means, and they age differently, get used differently, and hold up differently behind a bad line. Any stat that assigns one number to two skills has already lost the argument it was built to settle.
The bundling also hides who the tackler was. Breaking a cornerback’s arm tackle in the open field and breaking a middle linebacker’s wrap in a phone booth are not the same accomplishment, and a back whose carries funnel him into defensive backs will accumulate the stat faster than one who meets linebackers on every touch. Scheme decides that mix. Outside zone puts runners on the perimeter against smaller defenders; gap and duo concepts put them into the teeth of the front. Neither back chose the play call.
Game script sits underneath all of it
Running backs do not choose when they carry the ball. A back on a team that leads often gets fourth-quarter carries against stacked fronts that know the run is coming — heavy contact, early, with defenders unblocked by design. A back on a trailing team gets draws and second-and-long carries against light boxes and pass-rush alignments. The first back looks tougher by the numbers because his team was better. The stat cannot see the box count, the down and distance, or the score, and none of the three are his doing.
The rate version is better and still not clean
Yards after contact per attempt is the version worth using, for the same reason every per-attempt rate beats a season total: it stops rewarding workload. It is also more stable year to year than yards per carry, which is a genuine point in its favor and the strongest argument that some real signal lives in here. But stability is not the same as purity. An offensive line changes slowly. A team’s run scheme changes slowly. A back’s role changes slowly. A stat can repeat reliably because it is measuring a durable skill, or because it is measuring a durable environment, and year-over-year correlation alone cannot tell you which.
What it does measure well
Used carefully, the stat earns its keep in two places. First, as a tiebreaker between backs in the same backfield: same line, same scheme, similar down-and-distance mix, and now the comparison is close to fair. Second, as a floor indicator. A back with a poor yards-after-contact rate behind a line that grades well is a real warning, because the environment was already favorable and the number still came in low. The stat is at its most useful when you hold the environment fixed and at its least useful when you rank the whole league by it.
It is also a reasonable input for projecting a back into a new situation, provided you project the situation too. A runner moving from a bottom-five line to a top-five one should be expected to gain yards before contact he never had, and to see his after-contact rate move as well, because the contact he now absorbs arrives later and softer. Analysts who hold the rate constant across a change of address are assuming the one thing the stat cannot promise.
How to read it on StatLine
StatLine’s NFL tables carry the standard rushing line — attempts, yards, average, touchdowns — and the right move is to treat contact-based charting numbers from elsewhere as a supplement to that, not a replacement. Check attempt volume first, because low-attempt backs sit on samples too small to distinguish from noise. Then check the team context: a back on a strong rushing offense and a back on a weak one are not competing on the same field. Only after both of those does the after-contact figure carry information about the player.
The honest read
Yards after contact is a better stat than yards per carry. It is not the isolation of running-back skill it is marketed as. It depends on a subjective contact frame, on how far the blocking carried the runner before that frame, on which of two unrelated skills a given back uses to gain the yards, and on a game script determined by the rest of the roster. Read it within a backfield, within a scheme, and per attempt. Then remember that the offensive line never left the number — it just stopped being visible in it.