Coaching 140+ athletes with one system: a periodization-at-scale teardown
To coach a large roster with one system, you separate what scales from what does not. The training structure, the periodization phases, and the weekly template scale to the whole squad. The individual prescription, the loads tied to each athlete's training max, and the event-specific work scale to small subgroups. A coach running a 140-athlete squad does not write 140 plans. They write one periodized structure, split the roster into training groups and event subgroups, then let per-athlete numbers fill in against each athlete's own reference values.
The real problem is not roster size. It is repetition.
A coach with a 140-athlete squad is not doing 140 times the work of a coach with one athlete. Most of the training structure is shared. Sprinters in week three of a general preparation phase are doing variations of the same template whether there are eight of them or eighty. The work that does not scale is narrow: the absolute loads, the event-specific drills, and the handful of athletes coming back from injury.
So the question for any system is not "can it hold 140 names." A spreadsheet holds 140 names. The question is whether the system lets you write the structure once and apply it broadly, while still letting you individualize the few things that genuinely differ between athletes. Get that split right and a large roster is manageable. Get it wrong and you are copy-pasting the same session 140 times, which is how coaches end up back in a notebook.
Periodization gives you the scaling layer. The classical model organizes a training year into phases with planned shifts in volume and intensity, so the structure of a week is a property of where you are in the season, not of the individual athlete (Bompa & Buzzichelli, 2018). That shared structure is what lets one plan serve many athletes.
Step one: group the roster by who trains together
The first cut is the training group. These are the squads that show up to the same session: a sprint group, a throws group, a development squad, a senior squad. They share a schedule and broadly share a phase structure.
In Sprinting, athletes belong to groups, and the roster view filters by group with one click. You can search by name or email, sort by name or by last-active date to spot who has gone quiet, and select multiple athletes at once. Bulk operations let you add a batch of athletes to a group, move a batch from one group to another, or remove a batch, each behind a confirmation step for the destructive ones. For a coach onboarding a new intake of thirty athletes, that is one select-all and one assign, not thirty individual edits.
The grouping is also the unit your reporting and planning hang off. When you look at the roster, you see each athlete's group, age, sex, event list, and when they last trained, so the squad is legible at a glance rather than a wall of names.
Step two: subgroups for the work that splits within a group
A sprint group is not homogeneous. Inside it you have short-sprint specialists, long-sprint athletes, and maybe a few who double into the long jump. They warm up together and follow the same phase, but their main set diverges. This is the second cut, and it is the one most team-management tools handle badly.
Sprinting models this with subgroups. A coach defines a subgroup with a short abbreviation and a name, for example SS for Short Sprints or LJ for Long Jump. Each athlete can carry more than one subgroup, because a 200m runner who also long-jumps genuinely belongs to two. Subgroups are deliberately abbreviated to three characters so they read cleanly as badges across a crowded roster.
The payoff comes at the planning stage. When you build a session, you target specific exercises at specific subgroups. The acceleration block goes to SS, the speed-endurance block goes to the long-sprint subgroup, and the general strength work targets everyone by default. One session plan, written once, resolves to different prescriptions for different athletes inside the same group. That is the mechanism that lets a single session serve a mixed squad without the coach forking it into three.
Groups answer "who trains together." Subgroups answer "who does which part of today's session." You need both cuts to run a mixed squad off one plan.
Step three: periodize once, then duplicate the structure forward
With the roster grouped, the periodization itself is where one-system economy pays off most. A training plan is a sequence of phases, each phase a set of weeks, each week a set of sessions. The structure repeats with controlled variation, which is exactly what block and traditional periodization both rely on (Issurin, 2008).
In practice you do not write twelve distinct weeks from scratch. You build one good week, then copy it forward. Sprinting's duplicate-week tool takes every session from one week and copies it into one or more other weeks in the same phase, preserving the day assignments, so a Monday acceleration session lands on the other Mondays. You then adjust the few things that progress week to week: a little more volume, a slightly higher intensity, a new exercise variation. The shared 80 percent comes for free; you spend your attention on the 20 percent that changes.
This is the difference between planning a season and re-typing it. The coach's judgment goes into the progression logic. The mechanical duplication is the software's job.
Step four: individualize where it actually matters
Scaling structure does not mean every athlete lifts the same kilos. Individual response to the same training load varies enough that prescribing identical absolute loads across a squad is a mistake (Issurin, 2010). The trick is to individualize the numbers without re-authoring the plan.
Sprinting handles this with relative loading. Each set carries flat, per-set fields the coach edits directly: reps, weight, distance, time, rest, tempo, RPE, effort percentage, velocity, power, height, and resistance. When you prescribe by effort percentage against an athlete's training max or personal record, the same "squat at 80 percent" line resolves to a different bar weight for each athlete, computed live against their own reference value. You write the intent once. The system does the per-athlete arithmetic.
That is the resolution of the scale problem. The phase structure is squad-level. The session template is group-level. The exercise targeting is subgroup-level. The load is athlete-level. Each layer is written once at the right altitude, and the layers compose into a concrete, individual prescription without the coach touching 140 separate plans.
Getting an existing plan into the system fast
The friction with any new system at scale is migration. A coach who already runs a 140-athlete program has years of sessions in spreadsheets, documents, or photographs of a whiteboard. Re-typing all of it is the reason most large rosters never move off their current tool.
Sprinting includes an AI session parser to shorten that. A coach pastes free-form program text or uploads up to ten screenshots or photos of an existing plan, and the parser extracts structured exercises with the same flat per-set fields used everywhere else: reps, weight, distance, time, rest, tempo, RPE, effort, velocity, power, height, resistance. It also recognizes superset and circuit grouping. You review and correct what it pulled, which is faster than typing from a blank page. It reads those flat scalar values; it does not ingest device-level velocity-loss curves or force-plate profiles, so treat it as a fast first draft of structure, not a metrics import.
The honest framing: parsing gets the skeleton in quickly. The individualization and periodization steps above are where the coaching actually lives.
Where other tools land, honestly
Large-roster strength platforms handle scale competently. TeamBuildr, for instance, publicly describes serving athletic departments managing hundreds of athletes, with group-filtered reporting and velocity-based, percentage-based, and periodized programming (per teambuildr.com, accessed 2026-05-29). If your context is a weight-room-centric program, those tools are mature and worth a look.
Sprinting's defensible difference is track-first structure rather than raw roster capacity. The subgroup model maps to event specialization the way a track coach actually thinks. The session targeting splits a mixed sprint squad off one plan. The per-set fields include the ones field events and sprints care about, like distance, time, and height, alongside the gym ones. If you coach track and field and want the system to model events natively, that is the fit. If you run a barbell-heavy team program, weigh it against the established strength platforms.
| Scaling need | How Sprinting handles it | Layer it scales at |
|---|---|---|
| Athletes who train together | Training groups + bulk add/move/remove | Squad |
| Event specialization within a group | Subgroups (multi-assign per athlete) targeted per exercise | Subgroup |
| Repeating weekly structure | Duplicate-week into multiple weeks, day assignments preserved | Phase / week |
| Per-athlete load from one prescription | Effort % auto-computed vs each athlete's training max / PR | Athlete |
| Migrating an existing plan | AI parse of text or up to 10 screenshots into structured sets | One-time import |
FAQ
- How do I manage many athletes in one training system without writing a plan for each one?
- Separate the layers. Periodize the phase structure at the squad level, build the weekly session template at the group level, target exercises at event subgroups, and let per-athlete loads resolve from one prescription via relative percentages. You write each layer once at its correct altitude rather than authoring a full plan per athlete. In Sprinting that means training groups, subgroups, duplicate-week, and effort-percentage loading against each athlete's training max.
- What is the difference between a group and a subgroup for a club roster?
- A group is who trains together and shares a schedule, such as a sprint squad or a development squad. A subgroup is the split within that group by event focus, such as short sprints versus long jump. An athlete belongs to one group but can carry several subgroups, because event doublers genuinely train in more than one. When you build a session, you target exercises at subgroups, so one plan resolves to different work for different specialists.
- Can I copy a week of training to other weeks instead of rebuilding it?
- Yes. Sprinting's duplicate-week tool copies every session from one week into one or more other weeks in the same phase and preserves the day assignments. You build one strong week, copy it forward across the phase, then adjust only the progression details that change week to week. This is the main mechanism that keeps periodizing a long season from becoming repetitive re-typing.
- If I prescribe one squat set to a whole squad, does everyone get the same weight?
- Only if you prescribe an absolute weight. If you prescribe by effort percentage against each athlete's training max or personal record, the same line resolves to a different bar weight per athlete, computed live against their own reference. That is how you write one session and still give each athlete an individualized load, which matters because training response varies between athletes.
- Can I import my existing spreadsheet or whiteboard plans, or do I have to retype everything?
- You can paste free-form program text or upload up to ten screenshots or photos, and the AI parser extracts structured exercises with the standard per-set fields and superset grouping. You review and fix what it pulled. It reads flat scalar values like reps, weight, distance, time, RPE, effort, velocity, and power; it does not ingest device-level metrics like velocity-loss curves or force-plate profiles, so treat it as a fast structural first draft rather than a metrics migration.