Running Training Log: What to Track Beyond Distance and Pace

Open any running app and it will tell you two things about the run you just did: how far and how fast. Both are facts. Neither one tells you whether the run was any good.

Eight-minute miles on a flat loop in October and eight-minute miles up a hill in August heat are two entirely different sessions with identical numbers. A log that records only distance and pace will let you conclude you have not improved in a year when you have improved a great deal, or that you are flying when you are actually starting to dig a hole.

Why pace lies

Pace is an output. It is the result of your effort, filtered through terrain, gradient, heat, humidity, wind, surface, altitude, sleep, and how long ago you ate. Change any of those and the same physiological effort produces a different number.

The constant underneath is effort. Which is why the single most valuable thing you can add to your log is a one-to-ten rating recorded within a few minutes of finishing, before your memory starts rounding it toward how you wish it had gone. Effort plus pace tells a story neither one tells alone. Same pace, lower effort, over six weeks: that is fitness. Same pace, rising effort: that is fatigue, and it is a warning worth listening to.

The full list worth recording

Not all of this every time. The first two are non-negotiable and the rest are situational.

• Duration and effort. Time on feet is a truer training-load measure than distance, particularly on hills and trails where distance systematically understates the work.
• Route and surface. Road, trail, track, treadmill. It contextualises everything else and it matters for injury patterns.
• Elevation gain. The number that explains most "why was that so hard" days.
• Heart rate, and specifically its drift. If your heart rate climbs steadily through a run at constant pace, you are running beyond your aerobic capacity for that duration. A stable heart rate at a given pace across a run is a strong aerobic sign.
• Cadence. Useful mostly as a personal baseline. A sudden drop often means fatigue or a compensation you have not consciously noticed.
• Weather. One word. Heat and wind are worth ten to thirty seconds a mile and you will not remember which day was which.
• Shoes. More on this below, because it is the tracking that most often prevents an actual injury.
• How you felt the next morning. One line. This is the highest-value and least-recorded piece of data in endurance training.

Most runners run their easy runs too hard

If there is one pattern a decent log exposes, it is this. The majority of recreational runners spend most of their weekly volume in a moderate middle zone: too hard to recover from properly, too easy to drive real adaptation. It feels productive. It is the most common reason people plateau while training more.

Your log will show it. If the effort rating on your easy days is a 6 or 7 rather than a 3 or 4, and your hard days are also landing at 7 because you arrive tired, everything has collapsed into one zone. The fix is uncomfortable and simple: make the easy days genuinely, boringly easy, and you will find the hard days have another gear you had forgotten about.

Build volume gradually, and define volume by time

The old guidance about not increasing weekly mileage by more than roughly ten percent is a rough rule rather than a law, and it is often quoted more precisely than the evidence supports. What holds up is the principle: consistent, gradual increases beat aggressive jumps, and the injuries cluster right after the jumps.

Two refinements. Measure the build in time, not miles, especially if your terrain varies. And plan a lighter week roughly every fourth week rather than climbing until something makes the decision for you.

Track your shoe mileage. Seriously.

Foam loses its cushioning properties long before the upper looks worn, and the usual guidance falls somewhere in the range of three hundred to five hundred miles depending on the shoe, the surface, and the runner. The exact number matters less than the fact that almost nobody tracks it, and then wonders why their knees started complaining in a shoe that "still looks fine."

If you rotate two pairs, log which one you wore. When niggles show up in your notes, the shoe column is one of the first things worth checking.

The things that are running load but do not look like it

Strength sessions, cycling, a physical job, a heavy week of practices in another sport, and a long day on your feet all draw from the same recovery budget. A runner whose log contains only runs will keep concluding their easy 5k caused an injury, when in fact it was the fourth training session in three days.

This is the argument for keeping running in the same log as everything else you do. The events that break runners are usually visible only when the whole week is in one view.

Rehearse the race, and log the rehearsals

Every race-day variable should be tested in training and written down: what you ate and how long before, what you drank and how much, which shoes, which socks, the warm-up, the pacing plan. Then log the outcome honestly, including gut issues, which is where most first-time distance races are lost. On race morning you should be executing a plan you have already run, not experimenting.

The monthly review

Fifteen minutes at the end of each month, with four questions. How many sessions did I actually do compared to what I planned? Is my effort at a given pace trending down or up? Which niggles appear more than once in my notes? And what changed in the week before each one?

That fourth question is the one that saves seasons. Injuries almost never arrive without a trail: a jump in volume, a new shoe, a week of terrible sleep, a surface change. The trail is only visible if somebody wrote it down.

FAQ