Sorry I know this has been discussed, but my search only showed old results. I have 2 events this year, both of which I consider A events and they are 9 weeks apart so the old Plan Builder allowed me to have both of them as A events on my Calendar. When everything switched to AI earlier this year I had to change the second event to a B event, but now that I finished my first A event I wanted to make the second one an A event so I would get a proper taper. I assumed since the other A event was finished I could just go in and change the B to an A, but it wouldn’t let me. I deleted the old plan, and started a new plan with the start date as the original plan start date. It still wouldn’t work, until I changed the completed A Event to a B Event. Is this the correct thing to do? Should I just start a new plan with today as the start date? Should I just leave my second event as a B event and adjust the taper myself? Any pointers would be appreciated!
Watching. I liked the old system that allowed me to have multiple A events in a plan as long as they were an adequate distance apart.
yea, it was much more convenient than the mess I’ve been going through.
Yep, I had an A event in May, and have another in Oct. Have had to create 2 plans, and leave a gap between the 2 plans for a recovery week, since the second plan doesn’t look at any previous work and wanted to give me a VO2 workout 2 days after a 6+ hour race.
A big step backwards.
I had the same thing happen after my A event in June (I have another A event this fall). It wiped out my endurance/rest week and scheduled VO2 and threshhold workouts for the next week.
I’m a fan of the AI, but this is a bug. A system that has access to the past 14 years of my training should have “check recent training/events before starting new plan” as the default option.
I would go further, this is a functionality that has been removed. I don’t see a valid reason why we lost the ability to plan a full season of training with 2 A events months apart, as used to be the case.
I find I’m having to stick handle things more and more
100%. You’re telling me AI doesn’t know how to handle peaking for two separate races? Really? What year is this? Huge miss from TR.
I just had my A race. Or the weekend it was supposed to be and the plan had scheduled a rest week after it automatically. My next plan also has the rest week scheduled automatically after the event.
It is strange that mine behaved as expected and multiple others are not. Did you do an event specific plan or some like getting faster for xyz.
It’s to allow for dynamic endurance. I honestly don’t get why you would want 1 plan over two plans? I have two A races. 9 weeks apart, by having two plans the build and speciality are race specific. It is like 5 minutes of additional work if that to set up the second plan.
Are you saying that there was a rest week scheduled after your A race at one point and then those workouts were adapted to hard ones?
That sounds like a bug.
There should always be a recovery week scheduled after your A race. If this wasn’t happening for you, I’d have to take a closer look to see why that might have happened.
Really? I can’t see why anybody would want 2 separate plans over 1 unified yearly training plan. I’d much rather have a yearly plan that takes in all my events together to give me a single training structure to excel at my 2 main events. Why would I want 2 separate plans? I don’t want a reset after my event. I want one plan that gives me the best opportunity to crush both events. My racing year isn’t blocks or discrete. It’s a full year.
Here’s a quick example.
2 separate plans: A race in early May is a series of crits. A race in fall is long gravel race. 2 separate training plans has me focusing on the crits over winter into early spring. Sure, I get prepped for those crits. But now it’s mid-May and I don’t have the huge aerobic base I need for the gravel race. And the time to shift focus isn’t ideal. So now my gravel plan is not as optimized as it could be.
1 unified plan, same races. Since the plan knows I have a long gravel race later in the year, it sprinkles in long endurance rides and long sweet spot over winter and before the crit series. Now I still get the crit prep, but after that, I’m in a way better spot to hit the ground running for the gravel prep. Because I don’t treat the races as isolated events, I get a more unified training plan to maximizes both events. In the long run, it’s going to be way better.
The previous approach wasn’t one unified plan as it didn’t have the dynamic endurance. If you are concerned about base, set your A race crit to have a duration of like 4 hours. Although if the crit series is in May and Gravel race is fall, it should be more than enough time to build up volume
I feel like people thought the unified plan in the past was doing more than it was.
That is exactly what I am saying. Original schedule had my 2nd A race (this fall) as a B (because you can’t have two A races in a plan). Following my first A race in June (4 races in a weekend), the plan had a rest/endurance week following. Day after that last race, I changed my second A race to A, which required a new plan. The new plan changed my rest week to a normal week with VO2 and threshhold workouts.
In the past, I simply had to insure my A races were at least 8 weeks apart, and the program handled everything fine.
I agree 100%. Give me one plan that can take all my races into account, and I can have an 18-24 month plan that has me dialed in for each of my A races.
Workarounds are just proof it doesn’t work. I shouldn’t need a workaround. If AI is supposed to be smart and learn, it should be able to figure this out. The fact it can’t is because TR is hampering the functionality. Any human coach could figure this out, or at least see the issue. Thats the crux of the problem.
It was giving me more than 2 hour rides, that’s for sure. Bottom line is that the 2 separate plan option is worse than 1 plan for a lot of people. If it works for you, great. But it should work for everybody. And it doesn’t.
The example above wasn’t pulled from thin air. It is what TR gave me. If I put the gravel race as the A race, it gave me base all spring and treated the crit series as an afterthought. No taper, no rest, very few hard suprathreshold workouts. It put it in the middle of a base phase. If I put the crit as the A and gravel as B, I was getting almost no long endurance or long SweetSpot. I wasn’t really getting any long rides at all. Both options kind of stunk.
Ahh, so it was the changing of event priorities that caused that. That makes sense since we treat A and B races differently.
I can see how this can be annoying, though.
At that point, I’d argue that your preparation for the Crit series wouldn’t be as good as it could be.
For A races, the intention from our end is to go all in on those events. Prepping for a gravel race that’s 8-10 months from now when you have a crit series in 5 months seems a bit unnecessary to me.
If they’re both truly A races and there are 4-5 months between them, I’d recommend focusing on each race individually.
While crits are different than gravel races, you’re still going to come out of that crit series with good aerobic fitness and there is plenty of time to build into sustained work before that gravel race. 
In the past, did it manage this better? I always set the goals up as separate plans as logically it made sense. I don’t see how it deprecated functionality vs not delivering it ideally.
Always event specific.