Automatic shift detection that understands hockey
The engine watches your heart rate and wrist motion — live on the watch and again on the phone — and tells you when you're on the ice and when you're on the bench.
How it detects a shift
Ice time and bench time leave different fingerprints. On a shift your heart rate climbs toward your working ceiling and your wrist accelerates; on the bench it falls toward your aerobic floor and your motion settles. The engine combines all three signals — and because heart rate lags, it never trusts a single reading.
- Heart rate: the rise into a shift and the fall back to your aerobic floor.
- Wrist motion: the acceleration of actually playing, and the stillness of the bench.
- Combined, on device: no signal is trusted alone, and nothing is sent anywhere.
Built for the messy realities of real hockey
Real games aren't tidy. Heart rate lags at the start of a shift, some shifts are quiet, stoppages are long, and some games are short. The engine handles all of it — and when it's genuinely uncertain, it never guesses silently.
Review candidates, not silent guesses
Uncertain sessions are never dropped or falsely tagged. They're kept as review candidates with an explanation, so you can confirm, adjust, or delete. Your call, your record.
Personalizes to your body
Your aerobic floor, working heart-rate ceiling, and between-shift recovery are learned from your own games. Age-based formulas are only the starting point — the more you play, the more the engine knows you.
Tuned and tested on real games
The detection engine was tuned against actual captured games — heart rate and wrist motion from real hockey — with a replay pipeline that re-tests every algorithm change end-to-end.
Fine Tune
Every detected boundary is reviewable. Move a boundary, crop the game, calibrate your aerobic floor — and watch the engine react to real data.
Common questions
The answers players actually ask about automatic shift tracking.
Why it matters
Ice time and work:rest are the two numbers every player wants, and both depend on getting the shift boundaries right. If detection calls a shift early or late, every metric built on top of it inherits the error. That's why the engine is built to be reviewable rather than assumed perfect.