Post-Match Coach Reflection Template: 7 Questions That Build Better Coaches

Why Write a Post-Match Reflection?

Structured post-match reflection is the single biggest development tool a youth soccer coach has that costs nothing. 15 minutes of honest writing after every match, across a 30-match season, is 7.5 hours of deliberate coaching development. That compounds. Coaches who do this consistently for 2 seasons can see measurable improvements in match preparation, in-game decisions, and player communication.

Most grassroots coaches skip this because it feels optional and because nobody ever asks to see the reflections. They are doing themselves a disservice. The value is not in the document; it is in the thinking the document forces.

The 7-Question Reflection Template

1. What was the intended game plan?

One paragraph. What we were trying to do tactically going into the match. Formation, style (possession-based, counter-attacking, high press), who was in key roles.

Why this matters: separates "we lost because of bad luck" from "we lost because the plan was wrong." Most post-match bias blends them.

2. What actually happened?

2 to 3 paragraphs. Honest account of how the match unfolded. Key moments (goals, tactical shifts, substitutions). Written without judgment, just facts.

Why this matters: distinguishes memory from event. Memory compresses and distorts within 24 hours; written accounts capture what actually happened.

3. What did the team do well?

At least 3 specific things. Avoid generic "worked hard" comments. Write things like "Sam's weak-foot crosses from the left flank created three chances in the second half" or "midfield pressed as a unit for the first 25 minutes, forcing two turnovers into goals."

Why this matters: specific positives tell you what training paid off. They also protect you from the trap of only processing negatives.

4. What did the team struggle with?

At least 3 specific things. Same rule: specific, not generic. "We conceded on 3 corners out of 6" not "defending set pieces was poor." "We lost 70% of second balls in their attacking third" not "midfield was slow."

Why this matters: specifics drive next training session's focus. Generic struggles do not.

5. What did I do well as a coach?

2 to 3 things. Genuinely. Decisions you made that mattered (a timely substitution, a half-time adjustment, a clear pre-match brief). This is not self-congratulation; it is pattern recognition.

Why this matters: coaches who only list their mistakes underdevelop their strengths. Write what worked too.

6. What did I get wrong as a coach?

2 to 3 things. Honestly. Decisions you would change. A substitution that did not work. A tactical tweak you delayed. A player you over-coached. A moment you lost your temper on the sideline.

Why this matters: writing coach-specific mistakes (not player mistakes) is where real development happens. Coach-blame trains improvement; player-blame trains nothing.

7. What is the single most important thing to address in the next session?

One thing. Not three. The one theme from this reflection that goes into next practice's focus.

Why this matters: forcing yourself to pick one creates focus. "Work on defending, passing, and pressing" at next session is three diluted drills. "Work on second balls in the attacking third" is one clear theme.

How Long Should a Reflection Take?

15 minutes is the target. Less and you skip the honesty. More and you over-analyse a single match.

When to write it: within 24 hours of the match. Memory degrades fast. By 48 hours your reflection is already half-fiction.

Where to write it: a notebook or a single Google Doc per season. Hobbit AI's Write module can structure the 7 questions with prompts that guide honest answers.

Sample Reflection (U10 Match, Loss 1-3)

Format: short, direct, honest.

1. Intended game plan: 3-2-1 with wide fullbacks pushing high; possession-based build from the back; press opposition centre-backs on bad touches.

2. What happened: We controlled first 15 minutes, had 60% possession, one chance. Conceded on a corner at minute 20. Pressed harder, conceded on a counter at minute 35 from our own high line. Half-time 0-2. Second half, shifted to 3-3 with deeper fullbacks. Scored at minute 55 from a corner. Conceded at minute 70 from a long ball over the top. Final 1-3.

3. Team did well: (a) first 15 minutes matched the game plan closely, (b) Sam's corner delivery at minute 55 was pro quality, (c) nobody dropped their head after 0-2.

4. Team struggled with: (a) marking on corners (2 of 3 goals from corners), (b) recovery pace when high line got broken, (c) building out from the back against a man-press.

5. I did well as coach: (a) half-time adjustment to deeper fullbacks stopped the bleeding, (b) pre-match brief was clear; players executed the first 15 minutes well.

6. I got wrong as coach: (a) should have adjusted fullback depth at minute 25, not half-time; (b) should have practiced corner defending more intensively last week, we knew this opponent was set-piece strong; (c) I let frustration show at minute 35 after the second goal; team fed off it.

7. One thing for next session: corner defending. 20 minutes of zonal vs man-mark, scenario rehearsal with attacking corner patterns. Everything else can wait.

What Makes a Reflection Actually Useful?

Honesty

If every reflection concludes "team played well, I coached well, unlucky result," the tool is being used wrong. Growth requires honest identification of mistakes. A season of honest reflections reads as uncomfortable; that is a feature.

Specifics

"We defended poorly" is a worthless sentence. "We let 3 of 6 corners result in shots on goal" is useful. Numbers, names, moments.

Distinction between player and coach

Players make mistakes that you can train out of them. Coaches make mistakes that only you can address. Mix the two and you end up blaming kids for your planning gaps.

The "one thing" discipline

Resisting the urge to identify 5 things to fix is the hardest part. Picking one creates the focus that makes the next session actually productive.

What Not to Write in a Reflection

Reflections are for you, not for the group chat. Never:

• Share specific reflections with parents (especially player criticisms)
• Post them on social media
• Share them with players (summarised lessons are fine; raw reflections are not)

Reflections are a private coaching development tool. Keep them that way.

Common Reflection Mistakes

• Skipping it after wins: wins teach as much as losses. Often more, because ego is less involved.
• Writing fluff: "team worked hard, we'll learn from this" is useless. Be specific.
• Waiting longer than 24 hours: memory is already fiction.
• Over-focusing on players: coach mistakes are where you have control.
• No action item: a reflection with no "one thing for next session" is just journaling. Reflection connects to action.

Key Takeaways for Post-Match Coach Reflection

• 15 minutes per match, 7.5 hours of deliberate development per season.
• 7 questions: intended plan, what happened, did well, struggled, coach did well, coach got wrong, one thing next.
• Within 24 hours of the match. Delay kills honesty.
• Specific over generic: numbers, names, moments.
• Coach mistakes matter more than player mistakes: you can change coach behaviour.
• Pick one thing to address in next session. Just one.
• Private tool, never shared externally.
• Write after wins too. They teach as much as losses.