Hi all,
I’d like to raise something that comes up every time I build a triathlon plan: swim frequency is fixed.
No matter which plan I build — sprint, olympic, low volume or high volume — Plan Builder always schedules 4 swims per week. My pool access realistically allows 2, sometimes 3 sessions per week. That’s not a motivation problem, it’s a logistics one, and I suspect I’m not the only athlete in that situation.
Right now the only workaround is to build the plan first and then delete individual swim workouts week by week. That works mechanically, but it has two downsides: it’s tedious across a full block, and more importantly the rest of the plan doesn’t react. The bike and run load stays exactly as it was, so I’m not sure whether I’m ending up with a coherent plan or just a plan with holes in it.
What I’d love to see is a discipline-level frequency setting during plan creation — something like “swims per week: 2 / 3 / 4” — with the system adjusting the remaining disciplines accordingly. Athletica.ai handles this well: you declare how many sessions per sport you can commit to, and the plan is built around that constraint rather than patched afterwards.
To be clear, I’m not asking TrainerRoad to turn into a different platform. AT and the progression logic are the reasons I’m here. But being able to declare a real-world swim constraint up front, instead of deleting sessions after the fact, would make the plans a lot more usable for age-groupers with limited pool access.
Has anyone else run into this, and is there a better approach I’ve missed?
Thanks.
