Documentation Home

Player ratings,
analytically grounded.

The Pivot Pipeline transforms 60+ real-world hockey data sources into Eastside Hockey Manager player ratings across 17 league pipelines. Every rating is auditable, defensible, and built on the data each league actually tracks.

14,500+
Players Rated
17
League Pipelines
630+
Scouted Prospects
~28k
Lines of Code
Read the Pipeline Guide โ†’ Explore Data Sources

Where to start

Choose the entry point that matches what you're trying to learn.

Live
๐Ÿ“–
The Pipeline Guide
A comprehensive visual walkthrough of how raw hockey data becomes player ratings. Written for hockey fans first, technical readers second. Covers every modeling phase, the data sources, the CA tier system, and the role suggestion engine.
Open the guide โ†’
Live
๐ŸŒ
Data Sources by League
What data does each of the 17 league pipelines actually use? With three example players per league (top forward, defenseman, and goalie), this is the deep dive into what makes each league's ratings tick.
Browse leagues โ†’
Live
โš™๏ธ
Pipeline Flow
The architecture diagram. From raw scraping through master file build, modeling phases, scouting overlay, cross-pipeline reconciliation, final merge, and into the playable EHM database.
View the flow โ†’
Live
๐Ÿ“
Design Specs
The technical reference docs for the research team. NHL pipeline gold standard, AHL/European tier-2 adaptations, gap-filling techniques for thin-data leagues, and the porting checklist for new league additions.
Browse specs โ†’
Soon
๐Ÿ“Š
Interactive Dashboards
Per-team depth charts, attribute distribution viewers, draft class browsers, and prospect overlay audits. The QA tooling we use internally, opened up for the community.
Coming next release
Soon
๐ŸŽฏ
Player Profile Lookup
Type a player name, see exactly what data drove their rating โ€” the input signals, the modeled attributes, the role decision, the scouting overlay nudges, the CA suggestion math. Full transparency.
Coming next release

17 league pipelines, one rating scale

Every league below is rated on the same absolute Current Ability scale. An SHL first-liner at CA 110 sits exactly where you'd expect relative to an AHL top-six forward or NHL bottom-six player.

What's shipped

The pipeline ships alongside each Premier Pivot Rosters / TBL Database update. Each release builds on the last.

May 2026 ยท vNext+
Multi-league expansion + cross-pipeline reconciliation
12 European leagues, ECHL/SPHL added, junior pipeline overhaul, 630+ scouted prospects, multi-league season handling for callup/loan players, future draft class cleanup through 2100.
March 2026 ยท vNext
NHL/AHL pipeline rebuild
Complete overhaul of the NHL/AHL ratings โ€” z-score distributions replacing percentile-rank, Bayesian shrinkage for shooting attributes, EDGE tracking integration, career-informed mental attributes, CA & role suggestion engine, NHL/AHL quality-preferred merge.
Earlier 2026
Original NHL/AHL re-rates pipeline
Initial public release of the analytics-driven re-rates approach, with Natural Stat Trick + MoneyPuck data foundation.

Honest about how this is built

This project uses substantial AI assistance โ€” originally ChatGPT, currently Claude (Anthropic). The AI does the implementation work for the modeling, scripting, and documentation. The human (xECK29x) provides hockey expertise, oversight, validation, and direction throughout.

That setup matters for two reasons. First, the AI is a powerful tool but it requires deep domain knowledge to guide โ€” without hockey instincts informing every decision, you get reasonable-looking nonsense. Second, transparency is part of the contract with the community: the methodology is auditable precisely because the documentation exists.

This repo is the public face of that transparency. The code lives in a private repo (selectively shared with research collaborators) because it includes API integrations and scraping tools that aren't appropriate to publish openly. But every methodology decision, every formula, every weight is documented here โ€” and that's where you can challenge it, propose changes, or just understand what's happening under the hood.

Got feedback?

The whole reason this repo exists is auditability. If you think a rating is wrong, a formula is off, or a methodology choice deserves debate โ€” file a GitHub issue, post on the EHM forums, drop a thread on r/EHM. That's all in scope.