How to Keep a Running Log: Using Data Analysis to Improve Training Efficiency

“You can’t improve what you can’t measure.” This management adage applies equally to running training. Systematic training logs are not just a pile of numbers—they are an essential tool for understanding your body, identifying training blind spots, and preventing injuries.

1. Why You Need a Running Log

The core value of a running log:

1. Spot Training Trends: See when your training volume is too high/too low
2. Injury Prevention: Injuries often have warning signs; you only notice them when looking back at your log
3. Pace Calibration: Track pace differences across various weather conditions and terrains
4. Sustained Motivation: Seeing long-term accumulated results reinforces your confidence to keep going
5. Race Preparation Review: Having a reference point for your next race preparation

2. Core Data You Must Record

Basic Data for Every Run

Field	Description	Importance
Date and Time	Include start time	★★★
Distance (km)	Accurate to 0.1 km	★★★
Time (min:sec)	Total moving time	★★★
Average Pace (/km)	Total time ÷ distance	★★★
Route	Brief description or place name	★★☆
Workout Type	Easy run/Tempo/Intervals/Long run	★★★

Advanced Data to Record

Field	Description	Recommended Tool
Average Heart Rate	Assess training intensity	GPS watch
Maximum Heart Rate	Confirm intensity ceiling	GPS watch
Elevation Gain	Quantify hill training	GPS watch
Cadence (steps/min)	Running form efficiency indicator	GPS watch
Stride Length (cm)	Analyze alongside cadence	GPS watch
Perceived Temperature	External factor affecting pace	Manual entry

Body Condition Records

This is the most valuable yet most overlooked part of the log:

Field	Description
Morning Resting Heart Rate	Before getting up each morning; be cautious if 5 bpm above baseline
Sleep Hours and Quality	Directly affects training effectiveness
Fatigue Level (1-10)	Subjective assessment, but very useful
Muscle Soreness Locations	Record where and when soreness begins
Nutrition Intake	Especially before and after long runs

3. How to Analyze Running Data

Weekly Training Volume Trend Analysis

Review at the end of each month:

• Average weekly mileage for the month
• Highest mileage week vs. lowest mileage week
• Number of high-intensity workouts (whether exceeding 2 per week)

Warning Sign: If a week’s mileage exceeds the previous week by more than 20%, and fatigue or minor pain appears afterward, this is direct evidence of “too-rapid progression.”

Pace Improvement Tracking

Under the same level of effort, is your pace improving?

The best method is tracking pace changes on a fixed route at a fixed intensity (same heart rate zone):

Date	Route	Heart Rate Zone	Pace
Jan 15	Riverside 6 km	70-75% HRmax	5:45/km
Feb 15	Riverside 6 km	70-75% HRmax	5:38/km
Mar 15	Riverside 6 km	70-75% HRmax	5:30/km

Pace decreasing (number getting smaller) = aerobic capacity improving

Injury Prevention Analysis

Whenever pain occurs, review the log from the previous 2 weeks:

• Whether training volume suddenly increased
• Whether high-intensity workouts were too frequent
• Whether sleep quality declined
• Whether you switched to new running shoes

4. Recommended Running Log Tools

Phone/GPS Tracking Apps

App	Pros	Cons	Best For
Strava	Strong social features, clear analytics	Advanced features require payment	Runners who enjoy community
Garmin Connect	Perfect integration with Garmin watches	Interface is more complex	Garmin users
Nike Run Club	Easy to use, free	Data analysis is more basic	Beginners
Polar Flow	Excellent training load analysis	Requires Polar devices	Serious trainers

Recommended GPS Watches

Tier	Recommended Model	Best For
Entry-level	Garmin Forerunner 55	Beginners, light trainers
Mid-range	Garmin Forerunner 265	Serious race preparers
Advanced	Garmin Fenix 7	Multi-sport runners
Advanced	COROS PACE 3	High value-for-money mid-range choice

Paper Logs

Old-school but effective, especially for runners who prefer to spend less time looking at screens:

Recommended Format (one page per week):

• Left side: simple daily records (5 columns: date, distance, pace, heart rate, how you felt)
• Right side: weekly training highlights review, next week’s goals

5. Practical Case Study of Training Log Analysis

Suppose you are preparing for the Taipei Marathon (December). Here is how to use your log:

September Review: You notice 3 consecutive weeks at 60 km, but in week 4 the mileage suddenly jumps to 75 km, and minor knee discomfort appears that same week
→ You recognize that your mileage increase needs to be more gradual

October Observation: You notice that after every run in cold, wet weather, your resting heart rate the next morning is 4 bpm higher than usual
→ You learn that you need more recovery time in low temperatures

November Analysis: Comparing your pace on the same riverside route across different seasons, you find your aerobic efficiency in November is 12% better than in July
→ You understand the impact of Taiwan’s summer heat on performance, providing a reference for future race preparation

6. Simplified Log for Busy Runners

If keeping a full log feels too tedious, the most minimal version only requires recording three things:

1. How many kilometers (or minutes)
2. How it felt (easy/moderate/hard)
3. Any physical discomfort

These three pieces of information are already enough to help you spot early signs of overtraining.

Conclusion

You can start keeping a running log today—no special tools required. Six months from now, you’ll be pleasantly surprised by your progress and will have a much better understanding of how your body responds to training. Data is not the goal; it is a tool to help you make smarter training decisions.

Related Reading

• How to Keep a Road Running Training Log: Analyzing Weekly Reports to Find Training Blind Spots
• Building a Road Running Training Log: Effective Recording Methods for Long-Term Progress
• The Importance of a Cycling Training Log: How to Record and Analyze Your Progress
• Swimming Training Log: Key Data for Recording and Tracking Swimming Progress