Why this is hard
The long run is the anchor of most running programs. Missing it feels like losing a week. But running long on accumulated fatigue, poor sleep, or lingering soreness compounds into injury risk that doesn’t show for days. The cost of a forced long run is invisible until Tuesday.
Where athletes usually go wrong
Running the prescribed distance regardless of how legs feel. Treating the long run as non-negotiable. Not adjusting pace when soreness signals are present. Assuming cardiac readiness (HRV fine) means musculoskeletal readiness.
What other tools miss
HRV recovered overnight — but calves haven’t. TrainingPeaks says 16 miles — doesn’t know you ran hills Wednesday. Garmin says productive — can’t feel your achilles tightening.
How Rudder helps
Captures leg soreness and energy before any data. Checks load: hard sessions in last 3 days, consecutive running days. If soreness is moderate + recent hard session: MODIFY (cut distance or switch to easy). Warmup gate for borderline days.
Example decisions
18-mile long run planned. Ran tempo Wednesday, hills Thursday. Legs moderate sore. HRV fine.
MODIFYLong run day. Feel flat but not sore. Slept 7h.
GO WITH LIMITS3rd week of marathon block. Everything aches.
MODIFYBest integrations for this goal
Strava (run load and consecutive days), Oura / WHOOP (sleep and recovery baseline), TrainingPeaks (planned workout context).
Frequently asked
- Should I do my long run if I feel tired?
- Depends on the type of tired. Rudder distinguishes between normal training fatigue (safe to run) and accumulated overload (back off). The warmup gate helps: start easy, see how the legs respond after 15 minutes.
- How does Rudder protect my long run?
- Rudder knows when your long run is coming from your plan. Earlier in the week, it may recommend easier sessions to preserve your capacity for the key long effort.
Related
The long run matters.
So does the rest of the week.
Start your free check-in