Tracking match stats without missing the match

There are two failure modes in club stats and both are common. The first is recording nothing, then arguing on Monday about a game nobody can remember accurately — because nobody can; memory of a match is dominated by the last five minutes and the goal. The second is recording everything: a volunteer with a laptop and a 30-column spreadsheet who by half time has missed two scores, gets frustrated, and never comes back.

The version that lasts is small, tapped rather than typed, and produces about six numbers you'll actually use.

The five things worth recording

In GAA, these five earn their place. Everything else is a nice-to-have you can add in year two if the habit sticks.

1. Every shot, with its outcome and roughly where it came from. Not just scores — wides, drops short and saves are the difference between “we can't score” and “we're shooting from the wrong places”. A team taking eighteen shots and converting nine has a completely different problem from a team taking ten and converting nine.
2. Scorer attribution — who scored what, and from play or from a free. A forward on 1-4 with three from play is a different player from one on 1-4 with three placed balls, and the scoreboard can't tell you which.
3. Restarts: won or lost, short or long, which side. Twenty-five kickouts or puckouts a game is the biggest repeating pattern in the match. If you only ever track one thing, track this.
4. Turnovers, with the third they happened in. Won in their third is a scoring chance. Conceded in your own is a concession waiting to happen. The middle third is noise; don't agonise over it.
5. Minutes played. Unglamorous and the most useful of the lot, especially at underage — it's the denominator for everything else, and it's the number a parent will ask about. More on that in the guide on game time at underage.

Notice what's missing: possessions, passes completed, distance covered, tackle counts. All interesting, none of them recordable by one person watching a live match, and the first three need video to be honest about anyway.

The one-thumb rule

Here's the working constraint. The person recording is standing on a sideline, in wind, possibly holding a bag, and needs to be watching the ball. So:

• Every event is one tap, maybe two. If recording a wide takes three taps and a scroll, wides stop being recorded around the twentieth minute — and then your shot data is silently biased towards scores, which is worse than having none.
• Never type a name. Players are buttons with numbers on them. Typing on a phone in the rain is where stats projects go to die.
• Undo has to be one tap too. You will tap 12 when you meant 14. If fixing that is painful, the recorder starts leaving errors in rather than losing the next passage of play.
• One job per person. If you have a second volunteer, give them the opposition, not extra columns on your own team.
• Assume the signal drops. Half the pitches in the country have no usable coverage. Whatever you use has to keep working with no bars and catch up afterwards — if a tool loses ten minutes of taps when the signal goes, it's not a pitch-side tool.

FullPanel's matchday board is built to that spec: big score buttons with scorer attribution, per-player metric taps you define per team, a live clock, substitutions, and a pitch-side queue that holds events on the phone if coverage drops and replays them in order when it comes back. You can try the whole thing with no account on the free matchday board — it's the same engine, running against your own device rather than your club's records.

What the numbers actually tell you

This is where most club stats go wrong — not in the collecting but in the reading. Three habits will keep you honest.

Use rates, not counts

“Nine points” means nothing on its own. Nine from fourteen shots is a good day; nine from twenty-four is a problem with shot selection that a scoreline win will hide from you. Same with players: judge a corner forward on conversion and shots created, not on his tally, and judge a sub on what he did per minute rather than per appearance.

Respect the sample size

One match tells you almost nothing about a player and quite a lot about a pattern. A forward going 1 from 6 has had a bad day; a forward going 6 from 30 across a half-season has a technical issue you can coach. Resist reacting to a single game — the temptation is strongest exactly when the emotion is highest, which is exactly when the data is least reliable.

Ask what the number can't see

Your wing back has four turnovers conceded. Is he careless — or is he the only player being asked to carry the ball out of a press with no options ahead of him? Numbers point at where to look; they don't tell you what you're looking at. The best use of a stat sheet in a selectors' meeting is to generate a question, then answer it by watching the clip or remembering the passage.

Making it a habit

Start with one thing: restarts, for four matches. One selector, one phone, won/lost and side. It takes no skill and it will change something about how you set up. When that has stuck, add shots. When shots have stuck, add turnovers by third. A club that adds one metric a month has a complete picture by the end of a season; a club that starts with a complete picture has nothing by May.

And decide up front who sees what. Per-player numbers belong to the management team. Comparative stats put in front of a fifteen-year-old, or worse in a group chat, do damage that no insight is worth — in FullPanel they're visible to coaches only, and never to players or parents, for exactly that reason.