Start with the boundary question, not the age chart
Most clubs default to age-based groups because registration software wants a birth year. Age is a poor primary filter past the first few years of swimming. Two 12-year-olds can be four seconds and two training years apart on 100 free. Group them by age alone and you either bore one or break the other.
Use three filters, in this order:
- Ability — best times relative to standard, and more importantly, what they can hold on a repeat set. A kid who can hold 1:15 on 100s free at aerobic pace belongs in a different lane than one who can't hold 1:30.
- Training age and event specialization — a 14-year-old sprinter with three years in the sport trains differently than a 14-year-old distance swimmer with the same training age. Once swimmers specialize, group by what they need to practice, not just how fast they are overall.
- Age, last — mainly to keep social and developmental fit sane. A talented 10-year-old usually shouldn't practice with 16-year-olds even if the times overlap, for reasons that have nothing to do with physiology.
Split a group when you can no longer write one set that serves everyone in it without half the lane either coasting or drowning. That's a feel call, but there's a numeric proxy: if the pace gap on a core threshold set (say 100 free at threshold) exceeds about 8-10 seconds within a lane, you're writing two sets disguised as one.
Merge groups when numbers drop and you're running a lane of three with a coach standing over them. A group under about 6-8 swimmers rarely justifies its own coach and its own program — fold it into an adjacent group and adjust the work for a subset within the same set.
What to track per group
Per squad, per week, track:
- Weekly volume — total distance, broken out by stroke if you're picky, but distance alone is enough for most decisions.
- Rolling weekly average — volume averaged over the trailing 3-4 weeks.
- Zone distribution — percentage of the week's work in aerobic (A1/A2), threshold, VO2/aerobic capacity, and speed/anaerobic zones.
The rolling average matters more than any single week's total. A raw weekly number is noisy — a meet week, a holiday, a pool closure, or a coach who ran a monster main set on Tuesday will all distort a single week's total without meaning anything about the squad's actual trajectory. A group that logs 28,000 / 34,000 / 22,000 / 31,000 over four weeks looks fine week to week, but the rolling average tells you the real number the squad is training at is around 29,000, not whatever happened last Thursday.
The rolling average also catches drift early. If a squad's target load is 32,000 m/week and the rolling average has quietly slid to 26,000 over six weeks, no single week screamed a problem, but the trend did. That's a conversation with the assistant coach before it shows up as a flat taper or a slow August.
Zone distribution is the check on quality, not just quantity. Two squads can both hit 30,000 m in a week — one at 70% aerobic and 10% threshold, the other at 50% aerobic and 25% threshold. Same volume, very different stress. If you're only logging total meters you'll miss that entirely.
Keeping multiple coaches on one program
The failure mode with several assistants running their own squads is not lack of talent — it's drift. Each coach has their own preferred rep counts, their own feel for pace, their own habit of adding "just one more" round when the group looks good. Over a season that turns one program into four different programs wearing the same team suit.
Fix it with a shared weekly template, not a shared set. Give every squad coach the week's targets — total volume, zone percentage breakdown, and the one or two focus sets for the week (say, a threshold broken 500 on Tuesday and a race-pace set on Friday). Let them write the actual sets for their group's ability level. The structure stays consistent; the execution stays theirs.
Review actual volume and zone numbers against target at a weekly staff meeting, five minutes per squad. This is where the rolling average earns its keep again — it's a much better meeting topic than "how was Tuesday," because it shows whether a squad is tracking to plan over weeks, not just vibes from one practice.
A sample structure for a mid-size club
Six coaches, four squads:
- Senior (2 coaches, split by lane within one program) — event-specialized sub-groups for sprint/mid-distance and distance/IM, sharing a training week structure.
- Age Group (2 coaches) — split by ability into two lanes-worth of groups if numbers support it, common weekly volume target with paced adjustments.
- Pre-Comp (1 coach) — technique and aerobic base focus, low volume, no zone tracking beyond "easy vs. moderate."
- Masters (1 coach) — ability-based lanes within one practice, volume tracked loosely, mostly for member engagement rather than performance planning.
Common mistakes
- Groups too broad: one "Age Group" squad spanning 9 to 14-year-olds with a 20-second pace spread. You end up writing sets for the middle and losing both ends.
- Groups split too finely: six squads for 40 kids, none with enough numbers to hold a consistent lane pace or generate meaningful weekly data. Consolidate until each group has enough swimmers to make its numbers mean something.
- No shared tracking format: if each coach logs volume differently — or not at all — you can't compare squads, spot drift, or hand a group to another coach mid-season without starting from scratch.
Getting groups and tracking right is mostly discipline, not cleverness. The clubs that do it well aren't smarter about grouping — they just check the numbers every week instead of assuming the plan on paper is what actually happened in the water.
SwimIQ helps with the tracking side of this directly — log or photograph what each squad actually did, and it rolls the sets up into weekly volume, rolling averages, and zone distribution per group, so a head coach can spot a squad drifting off target without chasing down six sets of notebooks.