The StatLink Ontology
One standardized model for fragmented sports data.
Sports data lives in scattered spreadsheets, film rooms, and apps that never talk to each other. StatLink's advantage is an ontology that maps all of it onto one model so analytics can actually run on top of it.
The StatLink Ontology defines the core objects and relationships that make up sports performance within the platform — including accounts, organizations, teams, players, scorecards, metrics, trials, evaluation workflows, and the hierarchy through which performance observations become rankings and intelligence.
Fragmented in
Spreadsheets, film grades, submissions, and app data with no common structure.
Standardized here
Every observation is mapped onto shared objects and relationships.
Analytics out
A clean model that rankings, projections, and RAVEN can reason over.
The model at a glance
Everything converges on the Trial
Read it top to bottom. Identity and organization say who is involved; two evaluation paths feed in; both terminate at a single atomic object — the Trial — and trials aggregate upward into rankings. Switch to the tree outline for a compact, top-down view of the whole model.
Who can act in StatLink, and who is being evaluated. Every account is exactly one type, and each type manages player profiles at a different scope.
- Manager→Manages Teams & Player Profiles
- Player→Manages their own Player Profile
- Parent→Manages Player Profiles
There is no separate organization object. Depending on account type, you manage a Team/Organization — simply a group of player profiles — and/or an individual Player Profile.
A group of player profiles
A single player, managed on its own
Path A
Submission workflowThe general StatLink data-entry flow: a Submission uses a Scorecard, which groups the Metrics being evaluated. Each Metric can be tagged with outcome types.
- MetricOutcome typeOutcome type
- MetricOutcome type
- MetricOutcome typeOutcome typeOutcome type
Path B
Football & flag contextGranular film-grading context, currently specific to football and flag football. An Event holds many Sessions; each Session uses a Scorecard and holds many Plays, and every Play records a Metric with an outcome.
- Sessionuses a ScorecardPlayMetric + outcomePlayMetric + outcomePlayMetric + outcome
- Sessionuses a ScorecardPlayMetric + outcomePlayMetric + outcomePlayMetric + outcome
The atomic unit of StatLink — a single observation with an outcome. Every time an outcome is tagged, whether from a submission or a play, that is exactly one Trial. No matter where the data came from, the rest of the platform reasons from this one object.
Metric ranking
Per-metric performance
Scorecard ranking
Groups a scorecard's metrics
Characteristic ranking
Groups metrics mapped to it
Overall ranking
The full picture
Metrics are the base. Each metric rolls up into its Scorecard and is also mapped to a Characteristic chosen by the scorecard's creator — two parallel groupings of the same metrics — and both feed the Overall ranking.
In one sentence
The StatLink Ontology defines the core objects and relationships that make up sports performance within the platform — accounts, organizations, teams, players, scorecards, metrics, trials, evaluation workflows, and the hierarchy through which observations become rankings and intelligence. At its center is the Trial: a single observation with an outcome — every tagged outcome is exactly one Trial.
Go deeper
The five domains, with examples
The same model, broken out domain by domain. Each tab defines the objects and walks through a concrete example of how they fit together.
Identity & Access
An Accountis a person's access to StatLink, and every account is exactly one type— Manager, Player, or Parent. The type determines what that account can manage. A Player Profile is a separate object, so it can hold years of data before that athlete ever has an account.
- Account
- Authenticated identity with permissions; exactly one type.
- Manager
- Account type that manages Teams/Organizations and Player Profiles.
- Player
- Account type that manages its own Player Profile.
- Parent
- Account type that manages authorized Player Profiles.
- Player Profile
- The representation and collection of data for a single athlete being evaluated.
Key distinction
- Manager account
- manages → Teams & Player Profiles
- Player account
- manages → own Player Profile
- Parent account
- manages → child Player Profile(s)
- Player Profile
- can exist without a Player account
See where the ontology fits in the wider ecosystem
The ontology is the foundation StatLink and IMPACTCAP are built on. See how the platforms, the shared intelligence engine, and the consumer brands fit together.