How to Use This Book
This book is meant to be worked, not just read. Read it the way a new quality control coach works through a playbook in June: with a pencil, a stack of blank diagram sheets, and the expectation that someone will ask you to draw it from memory on Thursday.
This page explains how each chapter is built, what the margin symbols mean, how the drills and the Playbook Project work, and who the people in the story are.
How each chapter is built
Every chapter lives in its own folder and contains seven files.
| File | What it is | How to use it |
|---|---|---|
index.md |
The chapter — usually 9,500 to 13,000 words, opening with a specific moment (a snap with the play clock running, a call that went wrong, a napkin diagram) before any theory | Read it with a pencil. Redraw each diagram before you read its description. |
key-takeaways.md |
A one-page card: takeaways, action items, common mistakes, decision framework | Print it and clip it inside your playbook. |
exercises.md |
Parts A (concepts), B (diagrams), C (calls), D (film and analysis), M (mixed practice with named earlier chapters), E (extensions) | Do A–C at minimum. Part M builds long-term retention. |
quiz.md |
15–25 questions with hidden answers and a scoring guide | Take it a day or two after the chapter. |
case-study-01.md |
A fully worked scenario, usually from inside the Outlaws' building | Read it as a staff meeting: what would you have called? |
case-study-02.md |
A deliberately different scenario — another opponent, another level, or the idea gone wrong | Compare it with the first. The differences are the lesson. |
further-reading.md |
Annotated pointers to real books, rulebooks, data sources, and documented history | Go deeper on whatever grabbed you. |
Major sections are numbered by chapter (13.1, 13.2). Every chapter after Chapter 2 has a Spaced Review,
and every chapter ends with a Project Checkpoint. Every term is defined the first time it appears in each
chapter, with the first use in bold, because you may reach Chapter 22 from a learning path without reading
Chapter 5. For every definition in one place, use Appendix I — Glossary and
Appendix A — Terminology and Notation.
The callouts
Boxed asides marked with an icon are reserved for things that deserve to stand apart. When you see one, slow down.
| Callout | What it means |
|---|---|
| 💡 Coach's point | A key principle stated plainly — the sentence you'd write on the whiteboard |
| 🎙️ On the headset | Lyle's real-time thinking during a call: the situation, the options, the decision |
| 🛡️ The defense's view | What the defensive coordinator sees and is trying to do. Know your enemy. |
| 🎬 Film room | What to look for on All-22 or end-zone film to identify or evaluate the concept |
| ⚠️ Common mistake | A named, specific error and its fix |
| 🩺 Player safety | Quarterback hits, blocking legality and safety, heat, and practice load. Never skip these. |
| 📈 By the numbers | An analytics aside, always with its sample size and caveats |
| 🏫 Any level | How the idea changes in high school or college: hashes, personnel, practice time, rules |
| 📊 Diagram (described) | A plain-language description after every diagram, so no reader is left out |
| 🔄 Check your understanding | A retrieval question. Answer it before opening the hidden answer. |
| 🧩 Productive struggle | A problem posed before the solution is taught. Try it, even if you get it wrong. |
| 🔍 Why this works | The mechanism underneath a rule, not a restatement of it |
| 📋 Try it | A drill with real inputs and a fully worked answer |
| 🪞 Learning check-in | A pause to judge your own understanding (every third chapter) |
| 🚪 Threshold concept | A gateway idea. Once it clicks, you see the game differently. |
Threshold concepts are the eight ideas that separate people who can recite offense from people who understand it. Each gets extra room and an explicit "before" and "after" picture of what understanding it looks like. If one doesn't click on the first read, that's normal; come back to it.
| Chapter | Threshold concept |
|---|---|
| 7 | The defense tells you where to go. |
| 9 | You block an area, not a man — and the back reads the blocks. |
| 12 | You can "block" a defender with a decision. |
| 15 | The quarterback reads a defender, not a receiver. |
| 19 | The run game is the first half of every play-action pass. |
| 22 | Protection is arithmetic, and the quarterback is part of the protection. |
| 25 | A play call is a bet on a distribution, not a promise of an outcome. |
| 38 | An offense is a system of constraints. |
Learning check-ins appear in Chapters 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 36, and 39. They ask how well you actually know the material, not how familiar it feels. A receiver who has heard the option-route rule forty times is not the same as one who can run it against press on third down.
The four drills
Every chapter has at least two 📋 Try it drills, and the exercises are built from four signature formats. Work
each drill before you open the hidden answer.
Draw it up. Given a defense and a concept, draw the play against it, before and after the snap: who blocks whom, where every route goes and how deep, where the back aims, which defender the quarterback reads. A coordinator who can't draw his own call against the likely defense can't teach it or fix it at halftime.
Make the call. Given a situation — down, distance, field position, score, time, timeouts, the defense's personnel and shell, some tendency data — make the call and defend it in a few sentences. The worked answers lay out two or three defensible calls and what each one bets on, because the reasoning is graded, not the result.
Find the conflict. Given a defensive structure, name the defender who has two jobs and the play that makes him choose: the Will with the backside A gap and the slant window, the corner with the flat under a corner route, the safety who fills the alley with a deep quarter behind him.
Whose fault? Given a play that failed — a sack, a tackle for loss, an interception — identify the player who broke his rule, name the rule, and give the fix. "The line got beat" is never the answer. Somebody misidentified the Mike, read the wrong defender, or called a play into the one look it couldn't handle — and sometimes that somebody is the coordinator.
Spaced review and mixed practice
From Chapter 3 on, each chapter's Spaced Review asks you to retrieve two or three earlier ideas — usually one
from the last chapter or two and one from much further back. It asks first and restates second. Don't skip it
because you "already know that"; the point is to find out whether you do. Each exercises.md also has a Part M
mixing the current chapter with named earlier ones. It feels harder than practicing one thing at a time. On
Sunday the defense doesn't tell you which chapter's problem it's about to show you.
The Playbook Project
Every chapter ends with a Project Checkpoint that adds one deliverable to an offense you build yourself. In Chapter 39 you assemble it into a 60–70 play core offense plus a weekly game-planning process, with a full game plan against the Sacramento Sentinels' defense.
Choose your level before you start, and stay with it:
- High school — fewer players, fewer coaches, far fewer practice hours, and the widest hashes. Your code's rules for linemen downfield, motion, and substitution differ in details from the NFL's; check your rulebook.
- College — wider hashes than the NFL, strict practice-hour limits, and a wide range of defenses week to week.
- Pro — the Outlaws' world: narrow hashes, the coach-to-quarterback radio, and a new defensive coordinator to beat every Sunday.
- Film room — for analysts, media, fans, and fantasy or betting readers. You build an analytical framework — recognition cards, charting sheets, a tendency template, a grading rubric — instead of a playbook to install.
| Ch | Deliverable | Ch | Deliverable |
|---|---|---|---|
| 1 | Offensive Philosophy Statement | 21 | Quick Game |
| 2 | Lineage Map | 22 | Protection Plan |
| 3 | Formation Family | 23 | Scouting Template + Sentinels Defensive Tendency Report |
| 4 | Personnel Packages & Role Cards | 24 | Game Plan v1 + 15-Play Opening Script |
| 5 | Offensive Line Rules Sheet | 25 | Call Sheet v1 + Play-Caller's Pregame Checklist |
| 6 | Skill-Position Role Cards & Route Tree | 26 | Situational Package |
| 7 | Defensive Recognition Card | 27 | Motion & Shift Menu |
| 8 | Nomenclature System & Wristband v1 | 28 | Offensive Metrics Dashboard + Fourth-Down / Two-Point Chart |
| 9 | Inside Zone Install Sheet | 29 | Wide Zone & Boot Family (or "Shanahan Borrow List") |
| 10 | Outside Zone Install Sheet | 30 | Spread Quick-Game & Tempo Borrow List |
| 11 | Gap Scheme Sheet | 31 | QB-Run Package |
| 12 | Option Package | 32 | Tempo Package |
| 13 | RPO Menu | 33 | Gadget Package |
| 14 | Short-Yardage & Goal-Line Package | 34 | Installation Calendar |
| 15 | Concept Framework | 35 | QB Development Plan |
| 16 | Core Coverage-Beater Set | 36 | In-Game Adjustment Protocol |
| 17 | Man-Beater Package | 37 | Coordinator Interview Binder |
| 18 | Shot Package | 38 | System Map |
| 19 | Play-Action Package | 39 | The Complete Playbook + Sentinels Game Plan |
| 20 | Screen Package | 40 | Film Grading Rubric |
The Full Outline describes each deliverable. Each Project Checkpoint names the piece you just finished, specifies the new one concretely — format, contents, and a short filled-in example — and previews the next. Keep everything in one binder. By Chapter 39 you'll be editing thirty-eight pieces you already built.
Three appendices serve the project. Appendix F holds blank scouting, script, call-sheet, and halftime templates. Appendix G is the Sentinels' scouting packet — your opponent. Appendix L is the Outlaws' own core playbook, a worked example of the finished product. Build yours first, then compare.
The people in the story are fictional
The book follows one season of the Austin Outlaws through the eyes of their offensive coordinator, Lyle Petrakis, and their young quality control coach, Teo Arriaga. Every one of them is fictional — so are the Outlaws, the Sacramento Sentinels, the St. Louis Stallions, the Portland Pioneers, the Birmingham Forge, the Oklahoma City Ospreys, everyone on those teams, and every score, call, and statistic attached to them. They are composites that live inside the real rulebook and the real history of the game.
The reason is honesty. Nobody outside a real building knows what a real coordinator was thinking or what a real quarterback read. With a fictional staff, the book can show you the call sheet, the headset, the halftime whiteboard, and the Monday argument, and every word is true inside the story. A fictional season also lets the same players and snaps recur across forty chapters, so you can watch one play from several angles as you learn.
Real coaches, players, and teams appear only where the history is well documented, and the book never invents a quotation or a statistic for a real person. A number about the Outlaws is a teaching number; a number about the league is a hedged range with its caveats attached.
The season you'll follow
The season is framed by three games against the division rival Sentinels and their defensive coordinator, Russ Kimbrough:
- Game 1 — Week 6 in Austin. Where the Outlaws' signature ideas first meet Russ's defense.
- Game 2 — Week 15 in Sacramento. The halftime-adjustment game, and the source of the protection lesson the Outlaws spent the rest of the season fixing.
- Game 3 — the divisional playoff in Sacramento. Everything both staffs learned about each other, on one afternoon.
The book is organized by topic, not calendar, so a playoff snap may appear in Chapter 7 and a Week 6 snap in Chapter 36. Other opponents appear when they're the better teacher: the St. Louis Stallions, a single-high, eight-man-box defense that makes play-action pay; the Portland Pioneers, the league's most disciplined Cover 2; the Birmingham Forge, who blitz everything and play man behind it; and the Oklahoma City Ospreys, with press corners and simulated pressures.
The four anchor plays
Four plays from the season are told in full in their home chapters and revisited, again and again, from new angles as your understanding grows. The chapters refer to them by short labels — Anchor A through Anchor D — so learn them on sight.
| Label | Name | What it is | Home chapter |
|---|---|---|---|
| Anchor A | The Inside Slant | Game 1's first two snaps: inside zone with a slant read on the Sentinels' Will linebacker, Jordan Ames. When he comes downhill for the run, the quarterback throws the slant behind him; when he sits back for the slant, the quarterback hands off into the space he left. Ames is wrong either way. | Chapter 13 — RPOs |
| Anchor B | The Portland Smash | Week 10 against the Portland Pioneers' Cover 2: smash puts the cornerback in a hi-lo between a hitch and a corner route. Both of his choices lose. | Chapter 16 — Smash, Flood, and Levels |
| Anchor C | The Third-and-Seven | A third-quarter third down in the divisional playoff, called against the pressure that had beaten the Outlaws in Week 15 — a double-A mug with a corner fire zone. Several calls were defensible; the reasoning is the skill. | Chapter 25 — Play Calling |
| Anchor D | The Four-Play Sequence | Game 1's fourth-quarter tying drive: inside zone, inside zone, a play-action post from the same look, and inside zone again — each play built on what the last one taught one safety. | Chapter 19 — Play-Action Passing |
Anchor A and Anchor D are previewed in Chapter 1, and all four are revisited as one system in Chapter 38 and graded one last time in Chapter 40. When one comes back, try to remember how it went and why before you read on. That's spaced review too.
Before Chapter 1
Read Reading the Diagrams first; twenty minutes there will save you hours later. Then decide how you'll travel. Learning Paths lays out routes for aspiring coaches, high school and college staffs, analysts and media, fans and fantasy or betting readers, and a fast track for experienced coaches.
A full instructor companion — syllabi, chapter notes, discussion guides, assessments, and rubrics — accompanies the
book in the instructor-guide folder.