TRV-2026-0186Certified recordPeer-reviewed

Machine learning applications in sport: a scoping review

Machine learning (ML) applications continue to grow in popularity across the sport industry, offering new opportunities for performance enhancement, injury prevention, and decision-making. The present scoping review examined the landscape of ML applications in sport by analyzing 270 peer-reviewed studies published between 2002 and 2024. ML was applied across 12 broad subject areas, with computer science, biomechanics, and sport psychology emerging as the most common domains of application. Key applications inclu…

Sports · The Trace — both readings · certified 2026-07-13 · v5 · article view · machine-readable

Current reading — gain

Machine learning models demonstrated promising accuracy for sport applications including action recognition, injury prediction and prevention, and athlete selection, offering opportunities for performance enhancement and decision-making.

Current reading — problem

Practical utility of machine learning in sport was often limited by issues of data quality, interpretability, and accessibility for end users such as athletes and coaches.

What this doesn’t fix

Practical utility was often limited by data quality, interpretability, and accessibility for end users, constraining translation from accuracy to real-world use.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0186, v5: “Machine learning applications in sport: a scoping review.” Truvace, 2026-10-10. /record/TRV-2026-0186 (accessed at citation time). sha256 d7f7908735594536…

Calibration history

Every change to this record since certification, in the open.

  1. Sources changedv5d7f790873559…

    Source set updated

  2. Sources changedv4086f8ccc8c12…

    Source set updated

  3. Sources changedv35990224d8cf8…

    Source set updated

  4. Sources changedv221f7651b4ba9…

    Source set updated

  5. Certifiedv13a3687caae4e…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0186 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.