TrainingPeaks is a fantastic tool for planning and analysing our training, but we need good quality data to make informed decisions. If we have bad data we end up making bad decisions which can lead to burnout or even failing to finish your race! So, how do we keep our data clean? There are three areas I consider to be very important, we’ll take a look at each on a case by case basis, looking at common pitfalls and how we can avoid them.
- Consistent data
- Enough data
- Accurate Thresholds
We need to make sure that the data from one workout is comparable to the workout before it, and the ride after it. The biggest area this can be a problem is with cycling power, specifically when athletes change power meters between activities or fail to recalibrate their devices.
If you are only training indoors and using the power meter built into your trainer, you need to make sure you are re-calibrating the power meter (known as completing a spindown in most cases) every time you transport it, or every four weeks out of habit. As trainers are moved around and knocked about, they can lose their accuracy so the trainer needs to recalibrate itself to ensure the data stays accurate. I once failed to recalibrate my turbo trainer for several months, got myself up to an FTP of 4 W/KG, then re-calibrated my trainer, found workouts impossible, and discovered I was only at 3.6 W/KG! If you are planning to use your power pedals on race day, you should use your power pedals for every ride so you’re training at the same numbers you’ll be racing at, otherwise you run the risk of your intensity factor target on race day being based on turbo numbers, not power pedal numbers, resulting in you blowing up as a result. If you are using a bike based power meter (which I highly recommend) you still need to perform a zero offset (or recalibration as some brands call it) weekly, or whenever you move the power meter from one bike to another. Another issue can be the right pedal running out of battery or experiencing connectivity issues with the left pedal, so keep an eye on that.
Running power meters do not require regular calibration, however the numbers are based on your weight, so any changes to your weight will require you to reset your thresholds. As such I only recommend updating your weight if you have lost/gained weight that has been fairly static for a couple of months, or at the start of the season before your baseline testing.
Heart rate can occasionally be very low if the your chest strap takes time to make a good connection, or if your optical monitor struggles to get an accurate reading for whatever reason, such as a loose watch strap or heavy sweating. If you find yourself with a consistently low heart rate reading during a workout, make sure your monitor isn’t upside down!
GPS accuracy varies a lot, especially in urban areas or thick woodland, where you can end up with very high or low numbers. I once had an athlete run a 10K around the City of London, where the GPS trace accidentally made its way to the top of a skyscraper, leading TrainingPeaks to mistakenly believe she’d gained 150M of elevation in 10 seconds, sending the TSS score rocketing.
Finally we have elevation, if your GPS or altimeter is putting out bad data it can have you down as running thousands of metres above sea level, resulting in grossly exaggerated TSS scores.
If you find yourself with dropouts or spots of bad data, TrainingPeaks allows you to rectify this on the graph view within a workout. Simply click and drag your cursor over the problematic area, then click on the appropriate button in the top right of the graph for different data field: W for watts, KPH for speed and BPM for heart rate. From here you can select “fix”, which will allow TrainingPeaks to create a preview of the data smoothed out, with the option to apply or discard the changes. In some cases, such as with horrifically inflated elevation data, it can be better to delete the data field entirely, or switch the TSS calculation to hrTSS. If you start playing around with the data but make a mistake you can’t undo, you can simply download the workout from the “files” section in the top right hand corner of the workout view, and re-upload the original file. You’ll lose any comments or other changes you made to the workout, but the original file will always be in tact.
Sometimes bad data slips under the radar, looking at the PMC for big spikes can be helpful, as can browsing your peak performances on the TrainingPeaks mobile app and looking for numbers which you know are unrealistic. If a huge wattage or jump in pace isn’t accompanied by an increase in heart rate, you can be pretty sure it’s bad data.
The performance manager chart found in your dashboard is a coach and athlete’s best friend, it allows us to see how fit an athlete it, how fatigued they are, and how ready they are to perform. The numbers here will only be accurate if we have enough data from your training history to give us accurate insights into your training history. A world champion could create a TrainingPeaks account, but without any information on their training history TrainingPeaks will assume they are a novice, and suggest that they are incredibly fatigued after a couple of what would be a couple of very easy workouts for them.
If you are already an established athlete, you will need to sync your TrainingPeaks account to your fitness tracker/software of choice. Depending on the service you link to, it may or may not import all of your previous activities into TrainingPeaks (As an example, Garmin will, Zwift will not), and while manually uploading all of your data will seem like a gargantuan task, it is important you upload at least the last 42 days, as this is the constant that Critical Training Load (CTL) is based on. If you or your coach plan to use WKO, you will need all of your workouts from the last 90 days.
If you are a new athlete who doesn’t have any data to upload, then you will need to take the numbers with a pinch of salt for the first 42 days until TrainingPeaks has enough data to give you accurate figures. I’ve seen many posts on the TrainingPeaks Pain Cave Facebook Group group from individuals concerned that their form is -50 and wondering whether they are overtraining. More often than not they simply don’t have enough quality data uploaded so TrainingPeaks has no point of reference.
All calculations on TrainingPeaks are based on thresholds. If your thresholds are incorrect your TSS scores will be incorrect and everything else gets knocked out of place, from your PMC metrics to your workout metric, even the targets of your workouts themselves.
While I’m not going to go into testing protocols here, it’s important that you undertake fitness tests within the first 42 days for each sport you’re planning to log on TrainingPeaks. I spend the first month with each athlete focusing on fitness testing, staggering them so they’re not in close proximity, but ensuring we have good, relevant data to work with.
There are two problems athletes struggle with when setting thresholds, the first is basing their threshold off of their lifetime PB (in extreme cases, their best 10K time from 20 years ago), or not updating their thresholds regularly enough. By using a threshold that is too high you will struggle to complete workouts, by using a threshold that is too low you are doing yourself a disservice and not training hard enough, getting overly inflated TSS scored in the process.
I recommend you test each discipline every 6-8 weeks (perhaps more regularly if you’re a single sport athlete) for improvements. If you put in a slightly lower number during the test but your workouts otherwise feel good, you could put the result down to a bad day and leave the number where it is, but if you put in a noticeably lower number (+/- 10 watts or seconds per kilometre) you need to take it on the chin, lower the threshold, and review your training strategy. Do not become a victim of the vanity FTP.
To conclude, here are the main takeaway points:
- Ensure you use the same power meter for all workouts, and perform a zero offset regularly
- Ensure TrainingPeaks has all of your data from the last 42 days before you start using the PMC to plan your training
- Keep an eye out for big drops, spikes or gaps in data, and do your best to fix them using the tools in TrainingPeaks
- Be honest with yourself about your thresholds, and re-test regularly
It can be time consuming to look through your data and make sure everything is up to date. If this seems like too much work, or you don’t know what to do with your data once you have it in order, take a look at our online coaching.