Chapters 3 to 5 give technology-specific routines. This chapter puts them into one week.
7.1 A sample weekly cycle
Figure 7.1 and Table 7.1 use match-day notation: MD-4 means four days before the match, MD+1 the day after.
| Day | Wearables | Video | AI scouting | Meeting |
|---|---|---|---|---|
| MD-4 | Record + RPE | None | None | Planning (20 min): last week's report, this week's plan |
| MD-3 | Record + RPE | None | None | None |
| MD-2 | Record + RPE | None | Shortlist review, about 20 min (scout records decisions) | None |
| MD-1 | Record + RPE (light session) | None | None | None |
| Match | Record (if used in matches) | Record whole match | Live observation of flagged players | None |
| MD+1 | None | Tag; export 2-3 clips per player | None | None |
| MD+2 | Record + RPE | Individual reviews (a few players per week) | None | Short report to coaches |
7.2 Match-day and post-match review workflow
- Before: camera at the marked position; units fitted and locked (if used); scouts know which flagged players to watch.
- During: record without stopping. Do not use live numbers to decide substitutions; the match is for coaching.
- Same day: upload and name the video; download and check wearable data.
- Next day: tag the match; export player clips; the data owner flags any quality problem.
- Within two days: one short report to the coaching team, and individual clips to a few players.
7.3 Feedback to players and parents
- Players get short, individual and mostly positive feedback with one learning point, linked to the next session (Middlemas & Harwood, 2018). Give them numbers in context ("more than your October baseline"), not raw dashboards.
- Parents are told what is collected, why, who sees it and how long it is kept (section 2.5). Give them a plain summary once or twice a season, without rankings.
- Session-RPE lets you compare what the coach planned with what players report; treat a large gap as a reason to talk (section 4.3).
- Never use data to punish. Players who experience video or numbers as punishment switch off (Middlemas & Harwood, 2018).
7.4 Staged roll-out: pilot, review, scale
| Stage | What | How long | Decide at the end |
|---|---|---|---|
| 1 Pilot | One technology, one age group, one data owner | One season (or half) | Did the routine run every week? Did coaches use the report? |
| 2 Review | Look at the practical indicators (section 9.2) with staff and a few players | Two weeks | Continue, fix, or stop |
| 3 Scale | Add an age group or a second technology; combine data (chapter 6) | Next season | Repeat the review |
D2.3 (section 14.3) advises tracking practical indicators, for example feedback turnaround, review consistency, staff time and alert follow-up, before claiming performance improvements. Section 9.2 lists them.