Athlete program modifications allow coaches to assign a main program to multiple athletes. Then apply modifications and individualisations to the athlete versions without having to change the main program.
Examples of when you might use this include:
Applying a program to a team then making changes per athlete
Assigning a program to a sport then making individualisation from there
Assigning a program to an athlete that has a pre-defined purpose i.e. Lower leg push progression.
Modifying an athlete version
2. Select the athlete from the dropdown menu at the top-right corner of the page
From here you can choose between Synchronised or Branched.
Synchronised
A Synchronised Program allows you to make edits for an athlete, while also inheriting edits from the main program that don't overlap.
In a Synchronised Program you can:
Change the start date of the program
Add, remove or modify sessions and exercises
Example:
Your create a program that is 4 weeks long.
You create a "Synchronised" version for Joe. You make a number of edits specific for Joe
At a later date you return to the Main Program and add another 4 weeks.
Joe's program now consists of their initial 4 weeks + edits, as well as the 4 weeks now added to the Main Program.
After you modify a session, it will no longer sync with the main program, unless you restore it.
This can be noted by checking for the "Modified" heading on a session. If you were to edit Day 2 in the Main Program, those edits will NOT synchronise with Day 2 on Joe's Synchronised Version.
Synchronised Program Use Case
A common scenario for this workflow is managing a group of athletes — such as a team or individuals competing in the same sport — where the main training program evolves over time to reflect competition schedules and sport-specific demands.
In this case, you might build an initial preparation phase targeting a specific competition period. Once that phase is established, you can make individual adjustments for each athlete as needed.
When it’s time to create the next preparation phase in the main program for a subsequent competition, all athlete-specific versions will automatically inherit the updated structure and content of the new phase.
Branched
A Branched Program creates a copy of the main program to use as a starting point. From that moment, the main program and the athlete’s version become independent. The athlete’s version can then be treated as a standalone program.
A key distinction with branched programs is that any edits made to the main program after branching will not be reflected in the athlete’s branched version.
In a Branched Program you can:
Change the start date of the branched program
Add, remove or modify sessions and exercises
Add and remove weeks
Add and remove blocks and phases
Branched Program Use case
The typical use case for this is when the Main Program is more of a "blueprint" of a completed program. You can assign this blueprint to an athlete and make changes as you need.
For example, in a high-performance or athletic development setting, you may have a program designed for a specific training objective such as Field Sport Off-Season Hypertrophy. In this scenario, the Main Program would form the "template" for each of the assigned athletes, and you would make individual adjustments based on their needs. The main program remains unchanged, serving as a reusable foundation for future athletes or cycles.