The QB reads one conflict defender after the snap and either hands off or throws - taking whatever the defense gives, bounded by the linemen-downfield rule.
By The NFL Analytics Editorial Team · Published June 14, 2026
The run-pass option, or RPO, is one play that contains two: a run and a pass packaged together, with the quarterback deciding which to execute after the ball is snapped by reading a specific defender. Instead of choosing run or pass in the huddle and hoping it matches what the defense does, the offense lets the defense declare itself first - then takes whatever the read tells it the defense gave up. It is the closest thing football has to making a defender wrong no matter what he does.
The mechanic is elegant. The line blocks as if it is a run. The back takes a run path. A receiver runs a quick route. The quarterback puts the ball in the back's belly and watches one defender - typically a linebacker or safety on the edge of the box. If that defender commits to stopping the run, the quarterback pulls the ball and throws into the space the defender vacated. If the defender drops to take away the throw, the quarterback hands off into a box now short a man. The conflict defender cannot be right.
Every RPO is built around a single defender the offense chooses to "read" - the player the blocking scheme deliberately leaves unaccounted for so the quarterback can use him as a decision key. Because the offense is not blocking him, that defender is free to make a play; the trick is that whichever play he makes, the quarterback counters it.
The routes attached are almost always quick-developing - slants, hitches, bubble screens, quick seams - because the throw has to come out fast, before the run-blocking up front becomes illegal downfield action. The whole concept lives in a narrow timing window: long enough to read the defender, short enough to stay legal.
RPOs exist in the form they do because of one specific rule, and understanding it is essential to understanding why these plays look the way they do. Offensive linemen are not allowed to be more than a fixed short distance downfield - one yard beyond the line of scrimmage in the NFL - when a forward pass crosses the line. The penalty is "ineligible receiver downfield" (illegal man downfield).
This single rule shapes the entire concept in three ways:
So the linemen-downfield rule is not a footnote; it is the boundary condition that defines what an RPO can be. The college game's more permissive downfield allowance is a large part of why RPOs flourished there first and arrived in the NFL in a more compressed, quicker-trigger form.
RPOs are not just clever - they attack structural weaknesses that defenses cannot easily resolve. The pressure they apply is mathematical as much as schematic:
A defense has a fixed number of players. Loading the box to stop the run leaves windows for the quick pass; dropping to cover the pass leaves the box light. The RPO forces that trade-off to be made on every snap and immediately exploits whichever way it tips.
The read defender is asked to do two contradictory jobs - fit the run and cover the pass - and is punished for choosing either. Repeated RPOs wear on these players and make their pre-snap alignment a liability.
Because the quarterback only throws when the read says the pass is open, RPO throws tend to be high-percentage, low-sack, low-interception plays. They generate steady, on-schedule gains rather than boom-or-bust shots.
Like play-action, RPOs punish defenders who peek at the wrong key. The run action pulls eyes into the backfield exactly when a defender needs to be reading his coverage responsibility.
The defensive counters mirror the offense's logic: disguise the box count so the quarterback cannot reliably read it pre-snap, drill "pass-key" eye discipline so conflict defenders react to the right thing, and use simulated pressures that change who the conflict defender even is. As with most schematic battles, the result is an equilibrium - RPOs remain efficient, but defenses make the reads harder rather than impossible.
For analysts, RPOs create a genuine measurement headache, because the play is ambiguous by design. The same call can end as a run or a pass depending on a post-snap read, which breaks the clean run/pass split that most metrics assume.
The practical upshot: when you see RPO usage or efficiency numbers, they came from someone watching the film and tagging plays, not from a clean box-score field. That is worth remembering before treating any RPO statistic as precise - and a reason different sources' RPO counts can diverge.
The run-pass option packages a run and a pass on the same snap and lets the quarterback decide between them after the ball is snapped by reading one "conflict" defender, taking whatever that defender's reaction leaves open. It stresses defenses by forcing the box-count trade-off on every play and punishing the read defender for committing either way, generating efficient, low-risk gains. The whole concept is bounded by the linemen-downfield rule - offensive linemen may be only a short distance past the line on a forward pass - which forces RPO throws to be quick and short and makes officiating emphasis on that distance the lever that expands or limits the play. In play-by-play data, RPOs hide: they are recorded by their outcome as ordinary runs or passes, so studying them requires charting, which is why RPO usage and efficiency figures vary by source and should be read as estimates rather than exact counts.
Want the code behind these metrics? Work through the 45-chapter NFL analytics tutorial.
Browse tutorials Free tools