Missed a Week of Marathon Training? Exactly What To Do Next

If you missed a week of marathon training, don't panic and don't cram. The coaches who study this closely agree: missing up to about a week has almost no measurable effect on your fitness. Resume at a reduced volume rather than jumping straight back to full pace, prioritise your next long run and one quality session, and do not stack the missed workouts onto the weeks ahead.

Does Missing a Week Actually Ruin Your Marathon?

No, and this isn't just reassurance, it's backed by the physiology. Jason Koop, coach at TrainRight, has written specifically on this: the practical fitness degradation from missing up to a whole week of training is small, and it's genuinely hard to lose much more than a few percent of your fitness in that window. RunVermont's coaching team puts it just as plainly: missing fewer than 7 days typically causes no negative conditioning effect at all, and meaningful drops in your aerobic fitness generally take two to four weeks of complete rest to actually show up. Your body holds onto fitness longer than most runners assume, which is exactly why the panic response, cramming, doubling sessions, extending your next long run, tends to cause more damage than the missed week itself.

Missed 1 Day vs 1 Week vs 2+ Weeks: What Actually Changes

One or two missed days changes essentially nothing measurable. Up to about a week, you're still in the range where fitness loss is minimal and largely reversible within your next couple of sessions. Luke Humphrey, coach and author of the Hansons Marathon Method, has put real numbers on what happens beyond that: runners who lose 7 to 13 days of training tend to finish, on average, around 4.25 percent slower than they would have otherwise, while losing more than 28 days is associated with roughly an 8 percent slowdown. Those aren't small numbers, but they also aren't catastrophic, and they only really start to bite once you're missing weeks, not days. RunVermont adds a useful marker here too: past about three weeks off, it's worth adjusting your goal regardless of how much time is left before race day, since a real training effect takes roughly four weeks to rebuild once it's been lost.

How To Re-Enter Your Plan

There's broad agreement on the principle, ease back in below full volume, and some healthy variation on the exact number. Koop's guidance points toward resuming around 90 percent of your previous volume and reclaiming somewhere between half and three-quarters of what you missed over the following weeks, never all of it at once. RunVermont's coaches suggest a more staged version for anything beyond a few days: if you were out for a week or less, start your first week back at around 75 percent of scheduled volume before returning to normal; if you missed up to two weeks, start closer to 50 percent in the first week back, 75 percent in the second, then resume as normal. Treat that as the honest range, somewhere between 50 and 90 percent depending on exactly how much you missed, rather than a single magic number. What all three coaches agree on without exception: don't try to make up every missed mile by stacking sessions on top of your current plan. Trying to reclaim everything at once is how a one-week disruption turns into a two-week injury.

Which Workouts To Protect

If you're easing back in with limited time or energy, protect two things: your next long run and one quality session, whether that's a tempo run or intervals. Everything else, extra easy mileage, optional cross-training, is genuinely optional. The long run maintains the endurance adaptations that take longest to rebuild, and one quality session keeps your legs from losing their edge. Skipping the filler runs costs you almost nothing; skipping both of those two costs you real fitness.

• Long run: protect it, but reintroduce it at reduced distance before building back to your previous peak.
• One quality session per week: keep it, even if shortened, to preserve pace and running economy.
• Everything else: optional. Easy mileage and cross-training can flex around your schedule without meaningfully affecting your race outcome.

One more thing worth remembering as you ease back in: your first run back might feel unusually heavy or slow, and that's normal, not a sign the week off actually hurt you more than expected. The same logic applies here as when you have a single bad long run: one uncomfortable session is noise, not a trend, and it tells you almost nothing about your actual fitness on its own.

Coming Back From Illness vs. Travel vs. Injury

These aren't the same situation and shouldn't get the same re-entry. Travel disruption is usually just logistics and mild fatigue, resume close to normal once you're home and rested. Illness needs a genuine check: a common rule of thumb is symptoms above the neck (a mild cold, congestion) are generally fine to run easy through, while symptoms below the neck or a fever (body aches, chest congestion, fever) mean you should rest until they clear, then ease back in rather than resuming at full pace. Injury is the one category where none of the volume percentages above should apply on their own, if you're returning from an injury under a physical therapist's care, RunVermont's own guidance is direct: the PT, not a generic training rule, should decide when and how you resume running-related activity. Resume only once the injury is actually resolved, and expect to rebuild volume gradually regardless of how much time you lost.

A practical example: a head cold with no fever might cost you three or four easy days at most, resume as soon as you feel up to it, ideally with an easy run rather than jumping straight into a quality session. A flu with fever is different, most guidance suggests waiting until at least 24 hours symptom-free before any running at all, then treating the return like any other week-long gap, easing back rather than resuming at full volume on day one. The mistake to avoid either way is deciding you're fine before your body actually is, running through a fever specifically carries real cardiac risk, not just a slower race.

Why Static Plans Break Here, and What Adaptive Plans Do Instead

A generic PDF training plan has no idea you missed a week. It just keeps counting down toward race day, leaving you to either ignore it, panic and improvise, or force yourself back onto a schedule that no longer matches your actual fitness. This is precisely the moment a static plan turns from a guide into a source of anxiety. An adaptive plan does the opposite: it looks at what you actually ran, not what the calendar assumed you'd run, and rebuilds the weeks ahead around your real starting point, at a re-entry pace that matches how much you actually missed instead of a one-size-fits-all rule.

Concretely, that means the plan doesn't just delete the missed week and pretend it didn't happen, and it doesn't blindly shift every future workout back by exactly seven days either. It looks at how much volume you actually lost, factors in what caused the gap, illness, travel, injury each carry a different re-entry curve, and rebuilds your remaining weeks so your long run and quality sessions still land on a sensible progression toward race day, rather than a countdown that no longer matches reality.