How to plan the grassroots football season: blocks, goals and microcycles

Preseason gets you to the first match, and the weekly microcycle solves one week of training. Between those two scales sits the real gap: what the team builds between September and June, and in what order. Without that map, every week looks like the last one out of inertia, not because it follows a plan.

This article covers that middle scale: the blocks of a full season, with their goal and how to review them. For the concrete start of the first weeks, the guide on grassroots football preseason already covers that stretch week by week; this article picks up where that phase ends.

The grassroots season follows a stable pattern across most regional federations: preseason in August and the first weeks of September, a regular league from September to May or June depending on category and competition, and two long breaks at Christmas and Easter that cut the year into natural stretches.

Those breaks are not a problem for planning, they are the structure already sitting in front of you. Instead of treating the season as one uniform nine-month block, it helps to think in the stretches the calendar itself already marks. The Christmas break is the big border splitting the season into two halves; the Easter break is a minor cut inside the final stretch, useful for breathing and adjusting, but it does not force a change of block.

The exact competition format and calendar vary by category and regional federation, but the logic of the breaks repeats across almost the whole map.

Classic professional periodisation splits the season into macrocycles and mesocycles designed for teams training five or six days a week, with recovery protocols and a target competitive peak. That model cannot be copied as-is at grassroots level: with 2-3 weekly sessions and players still growing, there is no room for form peaks or for load that piles up across several sessions in a row.

What does work is adapting the underlying idea — splitting the season into blocks with their own goal, each roughly matching a school term — to the real rhythm of a grassroots club. Four blocks, built on the calendar from the section above:

Load inside each block is limited by age, not by the competitive calendar: a cadete in the middle of a growth spurt needs a much more cautious load progression than a juvenil, even if both play the same league in the same months.

The same block means different things depending on the group's age. It makes no sense to set the same quarterly goal for a prebenjamín as for a cadete, even if they share the calendar.

The detail of which task fits which age band, block by block, is in the guide on grassroots football exercises by age; the goal here is to set what to build in each stretch, not the exact drill for each session.

The block sets the goal for the stretch; the week is where that goal actually gets trained. Each weekly microcycle inside a block should add one more layer to the same idea, instead of jumping topic every week.

The concrete mechanics of a week — which session fits Monday depending on the weekend result, how load splits across sessions — is worked out in the guide on the Monday session and the weekly microcycle. This article stays at the annual scale, which block is active and what goal it chases; that guide solves the specific week inside that block.

A useful trick: when planning each block, decide its goal first and only then assign which microcycle introduces the idea, which consolidates it and which tests it in a match. Planning the week before the block usually ends in a jumble of loose topics with no thread connecting them.

December is the first real checkpoint, not a close. Before the Christmas break it is worth reviewing, block by block and player by player, whether the goal of blocks 1 and 2 was met: not just results, but what each player has improved since September and what to adjust in block 3.

June is a real close. Three things are worth checking: whether block 4's goal and the season's overall goal were met, which players have changed physical or developmental level over the year — especially relevant in cadete and juvenil — and what to carry into designing block 1 of the following season.

Avoid drawing conclusions from a single match, in December or in June. One bad result on a given day says little about whether the block met its goal; the useful question is whether the group progressed on what that block was aiming for, not whether it won last weekend.

The most repeated mistake is copying a senior team's logic: chasing a form peak for one specific match, adding load-and-deload microcycles designed for adults, or treating every week as if something had to be won. In grassroots football almost no single match justifies that approach, and the cost on children and teenagers is high.

The second mistake is leaving no margin for the club's reality: a pitch shared with other teams, sessions cancelled for rain, last-minute schedule changes, players missing for exams. A block plan that allows no lost weeks breaks at the first setback. It is better to leave one buffer week per block with no new goal, built to absorb these disruptions without derailing the whole plan.

The third mistake is setting the block's goal on the whiteboard and never reviewing it. A block that is never checked at the two checkpoints — December closes the first half and June the second — is just an intention, not a plan.