A useful goalie game report includes game details, completeness and confidence notes, saves and goals with the raw shot count, location views, clips for every event, a few carefully worded observations, and one specific question or practice focus. It should also state what the footage cannot prove.
Seven parts of a strong game report
Game identity
Team, opponent, date, season, and result give the report a stable place in the goalie’s history. These fields should remain editable when a schedule changes or the original entry is wrong.
Completeness and confidence
State whether the complete game was reviewed and flag any missing periods, obstructed video, or uncertain events. A transparent partial report is better than a complete-looking report built on missing footage.
Core results
Show saves, goals, total shots on goal, and save percentage together. The raw counts keep the size of the sample visible.
Location views
Map shot origin and net location using consistent zones. These views help the reader find relevant events; they should not be presented as an automatic technical diagnosis.
Event clips
Every confirmed save and goal should link to the corresponding moment, with enough context before and after the event to understand the play.
Observed patterns
Use bounded language: “Three of four screened shots produced rebounds” is clearer and more defensible than “rebound control is weak.” Link the reader directly to those clips.
One next step
End with one question, review set, or possible practice focus that the goalie can bring to a qualified coach. Avoid producing a long generic list of corrections.
Use language that matches the evidence
| Instead of | Prefer | Why |
|---|---|---|
| “You struggle high glove.” | “Two goals entered high glove on three tagged shots to that region in this game.” | States the sample and avoids a broad diagnosis |
| “Bad rebound control.” | “These four clips produced rebounds into the slot; ask your coach what they see.” | Connects the observation to reviewable evidence |
| “Work on positioning.” | “Compare depth on these two lateral plays with your coach.” | Creates a specific, answerable question |
| “Great game.” | “24 saves on 26 tagged shots; the complete report and clips are here.” | Preserves the evidence behind the summary |
Before you share the report
- Team, opponent, date, season, and result are correct.
- The report says whether the complete game was reviewed.
- Saves plus goals equal the total shots on goal.
- Each event opens to the correct clip.
- Every stated pattern includes a count or sample size.
- The sharing permission and audience are appropriate.
- The final takeaway is specific enough to discuss with a coach.
How reports can help over time
One report captures one game. A series of consistently tagged reports can make it easier to compare similar situations, revisit coaching questions, and see whether the mix of shots and outcomes is changing. Keep definitions stable and resist combining games with different levels of completeness.
Common questions
Should I send a game report to my goalie coach?
Yes, when the goalie and coach find it useful. Make the ask small: share the report and one specific question, rather than expecting the coach to interpret an entire dashboard without context.
Should a report include goals against?
Yes. A complete review includes both saves and goals. If you publish a separate highlight reel, keep the full report available privately for learning.
Can I compare reports from different games?
Yes, cautiously. Confirm that each game is complete, tagged with the same definitions, and accompanied by raw counts. Changes in opponents, team play, and shot environment remain important context.
Build your first complete game report.
Upload one recording, confirm the shot moments, and keep the numbers connected to the clips. Your first complete Goalie Vision game is free.
Create your first report free