3 Problems Without Data
Problem 1: Stagnation goes unnoticed
Development is rarely linear. A player improves for three months – then plateaus for six weeks. Your gut feeling notices it, but not always accurately enough.
Without documented ratings, you don't know: is this a normal plateau or a sign of lacking motivation, a lack of challenge, or a technical issue?
Data shows you when the stagnation began and in which area it lies. That is the difference between a vague feeling and a concrete course of action.
Problem 2: You have nothing to show
Player review, meeting with parents, club report – in all three situations you need reliable evidence.
"Your son is making good progress" is nice. "Your son has improved his ball control from a 4 to a 7 – in three months" is a clear statement.
Without documentation, you rely on impressions. With documentation, you speak with evidence.
Problem 3: Memories fade
Where did Max stand in September? How was Lena performing at the start of the season? You coach 16 players over 9 months. Details fade.
If you didn't write anything down in March, you're left empty-handed in November.
3 Building Blocks of Data-Driven Player Development
Building block 1: Documenting observations
The foundation is simple: rate your players across 17 attributes on a scale of 1–10. Not after every training session – 4–6 full ratings per season are enough.
These are:
- Start of the season (Where do we stand?)
- After the first half of the season (What has worked?)
- Mid-season (Stay the course or make adjustments?)
- End of the season (Overall summary)
- Optional: After intensive training blocks
Per rating: 5–10 minutes. For the entire squad: 2–2.5 hours per season.
Building block 2: Analysing data
Raw data alone doesn't help. You need comparative views:
- Trend over time: How has a player developed in a specific attribute?
- Comparison across all players: Who is leading the way, who is falling behind?
- Team average vs. individual player: Where is someone above or below the squad average?
Coach OS provides these views automatically. You don't need to build any spreadsheets.
Building block 3: Making decisions
Data leads to better decisions. Not because numbers are always right – but because they place discussions on an objective foundation.
When you decide which player gets more playing time, who you recommend for additional development, or what training focus the team needs next: data makes these decisions transparent and justifiable.
5 Data-Driven Decisions in Everyday Coaching
Decision 1: Distributing playing time fairly
Awarding playing time based on progress is fair and motivating. A player who has improved in three areas over the last 8 weeks deserves more minutes on the pitch.
Without data, allocating playing time is often influenced by personal preference or form on the day. With data, it becomes a transparent system.
Decision 2: Deriving training focal points from gaps
Your team average in spatial awareness is consistently low. It has stagnated at 4.1 for three months.
That is no coincidence – it is a clear indicator of what your next training focus should be. Based on this data, Coach OS can generate drill recommendations specifically targeted at closing this gap.
Decision 3: Trials and comparative data
You have a player whom another club wants to scout. Or a player asks whether they can hold their own in a higher division.
Instead of saying "I think he could do it", you can show concrete ratings – and compare them with your other top performers.
Decision 4: Identifying players who need extra support
A player has been consistently below the team average for four rating rounds. In the exact same two areas. That is no coincidence.
This doesn't call for a conversation about faults – but a constructive development chat. With concrete figures, clear focus areas and an actionable plan.
Decision 5: Team priorities for next season
End of the season: you want to know what the team needs most urgently. Not just your gut feeling – the data.
You see: physical attributes are good, technique has improved, but tactics are lagging behind across the whole squad. The decision for next season is clear.
3 Workflows: Data Without the Extra Effort
Workflow 1: After every session (3–5 minutes)
Capture quick impressions. Not a full rating – just notable observations.
"Jonas very strong in duels today. Lea looks tired." These notes feed into your next full rating.
Workflow 2: 4 complete rating rounds per season (2.5 hours in total)
All 17 attributes, all players, one structured rating round. It sounds like a lot – but it isn't.
With Coach OS, the evaluation grid runs smoothly. You enter numbers, Coach OS saves and analyses them. For 16 players: roughly 30–40 minutes per round.
4 rounds × 35 minutes = 2 hours 20 minutes per season. For complete development data across 9 months.
Workflow 3: Monthly trends (5 minutes per month = 1 hour per season)
Once a month, you open the trend view. You check: who is developing well? Who is plateauing? Are there any anomalies?
That's 5 minutes that prevent you from missing six weeks of stagnation.
Coach OS is our own software. What follows is therefore not a neutral market overview, but an example. The criteria in the rest of this article apply regardless – use them to evaluate any tool, including ours.
What Coach OS Provides Automatically
| View | What you see | Benefit |
|---|---|---|
| Trend over time | Development per attribute and player | Make progress visible |
| Comparison of all players | Squad ranking per attribute | Identify strengths and gaps |
| Team average vs. individual player | Deviation from team level | Identify individual development needs |
| Training recommendations | Drills based on data gaps | Set targeted training priorities |
| Review overview | Compact view for 1-on-1 chats | Conduct well-informed player reviews |
Players See Their Own Development
Ratings you enter into Coach OS become visible to players via Player OS.
This has a tangible effect: players who can track their own development engage with it much more actively. "I want to go from a 5 to a 7 in passing" becomes their own goal – one that you don't even have to set for them.
Player OS shows players their progression across all 17 attributes. Not as a verdict – but as guidance.
What You Should NOT Do
Mistake 1: Using data as a verdict
Ratings are observations – not judgements. A player with a 3 in speed is not "slow" – they have development potential in that area.
Always communicate data as an indicator for development, not as a label.
Mistake 2: Reducing players to numbers
17 attributes provide a framework – not the complete picture. Character, team spirit, leadership qualities, influence on squad morale: none of this can be captured purely in numbers.
Data complements your perspective. It does not replace it.
Mistake 3: Making ratings public
Player ratings are personal data. They do not belong in the team WhatsApp chat, on the notice board, or in public discussions.
In Coach OS and Player OS, a player's ratings are only visible to the player themselves and their coach.
Read more: Brighton and Brentford: Squad Planning with Data.
FAQ: Data-Driven Player Development
How often should I rate players?
4–6 complete ratings per season are sufficient: season start, after the first half of the season, mid-season and season end. Quick notes after individual sessions are optional, but help with the next full rating.
Which 17 attributes does Coach OS rate?
The 17 attributes are divided into 4 areas: Physical (e.g. stamina, speed), Technical (e.g. ball control, passing), Mental (e.g. focus, commitment) and Tactical (e.g. spatial awareness, pressing). The full list can be viewed in Coach OS.
Can players see their own ratings?
Yes. Through Player OS, players have access to their own development data. Ratings of other players are not visible to them.
How long does a complete rating round take?
For 16 players and 17 attributes, expect roughly 30–40 minutes. For 4 rounds per season, this amounts to around 2–2.5 hours of effort for comprehensive development data.
Are player ratings GDPR-compliant?
Yes. Coach OS stores all data on servers in Germany (Hamburg) and is GDPR-compliant. Player ratings are considered personal data – inform your club accordingly.
Can I use Coach OS for player reviews?
Yes. Coach OS features a meeting view that compactly summarises all relevant data for a player. Ideal for meetings with parents, player feedback or discussions with club officials.
→ Try Coach OS for free: coach-os.com