Running Training Log: How to Analyze Weekly Reports to Identify Training Blind Spots

Introduction

“I run a lot every week, but my performance never improves.” This is a common frustration among Taiwanese runners. The problem is often not insufficient training volume, but a lack of systematic reflection and adjustment mechanisms. The Training Log is the core tool of this mechanism—it doesn’t just record how much you ran, but helps you see “why” you are improving or stagnating.

From handwritten journals to Garmin Connect, Strava, and Nike Run Club, modern runners have a wealth of recording tools. But tools are just a means; what truly matters is the “habit of analysis”—spending 15–20 minutes each week reviewing your training, identifying blind spots, and adjusting direction for the following week.

What Should a Training Log Record?

An effective training log needs to record data across two dimensions:

Objective Data (Quantitative)

Recording Item	Description
Date and Training Type	Easy run/Long run/Intervals/Tempo, etc.
Distance (km)	Actual distance of each run
Time (minutes)	Actual running time (excluding warm-up preparation)
Average Pace	Overall or split pace
Average/Max Heart Rate	Objective indicator of intensity
Weather Conditions	Temperature, humidity, whether it was sunny
Surface Type	Asphalt, track, trail, treadmill

Subjective Feelings (Qualitative)

• RPE (Rate of Perceived Exertion): 1–10 scale, 1 = extremely easy, 10 = maximal effort
• Leg Condition: Light/Heavy/Tight/Sore
• Sleep Quality: Hours of sleep and quality assessment from the previous night
• Mood and Motivation: Mental state before and after training
• Nutrition and Fueling: Main meals before and after training
• Pain or Discomfort: Any unusual sensations in any body part (location, severity on a 1–5 scale)

Four Steps for Weekly Analysis

Step 1: Calculate Weekly Summary Numbers

On Sunday evening or Monday morning, calculate the following numbers:

• Total weekly mileage
• Number of training sessions this week
• Intensity distribution (low-intensity mileage vs. speed workout mileage)
• Longest run of the week
• Weekly average RPE

Compare with the previous week and the week before that to see whether the trend is rising, steady, or declining.

Step 2: Compare Plan vs. Actual

Compare the actual completed training against the plan:

• Which workouts were completed as planned?
• Which workouts were not completed or were cut short? What were the reasons? (Weather, fatigue, time, injury)
• Which workouts felt harder than planned? Easier than planned?

This comparison reveals the “gap between plan and reality,” which is the primary source of training blind spots.

Step 3: Identify Patterns and Warning Signs

After 3–4 consecutive weeks of log entries, the following patterns deserve special attention:

Signs of Progress:

• Pace at the same heart rate improves by 3–5 seconds/km each week
• RPE decreases (the same workout feels progressively easier)
• Faster recovery after long runs

Warning Signs (may require plan adjustment):

• RPE for the same workout has not decreased but increased for 2+ consecutive weeks
• The same body part repeatedly appears in the injury log with a rating of 2–3 or higher
• Low mood and persistently declining motivation before and after training (psychological symptoms of overtraining)
• Resting heart rate is more than 5 bpm higher than usual (often indicates the body is still recovering)

Step 4: Fine-Tune Next Week’s Plan

Based on the analysis results, make small adjustments to next week’s plan:

• If you feel particularly fatigued this week (RPE generally high): reduce volume by 10–15% next week
• If a specific type of run (e.g., Tempo Run) feels exceptionally difficult: adjust the pace or shorten the distance next week
• If you recover quickly after long runs and feel great: consider adding 1–2 km to next week’s long run

Common Training Blind Spot Cases

Through log analysis, here are the most common training blind spots among Taiwanese runners:

Blind Spot 1: Easy Run Pace Too Fast

• Symptoms: RPE for easy runs is often 5–6, heart rate exceeds 78% of max heart rate
• Cause: Pace vanity, pressure to keep up with running partners’ pace
• Solution: Set heart rate alerts and force yourself to slow down; accept that easy runs should be “truly easy”

Blind Spot 2: High-Intensity Workouts Too Frequent

• Symptoms: More than 2 speed workouts per week, weekly high-intensity mileage exceeds 30%
• Cause: Rushing to improve, no awareness of the 80/20 principle
• Solution: Clearly mark high-intensity workouts in the log, no more than 2 per week

Blind Spot 3: Ignoring Early Signs of Injury

• Symptoms: Knee or Achilles tendon discomfort repeatedly appears in the log at 1–2, but no action is taken
• Cause: The “just push through it” mentality
• Solution: If discomfort appears in the same area for 3 consecutive days, stop loading that area and consult a physical therapist

Blind Spot 4: Training Volume Fluctuating Too Much

• Symptoms: 60 km one week, drops to 20 km the next due to life commitments, then jumps back to 65 km the following week
• Cause: Irregular lifestyle, catch-up mentality
• Solution: Assess progress using a weekly moving average rather than single-week numbers; if you miss a session, let it go—don’t make up for it

Tool Recommendations

Common recording tools used by Taiwanese runners:

• Garmin Connect: Automatically records GPS data, provides heart rate zone analysis, suitable for runners with Garmin watches
• Strava: Strong community sharing features, lets you see friends’ training activity, great for motivation
• DIY Log in Google Sheets: Most flexible, allows custom formulas to calculate weekly mileage, intensity distribution, and trend charts
• Handwritten Journal: The most traditional, but offers the highest quality of subjective feeling records and the least psychological pressure

Practical Advice

• Record your feelings immediately after each session: Memory fades quickly; recording within 30 minutes after training gives the most accurate impressions
• Keep weekly analysis under 20 minutes: Keep the analysis within a fixed, short time frame; building the habit matters more than deep analysis
• Do a big review every season: Review every 3 months to look at quarterly trends and adjust long-term plans
• Don’t just look at pace: Pace is affected by weather, terrain, and fatigue; the combination of heart rate + RPE reflects your true state better than pace alone

Conclusion

The training log is a record of the dialogue between you and your body. Every page is a message your body sends you—the joy of progress, the warning of fatigue, the harbinger of injury. Runners who can “read” their logs will find breakthroughs when performance stagnates, hit the brakes before overtraining occurs, and head to the starting line with full confidence and preparation. Start logging today, and when you look back three months from now, you will be amazed to discover that within those numbers and words lies the most important wisdom of your running life.

Related Reading

• Building a Running Training Log: Effective Recording for Long-Term Progress
• How to Record a Running Log: Data Analysis to Improve Training Efficiency
• The Importance of a Cycling Training Log: How to Record and Analyze Your Progress
• Running Special Feature | Fatigue Monitoring in Periodized Training (R062)