Training Load: Why Distance Alone Does Not Tell You How Hard You Are Training

Training Load: Why Distance Alone Does Not Tell You How Hard You Are Training

Training load is the demand created by your training, not simply the number of kilometres in the week. Its meaning depends on volume, intensity, recent training history and how sessions are arranged. The same workout can be routine for one runner and a large jump for another because load is always relative to what came before.

Mileage is useful, but it only tells you how far you ran. To understand what the week asked from you, you also need to know how hard the running was and how that demand compares with what you have been doing recently.

That is why training load becomes useful when the distance looks ordinary but the week does not: more intensity, a much longer long run, or several demanding sessions close together can all change the picture.

But distance only describes part of what you asked your body to do.

Forty kilometres of mostly easy running does not create the same training demand as 40 kilometres containing several hard sessions. Likewise, two runs of the same duration can place very different demands on you if one is easy and the other contains sustained threshold work.

This is why training load matters.

The same workout does not mean the same thing to every runner

A 16-kilometre long run may be routine for a runner who has spent months running 45 to 55 kilometres a week. For someone whose longest recent run is 10 kilometres and whose weekly total has been closer to 25 kilometres, the same session represents a much larger change.

That is why load is relative. The useful comparison is not only the absolute workout; it is the workout in relation to the training the runner has recently absorbed.

Training load accumulates across sessions

Workouts do not happen in isolation. A long run completed after several demanding days can create a different overall week from the same long run placed after easier training.

This is also why making up a missed hard session can change more than the calendar. Session order affects recovery time and the amount of demanding work clustered together.

Progression matters more than chasing a perfect number

There is no single training-load score or weekly percentage that can tell every runner exactly how much is safe. Reviews of running injuries have found inconsistent relationships between many common training parameters and injury, while newer prospective evidence suggests that large jumps in single-session distance deserve particular attention.

The practical implication is not to avoid load. Marathon fitness requires progressively greater training demand. The goal is to increase that demand at a rate the runner can continue to absorb.

What this means inside SmartRunning

SmartRunning uses recent training context when deciding what should come next rather than treating weekly distance as the only signal. Volume, intensity, progression and the pattern of completed training provide different pieces of information.

The point is not to give the runner another dashboard to interpret. It is to make the next training decision more informed while keeping the guidance simple.

See how SmartRunning uses the training around the number, not just the weekly kilometre total, when deciding what should come next.

Why Recovery Weeks Belong in Marathon Training

Why Recovery Weeks Belong in Marathon Training

A lighter training week is not lost training. Reducing volume or intensity can lower accumulated fatigue while preserving continuity, making the next build more productive. The exact timing and size of a recovery week should depend on the training completed and the runner’s response; there is no evidence-based schedule that fits everyone.

When marathon training is going well, a lighter week can feel strangely difficult. The long run is growing, the weekly total is climbing, and then the plan asks you to do less.

That does not mean the training has stalled. Progression is only useful if you can absorb it. Recovery is part of that process, not the opposite of it.

Why reduce the training just when you are building momentum?

Because progression is only one part of training. Your body also needs the opportunity to absorb the work you have already completed.

Why training cannot simply increase every week

Training creates a stimulus by asking your body to do more than it is currently accustomed to. Over time, the body adapts and becomes capable of handling more.

That principle explains why marathon plans progressively increase the demands placed on the runner.

But the progression cannot continue indefinitely. Fatigue also accumulates, and at some point, additional training may stop producing the response you want if there is not enough recovery between periods of increasing load.

Periodization is the way training is organized to manage this process over time.

Instead of treating the preparation as one uninterrupted increase in distance and intensity, the training plan is divided into periods with different objectives and different levels of training load. Several weeks of progressive training may be followed by a lighter period before the next build starts.

Recovery is therefore designed into the training plan rather than added only when something goes wrong.

What happens during a recovery week?

A recovery week does not usually mean doing nothing.

You continue running, but the overall demand is reduced. That may involve lower mileage, a shorter long run, less intensity or some combination of these.

The purpose is to reduce accumulated fatigue while maintaining enough training to preserve continuity.

For a motivated runner, this can feel surprisingly difficult. Training more is tangible. You can count kilometres, complete workouts and see progression in the training log. Recovery can feel as though you are giving some of that progress back.

But a lighter week is not the opposite of training. It is part of the process that allows previous training to become useful.

If you continually add load without allowing enough time to absorb it, the quality of later training can deteriorate. The next build then starts from a position of accumulated fatigue rather than renewed capacity.

Recovery should reflect the training you did

Periodization often looks very neat on paper. Several weeks of progressive training are followed by a lighter week, and then the next build begins.

That planned structure is useful, but real training is rarely as tidy as the calendar.

You may miss sessions because of work or travel. Another period may go exactly to plan but leave you carrying more fatigue than expected. In both cases, what you completed matters as well as what was originally scheduled.

That is why SmartRunning does not rely on planned recovery weeks alone. It also follows your recent training load and how that training is developing. If the signs suggest that the current load is becoming too high, the training can be adjusted and additional recovery or rest introduced rather than simply waiting for the next planned lighter week.

Recovery is therefore both part of the structure of marathon preparation and something that can become more important when the training itself gives a reason.

Training tolerance changes

The amount of training you can handle is not fixed.

As you become fitter and more experienced, workloads that once seemed substantial may become normal. That is one of the objectives of training.

But tolerance can also temporarily decrease. A period away from running, illness, accumulated fatigue or demanding circumstances outside running can all affect how easily the next training block is absorbed.

This is one reason recovery cannot always be prescribed identically for every runner.

You do not need to wait until you are exhausted before recovery becomes appropriate. Well-designed training uses recovery proactively, both through the planned structure of the preparation and by responding when recent training suggests that more recovery is needed.

Think beyond a single week

Marathon training is long enough that the success of the training plan will never depend on squeezing the maximum possible training out of every week.

What matters is the amount of productive training you can accumulate over the whole preparation.

That requires progression, but it also requires enough recovery to keep that progression sustainable.

A recovery week can therefore feel like a temporary step back when viewed in isolation. Seen as part of several months of training, it has a different role: it helps make the next step forward possible.

One important distinction: research strongly supports reducing training load in a taper before competition, but it does not establish one universal mid-block recovery-week schedule for every marathon runner. The timing and size of easier weeks still need to fit the athlete and the training completed.

See how SmartRunning builds recovery into marathon preparation and responds when recent training suggests more is needed.

What Happened When About 60 Runners Trained With SmartRunning?

What Happened When About 60 Runners Trained With SmartRunning?

In an early observational SmartRunning group of about 60 marathon runners, 90% were recorded as reaching their stated goal and 6% reported an injury during preparation. These figures are encouraging, but they do not establish causation because there was no control group and key outcome definitions still need formal documentation.

A good result is worth sharing. It is also worth saying exactly what it can and cannot tell us.

The first SmartRunning prototype group produced two numbers we wanted to understand properly: a high proportion reached the goal recorded for their preparation, and a small proportion reported an injury. Neither number proves SmartRunning caused the outcome.

90% reached their stated goal

For a training app, that is obviously a result we are pleased to see.

But “reached their stated goal” can cover different objectives, and the strength of the result depends on how those goals were defined and recorded. Before we use the figure as formal evidence, the exact denominator, goal definition, follow-up and any dropouts should be documented clearly.

What we can say today is:

A high proportion of this first SmartRunning group achieved the goal recorded for their marathon preparation.

That gives us a promising starting point. It does not give SmartRunning permission to promise the same outcome to every future runner.

Only 6% of the group reported an injury during preparation.

Given how important injury awareness is to SmartRunning, that is a result worth following closely.

We are aware of the limitations of these first findings.

There was no control group following another plan, and “injury” can be defined in different ways. A physical complaint, an injury that causes missed training and a medically diagnosed injury are not necessarily the same outcome. The exact definition and observation period therefore matter.

The responsible conclusion is that this early group produced an encouraging injury outcome while using SmartRunning’s injury-aware training approach.

Encouraging evidence, not the end of the evidence

This was an observational early group, not a randomized controlled trial.

That does not make the results unimportant. For SmartRunning, the useful next step is to keep building the evidence: larger groups, clearer definitions, consistent follow-up and eventually better comparisons of outcomes between different types of runners.

That approach also fits how we want SmartRunning to behave as a brand: progress runners can trust, without turning promising numbers into hype. The brand itself is built around steadiness, clarity and protecting the runner’s long-term relationship with running.

So, the takeaway from this first group is deliberately measured:

The early results are promising. The next question is whether the same pattern holds as more runners use SmartRunning and the outcomes are defined and tracked more rigorously.

See how SmartRunning is being tested and how we are building the evidence without turning early results into promises.

Why Not Just Ask ChatGPT for a Marathon Plan?

Why Not Just Ask ChatGPT for a Marathon Plan?

ChatGPT can generate a detailed marathon plan from the information you provide. The practical difference with a purpose-built training system is continuity: the system can ingest completed training, apply predefined coaching rules and keep updating the runner profile without requiring you to decide what data to provide or when to ask for a new plan.

Yes, ChatGPT can write you a marathon plan. That is not the most useful question anymore.

The real comparison is what happens after the plan exists – when you miss a run, improve faster than expected, struggle through a week or build months of new training history.

Recent research on AI-generated sports training points to a related limitation: a language model can generate a plan, but the quality of that plan depends heavily on the knowledge and constraints the system is given. A 2026 Scientific Reports paper improved personalized training-plan generation by grounding an LLM in a domain-specific knowledge graph. That does not prove one coaching product is better than another, but it does reinforce the distinction between a general-purpose chatbot and a system built around defined training knowledge and rules.

The difference is who manages the coaching process

Suppose you ask a general AI assistant to coach you towards a marathon.

You can give it your race goal, recent times and training history. You can upload more data. After a difficult week, you can explain what happened and ask what to change. After another few weeks, you can provide the new information and ask again.

That can work well.

But you are managing the process. You decide what information to provide, when something needs reconsidering, how much history matters and when to ask for another decision.

SmartRunning is built so that you do not have to create that workflow yourself.

Your training data becomes part of an ongoing training system. New sessions add to the runner profile, and purpose-built training logic applies that information within the progression and coaching principles already built into SmartRunning.

The runner should not have to keep rebuilding the coaching context every time training changes.

A plan is easy to generate. Coaching it over time is harder

This is the important distinction.

Generating 20 weeks of workouts is a relatively contained task. Marathon preparation is not. Training changes the runner, sessions are missed, performance develops and the information available becomes richer as the weeks pass.

With a general AI tool, you can manage that evolving conversation yourself.

With SmartRunning, that ongoing interpretation is the product.

The dedicated algorithms, training data, coaching principles, individual runner profile, testing and conversational layer have already been brought together into one purpose-built system.

So why pay for SmartRunning if ChatGPT can generate a marathon plan? Not because ChatGPT cannot create one.

Because SmartRunning is designed to keep doing the coaching work after the plan has been created.

For this marathon. And all the runs after.

Try a purpose-built marathon coaching system that keeps interpreting your training after the first plan is created.

Too Much, Too Soon: How Quickly Should Running Increase?

Too Much, Too Soon: How Quickly Should Running Increase?

The familiar 10% weekly mileage rule is not a proven boundary between safe and unsafe training. Recent cohort evidence suggests that large jumps in the distance of a single run may matter more than simple week-to-week mileage ratios. Progression should therefore be judged in context, not by one universal percentage.

The 10% rule is memorable. That does not make it a law of running physiology.

A runner can increase weekly mileage by only 10% and still make one individual run dramatically longer than anything completed recently. The weekly total can look conservative while the session itself is a major spike.

The problem is that the familiar 10% rule is not a scientifically established line between safe and unsafe training.

A weekly percentage can hide a lot

Suppose you normally run about 40 kilometres a week and your longest run is around 12 kilometres.

The following week you run 44 kilometres in total. On paper, that is only a 10% increase. But if your long run has suddenly increased from 12 to 20 kilometres, one part of your training has changed much more than the weekly total suggests.

Recent research supports paying attention to that difference. A 2025 study of more than 5,000 runners found that large increases in the distance of a single run were associated with a higher risk of overuse injury, while simple week-to-week mileage changes did not show the same relationship.

That does not give us another “safe” percentage to follow. It tells us something more useful:

“Too much, too soon” cannot always be seen in your weekly mileage.

You should not have to calculate the answer yourself

This is where a training system like SmartRunning can do something useful.

You should not need to sit down every Sunday with a calculator and work out whether 8%, 10% or 12% is acceptable. Nor should one general rule determine progression for runners with very different recent training histories.

SmartRunning is designed to manage progression within its training logic, using the training you have completed rather than asking you to identify a supposedly safe percentage yourself. Its current controlled product principles explicitly include progression, training-load and recovery guardrails.

That does not mean progress should always be conservative. Marathon training must develop if you are going to become capable of running a marathon.

It means the increase should have a reason and fit the training around it.

Injury awareness is partly about restraint

There is a natural pressure in marathon preparation to keep moving forward. Race day is getting closer. The long run needs to grow. A good week can make you feel capable of more.

Sometimes more is exactly what should happen.

But progress is not improved simply by making every increase as large or as fast as possible.

An injury-aware plan should be willing to progress when the training results support it and equally willing not to accelerate simply because there are fewer weeks left on the calendar.

That is the useful meaning of avoiding “too much, too soon”.

Making the next increase fit the training that came before it.

Let SmartRunning manage progression in context rather than relying on a single weekly percentage rule.