Yards After Contact: Separating the Runner From His Blocking

The Yards a Runner Earns on His Own

Rushing yards are a shared product. On most carries, the offensive line and blockers create the first few yards before the back ever meets a defender; what happens after that is where the runner's own ability shows up. Yards after contact (YAC, in the rushing sense - not to be confused with receiving yards-after-catch) tries to separate those two contributions by counting only the ground a runner gains past the moment a defender first gets a hand on him.

The idea is intuitive. If a back takes a handoff, finds a clean lane his line opened, and is touched five yards downfield before churning for three more, only those final three yards are "after contact." The first five belong largely to the blocking. By isolating the post-contact portion, the metric tries to answer a question raw rushing yards cannot: how much did this runner add beyond what was blocked for him?

How It Is Defined and Charted

The core definition is simple to state but requires judgment to apply: for each carry, a charter marks the spot where the first defender makes meaningful contact with the ball-carrier, and the yards gained from that spot to where the play ends are credited as yards after contact.

Summed and averaged over a season, the headline number is usually expressed per carry:

Two things make this a charted statistic rather than something pulled cleanly from a box score:

• "First contact" is a judgment call. A glancing brush from a diving lineman, an arm-tackle that the back runs through, and a square hit are not the same event. Charters have to decide what counts as the contact that starts the YAC clock, and different services draw that line slightly differently.
• It traditionally required human film review. For years YAC was produced by charting operations watching every carry. Player-tracking data has since made it possible to estimate contact points more automatically, but the underlying definition - find first contact, measure the rest - is unchanged.

Because of that subjectivity, two providers can publish slightly different yards-after-contact figures for the same runner. The numbers are meaningful and comparable within a single source's methodology, but you should not mix and match them across sources as if they were identical measurements.

Broken and Missed Tackles

Closely tied to yards after contact is a companion charted stat: broken or missed tackles forced. These count the number of would-be tacklers a runner defeats - shedding an arm tackle, running through a wrap-up, or making a defender whiff entirely. The two metrics travel together because the most reliable way to pile up yards after contact is to make defenders miss or fail to bring you down.

The distinction analysts usually draw:

• A missed tackle is a defender who had a chance to make the tackle and failed - often a whiff in space.
• A broken tackle is contact that should have ended the play but the runner powered or spun through it.

Different charting shops fold these together or keep them separate, but the analytic value is the same: a high rate of broken/missed tackles forced is strong evidence that a back's yards after contact reflect real tackle-breaking ability rather than just being touched late by a trailing defender. Read together, yards after contact tells you how far a runner goes after contact and broken tackles tells you how he gets there.

What It Isolates: Runner vs. Blocking

The reason yards after contact exists is that raw rushing average is heavily contaminated by environment. A back behind a dominant line and a strong scheme will post gaudy yards per carry even with ordinary individual skill, while a gifted runner behind a poor line can look pedestrian on the stat sheet. Splitting each carry into a "before contact" and "after contact" portion is an attempt to attribute credit more fairly:

Consider a clearly hypothetical contrast to see why this matters:

This is also why yards after contact pairs naturally with rushing yards over expected (RYOE), which uses tracking data to model how many yards an average back would have gained in the same situation. They attack the same problem - stripping environment out of rushing production - from different angles: YAC splits the carry by contact point, while RYOE compares the result to a leaguewide expectation given the defenders' positions.

Caveats and How to Read It

Yards after contact is one of the better tools for evaluating runners, but it is not free of the same environment problems it is trying to solve:

• Contact point is subjective. Because "first contact" is a charting decision, the metric carries some measurement noise, and figures differ across providers. Trust the trend, not the third decimal place.
• Blocking still leaks in. A line that consistently puts a back into the second level lets him hit contact already moving downhill with momentum, which inflates the yards he gains afterward. Yards after contact reduces the blocking dependency but does not eliminate it.
• Scheme and role matter. A back used on tough short-yardage and goal-line carries will face contact earlier and in traffic; a back used in space on outside zone will not. Their yards-after-contact profiles are not strictly comparable without context.
• It is a rate built on charted plays. Small samples are noisy, and the broken-tackle counts especially need a full season to stabilize.

The bottom line

Yards after contact counts only the rushing yards a back gains past the point where the first defender touches him, splitting each carry into a "before contact" portion that mostly reflects the blocking and an "after contact" portion that mostly reflects the runner. It is a charted statistic - the contact point is a human (or tracking-assisted) judgment - so figures vary across providers and should be read as trends, not exact measurements. Paired with broken and missed tackles forced, it isolates the tackle-breaking, balance, and vision that a back carries with him regardless of his line, which is exactly what raw rushing average obscures. Read it alongside rushing yards over expected and an honest look at the offensive line, and never as a standalone grade.

Further reading

• See also Chapter 7: Rushing Analytics (DataField.dev).
• RYOE: Rushing Yards Over Expected - the tracking-data approach to the same problem
• Yards After Catch Over Expected - the receiving cousin of after-the-fact yardage
• Explosive Plays - how the big run fits into rushing value
• All NFL Analytics Explainers - the full library of metric guides
• nflfastR - open play-by-play data for rushing analysis