ENERGY PACING AND TRAINING STRESS SCORE
We have talked quite a bit this year about intensity factor, normalized power, and training stress scores and how they factor into pacing your races, especially the longer races. As I mentioned, many coaches have suggested a TSS of 280 on the bike to be optimal for a successful marathon in an Ironman. In this article, Alan Couzens explains why he thinks that number should be lower. Remember, the science of quantifying ideal fueling and pacing for an Ironman is still relatively new. Those who are studying the role your body’s energy systems play in helping you complete your Ironman are constantly bringing new data into the discussion, and for coaches who love reading and analyzing this data, the research is exciting. For those of you who are not training with a power meter or training to the point of understanding TSS and IF, this article is still a valuable read. You don’t have to worry about the “how”; I will take care of that. But I do think it’s interesting to investigate the
“why”. -Beth
ENERGY PACING AND TRAINING STRESS SCORE
ALAN COUZENS
Today I would like to address one piece in the puzzle of optimally pacing your Ironman. Many of you have looked at how to go about determining the optimal bike/run energy allocation for different courses and athletes. However, we haven’t yet looked at how to go about determining how much actual energy you have at your disposal, i.e. how much potential energy do you have available in your personal system, or put more succinctly, what are your energy reserves?
This is a more complex question than it appears at face value and is a function of things like:
• Training
• Nutrition
• ‘Freshness’
• Muscle Mass
• Duration of your event
Let’s take a look at a couple of these factors individually.
Muscle Mass/Training
Well trained muscle typically stores ~700mmol of glycogen (per kg of dry weight) (Starling et al 1997, Adamo et al. 1998). This equates to ~20kcal/lb of muscle. So, for a mesomorphic (Muscular) 165lb male with 75lb muscle mass, typical muscle glycogen stores are in the range of 1500kcal.
Add to this liver & blood glycogen and glucose stores of ~500kcal and a well trained athlete of average size has approximately 2000kcal at their disposal. It should be noted that an untrained individual typically stores approximately half of this amount.
Duration of the Event
In addition to having access to these stores at the start line, the intelligent athlete will take in an optimal amount of carbohydrate during the event that will lead to an additional 240-280kcal/hr of energy at their disposal.This implies that the longer the event continues, the larger the total energy pool from which the athlete can draw, assuming all other factors (such as rate of CHO absorption) are equal. This is important to remember when we are comparing the energy demands of athletes with different race durations and has practical significance when attempting to define a TSS ‘budget’ for the athlete.
In power training terms, some coaches have hypothesized that there is a TSS ‘budget’ that is optimal for all athletes to observe during the bike portion of the event. This is generally recommended to be in the vicinity of 280TSS. Thus, depending on anticipated bike split duration, the intensity of the bike leg is manipulated to assure that the athlete doesn’t exceed 280TSS over their total race duration. For athletes in the 5.5-6.5hr bike split range, this then results in an intensity factor of 0.65-0.71, or, with typical Ironman variability indices, an average power of 60-68% of FTP.
However, while this is a good starting point for many athletes, it does not take into account some of the individual considerations mentioned above. A good rule of thumb that I have found to work quite well when comparing power data in the field with lab data is:
1TSS = 10kcal of glycogen.
In other words, a bike equaling 280TSS would be approximately equivalent to 2800kcal of glycogen/glucose output. So, for our hypothetical 165lb guy above, riding with an IF of 0.68 for a ~ 5:43 bike split, he starts with 2000kcal and gets 240-280kcal/hr on the bike. His input would be 2000 (starting energy) + 1500 (@260/hr) for a total of 3500cals. With an output of 2800kcal, this leaves him ~700kcal or 70TSS when starting the run. Even with an extra 260kcal or 26TSS/hr in exogenous CHO during the run, the picture isn’t pretty. For a 4hr run this is 180TSS or 45TSS/hr @ an IF of 0.67. Unless you’re working with an FTP pace of 6:15 or better, ain’t gonna happen.
Nope, far more typical is the 5hr marathon that allows for an extra 26TSS and a more manageable IF of 0.64 for an athlete with an FTP of ~7:20 (RUN PACE). A 6hr bike/5hr run is not the best way to distribute your energy. Yet it is almost inevitable for the average athlete who approaches the bike with a desire to ride at or above the typically recommended IF/AP power numbers.
In my experience, for the majority of courses, a far better way for most athletes to distribute their energy is to split their TSS budget down the middle and devote half to the bike and half to the run (for most folks, the swim should be done so easily that its energy output is non-significant). So, for our hypothetical lean mean 165lb male Ironman with starting glycogen stores of ~2000kcal/200TSS and a predicted finish time of ~12hrs (meaning an additional 11x260kcal/hr in exogenous glucose), his energy reserves are in the range of ~480TSS. If this is split at 240 for the bike and 240 for the run, we would expect our ‘average’ athlete with a run FTP equaling a 7:20 pace on the run to run a 4:25 marathon at an IF of 0.72 and his bike split would be 6:05/144W bike at an IF of 0.6.So, to summarize the difference in approaches:
Typical (Bike-heavy energy split)
Bike = 280TSS @ an IF of 0.68
Run = 200TSS @ an IF of 0.64
Splits: 1:00/5:45/5:00 = ~12:00 :-(
Optimal (Even energy split)
Bike = 240TSS @ an IF of 0.6
Run = 240TSS @ an IF of 0.72
Splits: 1:00/6:05/4:25 = ~11:45 :-)
The effect of holding back 10% on the bike is magnified for faster athletes, with differences of 30 minutes or more expected at the pointy end of the field. Plus being the passer rather than the ‘passee’ on the run is a much more enjoyable way to race :-)
So, to summarize the 2 steps are:
1. Determine your total energy reserves
2. Split it down the middle and devote half to the bike and half to the run.
While the theoretical considerations mentioned above provide a good starting point in coming up with pacing targets for the limited number of race simulations that you do prior to your event, the best way to fine tune your pacing targets is to prove their validity in training and C races.
Athletes can expect a 20-30% super-compensation of glycogen stores when tapering for their A-race (Shepley et al. 1992). Therefore, the best way to verify your true energy reserves is with slightly under-distance time trials of >2/3 race distance/duration.In the above example, where we are targeting a race day energy output of 480TSS, I would expect the athlete to PROVE their ability to perform a big day of training of at least 320TSS (2/3 race duration) at the target racing intensities prior to their event. If the athlete is only able to manage a big day of 280TSS in the context of a normal training week, then I would amend the target race intensities accordingly.
As mentioned above, novice athletes or detrained athletes can have <50% of the glycogen storage capabilities of trained athletes. In practical terms, this manifests as 150 or 200TSS being a ‘big day’ in the early season. It should not be assumed that the athlete has a tolerance to 280TSS, 350TSS or 500TSS. It should be PROVEN. In this way, theory meets practice and the athlete’s actual energy reserves are assessed.
Hopefully, this article will provide athletes with the final piece in the puzzle when determining how to optimally pace their Ironman. There is a lot of free speed out there for the athlete who is brave enough to bet on their ability to finish strong by holding back on the bike. However, like most things related to Ironman, while this is a simple principle, it is anything but easy.
