Table of Contents
Eight weeks out, the longest run is already behind you and the race still feels abstract. The watch, meanwhile, has months of data: hundreds of runs, thousands of heart rate samples, a resting heart rate curve, and a race predictor that keeps changing its mind.
The final eight weeks are not the time to chase new metrics. They are the time to read the ones you already have, in the right order, and to stop looking at the rest. This guide covers what to compare, what a taper should change, and which numbers are safe to ignore once race day gets close.
What the Last Eight Weeks Are For
Most of the fitness you will bring to the start line is already built. The remaining weeks add a small amount of conditioning, sharpen pace, and, most importantly, let fatigue clear. Training data is useful here because it separates a normal heavy week from a hole you are digging.
That changes how you should read the watch. Earlier in the block, a hard session was a stimulus to recover from and repeat. Now every hard session has to justify its cost. A workout that leaves you flat for three days in September is more expensive than the same workout in June.
Use the data to answer three questions: is the aerobic trend still moving in the right direction, is recovery keeping up with the load, and does goal pace look plausible on tired legs? Everything else is commentary. The relationship between short-term and long-term load is worth understanding before you read the rest, and training load explained covers it without the jargon.
Long-Run Trends Beat Single Runs
A single long run is a noisy measurement. Sleep, heat, wind, route, and the previous week all change the number. The trend across four to six comparable long runs is far more informative than any one of them.
Comparability is the trick. Pick two or three routes you repeat, and compare runs at similar effort, similar weather, and similar terrain. If the route is hilly, compare against the same hills rather than against a flat course. If the summer has been hot, expect heart rate to run higher at the same pace, which is a normal response rather than a fitness loss. Adjusting pace for heat is a skill worth practicing before race day.
What you want to see is a gradual shift: the same pace at a slightly lower average heart rate, or a slightly faster pace at the same heart rate, over eight to twelve weeks. A flat trend late in the block is not a failure. It often means you are accumulating fatigue, which is exactly what a training block is supposed to do. Building an aerobic base with watch data explains how to set that baseline in the first place.
Pace-to-Heart-Rate Drift on Long Runs
Set a steady pace for the first hour of a long run and heart rate will usually creep upward in the second hour. The size of that drift is a rough measure of aerobic durability. A drift of a few percent is normal; a large drift at an easy effort suggests heat, dehydration, insufficient fuel, or accumulated fatigue.
To read it, compare the first and second halves of runs that are at least 90 minutes and reasonably steady. Do not over-interpret a single hot day. Look for a pattern across several long runs, and note the conditions in the workout title so future-you knows what happened.
Drift is also a fueling signal. If heart rate climbs sharply after 90 minutes while pace holds, the problem may be carbohydrate intake rather than fitness. That is useful information to have eight weeks out, when you can still rehearse a fueling plan, and much less useful on race morning.
Resting Heart Rate Is a Load Signal With a Lag
Resting heart rate is one of the oldest metrics on a running watch and still one of the most misunderstood. It does not measure fitness directly, and a single elevated morning reading means very little. It responds to training load, sleep, alcohol, illness, altitude, and stress, usually with a delay of a day or two.
Track the seven-day average rather than the daily number. A sustained rise of five to seven beats per minute above your normal baseline, lasting more than two days, is a reasonable reason to look at the rest of your week: sleep, stress, and whether a hard session is scheduled too soon. A sustained drop can be a sign that the taper is working, or simply that you have been resting more.
Neither direction is a diagnosis. If resting heart rate stays elevated alongside a fever, chest symptoms, or unusual breathlessness, that is a conversation with a clinician, not a training adjustment.
Race-Pace Confidence From Workout Data
The most useful race predictor is not the watch's algorithm. It is a controlled marathon-pace segment inside a long run, completed on tired legs, with heart rate and perceived effort recorded alongside the pace.
Compare the same segment across the block. If goal pace felt controlled at a lower heart rate in August than it did in June, confidence is justified. If goal pace now requires a max effort that used to feel aerobic, the goal may be ahead of the current fitness, or the block may be carrying too much fatigue to judge.
Be careful with conversions. A fast 10K does not guarantee a marathon time, and a great half marathon in cool weather does not automatically translate to a warm fall race. VO2 max estimates are even less useful for pacing, because they describe aerobic capacity rather than the durability and fueling that decide the last 10 kilometers.
Taper Signals: What Should Change
A taper usually means reducing volume by roughly 40 to 60 percent over two to three weeks while keeping some intensity. The data should reflect that: fewer kilometers, fewer hard sessions, and a gradual stabilization of recovery markers.
What you hope to see is a resting heart rate that holds steady or drifts slightly down, heart rate variability that stops falling, and sleep that becomes a little more consistent. What you should not expect is a dramatic jump in fitness scores. Tapering reveals fitness; it does not create it.
A common mistake is adding work because the numbers look good. If readiness is high and legs feel fresh three weeks out, the temptation is to squeeze in one more hard long run. Resist it. The training that matters is already banked, and the cost of an extra session is paid on race day.
What to Ignore in the Final Fortnight
The last two weeks are when watch software becomes a source of anxiety. Several numbers are especially noisy and should be treated as entertainment rather than guidance.
- Race predictors. They swing with a single workout and rarely account for course, weather, or fueling.
- Training status labels. A watch calling a taper week unproductive is describing a model, not your preparation.
- VO2 max estimates. They move slowly and say little about marathon durability.
- Single-day readiness scores. One poor night of sleep can crater the score without any change in fitness.
- Calorie burn. It is an estimate, and it is not a fueling plan.
Keep recording, but narrow your attention to sleep, resting heart rate, and how the easy runs feel. Those three are enough to catch a problem without inviting second-guessing.
Race Week: Record, Don't Chase
In race week, the watch's job changes from coaching to documenting. Record sleep duration, resting heart rate, and the feel of two or three short shakeout runs. Note the weather forecast and the course profile. None of this should change the plan unless something is clearly wrong.
One useful habit is to run the first kilometer of the course, or a similar stretch, at goal effort and check that pace and heart rate agree with expectation. That is calibration, not a workout. Keep it short, keep it easy, and resist the urge to prove anything.
On race morning, do not stare at readiness. A tapered runner often sleeps badly the night before, and the watch will report it. The relevant question is whether you feel normal after warming up, not whether an algorithm approved of your night.
The Eight-Week Checklist
Use this as a weekly review rather than a daily one. It takes about ten minutes and keeps the data in proportion.
- Compare this week's long run with the last three comparable runs, not with a personal best.
- Check the seven-day resting heart rate average against your baseline.
- Confirm that weekly volume is trending down in the taper, not just on paper.
- Review one marathon-pace segment for pace, heart rate, and perceived effort.
- Note sleep and stress, because they explain more variance than any training score.
- Hide or ignore race predictors and training status labels until after the race.
The bottom line: the last eight weeks reward restraint. Trust the trend in your long runs, use resting heart rate as one signal among several, and let the final fortnight be boring. A boring taper is usually a well-executed one.
Frequently Asked Questions
Should I trust my watch's marathon race predictor? Treat it as a rough range, not a target. Most predictors extrapolate from recent workouts and do not account for course elevation, heat, wind, or fueling. A controlled marathon-pace segment in a long run is a better guide, especially when compared across several weeks.
What resting heart rate change should worry me before a marathon? A sustained rise of five to seven beats per minute above your seven-day baseline, lasting more than two days, is worth noting. Look at sleep, stress, and training load first. If it comes with fever, chest symptoms, or unusual breathlessness, speak to a clinician rather than adjusting your taper.
How much should my weekly volume drop during the taper? Many marathon plans reduce volume by about 40 to 60 percent across two to three weeks while keeping some short, fast work. The exact number matters less than the direction and the consistency. If the watch shows a sudden crash in volume and you feel stale, a little intensity can help.
Is heart rate drift on long runs a sign I am not ready? Not by itself. Some drift is normal, especially in heat or humidity. A large drift across multiple similar runs suggests fatigue, dehydration, or under-fueling. Compare the first and second halves of several runs before drawing a conclusion, and treat a single result as a prompt to check conditions rather than a verdict on fitness.
Should I keep wearing the watch during the race? Yes, if only to record splits and heart rate for later review. Set the screen to the fields you actually need, such as pace, elapsed time, and heart rate. Avoid checking readiness scores or pace predictions mid-race; they cannot change the outcome.
See Also
- Training Load Explained: Acute, Chronic, and What Your Watch Shows
- Building an Aerobic Base With Watch Data
- VO2 Max on Wearables: What Your Score Really Means
- Training Readiness and Recovery Scores Explained
- Heat and Heart Rate: Adjusting Pace With Wearable Data
- How to Use GPS Smartwatches for Accurate Outdoor Tracking