The Hook
You installed the RPO three weeks ago. You thought it was perfect. The read is clean. The throw windows are there on film. You practiced it all week. You called it three times on Friday night. All three times, something went wrong. Either the QB held it too long and got sacked. Or he pulled it out too early and threw it into coverage. Or the timing between the QB and the running back got out of sync and they were both on different pages entirely.
So you pulled it off the call sheet. It’s been sitting there ever since, untouched, a reminder that something isn’t working.
Here’s what most coaches don’t understand: the RPO didn’t fail because the concept is bad. It failed because something in the execution is broken. And there are three places where it usually breaks.
The Three Places RPOs Die
Mistake #1: Too Many Reads, Too Little Time
This is the most common failure I see. The coach designs an RPO that looks sophisticated on the whiteboard—three levels of reads, multiple check options, progressions based on coverage rotation. It’s beautiful scheme. It’s also not getting executed because the quarterback is thinking instead of playing.
Here’s how you know this is your problem: your QB is holding the ball longer than two seconds before he makes a decision. Or he’s indecisive—he pulls it out and then looks like he wants to hand it because he’s not committed. Or he’s staring down receivers instead of attacking the read. All of these are symptoms of a quarterback who is processing too much.
The issue is usually that you’ve given him a three-read progression when he only has time to process one. You’ve told him to check the linebacker first, then the safety, then the underneath coverage. By the time he’s worked through that checklist, the play is dead.
Your high school quarterback doesn’t process information at the rate your college-level scheme requires. That’s not a failure on his part—it’s a mismatch between the play design and the player capability.
How to Diagnose This
Ask yourself: can I explain my QB’s read to him in one sentence without using the word “then”? If your explanation is “Read the linebacker, then check the safety, then look underneath,” you’ve got a multi-read progression. Your QB is thinking.
The fix is simple: eliminate everything except the primary read. Not the primary and the secondary. Just the primary. One defender. One decision.
Watch your game film. Time how long the QB holds the ball. If it’s consistently longer than 2.5 seconds, he’s processing too much. Pull it back. Simplify the read.
Mistake #2: The Wrong RPO for Your Personnel
You watched a clinic video from a big-time program. They were running a beautiful arc-read RPO where the QB reads the unblocked linebacker and the running back is running an outside zone read. It looked perfect. So you installed it.
The problem: your quarterback isn’t that mobile. Your offensive line isn’t athletic enough to execute arc reads. Your running back doesn’t have the vision to make a read at full speed. And your best playmaker is your tight end, not your slot receiver. So the throw window doesn’t exist because the tight end isn’t built into the RPO concept.
The RPO isn’t bad. But it’s the wrong tool for your team.
Here’s what happens: the QB is uncomfortable with the footwork because the arc-read step pattern doesn’t fit his natural movement. The offensive line is struggling with the assignment because arc-read blocks are more complex than what they’ve been running all year. The running back is tentative because he’s not confident in the read. And the receivers aren’t the right fit for the concept.
So the play moves slow. The throw windows close. And you pull it off the sheet thinking the concept doesn’t work, when really the concept works great for Alabama—it just doesn’t work for your team.
How to Diagnose This
Look at your personnel. Who is your most dependable receiver? Is he a slot guy or a perimeter guy? Is your quarterback mobile enough to beat defenders with his feet, or is he a pocket passer? Does your offensive line have athletes, or do they have strong technique and toughness?
Now look at the RPO you’re trying to run. Does it use your best players the right way? Does it fit your QB’s strengths? Does it ask your offensive line to do things they’re built to do?
If you can’t answer yes to all three, you’ve got an RPO design problem.
The fix is working backward from your personnel. Ask yourself: given my QB’s strengths, my receivers’ skill sets, and my offensive line’s technical foundation, what RPO would actually take advantage of what I have? Then build that, not what you saw on clinic video.
Mistake #3: Not Enough Reps in Practice
This is a subtler problem, but it’s deadly. You installed the RPO three weeks ago. You got two reps on it the first week. You got three reps the second week. The third week, you were busy installing something else, so it got one rep. Then you called it Friday night.
Your quarterback hasn’t seen the read twenty times. He’s seen it six times. That’s not enough reps to build automaticity. It’s enough reps to know what you’re asking him to do. It’s not enough reps for the decision to become reflexive.
When a decision isn’t reflexive, it’s slow. When it’s slow, it’s wrong. So the play breaks down.
A good rule of thumb: your QB needs a minimum of fifteen to twenty reps in practice before you call it in a game. And those reps need to be spread out—not all in one week, but consistent over two to three weeks. If you’re trying to get an RPO ready in five days, you don’t have enough time to build the reps you need.
How to Diagnose This
Look at your practice schedule from the last month. Count the actual reps your QB has gotten on that specific RPO concept. Not walk-throughs. Reps where he’s making the read at live speed or game-speed. Are you at fifteen to twenty? Are you above ten?
If you’re under ten reps, that’s your problem. You haven’t practiced it enough.
The fix is building a four-week progression: two reps the first week, three the second week, four the third week, five the fourth week. By the time you’re calling it in a game, your QB has gotten fourteen reps minimum. The read is becoming automatic. The footwork is building muscle memory.
The Diagnostic: Which Mistake Is Yours?
Take a piece of paper. Write down three things you observed on game film of your failed RPO.
First, how long is the QB holding the ball? Less than two seconds is good. Two to three seconds is concerning. More than three seconds is the problem.
Second, is the QB uncomfortable in the footwork? Is he looking stiff? Is the timing off between him and the running back? Is the decision point awkward? That’s a personnel fit problem.
Third, when the QB makes the decision, does it look reflexive? Or does he look like he’s working through a mental checklist? And going back to practice film, how many reps has he actually gotten on this play?
Once you identify which problem you have, you can fix it.
How to Fix Mistake #1: Too Many Reads
The fix is simple: keep only the primary read. If the concept has three layers built in, cut it. Your QB reads the first linebacker and that’s it. If the linebacker is doing X, pull it. If he’s doing Y, hand it. Done.
This isn’t about losing sophistication. This is about gaining speed. A fast, simple decision beats a slow, complex decision every single time.
Go back to your game film. Identify the moment when the read should be made. Usually it’s within the first 1.5 seconds of the play. Now zoom in. Is there only one key defender that tells you the answer? If yes, that’s your read. If the answer requires you to look at two or three defenders, it’s too complicated for a high school QB.
The fix also means teaching the read in practice differently. No more mental checklists. The QB identifies the key pre-snap. The ball is snapped. The key does one of two things. The QB reacts. That’s the whole progression.
How to Fix Mistake #2: Wrong RPO for Your Personnel
The fix is working backward. Forget what you saw on clinic video. Start with your quarterback. If he’s a pocket passer, you’re not running an RPO that requires him to escape the pocket and create space. If your best receiver is tight, you’re not running an RPO concept that depends on perimeter spacing.
Ask yourself three questions:
Question 1: What’s your quarterback’s greatest strength? Accuracy? Mobility? Arm talent? Toughness? Whatever it is, your RPO has to play to it. If your QB’s strength is accuracy, you need an RPO where the throw is simple and the window is clear. If his strength is mobility, you need an RPO where he has space to move.
Question 2: Who’s your most dependable receiver? Not your biggest. Not your fastest. Most dependable. That’s the guy your RPO should feature. If it’s your tight end, the RPO gets him involved early. If it’s your slot guy, the throwing window is to the slot. Your best player needs to be built into the concept.
Question 3: What’s your offensive line good at? If they’re good run-blockers with strong footwork, RPOs that attack downhill make sense. If they’re bigger and stronger but not as quick, you might stay more compact and attack inside. The RPO can’t ask them to do something they’re not built for.
Once you answer those three questions, design your RPO to fit the answers. Not the other way around.
How to Fix Mistake #3: Not Enough Reps
This is about consistency. You need a systematic plan to get your QB reps on the RPO without it taking over your entire practice.
Here’s a simple model: pick four plays you’re calling this week. One is your inside zone RPO. The others are your base run game. During team reps, call them in this order: IZ, IZ RPO, IZ, IZ RPO. The QB is getting two reps on the RPO, but they’re distributed across the period, not back-to-back. He’s not bored. He’s getting work.
Do that twice a week for three weeks. Your QB will get twelve reps minimum, spread out so they’re not redundant but consistent enough to build the read.
The key is integration. Don’t call the RPO period then the run game period. Interleave them. This keeps the QB’s brain engaged because he’s switching between plays, but it gets him consistent reps on the RPO.
What Good Execution Looks Like
When you’ve fixed the problems, here’s what you see on film: the QB gets the snap, takes one step toward the mesh point or the edge, his eyes are locked on one defender, that defender makes his choice, and the QB reacts in less than 1.5 seconds. The throw is delivered or the ball is handed. The play is over.
It’s not flashy. It’s not complicated. It looks like he’s just executing a normal play. That’s what you’re aiming for.
The Real Problem
Here’s what separates coaches who get RPOs right from coaches who struggle: they’re willing to cut the complexity. They build the concept to fit the player, not the player to fit the concept. And they understand that practice reps aren’t optional—they’re the foundation.
Most coaches try to run RPOs that are too sophisticated for their quarterbacks. Most coaches try to use RPOs that don’t fit their personnel. And most coaches don’t practice them enough. When those three things align, the RPO fails.
The fix isn’t more complexity. The fix is more simplicity, better fit, and more reps.
Build Your System the Right Way
If you want to walk through the full diagnostic—how to identify what’s broken with your specific RPOs, how to redesign them to fit your personnel, how to build a rep progression that works for your schedule—I’ve got 30+ hours of content in the Offensive Coordinator Academy that covers this from every angle. We break down failed RPOs on actual high school film, show you where the break happens, and walk you through the fix.
You’ll see how other coaches diagnosed their issues, how they rebuilt their concepts, and how they got their RPOs working on Friday night. If you want to skip the trial-and-error and get your RPOs right the first time, that’s where to look: offensivecoordinatoracademy.com