How to use a running journal to improve your training

Photo by Lucas Andrade on Pexels

You’ve been running for a few months — maybe longer. You finish each session, check Strava, feel good (or bad) about the number, and move on. But two weeks later, when your knee starts nigging or you have three flat runs in a row, you’ve got nothing to go on. No context. No pattern. Just a vague sense that something’s off.

That’s exactly the problem a running journal solves. Not because writing things down is magic, but because training is too complex to hold in your head. A journal turns a blur of individual runs into a picture of how your body is actually responding to training over time. And once you can see that picture, you can do something about it.

This isn’t about logging every metric your watch can produce. Most runners don’t need more data — they need better information. This guide will show you how to keep a journal that’s genuinely useful, not one that becomes another thing to feel guilty about abandoning.

Why bother with a running journal at all?

Your GPS watch already records distance, pace, heart rate, and cadence. So why write anything down?

Because your watch doesn’t know you were up at 5am with a sick kid. It doesn’t know you felt unusually flat the day before an interval session, or that the run you did at 5:45/km actually felt harder than your previous run at 5:30/km. Research published in the International Journal of Sports Physiology and Performance consistently shows that subjective wellness measures — perceived exertion, mood, fatigue — are among the most reliable early indicators of overtraining and injury risk. Numbers alone miss this entirely.

A journal catches what data can’t. It’s the difference between knowing what happened and understanding why.

What to actually log (keep it simple)

The biggest mistake is trying to log everything. You’ll do it for a week, then stop when life gets busy — which it always does.

Aim for five things per session. That’s it:

1. Date and distance — obvious, but essential context
2. Pace or effort — either the actual pace (e.g. 5:50/km) or a 1–10 perceived effort score
3. How it felt — one or two sentences. “Legs felt heavy from the first kilometre” is more useful than “bad run”
4. Notable context — sleep, stress, weather, illness, soreness. One line is enough
5. Any pain or tightness — location, when it started, whether it changed during the run

That’s a 2–3 minute entry, max. If you’re consistently spending 10 minutes per session writing essays, you’ll burn out on it quickly.

Paper vs. digital: which actually works?

Both work. What matters is consistency, not format. Here’s a honest comparison:

The format that you actually use consistently is the right format. If a £3 notebook works, use that. If you’ll only do it in an app, use the app.

How to use your journal to spot patterns

The entries themselves aren’t the point — the patterns are. Set aside 10 minutes at the end of each week to read back through what you wrote. Look for:

• Effort creeping up at the same pace — if your easy run at 6:00/km consistently felt harder in week 6 than week 2, something is accumulating: fatigue, stress, poor recovery
• Soreness that keeps reappearing in the same spot — a recurring note about right calf tightness three sessions in a row is an early warning. Act on it before it becomes a proper injury
• Days where context explains performance — if you always run badly on Thursdays and you always work late on Wednesdays, that’s the answer
• Flat spells — three or four runs in a row where motivation is low and effort feels high can indicate overreaching, not laziness. Your journal will show you that pattern clearly

This is where the journal earns its keep. You’re not just recording what happened — you’re building a personal database that helps you make better decisions. Adjusting training load, adding a rest day, backing off before a minor niggle becomes something more serious.

Using your journal alongside a training plan

If you’re following a structured plan — say, building toward a first half marathon or working through a 12-week half marathon training plan for beginners — your journal becomes a way to track how the plan is actually landing on your body, not just on paper.

Plans are designed for a theoretical runner. You’re a real one. Log how each session felt relative to what it was supposed to be. If week 5’s tempo run was supposed to be at 5:20/km and you ran it at 5:35/km and it still felt like a 9/10 effort, that tells you the plan may be slightly aggressive for your current fitness. You can then choose to repeat the week, adjust the pace target, or add an extra easy day before the next hard session.

If you’re in early training and still building your aerobic base, your journal will also help you confirm whether your easy runs are genuinely easy. The test: could you hold a full conversation at that pace? If not, you’re running easy runs too hard — one of the most common mistakes recreational runners make, and one that’s almost invisible without a journal to reflect on.

What not to bother logging

Some things people log religiously that don’t add much:

• Split-by-split pace data — your watch already has this. You don’t need to rewrite it
• Exact heart rate numbers every session — log trends, not individual readings
• Weight — unless you’re tracking fuelling for ultra or marathon training and have a specific reason, this adds psychological load without much training value
• Every single thought you had during the run — some reflection is good, but a 500-word stream of consciousness for each session isn’t sustainable

The NHS guidance on monitoring health and recovery reinforces the value of listening to your body over time — and a concise journal is simply a structured way to do exactly that.

A simple weekly review template

Here’s a format you can copy and use at the end of each week — takes about 10 minutes:

Week ending: [date]
Total runs: [number]
Total distance: [km or miles]
Best session: [which one, and why it felt good]
Toughest session: [which one, and what made it hard]
Any pain/soreness to watch: [location, severity 1–10]
Overall energy this week: [1–10]
One thing to adjust next week: [specific change — e.g. “move Thursday’s run to Friday to allow more recovery after Wednesday intervals”]

That last line is the most important. A journal is only useful if it changes what you do. If you’re logging everything and never adjusting anything, you’re just collecting information.

The honest takeaway

• Log five things per session, not fifteen. Date, distance, pace or effort, how it felt, and any pain. That’s enough to build a useful picture without burning out on the habit.
• Review weekly, not just daily. Individual runs are often misleading. Patterns across four to six runs tell you something real.
• Use your journal to reality-check your training plan. If a session is consistently harder than it should be at the prescribed pace, that’s data — act on it.
• Don’t obsess over format. A battered notebook works just as well as an app, as long as you actually use it.
• The goal is better decisions, not more records. If your journal isn’t changing how you train at least occasionally, it’s not being used properly. Look for one actionable takeaway per week — even if it’s just “add an easy day before Saturday’s long run.”

Next read: How to build a running training plan from scratch