Free AI prompts for football coaches

You're a data analyst for a high school football defensive staff. I've attached a Hudl playlist export (Excel) of [OPPONENT]'s offense. Build me an interactive scouting report as a single HTML artifact.

STEP 1: CLEAN AND CHECK THE DATA FIRST
- Look at every column before doing anything. Tell me in the report's Notes which columns exist and which are missing (gain/loss, personnel, run direction, motion, etc.).
- Use only offensive clips. Split games in the order they appear in the export and label them G1, G2, G3...
- Exclude timeouts and pre-snap / no-play penalties. Keep plays with a penalty on the play in all run/pass splits.
- If there's no gain/loss column, estimate each play's yards from the change in ball spot to the next snap of the same drive, checked against the next down and distance. Touchdowns count the distance to the goal line. Incompletions and interceptions count zero. Plays with a penalty, fumble, or no next snap get no yardage. Report how many snaps couldn't be measured.
- Flag anything that looks inconsistent, such as one game using different formation names (possibly a different tagging staff), untagged formations, or odd plays like possible fakes.

STEP 2: HEADER
Opponent name, number of games, total snaps (runs and passes), offensive TDs, and the export file name and date.

STEP 3: TOP TELLS
6 to 8 cards for the strongest tendencies across all games. Each card has:
- A short label (e.g. "Red zone", "Formation", "Sequence")
- One big stat (e.g. "89% run inside the 20")
- The raw count behind it (e.g. "25 of 28") plus one or two sentences of context
- A one-line "Defend it" coaching point telling my defense what to do
Cover at minimum: overall run/pass, red zone, formation strength to the field vs. boundary, the most run-heavy formation, the most pass-heavy formation, 2nd-down call after a 1st-down run vs. after a 1st-down pass, shot plays/verticals, and 4th-down behavior.
Then a "More keys" list of 6 to 10 shorter one-line findings (screens, rollouts, explosive plays, how they react to blitzes, how they open games, where turnovers happen, 3rd and long runs, etc.).

STEP 4: SITUATIONAL FILTERS
Filter buttons for: Game (All/G1/G2...), Down, Yards to go (1-3, 4-6, 7+), Hash (L/M/R), Play type (Run/Pass), Field position (backed up own 1-20, own 21-50, plus territory opp 49-21, red zone opp 20-goal), and Formation. Show a live snap count and a Reset button. Every table and chart below must re-count from the filtered plays.

STEP 5: SECTIONS (each one responds to the filters)
- Down & distance: run/pass split by situation, with the formations and pass calls they lean on in each.
- Formations: every formation exactly as tagged, snaps, run %, pass %, % of strength set to the field (only counting snaps off a hash), and a G1/G2/G3... column showing usage by game.
- Field position: a chart of every snap at the yard line it was run from, offense driving left to right, one lane per down, run and pass in different colors. Hover or tap a dot to see the play. Nudge dots so they don't overlap.
- Hash & strength: run/pass by hash, and by strength side (field vs. boundary). The field is the wide side of the hash.
- Pass game: pass calls grouped by concept, the routes tagged most (share of pass calls that include each route), and repeat calls.
- 3rd & 4th down: 3rd down by yards to go with conversion rate, and a table of every 4th-down snap.
- Play log: every snap matching the filters, sortable by clicking column headers.

STEP 6: NOTES
- How yards were estimated and how many snaps have no yardage
- Definitions: Success = 40% of needed yards on 1st, 60% on 2nd, a conversion on 3rd or 4th. Explosive = run of 10+ or pass of 15+. Yards per dropback includes sacks and scrambles.
- What was included and excluded, with counts
- What this data can't show (e.g. run direction, schemes, personnel, if untagged)
- Things to double-check on film

RULES
- Every number in the report must be checkable with the filters. Show raw counts next to percentages.
- Label any tendency based on fewer than 8 plays as a small sample.
- Plain coaching language. No filler.
- Clean, readable design with a tab or jump menu for the sections, and it should work on a phone.

You're a data analyst for a high school football offensive staff. I've attached a Hudl playlist export (Excel) of [OPPONENT]'s defense. Build me an interactive scouting report as a single HTML artifact focused on their fronts, blitzes, and coverages.

STEP 1: CLEAN AND CHECK THE DATA FIRST
- Look at every column before doing anything. Tell me in the Notes which defensive tags exist (front, blitz/pressure, blitz name, number of rushers, coverage, pre-snap shell, stunts/slants) and which are missing.
- Use only clips where [OPPONENT] is on defense. Split games in the order they appear in the export and label them G1, G2, G3...
- Exclude timeouts, special teams, and pre-snap / no-play penalties.
- If there's no gain/loss column, estimate yards allowed from the change in ball spot to the next snap of the same drive, checked against the next down and distance. Report how many snaps couldn't be measured.
- Treat any snap with a blitz tag, a blitz name, or 5+ rushers as a pressure. Tell me which rule you used.
- Flag anything inconsistent: different front or coverage names across games (possibly different taggers), untagged coverages, or coverage tags that conflict with the pressure tag (e.g. 6-man pressure tagged Cover 3).

STEP 2: HEADER
Opponent name, number of games, total defensive snaps, overall pressure rate, most-used front, most-used coverage, and the export file name and date.

STEP 3: TOP TELLS
6 to 8 cards for their strongest tendencies across all games. Each card has:
- A short label (e.g. "3rd & long", "Red zone", "Vs trips")
- One big stat (e.g. "71% pressure on 3rd & 7+")
- The raw count behind it (e.g. "22 of 31") plus one or two sentences of context
- A one-line "Attack it" coaching point telling my offense what to call or look for
Cover at minimum: base front, how the front changes vs. 2x2 vs. 3x1 vs. empty, pressure rate by down and distance, pressure in the red zone and backed up, their favorite blitz and when it comes, base coverage, coverage vs. 3x1, what they play when they pressure (man vs. zone behind it), and any front or shell that tips a blitz or coverage.
Then a "More keys" list of 6 to 10 shorter one-line findings (pre-snap shell vs. post-snap rotation, field vs. boundary pressure, stunts, how they react after a big play, what they do in 2-minute or goal line, where they give up explosives, etc.).

STEP 4: SITUATIONAL FILTERS
Filter buttons for: Game, Down, Yards to go (1-3, 4-6, 7+), Hash (L/M/R), Field position (backed up own 1-20 from their offense's view, own 21-50, plus territory, red zone), Offensive formation faced, Front, Pressure (Yes/No), and Coverage. Show a live snap count and a Reset button. Every table and chart below must re-count from the filtered plays.

STEP 5: SECTIONS (each one responds to the filters)
- Fronts: every front as tagged, snaps, % of total, pressure rate from it, run and pass yards allowed per play, and a G1/G2/G3... usage column. Include a front-by-formation table (what front they show vs. each offensive formation).
- Pressure: pressure rate by down and distance, by field position, and by hash. Every blitz name as tagged with how often and in what situations. Number of rushers if tagged. Field vs. boundary pressure if the blitz side is tagged.
- Coverage: every coverage as tagged, % of total, man vs. zone split, coverage by down and distance, coverage vs. 2x2 vs. 3x1 vs. empty, coverage behind pressure, and pre-snap shell vs. post-snap coverage if both are tagged.
- Combos: their most common front + pressure + coverage combinations, with situations and yards allowed.
- Results: yards per play, success rate allowed, and explosives allowed against each front, pressure, and coverage. Show where they're most vulnerable.
- Field position: a chart of every snap at the yard line it was run from, one lane per down, pressure snaps in a different color. Hover or tap a dot to see the play.
- 3rd & 4th down: pressure and coverage by yards to go, with conversion rate allowed.
- Play log: every snap matching the filters, sortable by clicking column headers.

STEP 6: NOTES
- How yards were estimated and how many snaps have no yardage
- The rule used to count a pressure
- Definitions: Success allowed = offense gains 40% of needed yards on 1st, 60% on 2nd, a conversion on 3rd or 4th. Explosive = run of 10+ or pass of 15+.
- What was included and excluded, with counts
- What this data can't show (e.g. individual blitzers, run fits, disguise, if untagged)
- Things to double-check on film, especially coverage tags

RULES
- Every number in the report must be checkable with the filters. Show raw counts next to percentages.
- Label any tendency based on fewer than 8 plays as a small sample.
- Plain coaching language. No filler.
- Clean, readable design with a tab or jump menu for the sections, and it should work on a phone.

You're helping a high school defensive staff build a game-day call sheet. Attached: a Hudl export (Excel) of our opponent's offense, and our defensive call sheet (fronts, coverages, pressures).

Final product: a PRINT-READY PDF file (not a web page), letter landscape, 0.3" margins, for the sideline.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of every front, coverage, pressure and tag on our call sheet, and how a full call is built.
Check for anything unclear: undefined players or labels, pressures with no side (field/boundary/strong/weak), pressures naming players a front doesn't have, missing pairing rules, abbreviations you can't define.
If anything is unclear, STOP. Show the glossary, list numbered questions (one per term, with 2-3 likely answers when helpful), and wait for my answers. Then update the glossary and continue. If I say "skip," leave that term out and list it under "Not used."
If nothing is unclear, say so and continue. Never guess or use other playbooks' terms.

STEP 2: CLEAN THE DATA
- Offensive snaps only. Split games where the play # resets (G1, G2...).
- Drop timeouts and pre-snap penalties. Keep plays with a penalty on the play.
- Clean formation names. If one game uses different names (likely another tagging staff), group them and say so.
- No gain/loss column? Estimate yards from the next snap's ball spot in the same drive. TDs count to the goal line, incompletions zero.
- Group passes: screens, quick, dropback, rollout/play action, shots.
- Field = wide side of the hash. Count how often their strength goes to the field.

STEP 3: PAGE 1, SITUATIONS
One row each: 1st & 10, 2nd & 7+, 2nd & 4-6, 2nd & 1-3, 3rd & 7+, 3rd & 4-6, 3rd & 1-3, 4th down, Backed up (own 1-20), Red zone (opp 20-6), Goal line (opp 5-goal). Last three count every down.
Columns:
1. Situation + label: Strong (67%+), Lean (60-66%) or Balanced, run or pass
2. Run/pass % and counts
3. By hash L/M/R: % and count (e.g. "65% run, 22/34"). Under 5 snaps: count only, no tendency
4. Top 3 run formations with counts
5. Top passes: type counts, then top 3 pass calls with formation and count
6. Watch for & plan: 1-3 sentences of key numbers (yards per carry, explosives, conversions, what follows a 1st-down run), then "Plan:" in one sentence
7. Our calls ON A HASH: 3-4, ranked, first highlighted
8. Our calls MIDDLE OF THE FIELD: 3-4, ranked, first highlighted
Split 4th-down calls into 4th & 1-3 and 4th & 4+. Add direction tags (strong/weak, field/boundary) when a call needs one.

STEP 4: PAGE 2, KEYS
- Formation keys: snaps, tendency, % strength to field, what to expect, 2-3 suggested checks
- Hash tendencies: L/M/R, snaps, run/pass on 1st, 2nd, 3rd down, notes
- Field position: own 1-20, own 21-35, own 36-50, opp 49-36, opp 35-21, opp 20-6, opp 5-goal: snaps, tendency, notes
- Take these away: their 3-5 biggest plays and when
- Sequencing: 2nd down after a 1st-down run vs pass, and every short-yardage snap

STEP 5: PAGE 3, OUR CALLS
Legend from the final glossary, plus the "Not used" list.

RULES
- ONLY calls from our sheet, as clarified. Follow every pairing rule.
- Every number from the data, raw counts next to percentages.
- Plain coaching language.

PRINT DESIGN
- Header every page: opponent, games, snaps, runs/passes, date. Page numbers in footer.
- Min 8 pt font. Bold the first call in each cell.
- Thin stripe per row for tendency strength (dark/light/gray) that reads in black and white.
- Never split a row across pages. Try to fit page 1 on one page; if not, continue with the header row repeated.

You're helping a high school offensive staff build a game plan. I've attached two things: an interactive scouting report on our opponent's defense, and our offensive call sheet with our formations, plays, and tags.

STEP 1: DEFINE OUR VERBIAGE FIRST
Before building anything, read our call sheet and write a glossary of every term on it, grouped by:
- Formations (including what RT and LT mean)
- Motions
- Run plays
- Pass plays (including what coverage each one is best against)
- Route tags
- Call tags (RPO, READ, HOT, MAX, etc.)
- How a full call is built, using our format: Formation + Side + Motion + Play + Tag (e.g. "Trips RT Zip Stick, Z Go")

Define each term in one short line, in plain coaching language. If a term isn't clearly defined on the sheet, or you're not sure what it means, list it under "Needs clarification" and don't use it in the game plan. Don't guess, and don't swap in terms from other playbooks.

STEP 2: BUILD THE GAME PLAN
Build a game plan for the middle of the field (between the 20s) using ONLY formations, motions, plays, and tags from our call sheet. Don't invent new ones.

For each situation below, and for each hash (left, middle, right), give me:
- Their tendency from that spot: front, coverage, and blitz rate, with the raw count (e.g. "14 of 20 blitz")
- Our 3 best calls, ranked, with the best call first, written in our full call format
- One sentence on why the best call fits

Situations: 1st & 10, 2nd & short (1-3), 2nd & medium (4-6), 2nd & long (7+), 3rd & short (1-3), 3rd & medium (4-6), 3rd & long (7+).

Then add separate short sections for red zone, backed up, and 2-minute.

RULES
- Use the "Best vs" column on our call sheet to match pass plays to their coverage.
- Use HOT or MAX tags where they blitz 50% or more.
- Set our formation strength (RT or LT) to the field on each hash, unless their tendencies say otherwise.
- Only add a motion when it has a purpose, such as identifying man vs zone before a pass, or setting up Jet. Say what the motion is for.
- If a situation has fewer than 8 plays, say so and lean on their overall tendencies instead.
- End with 3 pre-snap tells our QB can recognize (front, shell, alignment, or how they react to motion) and what to check to.

STEP 3: OUTPUT
Show it as an interactive HTML artifact with:
- A hash toggle, so I can tap Left, Middle, or Right and see the calls for that hash
- A Glossary tab with the definitions from Step 1, so any coach or player reading the plan knows exactly what each call means
- The "Needs clarification" list at the top of the Glossary, if there's anything on it

You're helping a high school offensive staff build a practice script. Attached: a Hudl export (Excel) of our opponent's defense, and our offensive call sheet (formations, motions, plays, tags).

Final product: a PRINT-READY PDF file (not a web page), letter landscape, for a practice clipboard.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of every formation, motion, play and tag on our call sheet, and how a full call is built.
Check for anything unclear: undefined labels, plays with no "best vs" coverage, tags that don't say who they change, abbreviations you can't define.
Then ask me for our practice plan: periods, minutes, and reps per period. If I don't have one, suggest: Inside Run, 7-on-7, Blitz Pickup, Team.
If anything is unclear, STOP. Show the glossary, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave that term out and list it under "Not used." Never guess or use other playbooks' terms.

STEP 2: CLEAN AND READ THEIR DEFENSE
- Defensive snaps only. Split games where the play # resets.
- Drop timeouts and pre-snap penalties. Clean front, pressure and coverage names.
- Count pressure as any blitz tag, blitz name, or 5+ rushers. Say what rule you used.
- Flag coverage tags that don't fit the pressure (e.g. 6-man pressure tagged Cover 3).
- No gain/loss column? Estimate yards from the next snap's ball spot in the same drive.
- Find their tendencies by down and distance, hash, and field position: front, pressure rate, favorite pressures, coverage, what they play behind pressure, and how they react to motion if tagged.
- Field = wide side of the hash.

STEP 3: BUILD THE SCRIPT
Every rep gets:
1. Rep #
2. Hash (L/M/R)
3. Down & distance
4. Field position (backed up, open field, red zone, goal line)
5. Our call, in our full format
6. Scout look: the exact front, pressure, coverage and alignment the scout team shows, taken from their real tendencies
7. Coaching point (one line)

Rules:
- Weight reps toward what we'll see most. If they play Cover 3 on 60% of 1st downs, about 60% of our 1st-down reps face Cover 3.
- Every pass rep must face a coverage it beats, using our "best vs" column.
- Rotate hashes so each key look is repped from the left, middle and right. Set our strength to the field unless their tendencies say otherwise.
- Put HOT or MAX tags on reps that face their top pressures.
- Use motion only with a purpose (ID man vs zone, set up a play) and say why.
- Include each period's goal at the top of the period.
- Situations to cover across the script: 1st & 10, 2nd & short/medium/long, 3rd & short/medium/long, red zone, and goal line.
- No more reps than the plan allows.

STEP 4: SCOUT CARDS
After the script, a scout card for each rep: rep #, hash, D&D, and a simple diagram or text of the defensive look (front, who blitzes, coverage). One card per box, large enough to hold up in the huddle.

STEP 5: SUMMARY PAGE
- Their top 5 tendencies we're preparing for, with raw counts
- Rep count by coverage and pressure, compared to how often they actually show each
- Calls we repped most, and any situation we didn't cover

RULES
- ONLY plays from our call sheet, as clarified. Every number from the data, raw counts next to percentages.
- Plain coaching language.

PRINT DESIGN
- Header every page: opponent, practice day, total time and total reps. Page numbers in footer.
- Script table with columns: Rep, Hash, D&D, Field, Call, Scout Look, Coaching Point.
- Period headers in a shaded bar. Min 9 pt font. Bold the call.
- Never split a rep across pages. Readable in black and white.

You're helping a high school defensive staff build a practice script. Attached: a Hudl export (Excel) of our opponent's offense, and our defensive call sheet (fronts, coverages, pressures, tags).

Final product: a PRINT-READY PDF file (not a web page), letter landscape, for a practice clipboard.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of every front, coverage, pressure and tag on our call sheet, and how a full call is built.
Check for anything unclear: undefined players or labels, pressures with no side (field/boundary/strong/weak), pressures naming players a front doesn't have, missing pairing rules, abbreviations you can't define.
Then ask me for our practice plan: periods, minutes, and reps per period. If I don't have one, suggest: Inside Run, 7-on-7, Pressure, Team.
If anything is unclear, STOP. Show the glossary, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave that term out and list it under "Not used." Never guess or use other playbooks' terms.

STEP 2: CLEAN AND READ THEIR OFFENSE
- Offensive snaps only. Split games where the play # resets.
- Drop timeouts and pre-snap penalties. Clean formation names. If one game uses different names (likely another tagging staff), group them and say so.
- No gain/loss column? Estimate yards from the next snap's ball spot in the same drive.
- Group passes: screens, quick, dropback, rollout/play action, shots.
- Find their tendencies by down and distance, hash, and field position: run/pass, top formations, top runs and passes from each formation, strength to the field or boundary, motion, and what they call on 2nd down after a 1st-down run vs a pass.
- Find their 3-5 biggest plays.
- Field = wide side of the hash.

STEP 3: BUILD THE SCRIPT
Every rep gets:
1. Rep #
2. Hash (L/M/R)
3. Down & distance
4. Field position (backed up, open field, red zone, goal line)
5. Scout look: the formation, strength, motion and play the scout offense runs, taken from their real tendencies
6. Our call, in our full format
7. Coaching point (one line: the key, the tell, or the fit)

Rules:
- Weight reps toward what we'll see most. If they run 70% from a formation on 1st down, about 70% of our 1st-down reps vs that formation are runs.
- Every rep's call must fit the play: run calls vs runs, coverage and pressure that take away the pass concept. Follow every pairing rule on our sheet.
- Rep each of their biggest plays at least once, with the call that takes it away.
- Rotate hashes so each key formation is repped from the left, middle and right, with the strength set the way they actually set it.
- Include at least one rep of each formation tell, so players learn to recognize it.
- Include each period's goal at the top of the period.
- Situations to cover across the script: 1st & 10, 2nd & short/medium/long, 3rd & short/medium/long, red zone, and goal line.
- No more reps than the plan allows.

STEP 4: SCOUT CARDS
After the script, a scout card for each rep: rep #, hash, D&D, and a simple diagram of the offensive formation with the play drawn (run path or routes), plus motion if any. One card per box, large enough to hold up in the scout huddle.

STEP 5: SUMMARY PAGE
- Their top 5 tendencies we're preparing for, with raw counts
- Rep count by formation and run/pass, compared to how often they actually show each
- Our calls repped most, and any situation or formation we didn't cover

RULES
- ONLY calls from our call sheet, as clarified. Every number from the data, raw counts next to percentages.
- Plain coaching language.

PRINT DESIGN
- Header every page: opponent, practice day, total time and total reps. Page numbers in footer.
- Script table with columns: Rep, Hash, D&D, Field, Scout Look, Our Call, Coaching Point.
- Period headers in a shaded bar. Min 9 pt font. Bold the call.
- Never split a rep across pages. Readable in black and white.

You're my halftime assistant. I'm a high school defensive coach. Our opponent's scouting report and our defensive call sheet are in this project.

At halftime I'll paste a first-half chart of their offense. Each row is one snap: quarter, down, distance, yard line (minus = their side of the 50, plus = ours), hash, formation, strength, motion, run/pass, play type, result, yards, and our call.

Answer FAST and SHORT. I'm reading this on my phone walking to the locker room.
- Plain text only. No files, no code, no tables, no charts.
- Don't show your work or explain your method.
- Under 200 words total.
- Every claim needs a raw count (e.g. "9 of 11 runs").
- Use ONLY calls from our call sheet, in our format, and follow its pairing rules.
- If the chart has blanks, use what's there. Never invent snaps.
- If something changed from the scouting report, say so.

Use exactly this format:

FIRST HALF: [snaps], [run %], [yards per play]

WHAT'S NEW: 1-2 things they're doing that the scouting report didn't show

TOP 3 TENDENCIES:
1.
2.
3.

WHAT'S HURTING US: the call or calls giving up the most yards, and what's beating them

ADJUSTMENTS:
1. [situation]: [call] because [reason]
2.
3.

FIRST SERIES, 2ND HALF:
1st down: [call]
2nd down: [call]
3rd down: [call]

You're my halftime assistant. I'm a high school offensive coach. Our opponent's defensive scouting report and our offensive call sheet are in this project.

At halftime I'll paste a first-half chart of their defense against our plays. Each row is one snap: quarter, down, distance, yard line (minus = our side of the 50, plus = theirs), hash, our formation, our play, run/pass, their front (3, 4 or 5 down), pressure (none, or who came: LB, DB, edge), their shell (1-high, 2-high, 0-high), result, and yards.

Answer FAST and SHORT. I'm reading this on my phone walking to the locker room.
- Plain text only. No files, no code, no tables, no charts.
- Don't show your work or explain your method.
- Under 200 words total.
- Every claim needs a raw count (e.g. "7 of 9 snaps").
- Use ONLY plays, formations and tags from our call sheet, in our format. Match pass plays to the shell using our "Best vs" column.
- If the chart has blanks, use what's there. Never invent snaps.
- If something changed from the scouting report, say so.

Use exactly this format:

FIRST HALF: [snaps], [yards per play], [run yards per carry], [pass yards per attempt]

WHAT'S NEW: 1-2 things their defense is doing that the scouting report didn't show

HOW THEY'RE PLAYING US:
1. [front and shell they show most, with counts]
2. [when and how they pressure, with counts]
3. [how they adjust to our formations or motion]

WHAT'S WORKING: our 2 best plays so far, with yards per play
WHAT'S NOT: our 1-2 worst plays, and what's beating them

ADJUSTMENTS:
1. [situation]: [play call] because [reason]
2.
3.

FIRST SERIES, 2ND HALF:
1st down: [call]
2nd down: [call]
3rd down: [call]

You're helping a high school offensive staff self-scout. Attached: a Hudl export (Excel) of OUR offense this season, and our offensive call sheet (formations, motions, plays, tags).

Goal: find what an opposing defensive coordinator sees when they scout us, then tell us what to CHANGE, TAKE OUT and ADD before our next game.

Final product: a PRINT-READY PDF file (not a web page), letter landscape, 2-3 pages.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of our formations, motions, plays and tags, and how a full call is built. If anything is unclear, STOP, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave it out. Never guess or use other playbooks' terms.

STEP 2: CLEAN THE DATA
- Offensive snaps only. Split games where the play # resets (G1, G2...).
- Drop timeouts and pre-snap penalties. Clean formation and play names.
- Split each call into formation, side, motion, base play and tag.
- Success: 40% of needed yards on 1st down, 60% on 2nd, a conversion on 3rd or 4th. Explosive: run 10+, pass 15+.
- Field = wide side of the hash.

STEP 3: SCOUT US LIKE THEY WOULD
- Run/pass by down and distance, hash and field position.
- Each formation: run/pass, top plays, strength to field or boundary.
- Motion: what follows each motion.
- Sequencing: 2nd down after a 1st-down run vs pass. Every short-yardage snap.
- Drift: compare the first half of our season to the second half. Are we getting more predictable?
- Any formation, motion, hash or situation where one play type is 75%+ on 8+ snaps is a TELL.

STEP 4: GRADE OUR PLAYS
For each base play: calls, yards per play, success rate, explosives, and which formations and situations it works or fails in.

STEP 5: CHANGE, TAKE OUT, ADD
CHANGE: plays that work but are predictable or used in the wrong spot. Say what to change (formation, side, motion, down) and why.
TAKE OUT: plays with low success on 8+ calls, or plays that only run from one tell. Say what replaces them.
ADD: tendency breakers. For each TELL, a play from our call sheet that looks the same but does the opposite (pass from our run look, run from our pass look, a different play off the same motion). Also plays that work but are under-used.
Give 3-5 items in each list, ranked by impact. Every item needs a raw count (e.g. "Tight: 72 of 85 runs").

PDF LAYOUT
Page 1: WHAT THEY'LL SEE. Their call sheet on us: our top 6 tells, each with the count and the defense they'd call against it.
Page 2: CHANGE / TAKE OUT / ADD, three columns, ranked.
Page 3: Play grades table, drift (first half vs second half of the season), and data notes.

RULES
- ONLY plays from our call sheet. Every number from the data, raw counts next to percentages.
- Fewer than 8 snaps: show the count, but don't call it a tell or grade it.
- Plain coaching language. Min 9 pt font. Readable in black and white. Header with team, games, snaps and date on every page.

You're helping a high school defensive staff self-scout. Attached: a Hudl export (Excel) of OUR defense this season, and our defensive call sheet (fronts, pressures, coverages, tags).

Goal: find what an opposing offensive coordinator sees when they scout us, then tell us what to CHANGE, TAKE OUT and ADD before our next game.

Final product: a PRINT-READY PDF file (not a web page), letter landscape, 2-3 pages.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of our fronts, pressures, coverages and tags, and how a full call is built. If anything is unclear, STOP, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave it out. Never guess or use other playbooks' terms.

STEP 2: CLEAN THE DATA
- Defensive snaps only. Split games where the play # resets (G1, G2...).
- Drop timeouts and pre-snap penalties. Clean front, pressure and coverage names.
- Rebuild each snap's full call (front + pressure + coverage).
- Stop = the offense did NOT gain 40% of needed yards on 1st down, 60% on 2nd, or convert on 3rd or 4th. Explosive allowed: run 10+, pass 15+.
- Field = wide side of the hash.

STEP 3: SCOUT US LIKE THEY WOULD
- Front, pressure rate and coverage by down and distance, hash and field position.
- Each front: what coverage it shows behind it. Each pressure: what coverage it plays.
- What we call vs each of their formations (especially Empty and Trips).
- Who blitzes: is one player most of our pressure?
- Drift: first half of our season vs second half. Are we getting more predictable?
- Any front, situation or formation where one call, coverage or pressure choice is 75%+ on 8+ snaps is a TELL.

STEP 4: GRADE OUR CALLS
For each call: snaps, yards per play allowed, stop rate, explosives and TDs allowed, yards per carry and per pass against it, and what beats it (runs, screens, quick, play action, shots).

STEP 5: CHANGE, TAKE OUT, ADD
CHANGE: calls that work but are predictable or used in the wrong spot. Say what to change and why.
TAKE OUT: calls with a low stop rate or high yards allowed on 8+ snaps. Say what replaces them. If fewer than 3 qualify, say so.
ADD: tendency breakers. For each TELL, a call from our sheet that looks the same pre-snap but plays different (zone from our man look, pressure from our two-high look, a different coverage behind a front). Also calls that work but are under-used.
Give 3-5 items in each list, ranked by impact. Every item needs a raw count (e.g. "Bear: Cover 1 on 69 of 69").

PDF LAYOUT
Page 1: WHAT THEY'LL SEE. Their call sheet on us: our top 6 tells, each with the count and the play they'd call to beat it.
Page 2: CHANGE / TAKE OUT / ADD, three columns, ranked.
Page 3: Call grades table, drift (first half vs second half), and data notes.

RULES
- ONLY calls from our call sheet. Every number from the data, raw counts next to percentages.
- Fewer than 8 snaps: show the count, but don't call it a tell or grade it.
- Plain coaching language. Min 9 pt font. Readable in black and white. Header with team, games, snaps and date on every page.

You're helping a high school defensive staff prepare for a REMATCH. Attached:
1. SCOUT: a Hudl export of our opponent's offense from the games we scouted before we played them the first time
2. VS US: a Hudl export of their offense against us in our first game, with our defensive call on each snap
3. SINCE (optional): a Hudl export of their games after they played us
4. Our defensive call sheet

Goal: compare what we expected to what they actually did against us, find what they changed for us, and build our plan for the rematch.

Final product: a PRINT-READY PDF file (not a web page), letter landscape, 3 pages.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of our fronts, pressures, coverages and tags, and how a full call is built. If anything is unclear, STOP, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave it out. Never guess or use other playbooks' terms.

STEP 2: CLEAN ALL FILES THE SAME WAY
- Offensive snaps only. Drop timeouts and pre-snap penalties.
- Use the same formation and play names across every file. If a name differs between files, match them and list the matches.
- No gain/loss column? Estimate yards from the next snap's ball spot in the same drive.
- Success: 40% of needed yards on 1st, 60% on 2nd, a conversion on 3rd or 4th. Explosive: run 10+, pass 15+.
- Field = wide side of the hash.

STEP 3: EXPECTED vs WHAT THEY DID TO US
For each, show SCOUT vs VS US side by side, with raw counts:
- Run/pass by down and distance, hash and field position
- Formations: how often, run/pass, strength to field or boundary
- Top plays, motion, and 2nd-down sequencing
- Formations or plays they showed us that weren't in the scout (NEW FOR US)
- Tendencies they broke against us (a formation that was 75%+ one way in the scout and wasn't vs us)
Flag any change of 20+ points on 8+ snaps.

STEP 4: HOW THEY ATTACKED OUR CALLS
- For each of our calls in game 1: snaps, yards per play, success allowed, explosives and TDs allowed, and what beat it.
- Which of our calls did they seem to target (more of a play after it worked)?
- First half vs second half of game 1: what they changed at halftime, and whether it worked.

STEP 5: SINCE WE PLAYED (if the SINCE file is attached)
- What's new since our game: formations, plays, personnel or tendencies.
- Did they keep what worked against us?

STEP 6: THE REMATCH PLAN
- WHAT THEY'LL TRY: their 5 most likely plans for us, ranked. Weight what worked against us most, but expect them to keep adjusting.
- KEEP: our calls that won in game 1, and when to use them.
- FIX: our calls that got beat, and what replaces them.
- NEW LOOKS: calls from our sheet we didn't show them in game 1, to break the tendencies they saw from us.
- Situation call list: best 2-3 calls for 1st & 10, 2nd & short/medium/long, 3rd & short/medium/long, red zone and goal line.

PDF LAYOUT
Page 1: WHAT CHANGED. Scout vs game 1, side by side, with the NEW FOR US list and the biggest changes.
Page 2: HOW THEY ATTACKED US. Our call grades from game 1, what beat us, and their halftime changes (plus the SINCE section if attached).
Page 3: THE REMATCH PLAN. What they'll try, Keep / Fix / New looks, and the situation call list.

RULES
- ONLY calls from our call sheet. Follow every pairing rule.
- Every number from the data, raw counts next to percentages. Always label which file a number comes from (SCOUT, VS US, SINCE).
- One game is a small sample. Under 8 snaps: show the count, but don't call it a tendency.
- Plain coaching language. Min 9 pt font. Readable in black and white. Header with opponent, games in each file, snaps and date on every page.

You're helping a high school offensive staff prepare for a REMATCH. Attached:
1. SCOUT: a Hudl export of our opponent's defense from the games we scouted before we played them the first time
2. VS US: a Hudl export of their defense against us in our first game, with our offensive call on each snap
3. SINCE (optional): a Hudl export of their defense in games after they played us
4. Our offensive call sheet

Goal: compare what we expected to what their defense actually did against us, find what they changed for us, and build our plan for the rematch.

Final product: a PRINT-READY PDF file (not a web page), letter landscape, 3 pages.

STEP 1: CHECK OUR VERBIAGE, THEN STOP AND ASK
Write a short glossary of our formations, motions, plays and tags, and how a full call is built. If anything is unclear, STOP, list numbered questions (2-3 likely answers when helpful), and wait. If I say "skip," leave it out. Never guess or use other playbooks' terms.

STEP 2: CLEAN ALL FILES THE SAME WAY
- Defensive snaps only. Drop timeouts and pre-snap penalties.
- Use the same front, pressure and coverage names across every file. If a name differs between files, match them and list the matches.
- Count pressure as any blitz tag, blitz name, or 5+ rushers.
- No gain/loss column? Estimate yards from the next snap's ball spot in the same drive.
- Success: 40% of needed yards on 1st, 60% on 2nd, a conversion on 3rd or 4th. Explosive: run 10+, pass 15+.
- Field = wide side of the hash.

STEP 3: EXPECTED vs WHAT THEY DID TO US
For each, show SCOUT vs VS US side by side, with raw counts:
- Front, pressure rate, favorite pressures and coverage by down and distance, hash and field position
- What coverage they play behind pressure
- How they lined up vs each of our formations, and how they reacted to our motion
- Fronts, pressures or coverages they showed us that weren't in the scout (NEW FOR US)
- Tendencies they broke against us (something that was 75%+ in the scout and wasn't vs us)
Flag any change of 20+ points on 8+ snaps.

STEP 4: HOW THEY DEFENDED OUR PLAYS
- For each of our base plays in game 1: calls, yards per play, success rate, explosives, and what they were in when it worked and when it didn't.
- Which of our plays did they take away, and how?
- First half vs second half of game 1: what they changed at halftime, and whether it worked.

STEP 5: SINCE WE PLAYED (if the SINCE file is attached)
- What's new in their defense since our game.
- Did they keep what worked against us?

STEP 6: THE REMATCH PLAN
- WHAT THEY'LL TRY: their 5 most likely plans to stop us, ranked. Weight what worked against us most, but expect them to keep adjusting.
- KEEP: our plays that won in game 1, and when to call them.
- FIX: our plays they took away, and what replaces them (use our "best vs" column).
- NEW LOOKS: formations, motions, plays and tags from our sheet we didn't show them in game 1, to break the tendencies they saw from us.
- Situation call list: best 2-3 calls for 1st & 10, 2nd & short/medium/long, 3rd & short/medium/long, red zone and goal line, in our full call format.

PDF LAYOUT
Page 1: WHAT CHANGED. Scout vs game 1, side by side, with the NEW FOR US list and the biggest changes.
Page 2: HOW THEY DEFENDED US. Our play grades from game 1, what stopped us, and their halftime changes (plus the SINCE section if attached).
Page 3: THE REMATCH PLAN. What they'll try, Keep / Fix / New looks, and the situation call list.

RULES
- ONLY plays from our call sheet. Every number from the data, raw counts next to percentages. Always label which file a number comes from (SCOUT, VS US, SINCE).
- One game is a small sample. Under 8 snaps: show the count, but don't call it a tendency.
- Plain coaching language. Min 9 pt font. Readable in black and white. Header with opponent, games in each file, snaps and date on every page.

You're helping a high school football coach turn a scouting report into a quiz for players. Attached: our scouting report on this week's opponent.

Final product: an interactive HTML quiz players can open on their phones, as one self-contained file.

STEP 1: CHECK BEFORE YOU BUILD
Read the report, then ask me in one short message:
1. Is this quiz for our offense or our defense?
2. Our team name and colors (or use navy and gold).
3. How many questions (default 8).
If any term in the report is unclear, ask about it here too. Never guess.

STEP 2: PICK THE QUESTIONS
- Use ONLY tendencies from the report. Never invent a number.
- Only use tendencies with 8+ snaps behind them, and pick the strongest ones (75%+ if possible).
- Mix the types: formation tells, motion, hash and field side, down and distance, sequencing (what comes after a 1st-down run), red zone, and their biggest plays.
- Write each question as a game situation a player would see: down, distance, where the ball is, the hash, and the formation.
- 4 answer choices. One right answer, three that sound reasonable. Vary which letter is correct.
- Plain language a 15-year-old understands. No coaching jargon unless it's in our call sheet or the report.

For each question include:
- The situation (down, distance, ball on, hash, formation)
- The question
- 4 choices and the right answer
- A one-line coaching point: what the player should DO about it
- The proof from film, as a raw count (e.g. "31 of 37 runs")

STEP 3: BUILD THE QUIZ
- Start screen: quiz title, number of questions, optional name and jersey number box, Start button.
- Each question: a scoreboard bar (down, to go, ball on), a small field drawing showing which hash the ball is on and which side is the field (wide side), the formation name, then the question and 4 big tap-friendly answer buttons.
- After each answer: lock the choices, show right (green) or wrong (red), the correct answer, the coaching point and the film count, then a Next button.
- Progress bar showing right and wrong answers so far.
- Results screen: score, a short verdict (8/8 = game ready), a list of missed questions with the right answers, a "Take it again" button and a "Retry only the ones I missed" button.
- Remember each player's best score on their phone (localStorage, wrapped in try/catch).

DESIGN
- Mobile first, big text, thumb-sized buttons, works in light and dark mode.
- Our team colors. Clean and simple, like a scoreboard.
- One self-contained HTML file: CSS and JavaScript inside, no outside images.
- Footer: opponent name and "Built from our scouting report."

OPTIONAL (only if I ask): a Google Apps Script that builds the same quiz as a self-grading Google Form, with name and jersey number questions, 1 point per question, feedback on every answer, and a linked results sheet, so coaches can see every player's score.

You're helping a high school defensive staff build this week's "last play predictor" for game night. Attached: a Hudl export (Excel) of THIS WEEK'S opponent's offense, and our defensive call sheet.

How it works: after each whistle we enter what they just did. The tool moves the down and distance for us and predicts their next play before they break the huddle. Formation is handled by checks our players make, not the press box.

Final product: one self-contained HTML file that works on a tablet or phone with NO internet once it's open. All snap data inside the file. No outside fonts, images or libraries. Title it "[Opponent] Last-Play Predictor."

STEP 1: CHECK FIRST, THEN STOP AND ASK
Write a short glossary of our fronts, pressures, coverages and pairing rules. Then tell me:
- The opponent name, games and snaps in the file
- Which way the yard line runs, and whether there's a gain/loss column
- How you'll split drives (play # gaps, game breaks)
- Formations you'd merge (typos, different names for the same thing)
- Any unclear term on our call sheet
Ask numbered questions with 2-3 likely answers, and wait. Never guess.

STEP 2: PREP THE DATA
- Offensive snaps only. Drop timeouts and pre-snap penalties.
- Gain per snap: the gain/loss column, or the next snap's ball spot in the same drive. TD = to the goal line. Incomplete = 0.
- Each snap stores: down, distance, field position, hash, formation, run or pass, play name, and THE PLAY BEFORE IT in the same drive (run or pass, and its result: 10+, 4-9, 1-3, 0 or loss, incomplete, or start of drive), plus the play two back.

STEP 3: PREDICTION
- Match the next snap against their snaps on the same down. Need 8+ matches. Widen one step at a time: drop hash, field position, exact result (keep good vs bad), result, distance, then last play. Show what was ignored.
- Run % and pass % with raw counts, a confidence badge (High 15+, Medium 8-14, Low under 8), and their top 3 plays in matching snaps.

STEP 4: BACKTEST (at the top)
Predict every old snap from all the others. Show: % right using the last play; % right when it leans 75%+ (with the count); % right with down and distance only; % right always guessing their most common play type. Be honest if it's not much better, and tell me where it's strongest.

STEP 5: OUR CALL
Best call and a backup from ONLY our call sheet, each with a one-line reason. Follow every pairing rule. Use our short-yardage, red-zone and goal-line calls there. Add formation checks for their top formations in the matching snaps (8+ snaps only), e.g. "vs Empty: Odd 4."

STEP 6: DRIVES
- On open, a sheet asks where their FIRST drive starts: quick buttons (Their 10 to Our 20), a Their/Our toggle with an exact yard line box, and the hash. Then 1st & 10.
- An "End drive" button: Punt, Turnover, Touchdown, Field goal, Turnover on downs, End of half.
- Auto-end on a logged TD, turnover, or failed 4th down. On 4th down, remind me to tap End drive if they kick.
- Between drives: the prediction shows "Their offense is off the field," the drive summary, and a big "Start their next drive" button that asks for the new spot and hash. Gray out the play buttons so nobody logs by accident.

STEP 7: GAME-NIGHT FLOW (3 taps)
1. "Ran it" or "Threw it"
2. Yards: Incomplete, Sack, -3, 0, +2, +4, +6, +8, +12, +20, TD, Turnover, plus an exact box
3. Next snap's hash (logs the play). The tool updates down, distance and ball spot.
Also: Fix down & distance (penalties) and Undo (works on drive starts and ends too). Tonight's snaps count double. Log grouped by drive: start spot, plays, how it ended, each play and whether the lean was right, and the running hit rate.

DESIGN
Tablet: inputs left, prediction right. Phone: prediction on top. Big tap buttons, sheets that slide up for drive start and end, huge run % and pass % readable at arm's length, light and dark mode. Footer: "A probability, not a promise."

Before finishing, play 2 full drives through the flow and tell me the results.