Every serious runner has a training log — a record of every run, workout, and race. But the log is only valuable if you actually use it to learn from. Reviewing your year of running — what you did, what worked, what didn't — is one of the most effective ways to become a better runner in the year ahead.
This guide covers how to build a running log, what metrics to track, how to analyse your year, and how to turn that analysis into smarter goals and better training decisions.
Why Every Runner Should Keep a Training Log
A training log does several things that memory alone can't:
- Shows patterns — which weeks led to your best races? Which workout types improved your pace most?
- Identifies injury triggers — most running injuries follow patterns. A log lets you see: did your injury happen after a sudden jump in mileage? After adding speed work too soon?
- Creates accountability — logging a run (or not logging one) makes training concrete rather than abstract
- Documents progress — your first 5K time vs. your current 5K time is visible, specific, and motivating
- Informs future planning — "What worked last time" is only answerable if you recorded what you did
What to Track in Your Running Log
You don't need to log everything — too much data is as useless as no data. Focus on the metrics that drive decisions:
| Metric | Why It Matters | How to Capture |
|---|---|---|
| Date | Enables time-series analysis | Automatic in all apps |
| Distance (km) | Foundation of training load | GPS watch/app |
| Duration (min) | For non-distance based runs | GPS watch/app |
| Average pace (min/km) | Tracks pace improvements over time | GPS watch/app |
| Average heart rate | Cardiac drift, fitness trends | HR monitor |
| Elevation gain (m) | Route difficulty, training load | GPS watch/app |
| Session type | Easy/tempo/intervals/long run | Manual tag |
| How you felt | Subjective effort, fatigue, enjoyment | Short note (1–5 scale) |
| Races | Performance benchmarks | Manual record with result |
The "how you felt" entry is often underrated. Patterns in subjective fatigue often predict overtraining and injury 1–2 weeks before the injury occurs. If you felt unusually tired for 5 consecutive days without explanation, your log reveals this.
Tools for Logging and Analysing Your Running
GPS Apps (Automatic Logging)
Strava is the most popular choice for runners worldwide. It automatically logs every GPS run, calculates pace, elevation, heart rate zones, and provides year-in-review summaries. Its social features — segments, kudos, clubs — add a motivational community layer. The free version covers all essential logging; the paid Strava Subscription adds route planning and advanced analysis.
Garmin Connect is the best choice if you use a Garmin watch — seamless sync, detailed HR zone analysis, and a comprehensive annual stats summary. Apple Fitness works similarly for Apple Watch users.
Nike Run Club has excellent coaching plans and audio-guided runs built in, plus solid logging features.
Manual Running Journals
A paper running journal adds a reflective dimension that apps don't capture. Purpose-built running journals include space for mileage, pace, heart rate, weather, and a free-text notes field. Writing about a hard training session or a breakthrough race creates a narrative record that data alone can't replicate.
Spreadsheets (Google Sheets, Excel) are a middle ground: more flexible than apps for custom analysis, more structured than paper, and free.
Key Metrics for Your Year-End Review
At the end of each year, extract these totals from your log:
- Total annual mileage — how many km did you run in total? Year-over-year comparison shows training volume growth.
- Peak week mileage — your highest single week. Important for understanding your maximum training load and where injury risk spiked.
- Personal bests (PRs) — 5K, 10K, half marathon, marathon times. Did any improve this year?
- Number of races completed — races are your best performance benchmarks.
- Average monthly mileage — consistency metric. Months where mileage dropped significantly often correlate with illness, injury, or life disruption.
- Total elevation gain — if you run hills or trails, this reveals how much harder your training was than flat-only running.
💡 Trend spotting: Pull a monthly mileage graph. The pattern reveals everything — plateaus where your training stagnated, ramp-ups before races, drops when life got busy. This visual alone generates the most insight of your entire review.
Analysing Your Progress: Questions to Ask
Data without questions is just numbers. Use these questions to turn your log into actionable insights:
- Did my pace at the same heart rate (Zone 2 pace) improve over the year? This is the clearest measure of aerobic fitness gain.
- What were my 3 best training weeks? What made them possible?
- What derailed my training (injury, illness, travel, motivation dips)? How can I prevent the same disruptions next year?
- Which race performance am I most proud of — and what training preceded it?
- Did I rest enough? Look for recovery weeks in your log — if you went 10+ weeks without a deliberate down week, that's worth changing.
- What would I do differently?
Setting Goals for the Next Year
Your year-end review exists to make next year better. Goal-setting works best when it's based on actual data rather than wishful thinking. Use the SMART framework:
- Specific — "Run a sub-25:00 5K" beats "run faster"
- Measurable — your GPS log will confirm whether you hit it
- Achievable — based on your current fitness, is this realistic in 12 months?
- Relevant — does this goal align with why you run?
- Time-bound — which race, which date?
Set 1–3 outcome goals (race times, distance milestones) and 2–3 process goals (run 4 times per week, complete 12 long runs, hit 1,500 km for the year). Process goals are within your control; outcome goals depend on race conditions. Achieving your process goals makes the outcome goals likely.
Sharing Your Running Year
Year-in-review running posts are some of the most popular running content on social media every December and January. Strava auto-generates a "Year in Sport" summary with your annual mileage, longest run, fastest pace, and most-used shoes. This is a great starting point.
To make your year-in-review posts more engaging, pair the summary data with photos from your best runs and races. Use PaceOverlay to add your key stats — total year mileage, best race time, or a specific achievement — directly onto your favourite running photo of the year. The visual makes the achievement shareable in a way a text post can't match.
Overlay Your Running Stats
Add your pace, distance, and heart rate to your running photos and videos — share your stats the way the pros do.
Try PaceOverlay Free →For a year-in-review video, compile your best running footage from the year, add a live overlay from your most memorable race or workout, and share it as a Reel or TikTok with your annual stats. This kind of retrospective content consistently outperforms standard running posts in engagement.
FAQ: Running Log and Annual Review
How do I do a running year-in-review?
At the end of the year: pull your total annual mileage, personal bests, number of races, and peak weekly mileage from your GPS app. Identify your best month, your best race, and your biggest achievement. Write 3 things you're proud of and 2 things you want to change next year. Set 1–3 specific goals with target dates for the coming year.
What is a good yearly mileage for a runner?
It varies enormously by experience and goals. A healthy beginner might run 300–600 km in their first full year. Recreational runners typically cover 800–1,500 km per year. Competitive club runners cover 2,000–4,000 km. Elite marathon runners may exceed 5,000 km. The "right" annual mileage is the one that makes you progressively fitter without getting injured — this varies by individual.
Should I share my running data publicly?
Sharing selectively is fine. Sharing race results, annual totals, and milestone moments on social media is motivating for yourself and others in the running community. Be mindful of location privacy — avoid sharing the exact GPS route of your home neighbourhood runs by using Strava's Privacy Zone feature, which hides the start and end of your runs near your home address.
Conclusion
A running log is a mirror. It shows you exactly who you are as a runner — the consistency, the habits, the breakthroughs, and the setbacks. Reviewing that mirror at year's end is one of the most valuable 30 minutes you can invest in your running. The patterns you find will guide your training, protect you from injury, and help you set goals that actually matter. The data exists in your GPS app. All it takes is the willingness to look at it honestly.