Your plan may be too hard when easy runs sit 5 or more beats higher at the same pace for two weeks running. It may also be too hard when you miss 2 key sessions in 3 weeks. These are rules of thumb from coaching practice, not lab-tested cutoffs.
Notice the word “may.” The answer is rarely “quit” and rarely “tough it out.” It’s usually an adjustment.
Plan too hard vs overtraining: why the difference matters
A plan that doesn’t fit you is a mismatch problem. The workload is wrong for your base, your sleep, or your schedule. Fix the mismatch and the signs often fade.
Overtraining syndrome is different. It’s a deep, months-long breakdown. We cover that in our guide to the signs of overtraining.
Think of a car engine. A bad plan is like driving in the wrong gear. The engine strains, but swap gears and it hums again. Overtraining is a blown head gasket.
This post is about the gear problem.
Marathon plan too hard? Warning signs and the spike problem first
Many runners blame weekly mileage. The data points elsewhere. The Garmin-RUNSAFE study followed 7,391 runners for 1,000 km each. Overall, 44.0% got injured. But look at who.
Higher weekly distance was associated with lower injury rates. In short: more miles didn’t clearly break people. Sudden mismatches may have. This is a cohort study, so it can’t prove cause. Runners who handle big weeks may simply be sturdier to begin with.
The 10% rule has the same problem. In a randomized trial of 486 novice runners, 20.8% got hurt on a graded plan and 20.3% on a faster one (Buist et al.). That’s a tie, with a p-value of 0.90. Translation: the 10% rule is a habit, not a law.
What may matter more is the single big jump. Secondary coverage of a larger Garmin-RUNSAFE analysis (5,205 runners) reports that long runs above 110% of your longest run in the last 30 days carried more risk. Earlier work from Nielsen and colleagues also suggested that novice runners who ramped weekly distance too fast were more vulnerable to injury.
First-timers deserve extra care. A study of first-time New York City marathoners found that injuries during training were linked with no prior half-marathon experience and with running 4 or more days a week. Longer training runs went with fewer injuries on race day. In short: for new marathoners, injury was tied to doing too much too soon, not to the long runs themselves.
Some coaches also watch the ratio of this week’s load to the past month’s average. A reading of 1.5 or higher gets flagged. The evidence in runners is mixed, so treat it as a prompt to look, not a verdict.
Weekly totals hide spikes. One long run can sink you.
The 7 signs, with numbers
Each sign needs a pattern, not a bad day. Give it 7 to 14 days. The thresholds below are rules of thumb, not study results.
1. Easy runs stop feeling easy. Track your easy-run heart rate at the same pace over several weeks. If it trends up by 5 or more beats and stays there for two weeks, something’s off. This isn’t the same as in-run decoupling, which compares the start and end of one workout. Heat and caffeine can fake the trend, so check conditions first. Buchheit’s review warns that a high submaximal heart rate alone isn’t a clear fatigue marker.
2. Resting heart rate and HRV trend the wrong way. HRV (heart rate variability) is the tiny beat-to-beat timing change your watch tracks. Research discussed by Buchheit found it tracked heavy overreaching a bit better than resting heart rate did (r=0.88 vs r=0.81). A 7-day average below your normal band, with resting heart rate up, is a flag.
3. Key sessions fail or get skipped. Two missed or failed long runs or tempo runs in 3 weeks is our working threshold. Your body is voting. But tell the difference. A failed session means you started and couldn’t hold the effort. A skipped one might be a sick kid or a late flight. Log the reason every time, because three “life” skips in a row still say the plan doesn’t fit your life.
4. Sleep breaks and soreness lingers. Muscle soreness that lasts past 48 hours is one flag. A week of bad nights is another. Seven in a row is a handy rule of thumb. Write down your sleep hours and a 1-to-5 soreness score each morning. Patterns show up in a notebook faster than in your head.
5. Mood and motivation sink. Reports on mood scores suggest tension, anger and fatigue tend to rise with training load, while vigor falls. Dreading every run is data. Mood often improves once load drops, though it varies.
6. A spike you didn’t choose. A long run well above your recent longest, with the 110% mark as a rough flag. A sudden jump after a missed week, as in what to do after missing a week of marathon training, is the classic trap.
7. Every day is moderately hard. No true easy days means no true hard days either. Sports scientist Carl Foster called this “monotony”: your average daily load divided by how much it varies. Reported cutoffs put trouble above about 2.0. Here’s a simple self-check. If most days land within one notch of the same effort, you’re in the zone. Same grind, every day, wears people down even at modest mileage.
What to change, sign by sign
| Sign | Rule-of-thumb threshold | First change | Evidence strength |
|---|---|---|---|
| Easy-run heart rate up | About 5+ bpm for 2 weeks | Slow easy runs, drop one hard session | Coaching heuristic |
| Resting HR / HRV | 7-day average off baseline | Add a lighter week | Observational |
| Failed key sessions | 2 in 3 weeks | Cut intensity in 1 session, keep long run | Coaching heuristic |
| Soreness / sleep | 48+ hours / about 7 bad nights | Swap a run for rest | Coaching heuristic |
| Low mood | 2+ weeks | Reduce load, keep easy runs | Secondary reports |
| Long-run spike | Roughly 110% of 30-day longest | Return to prior long-run length | Secondary reports |
| Monotony | No easy days | Make easy days truly easy | Secondary reports |
The usual coaching move: cut intensity before volume. It’s a heuristic, not a finding from the studies above. The idea is to keep the easy miles that build your base and drop the second hard day.
Fewer hard days. Same easy miles.
A mini case study
Take a runner we’ll call Dana. She’s an illustrative example, not a real client. She’s 41, training for her first marathon on about 6 hours a week. In week 7, her long run jumped from 12 to 16 miles after a missed weekend. Two weeks later her easy-run heart rate sat 6 beats high at the same pace. She’d failed 2 of her last 3 tempo sessions, and her sleep was wrecked.
She dropped one hard session per week and held her long run at 13 miles for ten days. In this example, her easy-run heart rate fell back within 11 days. She finished in 4:12.
A plan can look fine on paper and still not fit your Tuesday.
What to do when you can’t guess
Self-coaching means you check these signs yourself. That’s tough on a busy week. AthleteOS reads your missed sessions, sleep, HRV, resting heart rate and easy-run heart rate trends from your connected watch. Mood and soreness are different. You tell it about those in check-ins. When the pattern says the plan doesn’t fit, the AI coach can trim intensity first, add a lighter week, or rebuild around the days you have. The Adaptation Log explains every change in plain English.
If you’re also fighting a cold, read when to resume training after being sick. Short on days? See a four-day plan that bends. Or try AthleteOS with the 14-day free trial.
When to stop and see a professional
Adjusting a plan won’t fix everything. Get checked if you have chest pain, fainting, a resting heart rate that stays high for weeks, or pain that wakes you at night. Also go if you still feel flat after 3 easier weeks. That may be more than a plan problem.
Hard training should feel hard. It shouldn’t feel broken.