Tracking Running Progress: Key Metrics That Actually Matter

Share

What should you track as a runner? Learn which metrics provide actionable insights versus vanity numbers, and how to use data for improvement.

Bob BodilyBob Bodily
4 min readMetrics & Analytics

Quick Hits

  • The best metrics are ones that inform decisions, not just satisfy curiosity
  • Volume (weekly miles/time) is the most fundamental metric to track
  • Trends matter more than individual data points
  • Rate of perceived exertion (RPE) is underrated and free
  • More data isn't always better—analysis paralysis is real
Tracking Running Progress: Key Metrics That Actually Matter

Modern runners can track everything. But should they?

Here's what actually matters.

Essential Metrics (Track These)

Weekly Volume

What: Total miles or time running per week

Why it matters:

  • Correlates with aerobic fitness
  • Correlates with injury risk (too much, too fast)
  • Foundation for all other training

How to use: Track week-over-week and month-over-month trends. Progress gradually.

Workout Performance

What: Splits and paces during quality sessions

Why it matters:

  • Shows fitness progression at specific efforts
  • Indicates if training is working
  • Validates race time predictions

How to use: Compare similar workouts over time. 5×1K this month vs. last month.

Race Results

What: Official times and paces

Why it matters:

  • Ultimate test of fitness
  • Provides reality check
  • Sets benchmarks for training

How to use: Compare equivalent races. Track age-graded performance over years.

Rate of Perceived Exertion (RPE)

What: How hard the effort felt (1-10 scale)

Why it matters:

  • Captures what data misses
  • Accounts for life stress, sleep, conditions
  • Free and always available

How to use: Note RPE for every run. Correlate with pace and heart rate.

Recovery Indicators

What: How you feel day-to-day, sleep quality, motivation

Why it matters:

  • Predicts injury and overtraining
  • Guides training adjustments
  • Personal and individual

How to use: Track subjective recovery. Notice patterns before problems.

Nice-to-Have Metrics

Heart Rate

What: Beats per minute during and after runs

Why it matters:

  • Objective effort measurement
  • Tracks cardiac adaptation over time
  • Helps enforce easy days

Limitation: Affected by heat, caffeine, stress, sleep

Cadence

What: Steps per minute

Why it matters:

  • Related to running economy
  • May indicate form changes
  • Generally increases with fitness and speed

Limitation: "Optimal" cadence varies individually

Heart Rate Variability (HRV)

What: Variation between heartbeats at rest

Why it matters:

  • Indicates recovery status
  • May predict overtraining
  • Provides objective recovery data

Limitation: Requires consistent measurement, varies with many factors

Training Load Metrics (CTL/ATL/TSB)

What: Calculated fitness, fatigue, and form

Why it matters:

  • Objective training quantification
  • Helps time peak fitness
  • Prevents overtraining

Limitation: Doesn't capture all training aspects, individual response varies

Vanity Metrics (Track If Fun, Not Essential)

Daily Pace

What: Pace for every easy run

Why it matters (limited):

  • Record keeping
  • Route comparison

Why it's overrated: Daily pace varies with conditions, fatigue, and route. Judging easy runs by pace misses the point.

Calories Burned

What: Estimated energy expenditure

Why it matters (limited):

  • Weight management context
  • Fueling guidance

Why it's overrated: Estimates are notoriously inaccurate. Better to eat by hunger and performance.

Step Count

What: Total steps per day

Why it matters (limited):

  • General activity level
  • Non-running activity

Why it's overrated: For runners, running volume matters more than total steps.

How to Use Data Effectively

Individual data points are noisy. Look at:

  • 4-week rolling averages
  • Month-over-month changes
  • Season-over-season patterns

One bad run means nothing. A month of struggling means something.

Compare Like to Like

Meaningful comparisons:

  • Same workout, different months
  • Same race, different years
  • Similar conditions and contexts

Misleading comparisons:

  • Hilly run vs. flat run
  • Hot day vs. cool day
  • Fatigued vs. rested

Act on Data

Data without action is entertainment.

Ask: "What does this data tell me to do differently?"

If the answer is "nothing," the data may not be essential.

Know When to Ignore

Ignore data when:

  • You're sick
  • Unusual life stress
  • Extreme weather
  • Equipment malfunction

Context always matters.

Avoiding Analysis Paralysis

The Trap

More data available → more time analyzing → less time training → worse results

The Solution

Pick 3-5 key metrics and focus on those.

Suggested minimal tracking:

  1. Weekly mileage
  2. Key workout performance
  3. How you feel (RPE/recovery)

Everything else is optional.

Weekly Review Process

5 minutes per week:

  1. Total volume vs. plan
  2. How did quality sessions go?
  3. How do I feel overall?
  4. Adjustments needed?

That's it. Move on.

Building a Simple System

What to Track

Metric Frequency Tool
Run distance/time Every run Watch/app
RPE Every run Notes
Workout splits Quality sessions Watch/app
Weekly total Weekly Spreadsheet/app
Race results As raced Manual log

What to Review

Review Frequency Focus
Run reflection Post-run How did it feel?
Weekly review Sunday Volume, workouts, recovery
Monthly review End of month Trends, adjustments
Quarterly review 4x/year Big picture progress

The best runners aren't always the best data analysts. Track what helps you train smarter, ignore what doesn't. Use your dashboard to see the metrics that matter, and our Training Load Calculator to understand your fitness trends.

Key Takeaway

Track what informs your decisions. Weekly volume, workout performance, race results, and how you feel provide the essential picture. Everything else is bonus—useful for some, noise for others.

Frequently Asked Questions

What's the most important metric to track?
Weekly volume (miles or time running) is foundational. It correlates with fitness and injury risk. Beyond that, tracking how you feel (RPE) provides context that pure data misses.
Should I track pace for every run?
Tracking is fine; obsessing isn't. Pace varies with conditions, fatigue, and route. Track it, but don't judge every run by pace. Heart rate or RPE provide better effort context.
How often should I review my data?
Weekly review of key metrics is sufficient for most runners. Monthly or quarterly reviews of trends are valuable. Daily obsessing is counterproductive.
What if my metrics aren't improving?
Plateaus are normal. Look for non-metric improvements (feeling better, recovering faster). Review training consistency and recovery. Sometimes the breakthrough comes after the plateau.

References

  1. Running analysis research
  2. Coaching best practices

Send to a friend

Know someone training for a race? Share this with their long-run buddy.