Hi Scott(s),
thank you for clarifying!
This leads me to my next questions.
In the book you specify Early and Late Base Period.
Let’s say I’m planning 2-3 goal A (may-july) events for the next season, along with some B and C tune up races in the middle.
I’m now at the beginning of my Transition Period, so no worries about time, but what I would like to know is when to consider all those “B” (base) weeks Late or Early.
Do you mean “early” and “late” according to the macrocycles or the whole season?
Try to better explain: will be there some early and late B weeks for every macrocycles / “A” race or absolute early (september > february) and late (from march towards the end of the season) base weeks?
I hope you understand my doubt.
I also have another question regarding the main topic (weekly elevation gain) of my post.
Let’s say I’m planning one of the Base weeks leading up to my A race (80k 4500mD+).
The goal would be to do 2 Late Base (peak?) weeks of 4500D+ each.
From the example at page 353 i see this scenario.
weekly Elevation: 4500mD+ (100%)
d1 – off
d2 – 15% weekly vert = 675
d3 – 10% of time = ?
d4 – 10% of distance= ?
d5 – 10% weekly vert = 450
d6 – 15% weekly vert = 675
d7 – 40% weekly vert = 1800
in this way there are something like 900m left ti distribute on the days where the elevation is not a specified target (d3 and d4).
is this the right approach?
my concern here is: in my previous training seasons I’ve always added lots of runs on flat and gentle terrain, also adding speed workouts (some of them on track).
in this way I do not have the time and room for flat runs: I fear I’m missing something.
Thanks and sorry for all this confusion.