Skip to content
TalentTECH home

Implementation guide

2 Before you start: preparing the academy

The D2.3 case studies show that academies which started with a clear problem, a named data owner and a realistic budget kept using their tools; others did not. The lesson: technology projects often fail before the first device is switched on. This chapter covers the five decisions to take first.

Chapter 2 of 9

Also on Zenodo, with the other three videos.

2.1 Start with a specific problem, not with the technology

Write down the one problem you want to solve this season. Examples:

  • "Our U15 scouts rate the same player very differently." (chapter 3)
  • "We do not know how hard last week was for each player." (chapter 4)
  • "Players do not understand our feedback on positioning." (chapter 5)

Then write how you will know it is solved. Use something you can count: for example, two scouts agreeing more often, or every player having a load record for every session. D2.3 (section 14.3) draws the same lesson from the Lithuanian cases: begin with a problem and an implementation plan, not with a purchase.

2.2 Academy digital-readiness self-assessment

Answer the seven questions in Annex B before choosing any tool. They cover people, time, equipment, internet, data handling, budget and player and parent trust. The answers place your academy in one of three bands:

BandTypical situationSuggested start
StartingNo data owner named; no stable laptop or Wi-Fi at the ground; no consent routineSession-RPE, a player's effort rating (section 4.1), a phone on a tripod for video (section 5.2), consent routine first (Annex C)
DevelopingOne person with time; basic equipment; some consent formsOne technology, one age group, one season
EstablishedData owner and backup named; stable equipment; written data rulesAdd a second technology and combine the data (chapter 6)

The bands are a planning aid, not a score. Many academies are "starting" in one row and "established" in another.

2.3 Budget, staff time and choosing sustainable tools

Staff time is the cost academies forget to budget; licence fees are only the visible part. For each tool, estimate the hours per week for setup, data download, checking and reporting, and name who will do them. D2.3's practitioner cases found that budget and the coach's own preferences decide whether a tool is adopted, and that planning for staff time matters as much as paying for licences.

Rules for a small academy:

  • Choose tools you can sustain for three seasons. Advanced features you cannot keep paying for are worth less than a tool you still use in season three.
  • Remove repetitive paperwork first. D2.3 (Table 14, Cases 8 and 9) draws the lesson "admin first, performance tech second": remove repetitive paperwork before adding sensors or AI. If staff are drowning in admin, a performance tool will not be used.
  • Pilot before you commit. One age group, one season, then decide (section 7.4).

2.4 Roles and responsibilities

Name one person for each role below. One person can hold several roles in a small academy, but each role needs a name and a backup. Write the names in your integration plan (chapter 9).

RoleResponsible for
Data owner (per tool)Setup, download, quality check, storage and access
InterpreterTurning numbers into a short report with one clear message (section 6.2)
Feedback leadWhat players and parents are told, and how (section 7.3)
Decision makerSelection, load and return-to-play decisions. Always a person, never a tool (section 2.5)
Data protection contactLegal basis, consent, retention, DPIA (section 2.5, Annex C). Your organisation's DPO if you have one

D2.3 (section 14.3) lists "assign responsibility for data quality, interpretation, feedback and decisions" as a shared lesson of the Lithuanian cases.

2.5 Data protection and safeguarding principles for youth players

Every tool in this guide collects personal data about young players. The rules below are principles. Annex C turns them into a checklist. This section is not legal advice: confirm each point with your data protection officer (DPO) or legal adviser, and with your national data protection authority's guidance.

  1. Follow the GDPR principles. Data must be processed lawfully, fairly and transparently, for clear purposes, limited to what is needed, kept accurate, kept no longer than necessary, and kept secure. The academy must be able to show it does this (Regulation (EU) 2016/679, Art. 5).
  2. Decide the legal basis first. Consent is one of six legal bases. Decide and document the basis for each use of data before you start (GDPR, Art. 6). If a player or parent feels that refusing a sensor or a camera would hurt their place in the squad, consent may not be "freely given". Ask your DPO or data protection contact (section 2.4) which basis fits, and make withdrawal as easy as giving consent (EDPB, 2020a).
  3. Involve parents for minors. The GDPR sets a "digital age of consent" of 13 to 16, depending on the country. It applies only to online services offered directly to children, for example a player app the child signs up to. All other processing needs its own legal basis and, for minors, normally involves parents. Check the age in your country with your national data protection authority. Verify parental consent in a proportionate way. When a player reaches the national age, tell them they can confirm or withdraw the consent their parents gave (EDPB, 2020a; European Commission, n.d.).
  4. Treat sensor data as health data. The GDPR's definition of health data is broad. Physiological measurements can count as health data whatever device produced them (GDPR, Art. 4(15), Art. 9; Article 29 Working Party, 2015). Heart-rate and other physiological data collected over a season are likely to be health data. Identify an Article 9 exception (for example explicit consent) with your DPO before collecting it.
  5. Do a data protection impact assessment (DPIA) when in doubt. Art. 35 GDPR requires a DPIA for high-risk processing, and national authorities publish lists. In a survey of over 100 sports clubs by Ireland's data protection authority, 9% had done a DPIA and 56% had no retention schedule (DPC, 2024).
  6. A person takes every decision. Under Art. 22 of the General Data Protection Regulation (GDPR), people have a right not to be subject to decisions based solely on automated processing. Recital 71 adds that such decisions should not concern a child. So an AI tool must not decide on its own whether a young player is selected or released: a qualified person reviews the evidence and takes the decision. Chapter 3 applies this rule to scouting tools.
  7. Explain it to players in simple words. What is collected, why, who sees it, and how long it is kept (GDPR, Art. 12-13).
  8. Video: analysis is not publication. Ordinary match video is personal data but not automatically biometric data; if a tool uses face recognition, stricter rules apply (EDPB, 2020b). Before posting any clip of a youth player online, have a clear legal basis (usually parental consent), say where it will appear and for how long, and allow withdrawal (DPC, n.d.).
  9. Secure the data. Use player codes instead of names where you can, protect accounts with strong passwords, encrypt laptops and phones, keep backups, and check security regularly (GDPR, Art. 32). Where a supplier stores the data, the contract should say who is controller, who is processor and where the data is kept.
  10. Know which law applies. Partners in Türkiye follow Law No. 6698 on the Protection of Personal Data (KVKK), which also treats health data as a special category (KVKK, 2016). In this guide, KVKK refers to the law; the authority of the same name publishes guidance on it.

The implementation guide is published under a CC BY-SA 4.0 licence.