9.1 Plan template
| Academy and age group(s) | |
| The problem we are solving (section 2.1) | |
| How we will know it is solved | |
| Readiness band (Annex B) | Starting ☐ Developing ☐ Established ☐ |
| Technology for this season (one) | AI tool ☐ Wearables ☐ Video ☐ Small-academy option ☐ |
| Data owner / backup | |
| Interpreter / feedback lead / decision maker | |
| Data protection contact; DPIA needed? (Annex C) | Yes ☐ No ☐ Asked DPO ☐ |
| Legal basis and consent routine in place | Yes ☐ Date: |
| Weekly routine (chapter 7): who does what, which day | |
| Budget: licences / equipment / staff hours per week | |
| Pilot period and review date | |
| Indicators we will track (section 9.2) | |
| Decision at review: continue / fix / stop |
9.2 Simple indicators to track
These indicators track implementation. They tell you whether the routine is running. They do not prove that players developed or that injuries fell; those claims need a study design this guide does not cover.
| Indicator | How to count it | Target to start with |
|---|---|---|
| Routine completed | Sessions with full data ÷ sessions held | 9 in 10 |
| Missing data | Players with no record for a session | Known and explained each week |
| Feedback turnaround | Days from session or match to short report | Within 2 days |
| Review consistency | Two-coder agreement (video); scout decisions recorded (AI) | Test run once a season; every flagged player has a decision |
| Staff time | Hours per week per tool, by the owner | Within the budgeted hours |
| Alert follow-up | Flags from any tool that a person reviewed | All of them |
| Staff and player feedback | Three questions at the review: useful? clear? too long? | Discussed at the review |
Feedback turnaround, review consistency, staff time and alert follow-up are the examples of "practical indicators" that D2.3 gives; the other rows are added by the authors (D2.3, section 14.3).