Football Routes and Names: Why Your Program's Naming System Matters More Than the Routes Themselves

Every passing concept in football starts with a simple agreement: what do we call this route? Yet walk into five different programs and you'll hear five different names for the same cut. One coach's "dig" is another's "in." A "china" route in one playbook is a "shallow cross" two towns over. This disconnect in football routes and names doesn't just create confusion during transfers — it quietly erodes execution speed, sideline communication, and the seconds you can't afford to waste on game day.

This article isn't another route tree diagram. (We've already published a complete guide to football routes that covers every route and its mechanics.) Instead, this is about the layer underneath: the naming architecture your program uses, why naming conventions diverge so wildly across football, and how to build a system where every coach, player, and sideline signal means exactly one thing.

Quick Answer: What Are Football Routes and Names?

Football routes and names are the standardized labels assigned to the paths receivers run on passing plays. The universal numbering system assigns digits 0–9 to specific routes (0 = hitch, 1 = flat, etc.), but naming conventions vary dramatically between programs. A consistent naming system lets quarterbacks, receivers, and coaches communicate route assignments in under two seconds — while inconsistent naming creates mental lag that kills plays before the snap.

Frequently Asked Questions About Football Routes and Names

How many football routes are there in a standard route tree?

The standard route tree contains 9 numbered routes (1–9), though many programs add a 0 route (hitch or sit) for a total of 10. Beyond the base tree, coordinators layer in option routes, combination routes, and concept-specific stems. A typical college playbook uses 14–18 distinct route names when you include variations like speed outs, skinny posts, and whip routes.

Why do different football programs use different route names?

Naming divergence stems from coaching lineage. The Air Coryell system, West Coast offense, and Erhardt-Perkins system each developed independent terminology in the 1970s and 1980s. Coaches carry their mentor's language into new programs. According to the NCAA football resources, there's no governing standard for play terminology, so each program self-governs its language.

What is the universal route numbering system?

The universal route numbering system assigns a single digit to each base route: typically 1 (flat), 2 (slant), 3 (drag/shallow), 4 (curl/hitch), 5 (comeback), 6 (out), 7 (corner), 8 (post), 9 (go/fly), and 0 (hitch/sit). Odd numbers generally break inside; even numbers break outside. However, at least three widely used variations of this numbering exist, which is part of the problem.

Do NFL teams use the same route names as college programs?

No. NFL terminology varies significantly by coaching staff. The Shanahan/McVay tree uses distinct language from the Andy Reid tree, which differs again from Bill Belichick's Erhardt-Perkins system. A receiver changing teams often learns an entirely new vocabulary for routes he's run since high school. The NFL Football Operations group documents rules but not play-calling language.

How do coaches communicate football route names during a game?

Methods range from hand signals and wristband cards to digital sideline communication platforms. At the professional level, quarterback helmet radios carry the call. Below that, most programs rely on visual signals — which is where naming complexity becomes a real-time problem. A 12-word play call with ambiguous route names is a miscommunication waiting to happen.

What's the fastest way to teach football routes and names to new players?

Start with the numbered tree (0–9) as the universal foundation, then layer your program's specific terminology on top. Pair each name with a physical walkthrough — not just a whiteboard drawing. Most programs report that 3–4 focused installation sessions over 10 days produce reliable recall, compared to a single film session which averages only 40–60% retention after 48 hours.

The Three Naming Systems That Split Football's Language

The reason your quarterback says "curl" and your new transfer says "hitch" for the same route traces back to three offensive philosophies that each built their own vocabulary.

The Air Coryell System

Don Coryell's San Diego offense in the late 1970s established route names that are still common today: "hook," "comeback," "post," "go." This system uses descriptive English words for routes, which makes them intuitive for new players. The tradeoff: words are longer to say and signal than numbers. I've worked with programs that still use pure Coryell language, and their play calls tend to run 3–4 seconds longer than number-based systems — a gap that matters when the play clock hits 10.

The Erhardt-Perkins System

Developed with the New England Patriots in the 1970s, this system names concepts rather than individual routes. "Ghost" might be a full passing concept where each receiver already knows their route based on formation and coverage. The advantage is brevity: one word can encode five receivers' assignments. The disadvantage is steep learning curves. A new player doesn't just learn route names — they learn an entire concept dictionary.

The West Coast Offense System

Bill Walsh's system combined elements of both, using a long, specific play call that names the formation, protection, and every receiver's route. A single play call might be "Split Right Slot 2 Jet Right Zip 82 Y Stick." Every piece means something, but the call itself can exceed 10 words.

A 12-word play call that takes 4 seconds to deliver leaves your quarterback 3 seconds to read the defense pre-snap. A 4-word call using a concept-based naming system gives him 7. That's not a coaching preference — it's arithmetic that decides games.

What This Means for Your Program

Most programs today run hybrids. You probably use number-based route calls for individual assignments but concept names for packaged plays. The problem isn't which system you choose — it's when your naming architecture has unintentional overlap, ambiguity, or inconsistency.

Here's a diagnostic I run with coaching staffs: hand your route naming glossary to your third-string receiver and ask him to draw every route from memory. If his drawings don't match your coordinator's intent on more than 2 of 10, your naming system has a communication leak. That leak doesn't show up in practice against your own scout team. It shows up at 7:43 in the third quarter when the wrong read turns a post into a pick-six the other direction.

The Naming Collision Problem (And How to Audit Yours)

A naming collision happens when two routes share a name, or one route has two names, within your own playbook. This is more common than most coaches admit.

Common Collisions I've Encountered

Route	Name Variant A	Name Variant B	Name Variant C
5-yard out	Out	Speed out	Quick out
12-yard in	Dig	In	Drive
Deep crosser	Over	Cross	Deep in
Flat route	Flat	Arrow	Swing
Post-corner	Post-corner	Sluggo	7 route

If your offensive coordinator calls it a "dig" in the meeting room but your position coach calls it an "in" during individual drills, you've built a translation tax into every rep. Multiply that across your entire route tree and your passing game is running through mud before the ball is snapped.

How to Audit Your Program's Route Names in 4 Steps

1. Collect every route name currently used in your playbook, install scripts, wristband cards, and signal sheets. Don't edit — just list them all.
2. Map each name to a single physical path on the field, including depth, break point, and angle. Flag any name that maps to more than one path.
3. Identify synonyms — different names your staff uses for the same route. Choose one. Eliminate the rest. No exceptions, no "well, the kids know what we mean."
4. Test recall with players 72 hours after installation. Any route where more than 20% of your receivers draw it wrong needs a name change, a teaching adjustment, or both.

This audit takes about 90 minutes. At Signal XO, we've seen coaching staffs discover 4–8 naming collisions in a single audit — collisions that had been silently degrading their passing game for seasons.

Why Digital Play-Calling Exposes (and Fixes) Naming Inconsistency

Here's something I didn't fully appreciate until I'd watched hundreds of coaches use visual play-calling systems: the moment you move from verbal calls and hand signals to a digital sideline communication platform, every naming inconsistency becomes visible.

When your play-calling lives on a coaching board app, each route needs a single, canonical name in the system. You can't have one coach typing "dig" and another typing "in" for the same concept. The software forces the conversation that should have happened in the spring meeting room.

This is one reason programs that adopt platforms like Signal XO often report that the technology's biggest benefit isn't speed — it's the naming discipline the system demands during setup. You have to define your terms before the platform will let you build plays. That constraint is a feature.

The average high school program carries 6 unintentional synonyms in its route-naming system. Each one adds a 0.3–0.5 second cognitive delay per play. Over a 60-play game, that's 18–30 seconds of cumulative mental lag your opponent doesn't have.

Building a Route Naming System That Scales Across Levels

If you're a youth or middle school program, the names you install now follow players for years. If you're a varsity coordinator inheriting players from three different feeder programs, you're dealing with three naming systems that need to merge into one. Here's a framework that works across levels.

The 3-Layer Naming Architecture

Layer 1: The Numbered Tree (Universal Foundation) Every player learns the 0–9 route tree. This is non-negotiable, regardless of your offensive system. Numbers are the common language. When your new transfer says "what's a 6 route," every player on your roster should be able to answer "out" without thinking.

Layer 2: Concept Names (Your System's Vocabulary) These are the one- or two-word names for packaged passing concepts: "Mesh," "Drive," "Smash," "Levels." Each concept name implies specific routes for each position. This layer is where programs differentiate, and it's where your play-calling sheet lives.

Layer 3: Tags and Modifiers These adjust a base concept without creating a new name: "Mesh Switch" (receivers swap assignments), "Drive Alert" (hot route override), "Smash Check" (coverage-dependent adjustment). Tags should follow consistent grammar — always a concept name + one modifier word.

Rules for Naming That Prevent Future Collisions

• One route, one name. No synonyms. If you call the 12-yard in-breaking route a "dig," it is never an "in" in your program. Period.
• Names should be phonetically distinct. "Curl" and "corner" sound similar in a loud stadium. "Curl" and "7" don't. The National Federation of State High School Associations doesn't mandate terminology, but their coaching education materials recommend phonetic clarity for sideline communication.
• Fewer syllables win. Every syllable in a play call is time. "Comeback" is two syllables. "Five" is one. Over a full game, monosyllabic route names save real time — time your QB uses to read the defense instead of decoding the call.
• Document everything in one place. Your route glossary should be a single page that every coach and player can access. If it lives in three different handouts, you've already lost.

From Naming to Signaling: The Last-Mile Problem

You can perfect your football routes and names in the meeting room and still lose the signal on the sideline. The last-mile problem is the gap between your coordinator's call and the quarterback's understanding, compressed into the 5–8 seconds between plays.

Hand signals are the most common transmission method below the college level. Each route or concept name needs a corresponding visual signal. The math gets ugly fast: 10 base routes × 15 concepts × 4 formations = hundreds of potential signals. Most programs simplify by signaling concept names rather than individual routes, but even then, signal complexity scales with playbook size.

This is where visual play-calling technology changes the equation. Instead of encoding route names into hand signals that players must decode in real time, platforms like Signal XO transmit the visual play directly. The route name becomes irrelevant to the transmission — the player sees the route drawn on screen, eliminating the naming-to-signal translation entirely.

That doesn't mean naming doesn't matter. Players still need shared vocabulary for audibles, hot routes, and line-of-scrimmage adjustments. But the primary play call — the 80% of communication that happens between plays — can bypass the naming bottleneck altogether.

The Transfer Portal Made This Problem Urgent

Five years ago, a naming inconsistency was a minor inconvenience. A player learned your system over a full offseason and adjusted. The NCAA transfer portal changed that calculus dramatically. Programs now onboard mid-year transfers who arrive knowing a completely different route vocabulary.

A receiver who spent three years calling an out route a "speed out" doesn't instantly rewire his brain when your system calls it a "6." The cognitive delay is real and measurable — I've seen it add a half-step of hesitation on breaks that turns a completion into a contested ball.

Programs that use the numbered tree as their foundation (Layer 1 in the framework above) have a massive onboarding advantage. Numbers are numbers regardless of which system a player came from. Concept names (Layer 2) take longer, but if your spring football installation prioritizes vocabulary alongside physical reps, most transfers report comfort within 12–15 practices.

A Practical Naming Reference You Can Steal

Rather than just listing routes, here's the naming decision matrix I recommend to programs. For each route, I've listed the most common name variants and flagged the one I'd choose for phonetic clarity, brevity, and minimal collision risk.

Route #	Path Description	Common Names	Recommended Name	Why
0	5-yard sit	Hitch, sit, stop	Hitch	Universally understood, distinct sound
1	Flat/sideline	Flat, arrow, swing	Flat	One syllable, no ambiguity
2	45° inside break, 5-7 yards	Slant, quick	Slant	Descriptive, one syllable
3	Shallow cross	Drag, shallow, cross	Drag	One syllable, distinct from "cross"
4	10-12 yard comeback to sideline	Curl, hook, comeback	Curl	One syllable, distinct sound
5	12-15 yard comeback	Comeback, come	Come	One syllable, shortens call
6	12-yard outside break	Out, speed out	Out	One syllable, universal
7	Deep outside break	Corner, flag	Corner	More descriptive than "flag"
8	Deep inside break	Post	Post	Universal, no alternatives needed
9	Vertical	Go, fly, streak	Go	One syllable, unmistakable

Tape this to your play-calling board. Make every coach on your staff use these exact names. If a coach slips and says "hook" instead of "curl," correct it immediately — not because it matters in that moment, but because language discipline compounds over a season.

Conclusion: Name It Once, Name It Right

The conversation about football routes and names usually stops at "here's the route tree." But the naming system underneath — the vocabulary your program agrees on, enforces, and communicates — determines how fast your offense processes information under pressure. A clean naming architecture with zero synonyms, phonetic clarity, and a layered structure (numbers → concepts → tags) gives your program a communication advantage that doesn't require more talent or better athletes.

If you're building or rebuilding your route nomenclature, start with the audit. Find your collisions. Eliminate your synonyms. Then put the final glossary somewhere every coach and player can access it in seconds — whether that's a laminated card, a wristband, or a platform like Signal XO that enforces naming consistency by design.

Part of our complete guide to football routes series — explore the full route tree, advanced route combinations, and printable route tree templates to build on the naming foundation covered here.

---

About the Author: Signal XO is a visual play-calling and sideline communication technology platform built for football coaches and teams at every level. Signal XO works with programs to eliminate communication breakdowns between the booth, the sideline, and the huddle — starting with the naming systems that make play-calling possible.

---