8-week 10K training plan for a week that keeps changing

Most 10K plans assume you can run on the days the plan chose. Real weeks do not work like that. A plan built as a set of rules instead of a grid survives contact with a delayed flight, a sick child and a bad night, and it produces the same fitness.

How many weeks do you need to train for a 10K?

Eight weeks is enough for most people who can already run 5K comfortably. Twelve gives more room for disruption and for a beginner who is still building the habit. Under six weeks, target finishing well rather than a time; there is not enough room for a build and a taper both.

The structure is three or four runs a week, in three phases, with the intensity distribution lopsided: the large majority of your running easy enough to hold a conversation, and the small remainder genuinely hard. The middle is where 10K training quietly goes to die.

Then the 10K plan starts later than you think, and that is fine. Spend four to six weeks first getting to a comfortable, continuous 5K with run-walk intervals that shrink the walking each week. Three sessions a week, all easy, no quality at all. Once 5K is comfortable, start the eight weeks above and treat the first block as it is written. Trying to compress the two into one block is how a first 10K becomes a first shin splint.

Beginners also benefit most from the rule that easy means easy. Early running fitness comes almost entirely from time on feet at low intensity; the hard sessions in the build phase are the icing, and the base is the cake.

What does an 8-week 10K plan look like?

Weeks 1–3, base. Mostly easy volume, one session of strides or short hill repeats to keep the legs quick. Volume climbs gently and the long run gets to about 10–12 km.

Weeks 4–6, build. One genuine quality session a week: intervals at around 5K effort (5 × 800 m, or 6 × 3 minutes) or a tempo at comfortably-hard for 20 minutes. Week 6 is a down week at roughly half volume.

Weeks 7–8, sharpen and taper. Quality moves closer to race pace — 4 × 1 km at target — then the last eight to ten days cut volume by 40–50% while keeping a little intensity so you arrive fresh rather than flat.

PeakU does this from your own data. A coach that reads everything you already track. Join the free beta →

Rules instead of a calendar

Write the week as constraints. Then any arrangement that satisfies them is a valid week, and a missed day is a rescheduling problem rather than a failure.

48 hours between hard days. Quality sessions, the long run, and heavy lower-body lifting all count as hard.

One quality session a week, two at most. More is how the middle-intensity trap opens up.

The long run is the one to protect. If the week collapses to two runs, make one of them the long one.

Easy means easy. If you are short on time, cut the duration of the easy run, not its easiness.

Never make up a missed week. Resume at the volume you left. Doubling up to "catch up" is the exact load spike the injury literature warns about.

What to do when the week goes wrong

Missed the quality session. Move it, respecting the 48-hour rule. If that is impossible, do it at reduced volume rather than skipping — three intervals beat none.

Two days lost to illness. Resume easy. Give it an easy day for each day missed before the next hard session, and drop one climbing week rather than compressing the block.

A bad night before a quality day. Swap it with an easy day later in the week. Nothing is lost, and the detail of when a short night matters is in should I work out after a bad night of sleep.

Only two days a week available. Long run plus one quality session. That is a genuine, if slower, 10K plan; three easy runs and no quality is not.

How fast should each run be?

Easy runs: conversational, in your lowest two heart-rate zones, slower than feels productive. Long run: the same, with the last two kilometres allowed to drift up in the sharpen phase. Quality sessions: 5K effort for the intervals, comfortably-hard for the tempo, goal pace for the race-pace work. Setting those by heart rate rather than feel is the single change that fixes most self-coached runners, and how to find your heart-rate zones without a lab shows how to set them from your own data.

Cadence is the other lever worth a look. Many runners over-stride at easy pace; a slightly quicker turnover reduces impact and makes the easy days easier. If music helps you hold it, matching music to your cadence is the practical route.

Should you lift during a 10K block?

Yes. Two short, heavy sessions a week hold your strength through the block, support running economy and keep the small stabilising muscles honest. Count every heavy lower-body session as a hard day under the 48-hour rule and keep it away from the long run and the quality session.

If the week is tight, cut lifting sets rather than lifting weight; the strength stimulus survives low volume better than it survives light loads. The longer version, for a half marathon block but with the same logic, is the 12-week half marathon plan.

What should race week look like?

• Monday: easy 30 minutes.
• Tuesday: 3 × 1 km at race pace with easy jogs between.
• Wednesday: rest or easy 20 minutes.
• Thursday: easy 20 minutes with four strides.
• Friday: rest.
• Saturday: 15 minutes easy with two strides, or rest.
• Sunday: race. First kilometre a few seconds slower than goal pace; the time comes from the second half.

Nothing new in race week: not shoes, not breakfast, not a warm-up routine. Feeling flat and restless on Wednesday is the taper working.

What PeakU does with this

PeakU builds 5K, 10K and half-marathon blocks toward a date and then treats them the way this article describes: as constraints, audited for ramp rate and hard-day spacing before you see them.

When readiness drops or a session slips, the plan reflows around the rules rather than leaving a hole in a grid — and because it reads your lifting from Hevy too, it knows that Wednesday's heavy squats were a hard day and spaces the intervals accordingly. The weekly review then names what actually changed and why, which is the part a static PDF plan can never do.

Hen Eytan · Founder, UPeak

Builds the UPeak apps and writes up the research behind them.