Smart Progressions
Progression rules move an athlete’s prescribed weight when they hit the targets you set. Preview every change before it lands, and roll it back if you change your mind.
Overview
A progression rule has three parts: which exercises it watches, what has to happen before it fires, and what it changes. When an athlete meets the trigger, the rule works out a new prescription for their upcoming sessions and shows it to you as a diff. Nothing changes until you apply it.
Rules are per athlete. A rule assigned to a group runs once for each member, so each athlete's own history drives their own numbers.
How To
Creating a rule
- Go to Planning > Smart Progressions
- Click New rule
- Give it a name, for example "Back squat, +5 lb when all reps land"
- Pick a trigger, what has to happen first
- Add one or more changes, what moves when it fires
- Choose which exercises it watches, and which athletes or groups it applies to
- Decide whether you review each change or it applies automatically
- Turn Active on and save
A rule does nothing until you turn Active on.
Triggers
- Athlete completed all prescribed reps — every set was logged at or above its rep target
- Session RPE at or below a target — the athlete rated the session at or below the number you set
- Reps completed and RPE at or below a target — both of the above, which covers "add 5 lbs when the athlete completes 3x8 at RPE 7 or below"
- Every pass — no performance condition at all
You can require several consecutive sessions before a rule fires.
RPE is recorded once per session, not per exercise, so an RPE trigger reads the whole workout rather than the individual lift.
Changes
- Weight — add a fixed amount or a percentage
- Reps — add reps to every set
- Sets — add a set, or set the count outright
- Intensity — prescribe a percentage of the athlete's estimated 1RM
- Target RPE — set the RPE you want the athlete working at
- Swap exercise — move to a different exercise
For weight and intensity you can also set a rounding increment, a ceiling, and a cap on how far a single application may move the number.
Reviewing or applying automatically
A rule set to Review does nothing on its own. You open an athlete's schedule and preview it when you want to.
A rule set to Apply automatically runs on the cadence you pick: every run, weekly, fortnightly or monthly. It changes athlete programming without anyone watching, so you get a notification afterwards saying what moved. Every automatic run can still be rolled back.
Automatic rules run overnight. A rule that has not reached its cadence yet is skipped until it has.
Progressing a schedule
- Open the athlete's schedule editor
- Click Preview progression
- Read the diff: one row per exercise per session, each with the reason it fired
- Untick anything you do not want
- Click Apply Progression
Progressing a whole group
- Open the group's schedule
- Click Preview progression
- Each member gets their own section, with their own numbers
- Untick anything you do not want, then apply
Members with nothing to progress are left out of the list.
Undoing a progression
Open the run from the athlete's progression history and roll it back. Any field you have since edited by hand is left alone rather than overwritten, and reported as edited since.
Why a rule might not fire
The engine will not add load on incomplete data, so it says nothing happened rather than guessing.
- Not enough sets recorded. The athlete app only saves sets the athlete typed into. If they did three sets but only filled in two, the session cannot be confirmed as complete.
- No RPE. An RPE trigger uses each set's RPE when the athlete logged one, and falls back to session RPE for sets that have none. It will not fire if a set still has neither.
- Not enough history. A rule asking for three consecutive sessions waits until there are three.
- Plyo exercises. These carry several weights rather than one load, so "+5" has no single thing to apply to. They are reported as skipped.
- Exercise swapping is turned off. A swap action needs the Exercise Swapping feature enabled for your organization. A progression will not route around that setting.
Every one of these appears in the preview with the reason, so you can see why a given exercise was left alone.
Things worth knowing
- Applying a progression turns those sessions into per-athlete copies. Later edits to the library workout will not reach them.
- A rule only progresses as far ahead as its horizon, 14 days by default. Later weeks progress on subsequent runs, once there is performance data to base them on.
- Weight has no unit attached to it. "+5" means five of whatever the exercise is configured in, so keep a rule to exercises that share a unit.
Tips
- Start with small increments and a cap on how far one application can move a number.
- Use an RPE trigger to make sure the quality is there before the load goes up.
- Preview before you apply until you trust a rule's behaviour.
Referenced by
- 'Schedule Editor'scheduling
- 'Schedule Templates'workouts
- 'Tracking a Workout (Athletes)'athletes