You Don't Need Full Corsi to Track Shot Attempts

Corsi — a team's shot-attempt differential at 5-on-5 — is an NHL analytics stat, built for a level where every shift and matchup is tracked by a full staff. At the youth level, chasing the exact pro-style number usually isn't worth the overhead. What actually helps a parent or coach is simpler: how many shots is this player getting on net, missing, or having blocked, game after game. Ice IQ tracks exactly that, per player, without a stopwatch or a spreadsheet.

Shot-by-Shot Logging

Log shots on goal and missed shots as the game happens, and add an action for blocked attempts with a custom template — the same raw actions Corsi is built from.

Per-Player, Per-Game

See shot activity broken down by game and rolled up across a season, instead of one aggregate team number.

AI Coach Turns It Into Advice

Rather than a raw shot-attempt percentage, the AI coach explains what the numbers actually mean for that player's next game.

Built for Youth Rosters

No dedicated stats staff required — one parent, player, or coach can log a full roster from their phone.

Corsi, Fenwick, and individual shot attempts

Corsi counts every shot attempt: shots on goal, shots that miss the net, and shots that get blocked. For a team, Corsi For (CF) is the attempts you take and Corsi Against (CA) is the attempts you allow, usually counted at even strength. Corsi For percentage (CF%) is CF divided by CF plus CA — above 50% generally means your team had the puck more than the opponent did.

Fenwick is the same idea without blocked shots. Individual Corsi (iCF) is simply the shot attempts one player takes, and that's the part that's realistic to track from the stands.

A worked example

Say you're tracking one forward. In a game they have 4 shots on goal, 3 shots that miss the net, and 2 shots blocked by a defender. Their individual shot attempts are 4 + 3 + 2 = 9. Only 4 of those 9 reached the goalie — about 44% — which tells you something the goal column doesn't: they're getting plenty of looks, but more than half aren't getting through.

That split is where the coaching is. A lot of blocked shots usually means shooting into bodies; a lot of misses often means rushed shots or poor angles. Both are fixable, and both are invisible if you only count goals.

Why team Corsi is hard at the youth level

Team Corsi needs every attempt for and against, for both teams, on every shift, usually split by game strength. NHL teams have staff and tracking systems for that. One parent in the stands can't do it reliably, and youth games are short enough that the sample is small anyway.

Individual shot attempts avoid both problems: one player, one set of numbers, and a sample that grows every game.

Tracking shot attempts in Ice IQ

The default forward template already includes shots on goal and missed shots. To count shots that get blocked as well, add an action for it in the template editor (custom templates are a Premium feature). Don't reuse the defenseman template's "Blocked Shot" — that one counts shots the player blocked, not attempts of theirs that were blocked.

One note on scoring: Ice IQ subtracts a point from a forward's game score for a missed shot, since it usually gives the puck away. For shot-attempt counting, a missed shot still counts as an attempt, so look at the counts rather than the score when you're measuring volume.

Why season trends matter more than single games

Frequently Asked Questions

What is Corsi, in plain terms?

It's a shot-attempt differential — shots on goal, missed shots, and blocked shots for a team versus against — used in the NHL as a rough proxy for puck possession.

Does Ice IQ calculate an official Corsi rating?

No. Ice IQ tracks the underlying actions per player — shots on goal and missed shots out of the box, plus blocked attempts if you add them to a custom template — which is the practical, youth-level version of what Corsi measures at the team level.

Why not just track full team Corsi at the youth level?

It requires tracking every shot attempt for both teams at 5-on-5, which needs a dedicated tracker per game. Per-player shot logging gives a parent or coach useful signal without that overhead.

Is this useful without an analytics background?

Yes — that’s the point. The AI coach explains what the logged shots mean instead of leaving you to interpret a raw stat.