More than a Metric: How Training Load is Used in Elite Sport for Athlete Management
Bibliographic record
Abstract
Training load monitoring is a core aspect of modern-day sport science practice. Collecting, cleaning, analysing, interpreting, and disseminating load data is usually undertaken with a view to improve player performance and/or manage injury risk. To target these outcomes, practitioners attempt to optimise load at different stages throughout the training process, like adjusting individual sessions, planning day-to-day, periodising the season, and managing athletes with a long-term view. With greater investment in training load monitoring comes greater expectations, as stakeholders count on practitioners to transform data into informed, meaningful decisions. In this editorial we highlight how training load monitoring has many potential applications and cannot be simply reduced to one metric and/or calculation. With experience across a variety of sporting backgrounds, this editorial details the challenges and contextual factors that must be considered when interpreting such data. It further demonstrates the need for those working with athletes to develop strong communication channels with all stakeholders in the decision-making process. Importantly, this editorial highlights the complexity associated with using training load for managing injury risk and explores the potential for framing training load with a performance and training progression mindset.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.017 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".