Running log guide
How to track a long run
Track long runs with duration, distance, effort, route, and execution notes so progress is visible without chasing one headline metric.
The short answer
Track a long run relative to your own recent training, because “long” is not one universal distance. Record planned and completed duration, distance, effort, route or surface, meaningful stops, and how the final portion felt. Compare similar runs across a training block, and avoid judging progress from distance or pace without the conditions that produced them.
Put this into practice
Run + Lift
5 days a week · 8 weeks · See every workout free
View the complete planKeep the full run
Let long-run context survive the finish line.
LogFast preserves duration, distance, effort, and your original description, while Coach uses the structured workout history.
Track a long runDefine long relative to your current week
A long run is generally the extended run in your schedule, but its useful length depends on your recent training, goal, and experience. Record the planned purpose—easy time on feet, steady endurance, route practice, or a structured finish—before evaluating the result. This prevents every long run from being graded only by distance.
Avoid importing a distance target or weekly progression rule without context. A run can become more demanding through time, hills, trail surface, faster segments, or accumulated fatigue even when distance is unchanged. The log should show which variable changed and whether that change was intentional.
Capture the minimum useful fields
Start with planned duration or distance, completed duration, moving time if known, distance, and overall effort. Add a talk-test note for an easy long run. Record route, elevation, surface, weather, and pauses when they materially affect comparison. Optional split detail is useful when the route or workout has distinct segments.
A practical entry is: “Planned 80 min easy; completed 82 min, 12.4 km; conversational through 65 min, RPE 4 at finish; rolling paved route, warm and windy; one 90-second water stop.” It documents execution without pretending that average pace tells the full story.
- Plan versus completion: time, distance, and intended effort
- Execution: pace or splits, talk test, RPE, and final-section feel
- Course: route, elevation, surface, and stops
- Context: weather and any change made during the run
Keep segments and interruptions visible
If the run included a steady finish, hills, or planned walk breaks, log those segments separately. For example: “60 min easy + 15 min steady; final segment RPE 6, controlled.” This prevents a mixed-purpose run from being compared directly with a fully easy run of the same average pace.
Pause data deserves a note when it changes interpretation. Moving time may be useful for pace comparison, while elapsed time captures the full outing. Neither is inherently the correct headline. Record both when stops, route navigation, or refueling make the difference meaningful.
Long-run progress is easier to see when the log preserves purpose, execution, and conditions together.
Review the block rather than one heroic day
Across several weeks, compare completion, effort, late-run control, and recovery of normal performance in later workouts. More distance is only one possible change. A similar run at lower effort, steadier pacing, or with fewer unplanned slowdowns may be equally informative.
Log the run soon after finishing, keep route or split context in the entry, and correct duration, distance, or effort before saving. Coach receives recent structured workout metrics, not the route or weather notes stored with the entry. Use the saved history for your own matched-session review; LogFast does not automatically collect the run from a watch.
Frequently asked questions
How far does a run need to be to count as long?
There is no universal distance. Treat the extended run in your current schedule as the long run and record its purpose, because the same distance can represent very different demands for different runners.
Should I track moving time or elapsed time?
Track both when stops are meaningful. Moving time helps with pace comparisons, while elapsed time reflects the full outing. Note why you stopped so the difference has context.
What is the best sign of long-run progress?
Look for repeated improvement in relevant outcomes: completion, controlled effort, stable late-run pace, or more work at a similar effort. No single metric is best for every goal.