Richt's RPO Philosphy A Good Fit For Top WR Recruits

Technically RPO is a system when you define what it is; a set of principles or procedures according to which something is done; an organized scheme or method.
 
Advertisement
It's both. Let's imagine this:

1) A RPO play is called - the run option is an inside zone run and let's say the pass option is a WR slant
2) The QB looks at the defense and sees the CB playing 10 yards off and the LB crowding the line (a pre-snap read)
3) The ball is snapped
4) At the snap of the ball, the QB notices the LB drop into the flat to take away the slant (post-snap read)
5) QB hands off to the RB and the RB runs to where the LB just was for an easy 6 yards

Same playcall:

1) CB is still playing off coverage, LB is still crowding the line (pre-snap read)
2) At the snap, the QB sees the LB crash down to take away the run (post-snap read)
3) QB pulls the ball out of the RB's gut and throws the WR slant right at where the LB just was for another easy 6 yards

Rinse. Repeat.

https://youtu.be/2F81g5OC-cA

On my phone so I'm not sure how to embed...@ 1:14 is an RPO executed perfectly. Watch what the outside backer does and the result is a TD
 
RPO works when your QB doesn't have to use a Walker to get around in the backfield.

Kaayak does...

I think the big issue with Kaaya running RPO is what happens when that first read is gone or the OL breaks down. It's not so much that we need a scramble-ball QB, but Kaaya has to be able to move his feet in order to extend the play once that first read goes away.

I think the guy before is talking about a read-option, which is different than RPO. It seems most poeple are confused by these concepts and don't understand the QB isn't necessarily a threat to run in RPO. I'm sure one could be, but that's not really the QB's function in RPO, where his primary responsibility is to either hand the ball off or throw it to a reciever. Read option on the otherhand is a designed run by either the RB or QB depending on the play of the defense.

"In football, an option is a running play where the quarterback can choose to either give the ball to another player or keep it himself. The read-option (also called zone-read) is the latest incarnation of this concept that features a quarterback in the shotgun who reads either a defensive end or outside linebacker to make his decision."

https://www.quora.com/What-is-a-read-option-offense-a-la-the-49ers

"The general concept [of RPO] is easy enough: the offense will isolate a defender who has both run and pass responsibilities. The quarterback reads what that guy decides to do, then either throws the pass if that guy attacks the run, or runs the running play if he stays back."

I'm no expert by any means but I can understand the difference between the two.
 
It's both. Let's imagine this:

1) A RPO play is called - the run option is an inside zone run and let's say the pass option is a WR slant
2) The QB looks at the defense and sees the CB playing 10 yards off and the LB crowding the line (a pre-snap read)
3) The ball is snapped
4) At the snap of the ball, the QB notices the LB drop into the flat to take away the slant (post-snap read)
5) QB hands off to the RB and the RB runs to where the LB just was for an easy 6 yards

Same playcall:

1) CB is still playing off coverage, LB is still crowding the line (pre-snap read)
2) At the snap, the QB sees the LB crash down to take away the run (post-snap read)
3) QB pulls the ball out of the RB's gut and throws the WR slant right at where the LB just was for another easy 6 yards

Rinse. Repeat.

https://youtu.be/2F81g5OC-cA

On my phone so I'm not sure how to embed...@ 1:14 is an RPO executed perfectly. Watch what the outside backer does and the result is a TD

This is exactly right. Good stuff. Another thing the RPO allows you to do is speed up the tempo of your plays, since by nature it's such a simple either-or philosophy. I know that's something Richt was keen on especially early in the season.
 
Also I'll touch on something on [MENTION=3]LuCane[/MENTION] mentioned way back before the season started. Kaaya likes to look "high to low" with his reads. RPO kind of dictates the opposite. This may also be why we switched to a more vertical passing game later in the season to play to what Kaaya naturally likes to read, if that makes sense.

DC's were baiting him. Showing an off look or uncovering the slot, knowing Kaaya would throw but having everyone flood to the slot and blow up the play. Brad was getting confused by what the defense was showing and wasn't able to adjust. He does like high to low, which may be his biggest problem, but that's not necessarily why they went away from RPO or weren't very successful at times.
 
Last edited:
Advertisement
What the **** are you talking about? Richt didnt even really use the rpo at uga.

Calm down bro, if you have the answer then use this as an opportunity to educate us all. No need to blow your top on this discussion. We will have plenty of time for that but right now I am really interested to know more about the use of RPO and it's impact on recruiting as well as it's affect on multiple receiver threats on one team.

There aint no impact on recruiting or wrs. You are implying that because richt uses the rpo thats why top wrs havent commited here yet. Then bring up uga when he didnt even use it there.

If that's the case then put your thoughts together and give us some sustenance rather than your spacey *** answer "There aint no impact on recruiting or wrs".

Ill give any kind of answer i want. You should have done your research on his offenses at uga before you posted.

:q3XKXeX:
 
Also I'll touch on something on [MENTION=3]LuCane[/MENTION] mentioned way back before the season started. Kaaya likes to look "high to low" with his reads. RPO kind of dictates the opposite. This may also be why we switched to a more vertical passing game later in the season to play to what Kaaya naturally likes to read, if that makes sense.

DC's were baiting him. Showing an off look knowing Kaaya would throw but having everyone flood to the slot and blow up the play. Brad was getting confised by what the defence was showing and wasn't able to adjust. He does like high to low, which may be his biggest problem, but that's not necessarily why they went away from RPO or weren't very successful at times.

Good call. I'll have to re-watch some video but that makes perfect sense. We came out in those first cupcake games throwing that WR screen every down when the CBs were off. Makes sense that a good DC would show that same off-coverage pre-snap then roll it to take that screen away.
 
What the **** are you talking about? Richt didnt even really use the rpo at uga.

Calm down bro, if you have the answer then use this as an opportunity to educate us all. No need to blow your top on this discussion. We will have plenty of time for that but right now I am really interested to know more about the use of RPO and it's impact on recruiting as well as it's affect on multiple receiver threats on one team.

There aint no impact on recruiting or wrs. You are implying that because richt uses the rpo thats why top wrs havent commited here yet. Then bring up uga when he didnt even use it there.

If that's the case then put your thoughts together and give us some sustenance rather than your spacey *** answer "There aint no impact on recruiting or wrs".

It's not that you don't know what you're talking about. It's that you don't know that you don't know what you're talking about. I think that's why he comes off that way.
 
Also I'll touch on something on [MENTION=3]LuCane[/MENTION] mentioned way back before the season started. Kaaya likes to look "high to low" with his reads. RPO kind of dictates the opposite. This may also be why we switched to a more vertical passing game later in the season to play to what Kaaya naturally likes to read, if that makes sense.

DC's were baiting him. Showing an off look knowing Kaaya would throw but having everyone flood to the slot and blow up the play. Brad was getting confised by what the defence was showing and wasn't able to adjust. He does like high to low, which may be his biggest problem, but that's not necessarily why they went away from RPO or weren't very successful at times.

Good call. I'll have to re-watch some video but that makes perfect sense. We came out in those first cupcake games throwing that WR screen every down when the CBs were off. Makes sense that a good DC would show that same off-coverage pre-snap then roll it to take that screen away.

watch the FSU game. FSUs d/c busted Brad's *** with it. They played him for a good quarter before Richt realized Brad didn't see what was going on. They saw the success we had on film and game-planned to take that away. For the most part they did, but it's because of how it was called. It needs to be called with tempo when teams aren't expecting it to continue or further create and take advantage of defensive confusion.
 
Advertisement
Also I'll touch on something on [MENTION=3]LuCane[/MENTION] mentioned way back before the season started. Kaaya likes to look "high to low" with his reads. RPO kind of dictates the opposite. This may also be why we switched to a more vertical passing game later in the season to play to what Kaaya naturally likes to read, if that makes sense.

DC's were baiting him. Showing an off look knowing Kaaya would throw but having everyone flood to the slot and blow up the play. Brad was getting confised by what the defence was showing and wasn't able to adjust. He does like high to low, which may be his biggest problem, but that's not necessarily why they went away from RPO or weren't very successful at times.

Good call. I'll have to re-watch some video but that makes perfect sense. We came out in those first cupcake games throwing that WR screen every down when the CBs were off. Makes sense that a good DC would show that same off-coverage pre-snap then roll it to take that screen away.

watch the FSU game. FSUs d/c busted Brad's *** with it. They played him for a good quarter before Richt realized Brad didn't see what was going on. They saw the success we had on film and game-planned to take that away. For the most part they did, but it's because of how it was called. It needs to be called with tempo when teams aren't expecting it to continue or further create and take advantage of defensive confusion.

Agree with this completely.
 
It's both. Let's imagine this:

1) A RPO play is called - the run option is an inside zone run and let's say the pass option is a WR slant
2) The QB looks at the defense and sees the CB playing 10 yards off and the LB crowding the line (a pre-snap read)
3) The ball is snapped
4) At the snap of the ball, the QB notices the LB drop into the flat to take away the slant (post-snap read)
5) QB hands off to the RB and the RB runs to where the LB just was for an easy 6 yards

Same playcall:

1) CB is still playing off coverage, LB is still crowding the line (pre-snap read)
2) At the snap, the QB sees the LB crash down to take away the run (post-snap read)
3) QB pulls the ball out of the RB's gut and throws the WR slant right at where the LB just was for another easy 6 yards

Rinse. Repeat.

https://youtu.be/2F81g5OC-cA

On my phone so I'm not sure how to embed...@ 1:14 is an RPO executed perfectly. Watch what the outside backer does and the result is a TD
Agree. What is interesting to me is the fact that we had RPOs on both the front side and backside. Unless Berrios is running a dummy route instead of blocking the playside LB.

Sent from my SAMSUNG-SM-G935A using Tapatalk
 
Also I'll touch on something on [MENTION=3]LuCane[/MENTION] mentioned way back before the season started. Kaaya likes to look "high to low" with his reads. RPO kind of dictates the opposite. This may also be why we switched to a more vertical passing game later in the season to play to what Kaaya naturally likes to read, if that makes sense.

Hmmm, I think it was the opposite, IIRC. I thought kaaya read Low to high at first and Richt tried to switch him to high to low.

I think Richt switched him to plays that were designed to get specific guys open with the initial read rather than have Kaaya go through progressions.
 
Advertisement
The FSU game is where I realized Brad struggled with Presnap reads and adjustments.

He almost got Ahmon killed in that game with his inability to process simple coverage.

FSu: has 4 defenders in the perimeter crowding the line of scrimmage

Miami : two wrs/offenders in the perimeter.

Brad: Throws it into the perimeter.... loss of 4 yards...

Fans: Blame Mark for bad playcalling. Even though Brad made the bad decision.
 
RPO is a new fad. All it really is I think is 2 plays are called in the huddle ( a run and a pass). When they get to the line if they don't like the run because the box is stacked they call a quick pass. If they get to the line and there are limited numbers in the box the switch to a run. It's nothing new really just now there's a title to it. Peyton Manning, Tom Brady, and many others have been doing this for years!

That's actually not what it is.
 
It's both. Let's imagine this:

1) A RPO play is called - the run option is an inside zone run and let's say the pass option is a WR slant
2) The QB looks at the defense and sees the CB playing 10 yards off and the LB crowding the line (a pre-snap read)
3) The ball is snapped
4) At the snap of the ball, the QB notices the LB drop into the flat to take away the slant (post-snap read)
5) QB hands off to the RB and the RB runs to where the LB just was for an easy 6 yards

Same playcall:

1) CB is still playing off coverage, LB is still crowding the line (pre-snap read)
2) At the snap, the QB sees the LB crash down to take away the run (post-snap read)
3) QB pulls the ball out of the RB's gut and throws the WR slant right at where the LB just was for another easy 6 yards

Rinse. Repeat.

https://youtu.be/2F81g5OC-cA

On my phone so I'm not sure how to embed...@ 1:14 is an RPO executed perfectly. Watch what the outside backer does and the result is a TD
Agree. What is interesting to me is the fact that we had RPOs on both the front side and backside. Unless Berrios is running a dummy route instead of blocking the playside LB.

Sent from my SAMSUNG-SM-G935A using Tapatalk

He's running a bubble to pull the flat defender out of the box.
 
Advertisement
Without even reading this whole thread I can already guess that there's countless false statements and wrong information in it regarding RPO's. There's tons of confusion about what an RPO entails. Every time the subject is brought up on here it's a **** show.


1. RPO's have nothing to do with mobile QB's, so hopefully we'll stop hearing about how Kaaya isn't mobile enough to run the concept. It's not the read/option. Now, if you have a mobile QB you can add QB run options into your RPO concepts, but having a mobile QB is not a prerequisite.

2. It's not based on how many guys are in the box. The offense doesn't read the whole defense, they read ONE PLAYER. (the "conflict defender")

3. We run RPO's with a ton of success. Richards has been killing defenses with the quick-slant RPO concept out of the 3x1 formation. Our bubble screens that everybody says we're so much better at this year than the prior seasons... that's cause they're RPO's now...not just a called play that we stay in regardless of defensive alignment.



An RPO is a run/pass concept that reads a single defender. (usually a 2nd level defender like a LB) In the NFL they've progressed to reading 3rd level defenders such as Safeties. (some advanced college offenses do that as well)
It's an easy concept for the QB. All he has to do is read that one defender. That defender will tell him what to do with the ball. If he's reading a LB and that LB crashes down to defend the run, he throws the slant. (long TD to Coley against GT) If the LB stays with the slant or bubble, he hands the ball to the RB. Very simple concept that even good high school offenses can grasp.
The good offenses attach RPO's to run plays such as buck sweep, power, iso, inside zone, outside zone, etc.



This guy does a great job of explaining it. Maybe this video should be sticky'd so the confusion stops.

https://www.youtube.com/watch?v=OxGF9NBCfa8&t=466s
 
My B. youre right. I thought berrios was the Split End.

He is running the bubble to pull the defender and the Split End is setting up a block for what could potentially be Berrios bubble
 
It's both. Let's imagine this:

1) A RPO play is called - the run option is an inside zone run and let's say the pass option is a WR slant
2) The QB looks at the defense and sees the CB playing 10 yards off and the LB crowding the line (a pre-snap read)
3) The ball is snapped
4) At the snap of the ball, the QB notices the LB drop into the flat to take away the slant (post-snap read)
5) QB hands off to the RB and the RB runs to where the LB just was for an easy 6 yards

Same playcall:

1) CB is still playing off coverage, LB is still crowding the line (pre-snap read)
2) At the snap, the QB sees the LB crash down to take away the run (post-snap read)
3) QB pulls the ball out of the RB's gut and throws the WR slant right at where the LB just was for another easy 6 yards

Rinse. Repeat.

https://youtu.be/2F81g5OC-cA

On my phone so I'm not sure how to embed...@ 1:14 is an RPO executed perfectly. Watch what the outside backer does and the result is a TD
Agree. What is interesting to me is the fact that we had RPOs on both the front side and backside. Unless Berrios is running a dummy route instead of blocking the playside LB.

Sent from my SAMSUNG-SM-G935A using Tapatalk

He's running a bubble to pull the flat defender out of the box.
That is a well designed play. Thanks for the insight.

Sent from my SAMSUNG-SM-G935A using Tapatalk
 
Advertisement
Back
Top