Data for Coaches: Build a Simple Matchday Dashboard

The first dashboard a coach should build, even without a data department.

A coach dashboard should help you make better football decisions. It does not need to look like a television graphic or a club data department report. The first version can be a spreadsheet. What matters is whether it helps you understand the match, plan training, and speak to players with more clarity.

Do not start with every metric

The temptation is to track everything: shots, passes, possession, entries, duels, pressures, crosses, set pieces, turnovers, field tilt, expected goals, running data, and more. That usually creates a dashboard nobody uses. Start with the behaviours you actually coach.

If your team is working on counter-pressing, track regains within a short window after losing the ball, where they happened, and whether they led to an attack. If your team is working on wide overloads, track wide entries, box entries, cutbacks, crosses, and shots from those attacks. The dashboard should follow your coaching focus.

The three questions

A useful matchday dashboard answers three questions. Did we create the behaviours we trained? Did we prevent the problems we expected? What should we work on next?

Those questions keep the dashboard practical. They stop you from collecting numbers just because they are available. They also make the dashboard useful for staff meetings because every number has a coaching purpose.

A simple first dashboard

Start with five to eight metrics. For example, final-third entries, box entries, shots, shots after regain, counter-press regains, crosses defended, set-piece chances, and goals conceded from transition. These can be tracked manually while watching the match back.

Add context columns. A final-third entry is more useful if you know the route: central combination, wide overload, direct pass, regain, or set piece. A shot is more useful if you know whether it came from good spacing, a cutback, a second ball, or an individual action.

Use counts and notes together

Numbers give structure. Notes give meaning. If you had 18 final-third entries but only two shots, the note might explain that the final pass was delayed, the box was underloaded, or the wide player had no inside support. Without notes, the number tells you something happened but not why it happened.

A good dashboard should include a short written interpretation. Three bullets are enough: what worked, what hurt us, and what we train next.

Build around your model

Your dashboard should reflect how you want to play. A possession-heavy team may care about build-up exits, central progression, rest defence, and counter-press. A direct team may care about first contact, second balls, territory, crossing, and box occupation. A development team may care more about decision quality than match outcome.

There is no universal first dashboard. There is only the dashboard that helps your staff make better decisions.

Data sources for different levels

At grassroots or non-league level, you can track manually from video. Use a simple sheet and keep definitions tight. At academy or semi-professional level, you might combine manual tags with video software. At professional level, event data, tracking data, and analyst workflows can feed richer dashboards.

The principle stays the same at every level: if nobody acts on the insight, the dashboard is not working.

Suggested columns

• Match date and opponent.
• Team theme for the week.
• Metric name.
• Count.
• Location or phase.
• Player or unit involved.
• Clip reference.
• Coaching note.
• Training action.

How to present it to staff

Keep the staff version short. Lead with the answer, then show the evidence. For example: our wide entries improved, but the far-side box arrival was still late. Show two numbers, two clips, and the training action. That is enough to shape a useful conversation.

If you present every chart you built, people will stop listening. Use the dashboard as a thinking tool, not a slideshow.

How to present it to players

Players need clarity. Use simple language and connect the data to action. Instead of saying our final-third conversion from zone 14 entries was poor, say we got into good central positions but arrived late in the box. Then show the clip and train the arrival.

The best player-facing dashboard is often one visual, one clip, and one challenge for the next match.

Common mistakes

The first mistake is copying professional dashboards without having the staff, data, or context to use them. The second is changing definitions every week. The third is showing numbers without clips. The fourth is creating a dashboard that confirms opinions but never challenges them.

A good dashboard should make you curious. If the data disagrees with your feeling, investigate. Sometimes the number is wrong. Sometimes your memory of the match is incomplete. The value is in the conversation.

A TCC starter build

Pick one team theme. Choose five metrics connected to it. Track three matches. Add one clip to each key finding. After the third match, ask what changed in training and whether the behaviour improved. That is the beginning of a real analysis workflow.

A dashboard does not need to be complex to be credible. It needs to be honest, consistent, and connected to coaching decisions.