How to Track Your Running Progress

Note: Some links in this article may be affiliate links. If you buy through them, we may earn a small commission at no extra cost to you. We only recommend gear and services we genuinely rate. Learn more.

Photo by Andrea Piacquadio on Pexels

Tracking your running progress serves two purposes: it tells you whether your training is working, and it gives you a reference point when things go wrong.

Without tracking, you’re training blind. You might be improving — or repeating the same sessions in the same conditions indefinitely without stimulus for adaptation. The objective data tells you which it is.


What to Track

Not everything is worth tracking. Focus on the metrics that indicate genuine fitness change rather than just logging noise:

Weekly mileage (or time on feet): The most fundamental metric. Consistent weekly mileage is the primary input to running fitness — tracking it tells you whether you’re training consistently or not.

Pace at a fixed route: Choose a regular running route — ideally flat and traffic-free — and run it periodically at easy effort. Tracking how pace changes on the same route at the same effort is one of the clearest measures of aerobic improvement.

Resting heart rate: Checked first thing in the morning before getting up. As aerobic fitness improves, resting heart rate typically decreases. An increase of 5–7+ beats per minute above your baseline is also a reliable indicator of accumulated fatigue or illness. Smart watches and fitness trackers monitor this automatically.

5K time (or parkrun result): The gold standard measure of running fitness for most recreational runners. A regular parkrun or timed 5K attempt every 4–6 weeks gives clear, comparable data on progress.

Heart rate at easy pace: If you run with a heart rate monitor, the heart rate required to maintain a fixed easy pace decreases as fitness improves. This is a sensitive indicator of cardiovascular adaptation.


Tools for Tracking

Strava (free): The most widely used running app. Records every run automatically via GPS, tracks pace, distance, elevation, and heart rate (if you wear a monitor). Provides weekly and monthly mileage summaries, personal records for common segments and distances, and year-on-year comparison. The free version is sufficient for most runners — premium adds training load analysis and more detailed data.

Garmin Connect / Apple Fitness / Polar Flow: If you have a GPS running watch, the associated app provides all the data Strava does, often with additional metrics (training load, recovery time, VO2 max estimate). Use the native app alongside Strava (they sync automatically).

A paper training log: Underrated. Writing down your runs, how they felt, and any notable conditions takes 2 minutes and creates a searchable history. Many coaches still prefer paper logs precisely because they include qualitative data (“felt tired but got through it”, “stomach issue in mile 2”) that no app captures.

Spreadsheet: A middle ground. Track date, distance, time, pace, and a brief note in a simple spreadsheet. Easy to create custom summaries (monthly mileage, trend charts).


Tracking Progress vs Just Recording Data

Logging runs is easy. Turning logged runs into actionable insight is what most runners skip.

Do a monthly review:

Compare this month to last month:
– Total mileage
– Longest run
– Average pace on easy runs

Look at the trend line, not individual runs: One slow run means nothing. A consistent slowdown across multiple easy runs at the same effort suggests fatigue accumulation or overtraining. A consistent improvement across 6–8 weeks at the same effort suggests genuine fitness gain.

Note patterns:
– Does pace always drop mid-week? Could indicate fatigue accumulation — an extra rest day might help.
– Are hard sessions consistently harder than expected? Could indicate insufficient easy running volume.
– Feeling flat for 2–3 weeks? Check weekly mileage — you may have ramped up too fast.


The Strava PR System

Strava records personal records (PRs) for distances from 400m to marathon on any segment of any run. Over time, your PR list becomes a meaningful record of peak fitness across different distances.

Watch your PRs, but don’t chase them: Running a 5K PR every week is a sure path to injury. Track PRs as indicators of where fitness has been; focus on training rather than PRs and they’ll follow naturally.


Tracking Injury and Health

The most useful running log includes injury data — when pain appeared, what it felt like, what you changed, and when it resolved. This is almost never done, and almost always regretted when the same injury recurs.

Simple injury log entries:

  • Date pain started
  • Location and description (“tight right calf, appeared in km 4”)
  • What training preceded it
  • What you did (rested, reduced mileage, stretched)
  • When it resolved and what helped

If the same injury recurs, you have an evidence-based account of what preceded it — the training pattern that leads to that specific injury for you.


Key Metrics for Common Goals

Building fitness: Weekly mileage trend (going up gradually), resting heart rate trend (going down), 5K time (going down).

Recovery from injury: Weekly mileage (increasing carefully), pain-free run duration.

Marathon training: Long run distance, total weekly mileage, heart rate at marathon goal pace.

Consistency: Number of weeks you hit your target runs per week, streak length.


Summary

Tracking running progress doesn’t require expensive gadgets or complex systems:

  1. Track weekly mileage — the fundamental input to running fitness, and the first place to look if progress stalls or injury occurs
  2. Use parkrun as your benchmark — a regular 5K effort every 4–6 weeks gives clear, comparable performance data
  3. Monitor resting heart rate — a rise of 5–7+ beats is an early warning sign of fatigue or illness
  4. Do a monthly review — compare to last month’s data and look for trends, not individual run variations
  5. Log injury data — note when pain appears and what preceded it; this prevents the same injury recurring from the same training error

Next read: How to build a weekly running schedule