Case Study 2 — The Sophomore Center and the Slanting Fifty
A high-school case from Lyle Petrakis's years as an offensive coordinator in northeast Ohio. The school, the opponent, and the players are fictional composites; the rules discussion describes real codes in general terms — check your current rulebook.
Setup
Before I ever coached in the NFL, I spent five years as a high school offensive coordinator in northeast Ohio. In my second season, our offensive line averaged about 235 pounds. Our center, Stan Wozniak, was a sophomore who weighed 190 pounds in his helmet and pads. His family went to the same church as mine, and his grandmother still called me "the Petrakis boy from the diner." He was the smartest football player in the building, and he was going to get run over every Friday.
We played in a league with one defense everybody feared: a rival from the next county that ran an odd front — a fifty — and slanted it on almost every snap.
The fifty front, for our purposes: a nose tackle head-up on the center (a 0-technique), two defensive tackles on the inside shoulders of our offensive tackles (4i-techniques), two outside linebackers standing on the line at the edges, and two inside linebackers behind the guards. At the snap, the whole front would slant — every down lineman stepping hard into the gap to one side of where he lined up — and the linebackers would fill behind them in the opposite direction.
Our line's rules at the time were what a lot of high schools still teach: assignment blocking by alignment. "On, inside, outside, backer." Each lineman decided before the snap whom he would block, based on where the defenders were standing. Against a front that stood still, it worked fine.
Against a front that moved at the snap, it was a disaster, because every assignment was decided against a picture that disappeared the moment the ball moved.
What Happens
The first meeting
We lost 21–7. We ran the ball 28 times for 41 yards. I remember the number because I wrote it on a placemat at my parents' diner at midnight and stared at it until my father turned off the grill.
On film, the pattern was the same on almost every run. Here's our inside zone — we called it inside zone, but our rules were really man rules — against their slant:
PRE-SNAP: Inside zone right vs. the fifty (high school)
M W
E T N T E
LT LG C RG RT Y
Q
R
📊 Diagram (described): Our offense: five linemen and a tight end on the right, the quarterback under center, and the back behind him. Their fifty front: a nose tackle head-up on our center, two tackles on the inside shoulders of our two tackles, an outside linebacker standing on the line at each edge, and two inside linebackers behind our guards.
With man rules, our center had the nose, each tackle had the 4i on him, and the guards — uncovered — went straight to the inside linebackers. At the snap, the front slanted to its left — toward our right, the side we were running to. The nose shot into our right A-gap, past Stan's play-side shoulder before Stan's hands came up. The tackle over our right tackle slanted across his face to the outside, and our right tackle, reaching for a man who was already past him, missed. On the backside, the tackle over our left tackle slanted inside, away from him, and our left tackle, assigned to him, chased him inside — and the backside outside linebacker came free behind the play. Our guards had climbed to linebackers who weren't there anymore, because the linebackers were "scraping" over the top behind the slant. Two or three defenders in the backfield, every snap.
Our left guard, a senior named Tommy Reyes, in the Monday film session: "Coach, I block my guy and then my guy's not there."
That sentence was the whole problem. Our rules told every player to block a man. Their front was designed to make the man move.
The fix: two rules and one call
I spent that week reading every zone-blocking clinic note I could get my hands on — the tradition that grew up around Alex Gibbs and the wide-zone teams was already well known in coaching circles — and on Wednesday I threw out our run-blocking rules and replaced them with two:
- Covered: if a man is on you or in your play-side gap, step play-side and block him.
- Uncovered: step play-side and help the man next to you, eyes on the linebacker. Whoever comes into your area is yours. Never chase a man out of your area.
And one call, for Stan: point at the nose and say his number. "Zero!" or "One!" if he shaded. That told the guards whether the center was covered. That's it. No calls about slants. The rules handled the slants.
POST-SNAP: same front slants to our right — area rules, not man rules
M --> W --> (linebackers scrape right)
E T N T E
\ \ \ \ \ (all five slant right)
v v v v v
LT LG C RG RT Y
=> => => => => => (everyone zone-steps right)
each slanting man runs INTO the next blocker's area
<---- R cutback lane opens behind the slant
📊 Diagram (described): At the snap the whole fifty front slants toward our right, and the inside linebackers scrape right behind it. Our five linemen and the tight end all take the same zone step to the right. Because every defender is moving into the area of the next blocker over, each one is met by whoever he runs into: the nose slants into the right guard's area and the right guard takes him; the center, now uncovered, steps right and helps, then climbs; the defensive tackle on the left slants inside into the left guard's area, and the one on the right slants outside into the right tackle's area, where the tight end is stepping to help. The back presses the play-side, sees the whole defense flowing right, and cuts back to the left, where the slant has left a lane.
Here's what changed. Against man rules, the slant made every assignment wrong. Against area rules, the slant made every defender run into a blocker. The defense's movement was no longer a problem for the line; it was a problem for the defense, because a front that slants hard one way leaves the other way thin — and the zone back's cutback read lives in exactly that space.
We repped it Wednesday and Thursday. Not much else. I cut our run game to two plays for the week — inside zone both ways and one counter — and our pass game to the three-step quick game with a simple slide protection, because I didn't want those five kids thinking about anything except the two rules.
The second meeting
We saw them again in the playoffs. We won 17–14. We ran for something like 180 yards — I didn't write that one on a placemat; I didn't need to. Most of it was inside zone, and most of the big ones were cutbacks.
Stan Wozniak never once blocked the nose tackle by himself the whole night. He didn't have to. When the nose slanted away, Stan was uncovered and helped; when the nose slanted into him, Stan was covered and a guard was already arriving to help. A 190-pound sophomore, protected by a rule.
Analysis
1. Rules that assign men lose to fronts that move. Man (or "on-inside-outside-backer") rules decide the block against the pre-snap picture. Slanting and stunting fronts are built to change the picture at the snap. Area rules decide the block after the defender moves — the same principle as the zone combo this chapter teaches: let the defense declare, then answer.
2. Simplicity was the scheme. I had installed seven line calls that season. The second meeting we had one. High school linemen get a fraction of the practice time pros get, and they share it with special teams, with two-way players, sometimes with the junior varsity. Every call you add competes with a rep you lose.
3. The defense's strength became its weakness. Slanting fronts are great at blowing up assignments. They're vulnerable to anything that cuts back against the slant, because every defender is moving the same way. Zone rules plus a cutback-reading back turned their movement into our running lane. That's the book's thesis in a high-school gym: the offense knows where the ball is going; let the defense guess first.
4. The level changes the details, not the principle. In the NFL, Gus Ferrante teaches the same two rules with ten times the vocabulary on top. At the high-school level, we had to check things the NFL coach never thinks about: high school codes have historically limited blocks below the waist to an area close to the ball at the snap and have tightened those rules over time, so we taught no low blocks at all; our splits were one rule (about two feet) because a kid who has to remember three split rules is a kid who forgets his first step; and every lineman used the same three-point stance on every play so our stance never told the defense anything. Check your current code on low blocks and on how far an ineligible lineman may be downfield on a pass — it matters the moment you add play-action or RPOs.
Discussion Questions
- Why does a slanting front beat "on-inside-outside-backer" rules so badly? Use the word "picture" in your answer.
- The fix cut the run game to two plays for a week. What did the offense give up, and why was it worth it at the high school level? Would it be worth it in the NFL?
- The cutback lane appeared because the whole front slanted the same way. How would a smart defensive coordinator adjust in the rematch — and what would you call next?
- Stan's one call ("Zero!" / "One!") told the guards whether the center was covered. Write the equivalent one-word call for your own center, and explain what information it carries.
- Compare this case to the Game 2 sack in this chapter. In both, the defense changed the picture late. What's the common lesson about when your blockers should decide whom they block?
Your Turn
You coach a high school team whose next opponent runs a 4-3 that stems — the defensive line shifts from one alignment to another right before the snap — on about half its snaps. Write a one-page line plan for the week: (1) the two run-blocking rules you'll use and the exact words your linemen will say; (2) the single call your center makes and what it tells the line; (3) the two runs you'll keep and the ones you'll shelve for the week; and (4) one sentence for your quarterback on what to do if the stem leaves an unblocked rusher on a pass.