This does look like a busy race calendar and (understandably) I’ve been told by many concerned friends that I’m doing too many races and I should just focus on one or two for the year or I’ll lose interest.. I thought I’ll try to explain my logic..
Thanks to tips from many triathletes I’ve met and info from various articles, I’ve used a grading technique to grade my races. The grading scales for my races is A to D (A being top priority).
Grading is my guide for the following:
· Amount of race specific training I’ll be doing in the leadup
· Tapering (Relaxing and cutting down on volume in the lead up to the race)
· Mental race planning in the leadup
· Pre-race diet
· How fast/hard I hope to push myself at the race*
· Recovery time after the race
*I usually try to push myself as hard as possible (within my abilities) on race day.. but the end result would vary depending on the preparation.
As a guide,
Grade D race will be more or less a tough training run with minimal preparation. I did the race 2 of the Duathlon series a week before my Marathon and with no cycling training. I also had a big night before the race but my sole aim was to simply have some fun and get one last tough training session prior to tapering for the marathon. I also wanted to get out early in the morning on a chilly winter day to get myself prepared for similar weather at the marathon..
Grade A race will be the key race for the year. This will be the Sydney marathon for me this year.
Based on the above, my race plan / calendar is as follows :

(may need to click on it to view it more clearly - HTML is not my strength!)
Entering races are usually not too cheap either.. but I still think I 'profit' mainly phyisically and financially by racing and not having a big night (or two) in town :)
I would have to change my plans if I was injured and/or have any other commitments.
This is my 2 cents on Race planning. Hopefully this will assist someone with their race plans! :)
"Luck is where preparation meets opportunity. "
— Randy Pausch (The Last Lecture)
No comments:
Post a Comment