For every confirmed shot on goal, record the time, save or goal, shot origin, and where the puck reached the goalie or crossed the goal plane. Keep misses and blocks separate. Use optional tags such as screen, rebound, rush, or lateral pass only when the video clearly supports them.
The four fields that belong in a standard tag
Event time
Mark the moment the puck reaches the goalie or enters the net. An editable timestamp matters because an automated suggestion may be close without being frame-perfect.
Outcome
Choose save or goal for shots on goal. Track misses, posts, and blocked attempts separately if they are useful to you, but do not place them in save-percentage calculations.
Shot origin
Use a consistent rink map with broad zones. Pick the last meaningful shooting location—not the location of an earlier pass and not a point made artificially precise by an unclear angle.
Net location
Mark where the puck crossed the goal plane or reached the goalie. If the puck is hidden by traffic or poor video, use an unknown option rather than guessing.
Use optional detail only when it helps
A complex mode can add visible context such as screen, rebound, deflection, rush, breakaway, or lateral pass. These tags are valuable for filtering clips, but forcing every field on every play makes mobile tagging slower and increases inconsistent guesses.
| Mode | Recommended fields | Best for |
|---|---|---|
| Standard | Time, outcome, shot origin, net location | Fast, repeatable review of every game |
| Detailed | Standard fields plus selected context and a note | Answering a specific coaching or development question |
| Uncertain event | Time, outcome if clear, and unknown for hidden fields | Preserving evidence without manufacturing precision |
Quality checks before trusting a shot map
- Every event opens to the correct moment in the video.
- Saves plus goals match the displayed shots on goal.
- Misses and blocked shots are not counted as saves.
- Unclear locations are marked unknown instead of forced into a zone.
- The same zone definitions are used from game to game.
- Any apparent pattern can be opened as a group of clips.
How to interpret a shot map
A shot map describes the events you tagged. It can reveal where the goalie faced volume, where goals entered, or which clips deserve a second look. It cannot independently measure shot difficulty or diagnose the cause of a goal.
Start with counts, not colours. If a net region shows two goals on three shots, the low percentage may be worth reviewing, but it is still a three-shot sample. Open all three clips before deciding what question to ask next.
Common questions
Where exactly should I mark the shot origin?
Use the location of the puck when it was meaningfully released toward the goal. If a deflection changes the play and your system supports it, keep the original shot and mark the visible deflection as context.
Should I tag every missed shot?
You can when team shot volume or pressure is relevant, but keep misses outside shots-on-goal and save-percentage totals. For a fast goalie review, confirmed saves and goals are the essential events.
What if I cannot see where the puck went?
Do not guess. Mark the field unknown, leave a short note if needed, and preserve the clip. Honest uncertainty protects the rest of the report.
Build a shot map from a real game.
Goalie Vision gives you a fast standard workflow and optional detail when you need it. Your first complete game is free, with no credit card required.
Track your first game free