Read on Twitter
Was talking to some buddies coaching HS football today and this came up, so I'll explain it for the TL because this will probably be useful to some of you guys.
In my opinion, the easiest way to scout opposing offenses is by using a #ing system for formations instead of words.
In my opinion, the easiest way to scout opposing offenses is by using a #ing system for formations instead of words.
If you care about who is on the ball, use *. If not, ignore it.
Basically:
There is an assumption (rule breaker comes later) that there is one receiver to each side of the formation. Assuming it's not empty, you can use a two-digit code to fill out the rest of the backfield.
Basically:
There is an assumption (rule breaker comes later) that there is one receiver to each side of the formation. Assuming it's not empty, you can use a two-digit code to fill out the rest of the backfield.
Evens=left
Odds=right
0/1: #2 slot
2/3: #3 slot
4/5: wings
6/7: inline TEs
8/9: offset FBs
F: inline fullback
Two-digit code has the "heaviest" player as the second digit (run strength).
In order of most "heavy" to less "heavy":
6/7
8/9
4/5
2/3
0/1
All equal: L 1st, R 2nd
Odds=right
0/1: #2 slot
2/3: #3 slot
4/5: wings
6/7: inline TEs
8/9: offset FBs
F: inline fullback
Two-digit code has the "heaviest" player as the second digit (run strength).
In order of most "heavy" to less "heavy":
6/7
8/9
4/5
2/3
0/1
All equal: L 1st, R 2nd
These would be examples of filling out the two-digit formation code (no backfield yet) under those assumptions. If you don't care about who is on/off the ball, the *s don't matter.
Next step is IDing an offset RB, which is why you want run strength as the last digit. If you have a consistent way to tell the run strength, you can make Near/Far calls relative to the strength.
For the purposes of this, we'll call the 1st digit of the code H and the 2nd Y.
For the purposes of this, we'll call the 1st digit of the code H and the 2nd Y.
With the two-digit code (under the right assumptions) you can easily go heaviest to lightest alignment and base the offset back off of the Y (second digit, heaviest alignment). If the back isn't offset, you don't have to tell the back anything.
Examples:
13 Far
57
Examples:
13 Far
57
The exception to these assumptions is when you get a nub (no WR to one side) formation. This is when you're going to need a Flip call (telling that the receivers are opposite of the Y.) You can use "Flop" to signify the traveling WR to be on the ball, if you care.
F=far
N=near
F=far
N=near
Those are really the only tools you need to chart an opposing offense from a formation standpoint (good luck with motion!) It may seem like a lot, but often staffs don't have a common language outside of their own offense and rarely will you cover all bases with your own.
Last notes:
Add G (gun)/U (under center)/P (pistol) if you care.
Anything that doesn't fall under this umbrella (unbalanced, heavy, wildcat, etc.) should probably just be ID'd as unbalanced/heavy/wildcat. They probably only run a few plays from it. Not worth the tendency study.
Add G (gun)/U (under center)/P (pistol) if you care.
Anything that doesn't fall under this umbrella (unbalanced, heavy, wildcat, etc.) should probably just be ID'd as unbalanced/heavy/wildcat. They probably only run a few plays from it. Not worth the tendency study.
More examples:
Flip 27 Near
67
47 Far
Some plays from Stanford/UCF 1st Q
It's worth having a simple, concise way to chart opposing offensive formations, with teams being more formationally varied now, than to have to ask "What do we mutually call this?" every week.
Flip 27 Near
67
47 Far
Some plays from Stanford/UCF 1st Q
It's worth having a simple, concise way to chart opposing offensive formations, with teams being more formationally varied now, than to have to ask "What do we mutually call this?" every week.
