# No rest week before a week-long stage-race. Really, TrainerRoad?

**URL:** <https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058>\
**Category:** TrainerRoad Software\
**Created:** [June 22, 2025, 9:11am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058 "2025-06-22T09:11:38Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![nene](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nene/32/120214_2.png) [@nene](https://www.trainerroad.com/forum/u/nene)\
**Post date:** [June 22, 2025, 9:11am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/1 "2025-06-22T09:11:38Z")

</div>

The training plan that TrainerRoad came up for me looks like this:

 ![Screenshot 2025-06-22 at 11.51.43](https://global.discourse-cdn.com/trainerroad/original/3X/a/6/a66fdffaf4a262921e53bae90849cee965ef8813.png)

It amazes me that it doesn’t suggest a rest week before the week-long event. That might be because it’s marked as a C-event. And in reality it’s no race at all. It’s a long hiking trip. But still, it’s not a recovery week in any way shape or form.

Well, I’m for sure not going to follow that suggestion.

I’m used to adjusting the workout-schedule that TrainerRoad suggests to me. But I have so far not seen a suggestion so terrible. Usually it suggests less than I personally would have planned, and then I add some extra on top of it if I feel like it.

---

<div class="post-metadata">

**Author:** ![NWcyclingman](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nwcyclingman/32/18640_2.png) [@NWcyclingman](https://www.trainerroad.com/forum/u/NWcyclingman)\
**Post date:** [June 22, 2025, 9:28am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/2 "2025-06-22T09:28:07Z")

</div>

100% because it is a c event. It’s treated like a hard ride(s).

If you feel you will be fatigued, adjust your training.

---

<div class="post-metadata">

**Author:** ![nene](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nene/32/120214_2.png) [@nene](https://www.trainerroad.com/forum/u/nene)\
**Post date:** [June 22, 2025, 9:57am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/3 "2025-06-22T09:57:51Z")

</div>

Sure.

I mainly posted it to provide some feedback on the deficiencies in TrainerRoad software.

If this happens because it’s a C-event, then IMHO it’s clearly a bug. Not all C-events should be considered equal.

---

<div class="post-metadata">

**Author:** ![OreoCookie](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/oreocookie/32/8298_2.png) [@OreoCookie](https://www.trainerroad.com/forum/u/OreoCookie)\
**Post date:** [June 22, 2025, 10:40am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/4 "2025-06-22T10:40:26Z")

</div>

> [@nene](#):
>
> If this happens because it’s a C-event, then IMHO it’s clearly a bug.

No, that’s how C-events are supposed to be handled: apart from whatever you do on the day of the race, you don’t modify your training calendar.

With B- and A-events you progressively add more significant modifications to your training schedule. So you should re-classify this event as an A- or B-event.

> [@nene](#):
>
> Not all C-events should be considered equal.

If your calendar were created by a human coach, they wouldn’t have classified this as a C-event.

---

<div class="post-metadata">

**Author:** ![NigelTufnel11](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nigeltufnel11/32/160164_2.png) [@NigelTufnel11](https://www.trainerroad.com/forum/u/NigelTufnel11)\
**Post date:** [June 22, 2025, 11:41am UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/5 "2025-06-22T11:41:25Z")

</div>

You should take a look at this page for more info on how to set up your events:

[https://support.trainerroad.com/hc/en-us/articles/360016099031-How-to-Add-A-B-and-C-Events-to-Your-Calendar](https://support.trainerroad.com/hc/en-us/articles/360016099031-How-to-Add-A-B-and-C-Events-to-Your-Calendar)

Summary:

 ![IMG_1039](https://global.discourse-cdn.com/trainerroad/original/3X/5/3/5321b7f0f0c36ffa449133f5fda2f35ad8a97124.jpeg)

So, no issue with the TR logic, your event was just set up incorrectly if you think you need a taper beforehand.

---

<div class="post-metadata">

**Author:** ![Twowkg](https://avatars.discourse-cdn.com/v4/letter/t/ce7236/32.png) [@Twowkg](https://www.trainerroad.com/forum/u/Twowkg)\
**Post date:** [June 22, 2025, 1:27pm UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/6 "2025-06-22T13:27:00Z")

</div>

> [@nene](#):
>
> Sure.
> 
> I mainly posted it to provide some feedback on the deficiencies in TrainerRoad software.
> 
> If this happens because it’s a C-event, then IMHO it’s clearly a bug. Not all C-events should be considered equal.

It’s not a bug, you are mis categorizing the event as a “c” race rather than a b or a race. C races are intended as training sessions by TR and don’t have any taper going into them.

A and B races do have a taper, if you want or need that you need to categorize the event as something other than c.

---

<div class="post-metadata">

**Author:** ![NWcyclingman](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nwcyclingman/32/18640_2.png) [@NWcyclingman](https://www.trainerroad.com/forum/u/NWcyclingman)\
**Post date:** [June 22, 2025, 3:04pm UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/7 "2025-06-22T15:04:08Z")

</div>

I can’t say I agree. It works as designed. If you want rest change it to a B or A. “C race" is essentially treated as a hard workout, and you should train through it without tapering.

Not a bug. More philosophical WAD.

---

<div class="post-metadata">

**Author:** ![nene](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nene/32/120214_2.png) [@nene](https://www.trainerroad.com/forum/u/nene)\
**Post date:** [June 22, 2025, 4:13pm UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/8 "2025-06-22T16:13:17Z")

</div>

Alright, I changed it to B event. It’s not any better now. Actually it’s even worse, because it added an opener before the event:

 ![Screenshot 2025-06-22 at 19.09.03](https://global.discourse-cdn.com/trainerroad/original/3X/1/c/1c151c1a61ff3eef81cc88df364a7deaf6b3f621.png)  
 ![Screenshot 2025-06-22 at 19.09.22](https://global.discourse-cdn.com/trainerroad/original/3X/e/f/ef636c8b581cb8f958e950f1385a1d7531adac8a.png)

Perhaps I should make it into an A event? But then TrainerRoad will complain that I have two A events too close together.

---

<div class="post-metadata">

**Author:** ![OreoCookie](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/oreocookie/32/8298_2.png) [@OreoCookie](https://www.trainerroad.com/forum/u/OreoCookie)\
**Post date:** [June 22, 2025, 4:40pm UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/9 "2025-06-22T16:40:48Z")

</div>

> [@nene](#):
>
> Perhaps I should make it into an A event? But then TrainerRoad will complain that I have two A events too close together.

You cannot escape reality. The idea is to peak for A-races. If they are too close together, you can’t.

---

<div class="post-metadata">

**Author:** ![nene](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/nene/32/120214_2.png) [@nene](https://www.trainerroad.com/forum/u/nene)\
**Post date:** [June 23, 2025, 3:07pm UTC](https://www.trainerroad.com/forum/t/no-rest-week-before-a-week-long-stage-race-really-trainerroad/104058/11 "2025-06-23T15:07:43Z")

</div>

Thanks.

For further context, my true A-event was actually a week ago. These two are more of a jump into the unknown. Not really planning to peak for these, but would just like to have a reasonably good form and not suffer too much.

I intentionally didn’t put these events into the calendar at the start of the year, as I thought they might just confuse TrainerRoad. So I first finished my true A-event (and I’m pretty happy how that plan went), and then created a new training plan for the rest of the stuff.

I understand it’s kinda crazy schedule, so I didn’t really expect a whole lot from TrainerRoad plan, but it really surprised me how excessively aggressive the suggested plan was.

I was pretty much planning to tweak the plan as you suggested. I’m probably also going to cut back even more on the volume - I’ll be getting enough of that on the coming weeks.
