How to Scout a Faceoff Specialist's Tendencies

Most first-time scouts try to watch an entire game and take notes on everything at once — the wing play, the ground-ball battle, the restart. That's how you end up with a page of scattered observations and no actual plan. Faceoff scouting works better in reverse: isolate every clip of the specialist you're facing at the exact moment of the whistle, and only the whistle. Everything else — what happens after possession is decided — is a separate problem.

In practice, that means pulling 15–25 reps minimum from recent film, cut down to just the stance, the clamp or rake, and the first two seconds after. If you only have one game of film on an opponent, that's still enough to spot a pattern; it just won't be a reliable one yet.

It's tempting to build an enormous taxonomy of every possible faceoff technique. In practice, three categories cover almost everything a coach needs to build a plan: the first move (clamp, rake, jump/possession counter, or a laned exit), the exit direction (which way the ball goes once he wins it), and the counter he goes to when his first move fails. Everything else is detail you can add later once the pattern is established.

The goal isn't a taxonomy for its own sake — it's a distribution. "He clamps 70% of the time, rakes the rest" is a plan. "He does a lot of different things" is not.

The move a specialist makes is only half the read. The other half is what triggers it — his own whistle timing, his stance width, where his top hand sits before the whistle. A specialist who telegraphs a rake with a wider stance, or a clamp with a specific hand placement, is giving your specialist a real, actionable tell — not just a probability.

This is the part manual scouting tends to skip, because it requires watching the same clip several times back to back rather than moving on after one pass. It's also the part that turns a scouting report into something a specialist can actually use in the circle, rather than a stat sheet he reads once and forgets.

However much data you collect, the report your staff actually uses on Friday needs to compress down to one sentence a specialist can carry into the circle: "Clamp-first at 65%, with a 22% rake changeup — take away the top-rail clamp early and force the rake." If your scouting document can't produce a sentence like that, it's still raw data, not a scouting report.

This is also the point where a lot of manual scouting efforts stall out — the tagging gets done, but nobody has the time left in the week to turn it into a plan. That compression step is exactly what FalconEye's opponent scouts are built to automate: the tendency breakdown and the exploit callout come out of the same report, generated from the film your staff already has.

A specialist's tendencies aren't static — they shift after a bad performance, a coaching adjustment, or simply as a season goes on. The programs that get the most value out of scouting treat it as a living file that updates every time they face (or watch film on) a given opponent again, not a one-time report built before a single game.

That's the difference between scouting as a task you do once a week and scouting as institutional knowledge that survives past this season — which is also, not coincidentally, the exact problem FalconEye was built to solve.