GUIDES · BETSLIP DOCTOR
What different parts of a play do NFL route, run-scheme and blocking classifications describe?
The NFL's 2026-season article describes three different classification tasks: a more detailed receiver-route classification, a run-scheme model that labels intended play design, and a blocking matchup model that labels block type and engagement timing. Those labels describe different parts of a play; they are not a single grade of success. The article announces model changes but does not provide a complete taxonomy, per-play outputs, or accuracy results.
For NFL fans trying to understand how tracking-based classifications describe different parts of a play. · Updated
Route Classification 2.0 describes route categories
The NFL article says its 2026 Route Classification 2.0 was retrained with a more detailed route tree. It gives examples such as separating a fade from a go route, distinguishing shallow and deep crosses, and improving screen detection by using both blocking movement and route path.
These examples explain the announced direction of the update; they are not the complete route tree. The article does not supply a current per-play label or a full list of categories that would let a reader classify a real route from a short description.
Run-scheme labels describe intended design, not the runner's final path
The 2026 article describes a primary run-scheme classification for intended play design, along with secondary tags. It distinguishes the gap a play was intended to use from the gap the ball carrier actually reaches. That distinction matters because a runner may change direction after the handoff, while a classification is trying to describe design.
The article names a finite set of primary labels and examples involving man, zone, and gap concepts, but it does not publish a complete usable taxonomy, individual-play results, or validation accuracy. A reader should not reverse-engineer the intended scheme from the runner's final path.
Blocking labels describe a blocker-defender interaction
The companion run-blocking matchup model is described as assigning block type and frame-level engagement start and end points. The article says those descriptions can be used to examine interactions such as double teams and a defender shedding a block.
An engagement label is still a model output. The article does not define every block type, explain every adjudication edge case, or state that an engagement label alone proves a play succeeded.
One fictional pass play and one fictional run play
Fictional pass: a receiver begins outside and takes a shallow path across the field while a blocker moves forward near the line. Those are the stipulated observations. The route path and blocking movement could be relevant to the kinds of distinctions the 2026 route article describes, including screen detection, but this example assigns no route or screen label. Fictional run: a play card in the scenario calls for an inside lane, the runner receives the handoff and cuts toward the outside, and a guard engages a defender while a second blocker joins. The planned lane, actual runner path, and described engagement are kept separate. No run-scheme or block-type output is supplied, and the cut does not prove what the model would classify or whether each block succeeded.
Related questions
Does the 2026 article provide the complete route and run-scheme taxonomies?
No. It names selected route refinements and describes the run-scheme model, but it does not give a complete taxonomy or classification outputs for individual plays.
Does a successful run prove that the blocking model assigned each blocker correctly?
No. The article describes modeled block types and engagement timing as analysis capabilities. It does not say that the final run result verifies each model assignment.