What's the Difference Between a Training Plan and a Training Log?
by The Next Race
Two tools. Completely different jobs. Constantly confused.
Most triathletes who struggle with their training aren't lacking fitness or motivation. They're using one of these tools when they need the other, or using neither when they need both.
Here's what each one actually does — and why having both changes everything.
The training plan
A training plan lives in the future. It tells you what to do and when to do it. It structures your weeks across a training cycle, allocates load across disciplines, builds in recovery, and sequences intensity so you peak at the right moment.
A good training plan answers the question: given my race date, my current fitness, and my available hours, what is the optimal sequence of sessions between now and race day?
Without a plan, training defaults to whatever feels right on any given day — which tends to mean too hard when you feel good, nothing when you feel tired, and no coherent structure connecting individual sessions to a race outcome. You accumulate fitness erratically rather than building it deliberately.
The plan is the architecture. Every session is a brick. The plan tells you which brick goes where.
The training log
A training log lives in the past. It records what you actually did — the sessions completed, the metrics recorded, the way you felt, the splits you hit. It's the historical record of your training life.
A good training log answers the question: what have I actually done, and what patterns does that reveal?
Without a log, your training history exists only in memory, which is unreliable and selective. You remember the great sessions and the disasters. You don't remember the six consecutive weeks in March where you quietly under-swam. You don't remember that your best race was preceded by an unusually light taper week. The data that would make you a better athlete is there — you just can't access it.
The log is the evidence. Every session recorded is a data point. Over time, the pattern of data points tells a story that memory never could.
Why you need both
The plan without the log is a forecast with no feedback. You build a training structure, execute it, and have no way of knowing whether what you actually did matched what you intended to do — or what effect it had. You can't refine future plans because you have no reliable record of past ones.
The log without the plan is data without direction. You have a detailed record of random training activity. Interesting, perhaps. Not useful for improving performance in a targeted way.
Together, they create a feedback loop. The plan sets the intention. The log records the reality. The gap between the two is where the coaching insight lives — why did I fall short of the planned volume in week six, and what did that cost me in race seven?
Athletes who use both consistently — who plan deliberately and log honestly — improve faster than athletes who do one or neither. Not because they train more, but because they train with more information.
The common mistake
Treating the plan as the log.
This happens when athletes record their planned sessions as completed, or when they adjust the plan retroactively to match what they actually did. The plan becomes a fiction that matches reality, and all the insight that the gap between plan and reality would have provided is lost.
The plan is what you intended. The log is what happened. They are allowed to be different. They're supposed to be different sometimes. That difference is information.
What this looks like in practice
A simple implementation: your plan lives in one place — a structured calendar with sessions, targets, and load built out ahead of time. Your log lives alongside it — the actual sessions recorded as they happen, with real metrics, real conditions, real notes.
Once a week, look at both. What was planned, what happened, and why did they diverge? That weekly review is where most of the learning occurs. It takes ten minutes. It is worth more than most training sessions.
Your future training is built on your past data. The log is how you make that data accessible. The plan is how you use it.