Wanting to do ramp test - how to prepare?

My question is if there are any recommendations on how to prepare for doing a ramp test (as in, some sort of [mini-] plan to optimize a ramp test?)

Background is that I’ve been a TR subscriber for about 14 months and am otherwise pretty happy with the AI FTP detection now inherent in the software (and which I believe has been good at tracking my FTP changes, both up and down) but am wondering if ‘exclusively using’ the AI FTP detection will turn into a crutch and prevent me from developing the skills needed to successfully execute an FTP test (ramp or otherwise, like an 8 or 20-minute test). I’d be hard-pressed to describe how ‘getting better at ramp/FTP tests’ would correspond to some ‘on the bike’ scenario, but I am convinced that ‘avoiding FTP tests because they are hard, and the AI FTP detection will automatically do that for me’ correlates to me not developing an arrow in my cycling quiver (to borrow the phrase).

I’m coming up on the completion of my training program (“A” event in a week, followed by the usual endurance rides the week after) and my thoughts have turned to what is going to be next, where I don’t have any particular “A” events beyond what I’ll do next week and thought that perhaps I might take a month or so (with the corresponding thought that a month is as somewhat random period) to choose) to do workouts that might lead to more success with the ramp test (and to some extent, given I yet to have a specific event to prepare for, maybe doing some preparation for an FTP test might be something to try).

And, not that I’m somehow ‘afraid’ of doing a ramp test (even if it’s a workout where - ideally and as I understand - you should complete it with a ‘10 out of 10 effort’, and it’s a draining workout), more that the parameters (power profile many minutes above my existing FTP, higher HR and for longer than other TR workouts, [likely] at or very near VO2max, etc.) seem to all be new.

Quick background is that my last ramp test was when I started with TR (Jun '22), where I stopped the test more on a mental limitation (sort of psyching myself out with the hard workout, I suppose) than a physical one - whereas now (many TR workouts later), I’m more used to pushing myself at powers above my FTP (think threshold/VO2 max workouts and such).

Part of me is like ‘just pick a new plan and do the ramp tests at the beginning of each block’ though on the other hand that might seem to preclude ramp test-like workouts (examples: Guyat, Piute -2, Rendezvous, Ragged, Dragontail, Tower, Tulaichean, Xueshan, Lolota) which I believe would help me get used to the ramp test.

In any event, what thoughts do you all have on ‘preparing for a ramp test’?

I make sure I’m rested. If you don’t like the result do the test in another week. Practice makes perfect.

3 Likes
  1. Rest on Day -2

  2. Ride easy for an hour on Day -1. Do some openers based on feel if you want

  3. Send it on Day 0

  4. Don’t bother with any of the above unless you just like ramp tests, I guess

  5. Do a long-form FTP test if you really want to second guess AI FTP detection

3 Likes

I’m very likely overthinking it - of course doing the test will most certainly get me used to doing the test :grin:

1 Like

If your training plan has you doing 10-15min intervals (or longer), you’re getting the prep you need for cycling. Doing a ramp test isn’t going to add much/anything - the point of the ramp is its easier than the 20 or 8 min protocols.

I don’t prep for them. Just pick a day I have fresh legs and send it.

FWIW, ramp tests tend to give me results that set my FTP a bit too high (vs AI FTP, 20 min, or 8 min tests).

I find the TR AI FTP detection to be unimpressive. Ramp test.

1 Like

If you’re looking for another arrow in your quiver, I’d do a long-form test like Kolie Moore’s, which gives you the benefits of dialing in your FTP, giving you a better idea of how long you can actually sustain it (30 min? 45? Longer?), and hopefully giving you the ability to feel when you tip from a sustainable effort to unsustainable, which is what you’re trying to measure with the test ultimately.

1 Like

I do 20 minute FTP tests (45 mins including warm up and cool down).

I try to replicate my prep for each so they are consistent (I’ve done 3 this year, 2-3 months apart).

I make sure I’m rested, so the day prior is either an easy ride or off day. Set my AC to 70 degrees with 2 fans pointed at me. I have oatmeal/coffee about 45 mins before the ride and a gel with caffeine around 10-15 mins before the 20 min start.

For pure training support, AI detection seems just fine. Personally, I look at my FTP as a measure of my training success and athletic performance. I’d have a hard time in good conscience saying “I have a 4 w/kg FTP” when I’ve never actually tested it. That’s like putting some calculations together and estimating someone’s 5k, 10k, half marathon time, etc., without ever actually running the race.

It’s a major sufferfest, but not that much worse that a hard interval session. Might as well just replace a weekly interval session with the FTP test.

During a structured program, I will accept AI detected FTP tests (sometimes), as they might better guide the plan.