If you are serious about your cycling, and more specifically your cycling performance training, then you will almost certainly have started training based on power. Which therefore mean you are using Functional Threshold Power (FTP). But are you getting the most out of this (excellent) training protocol?

Why use Power (FTP) in training?

Let’s start from the start as they say! In any form of structured training you require some metrix, often two: essentially “do xyzzy at this INTENSITY for this DURATION”. Duration can be expressed as distance or time. Intensity could be Rate of Perceived Exertion (RPE) at the most basic end, or heart rate (still the predominant method used in running), or indeed Power output as is becoming the accepted norm in cycling amongst those that take it seriously!

Why is Power (FTP) better than Heart Rate?

Simply because it is more real time, in other words it doesn’t have the unavoidable lag associated with measuring heart rate. This can matter most when for instance you are trying to achieve a certain prescribed power climbing a hill. Your HR might peak after you pass the summit, but power will give you a more real time read out DURING the climb.

This is not a Post about HOW to train with power!

There are quite a few points to understand and consider when starting out with power based training. These have been widely documented and therefore I shall let you read those else where. However, one of the basics is to understand that different power meters will give different power outputs, therefore sticking with one “source of truth” is helpful. Also power meters (certainly pedal based ones) should be calibrated before each session as they are susceptible to environmental changes. But for the purposes of this post I am assuming you are already using some form of FTP test and following a power based plan. Also you probably have a clear understanding of your race target power numbers.

So what do I bring to the party?

The observation that in order to understand your FTP number you need to understand the context it was achieved within. In other words, what platform (equipment) did you use? morning / afternoon / evening? Which testing protocol did you use? When did you last eat or even WHAT did you eat! And as much else as you can think of.

All of these contextual factors will influence performance, and often quite markedly. Therefore if we see a decline (or of course an improvement), in our FTP number then this *might* be due to our own physiology… but equally could be attributed to testing under different conditions. It follows that we need a consistent “testing environment” in order to ensure the integrity of our FTP value. And integrity matters, because we base everything else on(training and racing wise) on the foundation of our FTP Test Result.

So I have improved my app to enable you to record more relevant details about the environment you conducted your test in.

The Cyclists Calculator App has evolved.

Initially I wrote this app because I was fed up with having to convert between imperial and metric measures, as well as figuring out my anticipated finished time / duration for the cycle leg in a triathlon. This soon progressed to figuring out the speed I needed to achieve in order to deliver the time I wanted! This then went a step further to calculating my split time so I had one number on my cycle computer to think about. Perfect for those times “oxygen is in short supply”!

At the same time I thought it would be “nice” to record my FTP number, and calculate the % change for bragging purposes! And of course if you are going to do that, then you might as well set a reminder for when a re-test would be appropriate.

Quite a lot of people have bought the cycling app – so firstly, if that is you, then a huge thank you! And I’m pleased you saw value in it.

But it has grated on me that my app became “another” place to write down the same info. Dull and not helpful.

Then, based on the replicability principle of 5k time trials for runners (to set their training zones), it struck me that there was no easy and consistent place to record all the details associated with where, what and how you conducted your test. So that next time you could create the same conditions. Or understand what you changed that could have caused a difference.

The new version of my Cycling App provides this and is still less than you might pay for a good coffee. So it’s a no brainer… if you take your cycling training seriously.