The four-phase structure
A 90-minute session breaks down well into four phases, each with a distinct purpose. None of this is rigid — shorter sessions (60 minutes) compress proportionally — but the four-phase shape gives any session a coherent arc rather than feeling like a list of unrelated activities.
Phase 1: Arrival and warm-up (10-15 minutes)
Players arrive at different times — a simple, ungoverned activity (ball each, free play) that anyone can join as they arrive avoids the "everyone waits for everyone" problem. This flows into a proper warm-up (see our warm-up games guide) once most players are present.
Phase 2: Technical work (20-25 minutes)
The session's main technical focus — whatever the session's theme is (passing, first touch, finishing). This is where specific coaching points get introduced and repeated, in activities with enough repetition for them to land.
Phase 3: Phase of play / small-sided game (25-30 minutes)
The technical theme gets applied in a more game-realistic context — a small-sided game, ideally with a condition that rewards the session's focus (see our small-sided games guide). This is where "training" starts to feel like "football."
Phase 4: Game and cool-down (20-25 minutes)
A fuller game — less conditioned, more "just play" — followed by a brief cool-down and reflection (see our half-time team talks guide for the kind of brief, focused reflection that works). This is often the part players enjoy most, and ending on it sends everyone home positive.
Why this order
The progression — technical isolation, then applied, then full game — is a deliberate build in realism and complexity. Starting with the game (skipping straight to phase 4) means the technical focus never gets isolated long enough to actually develop; starting with too much technical work and never reaching a real game means it never gets tested in context. The four phases build toward each other.
Scaling for shorter sessions
For a 60-minute session, the same four phases compress roughly proportionally — arrival/warm-up (8-10 min), technical (15 min), phase of play (15-18 min), game/cool-down (15-18 min). The shape stays the same; only the time in each phase shrinks.
Adjusting the structure by age
Younger age groups (U7-U9) generally need shorter phases and more frequent transitions — attention spans are shorter, so five 15-minute chunks with variety often work better than the same four-phase shape stretched out. Older groups (U13+) can sustain longer technical phases and handle more complex phase-of-play conditions, since concentration and tactical understanding have both developed.
What to do when a phase isn't working
Sometimes a planned activity clearly isn't landing — players are confused, disengaged, or the intended coaching point isn't showing up in how they're playing. Being willing to cut a phase short or simplify it on the spot, rather than rigidly sticking to the plan because it's what was written down, usually serves the session better than persisting with something that isn't working.
Common pitfalls
- Phase 2 running long and eating into the game time — players generally remember the game most, so protect phase 4's time.
- No connection between phases — if phase 2's technical focus doesn't show up in phase 3's conditions, the session feels like unrelated activities rather than a coherent whole.
- Skipping phase 1's free-play element — leads to the "everyone waits for stragglers" problem that wastes time and energy at the start.
Building in flexibility without losing structure
A written plan is a starting point, not a script to be followed rigidly regardless of what actually happens on the night. Leaving a rough five-minute buffer somewhere in the middle of the session — unassigned, ready to absorb whatever runs long or short — means small overruns don't cascade into a rushed, cut-short game at the end, which is usually the part of the plan worth protecting most.
Planning for low turnout
A session planned for sixteen players doesn't automatically work with eight — some activities need reshaping on the spot (smaller grids, fewer teams, a condition removed) rather than persisted with at half the intended numbers. Having a rough mental fallback for "what if only half the squad turns up" before arriving at training means a thin turnout doesn't derail the whole session.