Passing, rushing, and field effects
Passing depth and timing
How provider week metrics for air yards and time-to-throw, together with game attempts and completions, describe a bounded passing process.
Precise definition
Passing depth and timing describe a bounded passing process through intended or completed air yards, time to throw, and attempt/completion totals—often mixing game-level counting stats with provider week aggregates and tracking- or model-derived measures. Those scopes are not game scheme grades.
Why it matters
Depth and timing summarize how far and how quickly the ball left the quarterback's hand within stated scopes; week aggregates and provider formulas carry their own caveats and are not scheme claims.
How it works
Air yards describe how far the ball traveled in the air
Intended and completed air yards summarize depth at the provider's stated scope. NFL Next Gen Stats public passing tables publish related week-level depth and timing signals with their own definitions.
Time to throw summarizes release timing, not line quality
Tracking-derived time to throw measures how long the ball stayed with the quarterback before release. It is not a grade of protection, coverage, or indecision by itself.
Attempts and completions remain game-level anchors
Game attempt and completion totals describe what happened in the contest. Week aggregates must stay labeled as week scope and must not be silently mixed into per-game denominators.
Observable signals
Week-level air yards and time-to-throw at the provider's stated scope
What it can mean: Across the week sample, throws tended toward certain depths and release times.
Caution: Week aggregates and tracking definitions are not game scheme grades.
Game attempt and completion totals beside those week signals
What it can mean: The game produced a countable passing volume that can be read next to—not as—week metrics.
Caution: Do not normalize week metrics into game metrics or mix denominators.
A short quick release contrasted with a deeper, slower-developing throw
What it can mean: Observable depth and timing outcomes can differ sharply across plays.
Caution: Time to throw is not line quality or indecision; CPOE, when sourced, is model-derived.
Illustrative example
Illustrative short quick release versus deeper slower throw
Illustrative teaching sequence, not a real game. Neutral offense on two first-and-10 snaps.
Step 1
Short quick release
Observation: A completion is recorded after a short throw with a quick release; air yards are low and yards after catch may add the rest.
Interpretation: Depth and timing here are short and fast—an observable process outcome, not a scheme label.
Step 2
Deeper, slower-developing throw
Observation: On the next illustrative snap, a deeper incompletion arrives after a longer time to throw.
Interpretation: The depth and timing profile differs; the longer timer still does not prove protection failure or indecision.
Step 3
Scope reminder
Observation: Game attempts/completions count both snaps; any week air-yard or time-to-throw table covering the player remains a separate weekly aggregate.
Interpretation: Process description stays useful only when game outputs and week aggregates keep their scopes.
Takeaway: Describe depth and timing as scoped process measures; do not promote them into scheme grades.
Limitation: This invented contrast cannot grade protection, coverage, or scheme, and week tables must not be treated as single-game facts.
Common misinterpretations
Mistake: Equating time to throw with offensive-line quality or quarterback indecision.
Better reading: Treat time to throw as a tracking-derived release timer within the provider's definition—not as a protection or decision grade.
Mistake: Using week air-yard averages as a grade of one game's scheme.
Better reading: Keep week aggregates at week scope; pair them with game attempts and completions without mixing denominators.
Metrics and limitations
- Intended and completed air yards
Measures: Provider depth measures for how far the ball travels in the air on attempts and completions—often week aggregates on Next Gen Stats tables.
Useful for: Summarizing passing depth at the provider's stated scope.
What it misses: Week aggregates and tracking definitions are not game scheme grades; do not mix into game denominators.
- Time to throw
Measures: Tracking-derived average or play-level time from snap or event start to release under the provider definition—commonly week-scoped publicly.
Useful for: Describing release timing within the stated sample.
What it misses: Not a measure of line quality or indecision; formula and sample qualifications apply.
- Attempts and completions
Measures: Game-level official pass attempts and completions.
Useful for: Anchoring volume in the contest itself beside week signals.
What it misses: Counting stats omit depth, timing, and expected completion context.
- CPOE when sourced
Measures: Model-derived completion percentage over expected when a provider publishes it for a stated sample.
Useful for: Adding expectation context beside raw completion rate.
What it misses: Model-derived, version-sensitive, and not a scheme grade; qualifying samples matter.