Numbers can support a review, but they should never replace the football story around the player.
Start with the development priorities
A review should return to the areas the player has actually been working on. If the previous focus was receiving under pressure, the conversation should include evidence from training and matches rather than a completely new list of generic traits.
This creates continuity and shows the player that development work matters.
Use context
Attendance, physical growth, position changes, competition level and confidence can influence performance. Context does not remove accountability; it helps coaches interpret what they are seeing accurately.
Two players with the same metric may have very different development stories.
Invite the player into the conversation
Ask what feels easier, what still feels difficult and what the player has noticed about their own decisions. Reflection is a skill that improves with practice.
The goal is not for the athlete to agree with every coach observation. It is to help them understand the reasoning and take ownership of the next work.
Finish with a small number of next actions
A review that ends with twelve weaknesses is difficult to use. Identify a few priorities, explain how they will be coached and decide when to revisit them.
That turns the review into the beginning of the next development block instead of a report card.
