What I Hand Over To Next Year’s U12 Coach

The handover nobody really explains

At the end of a U12 season you hand over a team that no longer exists.

Some kids move up an age group, some quit, some new ones appear from the rookie teams. The mix of parents changes, the social dynamics reset, and the new coach walks into something that is technically the same team, but practically a fresh start.

Still, there is always that question: what do you actually pass on? What survives a season change, and what belongs to one specific group of kids in one specific year?

Over time I ended up with a simple rule: pass on structure and long-term signals, leave short-term drama behind.

Player notes: what survives a season

I keep a short note for every player through the season. Not a dossier, just a few lines that I update when something is clearly not a one-off.

Stuff that tends to go in:

• Physical basics: left/right handed, throwing mechanics, running speed in simple terms ("fast", "average", "needs help with starts").
• Defensive comfort zones: positions they have actually played, and where they looked comfortable rather than just present.
• Offensive patterns: pulls everything, scared of the ball, never swings at first pitch, and similar recurring tendencies.
• Real development arcs: for example, going from avoiding fly balls to calling for them in the infield.
• Clear learning hooks: "Understands tagging rules well", "picks up signals quickly", "needs visual explanation".

The test is simple: if another adult could use this to help the kid in week 1 next season, it belongs in the notes. If it only makes sense if you lived through week 14 of a chaotic May, it probably does not.

What belongs to this group of kids only

The stuff you do not pass on matters just as much.

A 12-year-old having a bad month is not a permanent trait. Neither is a growth spurt, a friendship conflict, or the week they suddenly hated baseball because they lost their spot in the batting order.

So the handover does not need:

• Stories about "attitude" based on one rough stretch.
• Complaints from parents, unless there is a clear long-term safety or boundary issue.
• Old conflicts that have already cooled down.
• Labels like "lazy", "difficult", or "leader".

If something really is structural, it should show up in concrete behaviour anyway. "Often late" is more useful than "not motivated". "Easily distracted in the field, needs short reminders" is more useful than "difficult".

I wrote about this earlier in The client code I will not paste into an AI tool.

The next coach deserves space to form their own view. The kid deserves a reset button.

How to hand the notes over

The format works best when it is boring and predictable:

• One document or sheet with a line per player.
• Columns for: name, hand/throw, main positions, backup positions, a few notes on hitting, one or two learning hooks.
• A short section at the bottom for team-wide stuff: how you trained, what rules you used, how you handled playing time.

Then you talk it through in person. The document is just a map. The conversation is where you can say "This looks like a problem on paper, but it is already solving itself" or "This kid will probably respond well if you give them responsibility early".

The lineup system: what should survive

Lineups are where coaches quietly build or destroy trust.

Earlier I wrote about the lineup mistake with Tuur: a combination of trying to be fair, juggling positions, and ending up with a pattern where one kid kept getting the short end of the stick. It was not a one-off decision, it was a system that allowed the same small disadvantage to repeat.

So when I hand over a lineup system, I try to pass on principles instead of a frozen spreadsheet.

Stuff that should survive:

• Playing time rules: for example, simple agreements about how often kids start or how you avoid someone sitting out repeatedly.
• Rotation logic: how you move kids through infield, outfield, and bench in a predictable way.
• Safety boundaries: who is not ready for which position yet, and what they are working towards.
• Communication habits: when you tell kids about the lineup, and how you explain changes.

The next coach can plug their own preferences into that. Different personality, different game strategy, same basic fairness.

What should not survive from the lineup

What you do not want to hand over is a rigid template that bakes in this year’s mistakes.

If you send a ready-made rotation like "Tuur sits every third game" or "Player X never plays shortstop", you are quietly telling the next coach to keep repeating your blind spots.

More on this in my article Coaching Positions: How I Read 12-Year-Olds Before They Know Themselves.

It helps to separate three things:

• Policy: "We rotate outfield positions every inning".
• Current reality: "Right now, J. struggles to catch fly balls in right field".
• Direction: "We have been giving J. extra reps in right field in practice to change that".

Policy can carry over. Reality will change. Direction is an invitation for the next coach to decide whether to continue that path or pick a new one.

Protecting kids from last year’s story

A new coach meets a kid for the first time. If the first thing they hear is "He is always late" or "She cries when you move her down the lineup", that story will stick.

So the notes should be something a kid could read without feeling trapped by their past season. If a sentence would make them feel small or stuck, it does not belong in the handover.

That does not mean hiding real issues. It means framing them as things that can move:

• Instead of "Gets angry when making errors": "Helps to give them a clear next task after an error".
• Instead of "Scared of the ball": "Needs lots of controlled reps at low speed, improves when they know what is coming".

The next coach gets something useful. The kid gets a chance to be someone slightly different next year.

When to say nothing

Sometimes the most helpful thing you can do for the next coach is to keep quiet.

If a kid had a bad conflict with you personally, that does not automatically belong in the notes. If a parent emailed three angry paragraphs about playing time in May and then calmed down, that is not a permanent feature of the team.

Read also Using the Ghost forum to earn trust before selling themes.

A simple filter:

• Is this about the kid, or about me and the kid?
• Is this likely to matter next season, or was it specific to one situation?
• Does sharing this help the next coach help the kid, or does it mostly protect my own ego?

If it is mainly about you, it stays with you.

Leaving space for a new season

An end-of-season handover is not a transfer of control. It is just a small shortcut so the next coach does not have to rediscover everything the hard way.

The kids will change over the summer. Some will grow, some will switch positions, some will arrive with a completely different attitude. The best you can do is send forward a clear picture of where they were, without pretending that is where they will stay.

Pass on the structures that protect fairness. Pass on the long-term patterns that help kids develop. Leave the rest behind with this year’s dirt on the cleats.