Why one training run can be misleading
One slow run does not establish lost fitness. Review conditions, effort, recovery and symptoms before deciding what today’s result means for the longer-term plan.
The same review applies whether your programme includes threshold work or other sessions: distinguish uncertain performance data from symptoms that require action.
How this guide is meant to be used
Useful context for reviewing an unexpectedly slow run:
Adjust Marathon Pace hub · Heat · Wind · Hills · Harder-than-usual pace · Cardiac (HR) drift · Race-day adrenaline · Late-race slowdown
On this page
- Definitions: signal vs noise
- Why pace fluctuates (the big buckets)
- Make today’s decision first
- What to track (without becoming a slave to data)
- When a pace change says little about fitness
- When to make a broader change
- Four examples of interpretation
- A short training-note template
- FAQ
- References
Definitions: signal vs noise
Noise = normal variability that doesn’t require changing your plan (one off day, bad sleep, heat spike, windy route, low-fuel morning, heavy legs after a long run).
Signal = a repeated pattern (multiple sessions) that suggests your current load and recovery balance needs adjusting (e.g., persistent high RPE at easy pace, consistently rising HR at the same pace, struggling with workouts you usually complete reliably).
The most useful rule
One run is a data point. Three runs is a trend. Don’t rewrite your training plan because of one weird day.
Why pace fluctuates (the big buckets)
1) Conditions (context for today’s pace)
- Heat / humidity: HR rises at the same pace; effort feels harder.
- Wind: pace becomes “expensive” into headwinds; GPS gets noisy.
- Hills: forcing even pace spikes effort uphill and trashes quads downhill.
2) Recovery (sometimes noise, sometimes signal)
- Sleep: poor sleep increases perceived effort and reduces tolerance for intensity.
- Life stress: total stress load matters, not just training stress.
- Accumulated fatigue: what felt fine last week feels hard this week.
3) Fueling / glycogen (huge hidden variable)
Low carbohydrate availability can make steady paces feel harder and can reduce your ability to hit quality targets. One under-fueled morning run can look like lost fitness when it is really an empty tank.
4) Normal measurement noise
- GPS variance (trees, buildings, turns)
- Wrist HR inaccuracies (especially in cold or with cadence lock)
- Different routes, surfaces, shoes, and stop-start traffic
Make today’s decision first
Separate the decision about today’s run from the decision about your longer-term goal. A hot day may tell you little about lost fitness while still requiring a substantial change today.
On a small screen, swipe the table to see all columns.
| Question | Useful evidence | Action |
|---|---|---|
| Should I continue this session? | Symptoms, effort, weather and route safety now | Reduce, stop or seek help when needed |
| Should I revise the training load or goal? | Comparable sessions, recovery and the wider block | Review persistent patterns and their context |
There is no validated rule requiring three difficult runs in 7–10 days. Pain, illness or a marked change can justify action immediately.
What to track (without becoming a slave to data)
Sports monitoring literature generally supports combining subjective and objective markers—because no single metric is perfect. The most useful approach is usually trend-based: effort, heart-rate behaviour, sleep, and simple recovery context.
| Metric | Best use | Big mistake |
|---|---|---|
| RPE (effort) | Fastest early warning; track trends | Ignoring it because pace is fine |
| HR trend at easy pace | Detects rising strain or drift | Reacting to one spike instead of a multi-km trend |
| HRV (trend) | Helpful as weekly average or trend | Using one low value as a go/no-go decision |
| Sleep (hours + quality) | Often explains mystery bad sessions | Underestimating its impact on RPE |
| Fueling consistency | Explains performance swings in quality sessions | Only fueling when you already feel bad |
This matters even more in structured threshold systems. If you are using Norwegian Singles for marathon training, the whole method works better when you can keep threshold work controlled instead of forcing sessions on days that are clearly sending recovery warning signs.
When a pace change says little about fitness
One slow split on a climb or in strong wind is a poor reason to lower your estimate of fitness. It can still be a good reason to adjust effort during that run. A better-than-usual split also needs context before you make a goal faster.
Avoid dismissing pain, illness or a marked unexplained change as “noise”. The label is only a way to discuss uncertain performance data, not a reason to ignore symptoms.
When to make a broader change
Review load or the goal when comparable sessions repeatedly feel harder than intended, recovery worsens or circumstances change materially. Do not wait for a preset number of sessions if pain or illness appears.
A broad review may lead to reducing duration as well as intensity, resting or seeking assessment. It does not always mean retaining the mileage and trying the workout again a few days later.
Four examples of interpretation
On a small screen, swipe the table to see all columns.
| Observation | Reasonable next step |
|---|---|
| One slow exposed run in strong wind | Adjust today; do not infer lost fitness from pace alone |
| Several comparable runs with unusual effort | Review training, recovery and health |
| A normal watch score but painful walking | Prioritise symptoms and seek assessment |
| One unusually fast session | Record it without automatically making the goal faster |
A short training-note template
A useful note can be brief: “Planned 8 km easy; completed 6 km because effort was unusually high. Warmer than usual, poor sleep, no pain. Next action: rest and reassess.” A separate race-goal note might say: “Several comparable pace sessions have been harder than intended; review the target before adding more work.”
Use the training review questions for the broader decision. The note is a record of your reasoning, not a diagnosis.
FAQ
Should I ignore one poor run?
Review it in context. One run may say little about fitness, but symptoms or unsafe conditions still require action.
How many runs establish a trend?
There is no universal count. Comparability, the size of the change and recovery matter.
Can a watch recovery score decide the session?
Use it as one observation alongside symptoms, sleep, workload and how you feel; it is not a clearance test.
References
- Halson SL. Monitoring Training Load to Understand Fatigue in Athletes (2014). Full text (PMC)
- Coyle EF. Cardiovascular drift during prolonged exercise: new perspectives (2001). PubMed
- Jeukendrup AE. Nutrition for endurance sports: Marathon, triathlon, and road cycling (2011). Full text
- Granero-Gallegos A, et al. HRV-Based Training for Improving VO2max in Endurance Athletes (systematic review, 2020). Full text (PMC)
- Smyth B. Fast starters and slow finishers: a large-scale data analysis of pacing… (2018). Article page