Skip to content
TalentTECH home

Implementation guide

7 Integrating the tools into training routines

Chapter 7 of 9

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.

A sample training week with the three tools Seven columns from match day minus four to match day plus one. Each column lists which tool is used that day: wearables on training days, video review after the match, AI scouting shortlist reviewed once a week, and a short planning meeting. MD-4 MD-3 MD-2 MD-1 MATCH MD+1 MD+2 WearablesWearablesWearablesWearablesVideo +wearablesVideo reviewWearables + RPE+ RPE+ RPE+ RPE, lightrecord matchtag, export clips+ RPE Planningmeeting (20 min) AI shortlistreview (scouts) Player clips(2-3 per player) Short reportto coaches Owner:perf. staffOwner:scoutOwner:analyst / coachOwner:perf. staff Sample only. Adapt the days to your own match schedule. Keep one data owner per tool.
Figure 7.1 A sample week. Adapt the days to your match schedule. The constants are: wearables every training day, one AI shortlist review, one match review with a few individual player reviews, one short report, one data owner per tool.
Table 7.1 The sample week in detail
DayWearablesVideoAI scoutingMeeting
MD-4Record + RPENoneNonePlanning (20 min): last week's report, this week's plan
MD-3Record + RPENoneNoneNone
MD-2Record + RPENoneShortlist review, about 20 min (scout records decisions)None
MD-1Record + RPE (light session)NoneNoneNone
MatchRecord (if used in matches)Record whole matchLive observation of flagged playersNone
MD+1NoneTag; export 2-3 clips per playerNoneNone
MD+2Record + RPEIndividual reviews (a few players per week)NoneShort report to coaches

7.2 Match-day and post-match review workflow

  1. Before: camera at the marked position; units fitted and locked (if used); scouts know which flagged players to watch.
  2. During: record without stopping. Do not use live numbers to decide substitutions; the match is for coaching.
  3. Same day: upload and name the video; download and check wearable data.
  4. Next day: tag the match; export player clips; the data owner flags any quality problem.
  5. 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

StageWhatHow longDecide at the end
1 PilotOne technology, one age group, one data ownerOne season (or half)Did the routine run every week? Did coaches use the report?
2 ReviewLook at the practical indicators (section 9.2) with staff and a few playersTwo weeksContinue, fix, or stop
3 ScaleAdd an age group or a second technology; combine data (chapter 6)Next seasonRepeat 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.

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