Also on Zenodo, with the other three videos.
5.1 Overview: what video analysis is used for in an academy
Academies use video for three things: reviewing team tactics, evaluating individual technique and decisions, and giving players feedback they can see. Systems range from a phone and free software to automated cameras that follow play and upload to the cloud. For the background, see Module 4 of D2.1 and D2.2, and Cases 3, 8, 10 and 12 in D2.3.
The hard parts are a stable camera position, written definitions for what you tag, and feedback that players accept. The setup steps below are built around them.
5.2 Technical setup: step by step
Once, before the first recording
Choose and mark a fixed camera position.
Why: Film from as high as safely possible, near the halfway line, wide enough to see most players. One camera maker's example: halfway line, 3-5 m from the touchline, with all four corners of the playing area in view (Veo, n.d.-a). Use the four corners as your framing check (step 7). Mark the spot (Figure 5.1).
Write a one-line definition for every tag you will use.
Why: For example: "Long pass = more than 25 m" (Gong et al., 2019). "Press trigger = first defender closes within 2 seconds" is our own example. Without written definitions, two coaches tag the same match differently.
Check: your tag list fits on one page and every tag has a definition.
Test agreement between two coders.
Why: Have two coders (any two staff who tag video) tag the same 15-minute segment and compare. Where they disagree, fix the definition, not the person (Gong et al., 2019).
Set a naming pattern for files: date, age group, opponent or session type.
Why: A fixed pattern lets you find a match weeks later.
Decide who may see footage and where it is stored.
Why: Internal analysis and publication are different uses with different legal bases (section 2.5). Store footage under the agreed access rules.
Every recording
Charge the camera and clear storage the day before.
Set up at the marked position and check the frame.
Check: all four corners of the playing area are in view before kick-off.
Record the whole session or match without stopping.
Why: Gaps make timeline tags useless.
Upload or copy the file the same day and name it (step 4).
Why: A stuck upload is the most common video problem (section 5.5).
After every recording
Tag the footage using your defined tag list.
Why: Tag only what you defined (step 2). Add new tags only after writing a definition (Figure 5.2).
Export two or three short clips per player, mostly positive.
Why: Players respond to short, individual, mostly positive clips and switch off during long critical replays (Middlemas & Harwood, 2018). D2.3 (Cases 5, 6 and 8) found that players get 2-3 minutes or 3 clips; staff get the full report.
Review the clips with the player within a few days.
Why: Let players pick or comment on clips. Never use video to punish (Middlemas & Harwood, 2018).
5.3 Interpreting video: consistent criteria and agreement between coders
- Count only what you defined. A count of "good decisions" means nothing without a written definition of a good decision. Keep the tag list short and stable through the season.
- Check agreement regularly. Repeat the two-coder test (step 3) once a season, and whenever a new person starts tagging (Gong et al., 2019).
- Compare the player with their own earlier footage. Three clips from October next to three from March show development better than a comparison with a teammate (D2.3, Cases 6 and 7).
- Keep the full analysis for staff. The player sees the few clips; the coaching team sees the tagged timeline. Do not hand a 14-year-old a 90-minute review.
- Automated statistics are still counts. An automated camera's "passes" or "sprints" are produced by rules you did not write. Ask the supplier how each statistic is defined before you report it.
- Video can also develop the coach. A small study found that filming training helped youth coaches review their own coaching behaviour (Partington et al., 2015).
5.4 Using video in training and player feedback
- Record every match, tag the ones you will use. Tagging takes far more time than recording, so decide each week which footage gets tagged and by whom.
- One individual review per player per month is a realistic target for a small academy; this means a few players each week. Keep each review short and positive, with one learning point.
- Link clips to the next session. "Here is the moment; here is the drill on Thursday" turns video into practice.
- Psychological safety first. Players dislike critiquing teammates in front of the group (Middlemas & Harwood, 2018). Keep group sessions about the team shape, and individual points for individual meetings.
- Adapt the format. For players with visual or hearing impairments, add spoken or written description to clips, and check with the player what works.
5.5 Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| Match video will not upload | Missing title, slow or unstable connection, or a firewall | Check the recording has a title, test upload speed, switch to stable Wi-Fi or a cable, and ask whoever manages the network about the firewall (Veo, n.d.-b). |
| Players at the far side are too small to see | Camera too low or too close | Raise the camera and move back (step 1). Use position B only for drills near one goal. |
| Two coaches tag the same match differently | Definitions missing or unclear | Rewrite the definition, re-run the agreement test (steps 2-3). |
| Recording stops mid-match | Storage full or battery low | Clear storage and charge the day before (step 6). Keep a spare battery or power bank. |
| Player disengages in review | Session too long, too critical, or in front of peers | Shorten to 2-3 clips, mostly positive, one to one (section 5.4). |
| A parent objects to a clip online | No legal basis or information for publication | Take the clip down, then fix the consent routine (section 2.5, Annex C). |
5.6 Quick-start checklist by role
Coach
- Agree the tag list and definitions with the analyst.
- Pick 2-3 clips per player; mostly positive.
- Link each clip to a drill in the next session.
Scout
- Use tagged clips to check a live observation.
- Compare a player with their own earlier footage.
- Do not rank players on automated counts alone.
Analyst / performance staff
- Keep the camera position, file naming and tag list fixed.
- Run the two-coder agreement test each season.
- Upload and name every file the same day.
Academy manager
- Separate consent for analysis from consent for publication.
- Budget for storage, a tall tripod and a spare battery.
- Name who may see footage, and where it lives.