Skip to main content
Share

How to train a client for their first 10K

A novice runner gets injured at a rate of 17.8 injuries per 1000 hours of running — more than double the rate of an experienced one. The advice nearly every coach repeats to prevent that — never add more than 10% of volume per week — was tested in a randomized trial with 532 beginners and did not change the number of injuries. Evidence does set a ceiling, but it sits somewhere else.

Glossary

Running-related injury (RRI)
Musculoskeletal complaint of the lower limb or lower back attributed to running that forces the runner to cut back or stop training. It is the outcome the studies cited here measure.
The 10% rule
A heuristic proposing that weekly volume should never rise more than 10% over the previous week. It never came out of a trial — it spread as practical advice.
Weekly volume
Total kilometres or minutes run in a week. It is the number any progression is calculated against.
Running economy
The oxygen a runner consumes to hold a given speed. Better economy means the same pace at a lower cost.
Run-walk
A method in which the session alternates jogging segments with walking segments. It lets a runner accumulate running minutes weeks before they can hold them continuously.

A novice runner gets injured at a rate of 17.8 injuries per 1000 hours of running — more than double the rate of an experienced one. The advice nearly every coach repeats to prevent that — never add more than 10% of volume per week — was tested in a randomized trial with 532 beginners and did not change the number of injuries. Evidence does set a ceiling, but it sits somewhere else.

Why a first 10K is the most injury-prone stretch

Videbæk and colleagues published a systematic review with meta-analysis of injury incidence per hour of exposure in Sports Medicine (2015). Novice runners accumulate 17.8 injuries per 1000 hours of running; experienced recreational runners, 7.7. The gap is not talent and it is not technique — it is tissue.

A client coming off a sedentary year or out of the gym has a cardiovascular system that improves in weeks and tendons, bones and fascia that adapt over months. The lungs say yes before the tibia is ready, and that asymmetry is what produces the injury. Which is why the problem is almost never the final distance: it is how fast you got there.

Does the 10% rule work?

As a shield, no. As a starting point, it is fine.

Buist and colleagues published the GRONORUN trial in the American Journal of Sports Medicine (2008): 532 novice runners preparing for a 6.7 km event were randomly assigned either to a 13-week graded program built on the 10% rule or to the standard 8-week program. 20.8% of the graded group got injured, against 20.3% of the standard group. No difference.

The trial carries a caveat that explains the result: in practice both groups progressed above 10% — roughly 10.5% per week in the graded arm and 23.7% in the standard one — so what was compared was a less steep progression against a steeper one, not 10% against chaos.

Nielsen and colleagues followed 874 novice runners for a year with GPS watches and recorded 202 injuries (Journal of Orthopaedic & Sports Physical Therapy, 2014). Those who increased weekly distance by more than 30% over a two-week period were more vulnerable to distance-related injuries — patellofemoral pain, iliotibial band syndrome, medial tibial stress syndrome — than those who stayed under 10%. The authors' own recommendation is exactly that: progress by less than 30% over a two-week period.

Translated into programming: 10% is a comfortable default, but the ceiling the evidence supports is 30%. There is room between the two to fit the plan to the person instead of to the template.

How to build the 10-to-12-week block

The plan does not start at week 1 of a downloaded template. It starts at what the person tolerates today.

  • Measure the starting point before you write anything: how many continuous minutes they can jog today without the pace falling apart. That number, not the race date, defines week 1.
  • Three runs a week is enough. Two leave too many days without a stimulus; four or more add impact without adding useful information in someone who just started.
  • Raise one variable per week. If the long run grows, every other session stays where it is.
  • Most of the volume goes easy. In the NLstart2run study, with 1,696 novice runners, running at a higher intensity in the previous week was associated with a higher injury risk (Kluitenberg et al., Journal of Science and Medicine in Sport, 2016).
  • Use run-walk for as long as it is needed. Alternating jogging and walking lets you bank running minutes weeks before the client can hold them continuously.
  • Every third or fourth week, a shorter one. No trial validates deloads in novice runners: it is a programming convention, not evidence.

What strength adds, and which strength

Strength does not compete with running — it holds it up. Llanos-Lagos and colleagues pooled 31 studies with 652 middle- and long-distance runners in Sports Medicine (2024), and the interesting part is that not all strength work pays off equally.

Heavy loads — 80% of 1RM or above — improved running economy with an effect size of −0.266 (p = 0.039), and combining methods outperformed any single one (−0.426; p = 0.018). Plyometrics helped only at speeds up to 12 km/h (−0.307; p = 0.028). Submaximal-load and isometric work showed no significant effect (p > 0.131).

In other words: two weekly sessions of squats, deadlifts and loaded single-leg work beat long circuits with light dumbbells. The honest caveat is that this was measured in trained runners, not beginners: for a first 10K the payoff is not the stopwatch but tolerating the kilometres ahead. The full protocol is in why fast runners lift weights.

The mistakes that repeat in every first 10K

None of these is a knowledge error. They are calendar errors, which is why people who know better make them.

  • Running every session at the same effort, which in practice means running everything too fast.
  • Raising volume and frequency in the same week, then having no way to tell which one hurt.
  • Picking the plan back up where it was left after a missed week, instead of repeating the last week actually completed.
  • Judging progress only by the clock on race day, when what was built over ten weeks was tolerance.
  • Dropping strength from the calendar in the final month, exactly when running volume peaks.

What changes when running and the gym live in the same place

A coach preparing a 10K while also programming gym work ends up running two systems: strength in a spreadsheet, kilometres in the app on the client's watch. The question that actually matters — how much did volume rise this week against the two before it — stops being something you read and becomes something you reconstruct. When the programming for both and the log of every session sit together, the 30% ceiling stops being a principle and becomes something visible.

The limit the evidence supports is not 10% per week — it is not crossing 30% over two weeks.

What you are actually programming

A client's first 10K is not won with a more ambitious plan. It is won by arriving at the start line intact, and that depends on how fast you raised volume over the ten weeks before it.

The evidence is more modest than the gym-floor advice sounds: the 10% rule was never shown to prevent injuries, and what did get recorded is that crossing 30% over two weeks is expensive.

Start by measuring what the person tolerates today, raise one variable per week, and keep strength on the calendar. The rest is time.

Sources

If you program gym work and running for the same client and want both in a single history, book a demo.

The progression handbook, free

Leave your email and we hand you the progression handbook for coaches (the five overload levers, the RIR scale and the deload week), plus whatever we publish next. One email now and then, nothing else.

By subscribing you accept our privacy policy.