How Youth Soccer Coaches Can Build a Season-Long Practice Curriculum

A season practice curriculum for a youth soccer team is the short list of priorities you commit to teaching all season, the order you introduce them in, and the rule for when a tactical idea gets locked in instead of redesigned every week.

I co-founded Train Daily and coach youth soccer in Fort Wayne, IN. Most practice-planning advice treats the problem as a weekly one. What do you run on Tuesday, and what drill fills the last twenty minutes. A season curriculum asks a bigger question. What does this roster need to know by the end of the season that it doesn't know on day one, and in what order do you teach it so each piece builds on the last instead of starting over. Without that bigger plan, players relearn the same lessons every fall and a coach never finds out whether this year's team actually improved or just got a year older.

How many things should a soccer team's season actually cover?

Pick one or two. That's the number that works, not the number that sounds thorough in a parent email. I teach one or two things deeply each season and treat the rest as maintenance of skills the roster already has. This season it's a two-phase read of the game. When we have the ball, every player's job is to keep it and score. When the other team has it, every player's job is to win it back. I ask "what phase are we in?" in nearly every practice until players start asking each other instead of waiting on me.

A long list of priorities looks thorough on paper and does almost nothing on the field. Players need the same idea in enough different situations to actually own it, and a season runs out of practice time long before it runs out of good ideas to teach. Cutting the list to one or two forces you to pick the idea that changes the most games, not the one that's easiest to explain to parents.

Pick the wrong number and you feel it by midseason. A coach who tries to install six new concepts in six weeks usually ends up with a roster that can describe all six and execute none of them under pressure. A coach who picks one and sticks with it past the point of boredom usually ends up with a roster that can't describe it well but does it without thinking, which is the actual goal. The first version photographs better at a parent meeting. The second one wins more second halves.

How often should you change a youth soccer practice plan?

Less often than most coaches do, and almost never week to week. Chris Ramsey has talked about players absorbing roughly 30% of a new session the first time through, 60% the second time, and more on the third repetition. I used to write a new practice every week because repeating felt like I wasn't working hard enough. Now I build the week's priority into two or three sessions in a row with small variations in the constraint, not the idea, and more of it shows up in games.

I wrote more about holding one or two priorities for weeks instead of chasing a new wrinkle every night in a post on building a 9v9 practice plan, and the rule holds at any format. The hard part isn't deciding to repeat. It's sitting through the second and third rep of a drill that already feels finished to you, when it's only starting to land for the players.

How do you know when a tactical rule is ready to lock in?

Wait for a game to show you the gap, then lock in the fix and teach it the same way every time after that. My center backs now play five to eight yards behind the outside backs, and that rule came from a specific game where the middle of our field kept emptying out every time we pushed numbers forward. I taught it with a cone line six yards behind the outside backs that the center back isn't allowed to cross while the ball is live, and the rule has held since.

The same thing happened with which side gets the higher outside back in our 3-3-2. I noticed most opponents were attacking down their right, so I moved our higher back from the left side to the right and left the other back home. Neither rule came from a coaching manual or a podcast. Both came from watching a specific problem repeat and deciding it was worth a permanent answer instead of a one-game adjustment.

How should the curriculum change from preseason to the stretch run?

Preseason is for vocabulary, not execution. The first few sessions are where you introduce the season's one or two priorities and the cue words that go with them, and you should expect the early reps to look rough. That's normal. A team hearing "what phase are we in" for the first time isn't going to answer it well in week one, and trying to fix that with a longer explanation usually slows the learning down instead of speeding it up.

Midseason is where the tactical rules get locked in, because games are finally giving you real information about where the roster actually struggles instead of where you guessed it might. This is also where repetition does its heaviest lifting. Once a priority is installed and a rule or two is locked in, the job shifts from teaching new material to running the same core exercises often enough that players stop thinking about them and start reacting instead.

Late season and tournament stretches call for a different kind of practice altogether. You're not adding new ideas this close to the games that matter most. You're tightening the execution of whatever's already locked in, trimming anything still half-tested off the plan, and spending more of each session on the game-speed version of what the team already knows rather than the slower teaching version. A curriculum that tries to introduce something brand new the week before a tournament is solving a problem that should have been solved a month earlier.

What should stay flexible while you're still testing it?

Not every idea deserves a permanent rule right away. Our pressing triggers, a poor first touch, a backward pass, or slow ball movement, stayed a loose guideline for weeks before I taught them as a fixed list, because I wanted to see which trigger actually predicted a turnover before I built a drill around it. A season curriculum needs room for ideas you're still testing sitting right next to the ones you've already locked in, and mixing the two up is how a coach ends up teaching a rule that turns out to be wrong.

I keep a note on each player every practice, which is less about grading them and more about catching the moment an idea works or doesn't. If three players solve the same situation wrong in the same way, that's a pattern worth testing as a rule. If one player solves it wrong, that's a conversation, not a curriculum change. I use those notes to decide which column, locked in or still testing, an idea belongs in by midseason.

How do you check whether the curriculum is actually landing?

Ask a specific question, not a general one. "Did everyone understand pressing" gets you a room full of nods. "What's the first thing that tells you to press" gets you an answer you can actually grade. I check retention with a short question after nearly every session, and the gap between what I taught and what players can repeat back tells me whether to move on or stay another week on the same idea.

The days between games matter here too. My team's off-day assignments carry the season's priority forward instead of a random skill, so a player who can't explain the pressing trigger at practice gets another look at it before the next session instead of losing a week. That's how I get players to practice on their own time without it feeling disconnected from what we're building toward.

Checking what actually landed is the hardest part of running a curriculum instead of a collection of good drills. Train Daily builds a short reinforcement question into every assignment you send, so you see who can answer before the next practice instead of finding out at a scrimmage. I co-founded it, so weigh that accordingly.

What does a season curriculum look like written down?

Shorter than most coaches expect. Mine fits on one page: the one or two priorities for the season, the three or four tactical rules already locked in from real games, the ideas currently being tested, and the cue words I use to teach each one without a long explanation. "Picture, then ball" is the only thing I say for scanning. "CB behind the line" is the only thing I say for the center back rule. If I can't say it in four words, I probably haven't understood it myself yet, let alone found a way to teach it to a group of nine and ten-year-olds.

Writing it down also protects the curriculum from your own good ideas. A podcast or a weekend clinic will hand you a new idea every week if you let it, and most of them sound good in the moment. The written list is what stops me from swapping my one or two priorities for whatever I heard most recently. When a new idea actually contradicts something already in the plan, I write the conflict down and think it through instead of quietly overwriting what was already working.

The written curriculum sits above individual sessions, not in place of them. My post on structuring a single practice around Play-Practice-Play covers how I turn one of these season priorities into an actual two-hour session on the field.

Building your own season curriculum

Start with one priority, not three. Write down the tactical rules you've already locked in from real games this season, even if that list is short right now. Leave room next to it for the ideas you're still testing, and check what's landing with a specific question instead of a general one. A season curriculum isn't a longer practice plan. It's the plan for the whole season that one practice plan fits inside.