How do you respond and adapt a plan when an athlete gets sick and misses a week of training? This post we explain the mechanics behind the weekly update and finish with an example of that exact situation.
Plans in Bereda give weekly targets to use when building workouts into an athlete’s training calendar. These targets can be seen in the tooltip when you hover over individual training load bars, or in a spreadsheet format in the calendar view.
Athletes almost never 100% match the targets for a given week, sometimes missing by a large amount if they get sick or something pops up in their lives, and so it’s important that the ATP can adapt and evolve over time. Bereda achieves this with the “Weekly Update” feature.
When you open the weekly update, it shows the planned values for the first week of the plan which include Fitness (CTL), Form (TSB), Training Load and Training Hours. With the update, you’re able to enter the actual values the athlete hit by the end of the week, and the entry field hint text shows the corresponding date(s) for the value you’re looking for.
None of the values are required. Leave any value blank and Bereda will approximate it based on what you have input.
To get the most out of your past data, filling in Fitness (CTL) is recommended. If you only have access to Training Load values then you can input that instead and Bereda will approximate the Fitness (CTL) and Form (TSB). Filling in all 3 values will allow you to keep exact track of your training progress in past data.
If you don’t input a value for Training Hours, Bereda will approximate them based on the week’s actual Training Load and the planned intensity.
After a weekly update, the plan is in sync with the athlete’s real-world progress. The remaining weeks in the current mesocycle adjust automatically to maintain the Fitness (CTL) and Form (TSB) targets at the end of the current mesocycle, so they will all have new training load values. You can see the new training load and hour targets in the tooltips.
When athletes are close to hitting their targets in the previous week, then these changes are small. If the following weeks of training are already planned in an athlete’s calendar, an option is simply to tweak the duration of the weekend’s endurance ride to account for the change in weekly training loads. If an athlete missed their targets by a large amount, a coach can make decisions about whether to adjust the plan moving forward in more significant ways.
Add and Create Past Data
Over time, a history of an athlete’s training will get built up as you update the plan each week. To get a head start, you can seed Bereda with multiple years worth of data by importing it directly into the app.
This “Past Data” is something you can toggle on and off when planning.
If Past Data is toggled on, you can sync your plan with it so that the plan’s Starting Fitness (CTL) and Form (TSB) values match those at the end of the Past Data, on that specific date. If there is a gap (or overlap) between the plan and the Past Data, Bereda will adjust the plan to make the sync.
If the plan is in sync, your weekly update will add values to the past data.
You can also choose to update plans without Past Data toggled on, or when they’re out of sync, in which case Bereda will just “throw away” the values from the weekly update instead of adding them to the Past Data.
This gives you the ability to have extra plans on the side to test “what-if” scenarios, experiment with different startegies for the season, etc.
Example: Adjust a plan after a missed week of training
Here’s a common scenario: an athlete gets sick one week and doesn’t get much training done.
Your plan looks like this:
All of a sudden the following week has to be HUGE in order to hit the Fitness (CTL) and Form (TSB) values at the end of the current mesocycle. What do we do? Adjust the plan.
First, that sick week was essentially a rest week. The athlete is recovered now and ready to start a new mesocycle. So, instead of keeping the two weeks remaining in Base 1, followed by the four weeks in Base 2, we’ll adjust the plan by sliding the meso division and make two 3-week mesocycles, as seen above.
We still have a problem: because of the missed week our current Fitness (CTL) is much lower than planned. Even after sliding the mesocycle division, we have a LARGE ramp rate in Base 1, much more than Base 2 and the rest of the plan.
Using a Fitness (CTL) edit, we can even things out:
You’ll notice the black Fitness (CTL) points near the ‘A’ race. These are fixed points, which hold their value unless moved directly.
So, when we pull down the Fitness (CTL) at the end of Base 1, evening out the ramp rates, the entire plan is updating and still maintain the goals specified for the target ‘A’ race.
The final result:
Head back to: The Complete Guide to Bereda
Helpful? Confused? Let us know what you think by clicking the chat icon in the bottom right-hand corner of the screen.