Part of our complete guide to hand signals in football series on sideline communication and visual play signaling.
- How Three Programs Rebuilt Their Run Pass Option Signals — And What Everyone Else Is Still Getting Wrong
- Quick Answer
- Case Study 1: When a High School Program's RPO System Collapsed Mid-Season
- Case Study 2: The Program That Ran RPOs Faster Than Anyone Could Scout Them
- Case Study 3: What Happens When RPO Signals and Base Run Signals Conflict
- The Three-Layer Architecture Every RPO Signal System Needs
- Why Signal Theft Hurts RPOs More Than Any Other Play Type
- How Digital Signal Platforms Change the RPO Communication Equation
- Frequently Asked Questions about Run Pass Option Signals
- What makes RPO signals different from standard play signals?
- How do coaches protect RPO signals from being stolen?
- Can RPO signals work fast enough for no-huddle tempo?
- What are the most common RPO signaling errors at the high school level?
- How many signals does a well-designed RPO package actually need?
- What should a wristband look like for an RPO-heavy offense?
- Here's What to Remember
The single biggest mistake coaches make with RPO communication isn't the signal itself — it's treating the RPO as one play instead of three.
Run pass option signals carry more embedded information per signal than almost any other play type in modern football. A single call must simultaneously communicate a run assignment for the offensive line, a route for the receiver, and a read key for the quarterback. Compress all of that into a sideline signal under a 40-second clock, and the margin for miscommunication narrows fast. Over the years working with programs at multiple levels, I've seen this communication layer — not the scheme itself — become the limiting factor on how far an RPO package can actually develop.
This article builds from three case scenarios, draws lessons from each, and offers a framework for how programs should build their run pass option signals systems from the ground up.
Quick Answer
Run pass option signals must communicate three simultaneous components to the offense before the snap: the run concept (blocking scheme), the pass concept (route combination), and the read key or indicator for the quarterback. Effective RPO signaling requires either a multi-signal sequence or a coded visual system that embeds all three components without tipping the defense.
Case Study 1: When a High School Program's RPO System Collapsed Mid-Season
A high school program I worked with had installed a bubble-and-inside-zone RPO package going into their playoff run. The scheme was sound. The QB had good eyes. The problem surfaced in Week 7: their signal system used a single "bubble" indicator from the sideline, and by the time they faced their third opponent running it, opposing defensive coordinators were anticipating the call.
What had happened was structural. Their run pass option signals were too clean — one signal, one concept, fully readable by any defensive staff doing even basic film work.
What they changed: - Moved to a two-signal sequence: one for the run track, one for the pass concept - Added a live "dummy" signaler on the sideline — not uncommon at this level, but they hadn't been using one - Rotated which signaler was "live" using a pre-snap indicator worn by the signal-caller
The result wasn't just better security. It was faster identification by the QB, because the signals were now organized by function rather than by play name. This aligns with what our spread offense communication framework describes: separating signal components by offensive function — blocking, routes, reads — is more cognitively efficient than grouping by play identity.
Case Study 2: The Program That Ran RPOs Faster Than Anyone Could Scout Them
The second scenario comes from a small college program that had one of the more elegant RPO signal systems I've seen. Their tempo was fast enough that defensive substitutions were a constant problem for opponents — and their run pass option signals were a core reason why.
Their approach: they didn't change signals play-to-play. They changed the sequence of signals.
The core library was small — roughly 8 base signals, each representing either a run concept or a pass concept. The live signal was always the second one given after a specific anchor motion by the signal-caller. Everything else was noise.
The most theft-proof RPO signal system isn't one that's complex — it's one where the complexity is invisible. Defenders can see your signals. They can't see your sequence logic.
This approach maps directly to what modern football coaching at the sideline technology level describes as the evolution of sideline communication: moving from symbol-based to sequence-based encoding. The defense can decode your symbols. They cannot decode your sequencing rules unless they have your wristband.
Why this matters at tempo: - No-huddle means the signal system must operate in under 10 seconds - If the QB is reading the signal while simultaneously checking defensive alignment, the signal can't require heavy decoding - Sequence-based systems let the QB identify the live signal instantly once the anchor is recognized
Signal XO was designed specifically around this type of multi-component visual communication — the platform lets coordinators build signal libraries, assign sequence rules, and push updated wristbands without reprinting anything mid-game.
Case Study 3: What Happens When RPO Signals and Base Run Signals Conflict
The third case is the most instructive, because it exposed a flaw that many programs carry for entire seasons without ever diagnosing correctly.
A program had a well-developed signal system for their base offense. When they grafted an RPO package onto it mid-season, they kept the existing run signals and added new "RPO" signals as a separate category. Within three games, QBs were occasionally receiving two conflicting reads at the line — the run signal from the standard system and the RPO indicator from the new one — and defaulting to whichever they had more reps with.
The fix wasn't more signals. It was a hierarchy rule: any RPO indicator supersedes a base run call. Full stop.
This is the kind of operational detail that separates programs that run RPOs cleanly from programs that get yards despite their system rather than because of it. From a technology standpoint, this is also where football operations technology creates real leverage — when your signal system lives in a digital platform, you can build hierarchy rules directly into the call architecture rather than relying on player memory to resolve conflicts under game pressure.
The Three-Layer Architecture Every RPO Signal System Needs
Based on these scenarios and years of watching this problem at multiple levels, effective run pass option signals require three layers of deliberate structure.
Layer 1: Component Separation - Run track signals (inside zone, outside zone, power, counter) exist as one distinct category - Pass concept signals (bubble, slant, flat-go, now screen) exist as a separate category - QB read keys — leverage reads, force reads, coverage indicators — may be embedded or signaled separately depending on your installation depth
Layer 2: Sequence Logic - Which signal is live, and precisely how the QB identifies it before the snap - Dummy signalers and dummy signal protocols - How the sequence rule changes by game quarter, field position, or opponent
Layer 3: Conflict Resolution Rules - What happens when an RPO call overlaps with a base run call in the system - Who holds override authority (typically the designated signal-caller, not the QB) - How conflicts resolve in real time without burning a timeout
For a broader look at how these layers integrate with your pre-snap communication infrastructure, the Journal of Sport and Exercise Psychology has published meaningful work on how athletes process sequenced visual information under time pressure — the architecture of RPO signals isn't arbitrary, it maps directly to how QBs actually load and retrieve information mid-play.
Why Signal Theft Hurts RPOs More Than Any Other Play Type
Standard plays are vulnerable to signal theft, but the consequences are contained — the defense knows what's coming and sets up for it. With RPOs, the stakes are categorically higher.
A defense that successfully reads your run pass option signals before the snap doesn't just know the play. They can attack the one thing RPOs are designed to exploit: the conflict point between run and pass defense assignments.
If a safety knows a bubble RPO is coming, he no longer has to honor his run fit. He can cheat to the bubble receiver pre-snap. The read that was supposed to be easy for your QB suddenly doesn't exist at all.
Signal theft on a standard run costs you a few yards. Signal theft on an RPO collapses the entire read — it turns your offense's best play into its most dangerous.
This is why protecting your signal system deserves specific attention in RPO packages more than in any other part of the offense. The NFHS football rules don't prohibit opponents from watching your signals — they prohibit electronic communication to players, but visual signals remain legal and fair-game for defensive staffs. At the college level, the NCAA football rules framework similarly treats sideline signals as open information, placing the full burden of signal security on the offense.
For a deeper look at this vulnerability, our article on how signal theft and tempo wars are reshaping sideline technology covers the arms race that's accelerating at every level of the sport.
How Digital Signal Platforms Change the RPO Communication Equation
Wristband-based digital systems shift the communication burden from signal memorization to signal recognition. The QB doesn't need to hold 40 signals in working memory. They need to know the sequence rule for that game, find their wristband number, and execute.
For RPOs specifically, this matters because: - The play has three components, and all three need to reach the entire skill group simultaneously - Receiver route assignments tied to RPO calls can be updated weekly without full installation sessions - When a new RPO concept is added, it can be pushed to wristbands rather than taught through repetition
Signal XO allows coordinators to design wristband layouts digitally and update them between games or halves — which means your signal library can evolve throughout a season without the cognitive overhead of re-teaching the system from scratch. The NFL's communication policy offers useful framing here too: even at the highest level of the sport, the trend is toward hybrid visual-plus-digital systems that reduce the signal surface area defenders can exploit.
For programs still managing this manually, our article on snap count communication architecture covers the broader pre-snap infrastructure these digital systems plug into — and why getting the sequencing right at the snap count level is a prerequisite for effective RPO signaling downstream.
Frequently Asked Questions about Run Pass Option Signals
What makes RPO signals different from standard play signals?
An RPO signal must communicate a run concept, a pass concept, and a read key — three pieces of information in a single call. Standard play signals typically communicate one concept. This layered requirement makes run pass option signals more complex and more vulnerable to miscommunication if the system isn't deliberately structured around all three components.
How do coaches protect RPO signals from being stolen?
The most effective methods include: using dummy signalers to create visual noise, building sequence-based systems where the live signal is identified by its position in a sequence rather than its appearance, and rotating signal libraries between games or halves. Digital wristband platforms that allow mid-game updates add a further layer of protection that manual systems can't match.
Can RPO signals work fast enough for no-huddle tempo?
Yes, but only with a system designed for speed. The signal sequence must be short, live-signal identification must be immediate, and the QB must be able to read the signal while simultaneously processing defensive alignment. Programs that run effective no-huddle RPOs typically use a compressed signal library with heavy repetition on the sequence rules. Our no-huddle offense guide covers the full practice-to-game-day framework.
What are the most common RPO signaling errors at the high school level?
The three we see repeatedly: too few dummy signals (making the live signal obvious by elimination), failing to rotate the designated live signaler, and installing RPO signals that visually resemble existing run signals — creating the conflict-resolution problem from Case Study 3. All three are structural failures, not repetition problems. More reps won't fix a broken architecture.
How many signals does a well-designed RPO package actually need?
A clean system can run a complete RPO package with 6 to 10 core signals, provided the sequence logic is sound. Programs that create a unique signal for every RPO variant end up with bloated libraries that QBs can't reliably decode under game pressure. Fewer signals, cleaner sequences, heavier reliance on sequence logic — that's the design principle worth following.
What should a wristband look like for an RPO-heavy offense?
A well-designed wristband for RPO football groups run concepts, pass concepts, and read parameters in adjacent columns or sections — so the QB can process all three simultaneously rather than sequentially. The layout should mirror the way the QB processes the post-snap read, not the way the coordinator thinks about the play. Platforms like Signal XO allow coordinators to build and test this layout digitally before it ever reaches the field.
Here's What to Remember
- RPO signals carry three embedded components — run track, pass concept, read key. Build your system to handle all three explicitly, or the weakest layer will break under game pressure.
- Sequence-based systems outperform symbol-based systems for signal security. Opponents can decode your symbols with film study. They cannot decode your sequencing logic without your wristband.
- Conflict resolution must be a written rule, not a habit. When RPO and base run signals overlap, players need a hierarchy — not a judgment call at the line of scrimmage.
- Signal theft hurts RPOs more than any other play type because it eliminates the read itself, not just the play. Signal security is part of your RPO installation, not an afterthought.
- Digital wristband platforms reduce cognitive load and allow mid-game updates — critical for an RPO package that evolves as the season progresses.
- Keep your signal library small (6-10 core signals) and invest the complexity in your sequence logic, not your signal count. Complexity that lives in the sequence is invisible to opponents.
About the Author: Signal XO Coaching Staff is Football Technology & Strategy at Signal XO. The Signal XO Coaching Staff brings decades of combined football coaching experience to every article. We specialize in digital play-calling systems, sideline communication technology, and modern offensive strategy.
Signal XO