Most grassroots match reports never get written. The game finishes, you pack the goals away, someone's parent asks if you need the nets, and by the time you get home the detail has gone. That's a shame, because the report is the one thing that tells the parents who weren't stood pitch-side what actually happened to their kid for an hour on a wet Sunday.
I coach Springhead U12 Spartans, and I write a report after every game. Here is the way I do it, why each part is there, and how to make it quick enough that you'll actually keep it up past September.
Why bother at youth level
Parents watch their own child. They see their kid chase a ball and not much else. They don't see the build-up, the two lads who kept swapping positions to plug a gap, or the defender who had a quiet but faultless game. The match report is the only window they get into the parts you were actually coaching.
It also does a job for you. Write twenty of them across a season and you've got an honest record of who played where, who turned up, and how the team changed month to month. That beats trying to remember in May what happened in October.
A structure you can reuse every week
You don't need a new format every time. Pick one and run it for the whole season. Here's the one I use, and it fits on a phone screen:
The basics. Date, opposition, competition or friendly, final score. Boring, but it's the bit people scroll back to find weeks later.
How the game went. Three or four sentences. How it started, the moment it turned, how it finished. Tell the story, don't list every kick.
Goals and big moments. Who scored, who set it up, the save that kept you in it. Name the assist, not just the goal. The pass before the goal is often the better bit of play.
Something good about the team. A pattern, not a person. "We kept the ball on the floor in the second half" or "everyone tracked back when we lost it." This is where the coaching shows.
One thing to work on. Keep it about the group, framed as the next thing you'll practise. "We'll do some work on clearing our lines under pressure on Tuesday." Never single a child out for the bad bits.
Write it while it's fresh
The single biggest thing that decides whether a report is any good is when you write it. Do it Sunday afternoon and it's full of real detail. Leave it to Wednesday and it turns into "we won 3-1, good effort all round," which tells nobody anything.
A trick that helps: jot a few notes during the game or right at full time. The two goalscorers, the lad who had his best game, the moment it swung. Five words each is plenty. Those scraps are what you build the proper write-up from later.
Remember who's reading it
These get read by kids. A nine year old will reread the line about their goal for a week. So spread the credit, mention the players who don't make the scoresheet, and keep anything critical aimed at the team rather than an individual. If a child had a hard game, that's a quiet word at training, not a sentence in a report their nan is going to read.
Honesty still matters. You don't have to pretend a 6-0 loss was a triumph. But there's always something true and decent to point at: the heads that stayed up, the second-half rally, the keeper who kept making saves at 5-0 down.
The faster way to do it
If you want a head start, grab our match report template and fill in the gaps. It follows the structure above, so you're never staring at a blank page.
There's also the route I use now. If you tap the goals, assists and key moments into Trac as the game goes on, it can turn those taps into a written report in seconds. You tap, it writes, you check it reads the way you'd say it, and the parents have it before the kit's dry. That's what our AI match reports do, and it means the report actually gets written every week instead of when I find a spare half hour.
However you write it, the point is the same. A few honest, specific sentences after every game add up to something real by the end of the season. Pick a structure, write it while it's fresh, keep it kind, and keep it up.