You have been keeping a training log. You write down your numbers after every ride. Maybe you note the RPE, the sleep score, the mood. Maybe you even do it consistently, which puts you ahead of most riders already.
And it is sitting there. Unused. A graveyard of data that has never once changed a decision you made about your training.
I know because I have had this conversation with hundreds of riders across 1,400-plus podcast episodes. The pattern is always the same. They record diligently. They review rarely. And when they do review, they look at the data, nod vaguely, and carry on doing whatever they were going to do anyway.
The problem is not the recording. We have covered what to record elsewhere on this site, and the truth is most riders are already capturing enough data. The problem is the gap between having information and using information. A training diary that does not change decisions is a filing cabinet. A training diary that changes decisions is a performance tool.
This post is about the second one.
The Difference Between Recording and Deciding
Here is a question that separates useful diaries from decorative ones: when was the last time your diary told you to do something different from what you had planned?
Not a vague feeling that you should probably ease off. A specific moment where you looked at your notes, saw a pattern, and changed next week's training because of it. Moved a session. Dropped a day. Added recovery. Swapped an interval session for endurance work. Changed the plan based on evidence rather than impulse or guilt.
If you cannot point to a specific instance, your diary is a log, not a decision-making system. And the distinction matters because training is not about executing a plan perfectly. It is about adapting the plan to what your body is actually doing, which is rarely what you assumed it would be doing when you wrote the plan four weeks ago.
Joe Friel talks about this constantly. He has said on the podcast and in his books that the plan is a hypothesis. You write it based on your best understanding of what your body needs. Then reality happens — you sleep badly on Tuesday, work blows up on Wednesday, your knee aches on Thursday — and the plan needs to respond. The diary is where reality meets the hypothesis. If you are not reading it with the intention of adjusting the hypothesis, you are just doing admin.
Pattern Recognition: Where the Real Value Lives
Session-level analysis is useful but limited. You finish a ride, note that it was harder than expected, write down your RPE, and move on. That tells you something about today. It tells you almost nothing about why.
The real value of a training diary appears at the weekly and monthly level, when patterns emerge that no single session can reveal. And finding those patterns is a specific skill — one you can practise.
Day-of-Week Correlations
This is the first thing to look for and the one that catches the most riders off guard. Go through three or four weeks of diary entries and highlight the sessions that went badly. Not the ones where you were tired but completed the work. The ones that properly fell apart — power targets missed, RPE through the roof, sessions cut short.
Now look at what day they fall on.
I have seen this dozens of times in conversations with coaches. A rider says their Thursday sessions are always rubbish. They assume it means they are not fit enough for the Thursday workout. They push harder on Thursday. It gets worse.
The actual problem is Wednesday. Maybe Wednesday has a group ride that is supposed to be easy but never is. Maybe Wednesday is a long day at work with no proper lunch. Maybe Tuesday's session is harder than they think and the recovery window to Thursday is not long enough. The Thursday session is the symptom. Wednesday is the disease. And you will never see that in a single Thursday post-ride note. You see it in four weeks of Thursday post-ride notes sitting next to four weeks of Wednesday context.
The RPE Drift Pattern
When the same session at the same power output produces gradually rising RPE over three or four weeks, something is accumulating. Not acute fatigue — you would feel that immediately. Chronic fatigue, the kind that builds so slowly you do not notice it until you are already in a hole.
Track this by writing your RPE next to the prescribed power for your key sessions. A sweet spot session at 88% of FTP that felt like a 6 in week one, a 7 in week two, and an 8 in week three is not a fitness problem. It is a recovery debt. The power has not changed. Your capacity to produce it has. And if you are only looking at the power number, you will miss it completely because the power number looks fine.
Tim Cusick, who built WKO5 and has coached riders at every level, calls this the "hiding in plain sight" problem. The athlete is completing the work, hitting the numbers, ticking the boxes. But the subjective cost of hitting those numbers is climbing week on week, and that cost is the leading indicator of overreaching. By the time the power drops, you are already deep in it.
Session-Type Patterns
Some riders consistently fail at one type of session but perform well at others. They smash their endurance rides. Their tempo is solid. And every VO2max interval session is a disaster.
The obvious conclusion is that they are bad at VO2max work. The diary conclusion might be completely different. Maybe their VO2max session is always scheduled the day after their longest ride. Maybe they eat differently before high-intensity work. Maybe they do VO2max sessions in the evening after a full day, but their endurance rides are early morning when they are fresh.
The session type is not the variable. The conditions around the session type are. And your diary, if you have been recording context as well as numbers, contains the answer.
Decision Frameworks: When to Change the Plan
Spotting patterns is step one. Knowing what to do about them is step two. Here are three frameworks that turn pattern recognition into actual decisions.
The Performance Manager Concept — Applied Practically
Joe Friel's Performance Manager Chart — built on the TSS, CTL, ATL, and TSB framework from Andrew Coggan and Hunter Allen — is the standard tool for managing training load over time. Most riders have seen it in TrainingPeaks. CTL is your chronic training load, a proxy for fitness. ATL is acute training load, a proxy for fatigue. TSB is the difference, a proxy for form.
In theory, you train to build CTL, manage ATL so it does not overwhelm you, and peak by letting TSB rise before an event.
In practice, the Performance Manager Chart lies to you regularly unless your diary keeps it honest.
Here is the scenario I see constantly: a rider's TSB is positive, which means they should be fresh. But their diary says they have slept five hours a night for a week because their kid is ill. The Performance Manager Chart does not know about the kid. It sees reduced training, calculates reduced fatigue, and says you are ready to go. Your diary says you are shattered. Believe the diary.
The reverse is also true. TSB is negative, suggesting fatigue. But the rider has slept brilliantly, eaten well, taken two rest days, and their morning resting heart rate is the lowest it has been in a month. The chart says be careful. The diary says you are ready for a hard session. Again, believe the diary.
The Performance Manager Chart is a model. Models simplify reality. Your diary fills in the details the model leaves out.
The Three-Question Weekly Review
Every Sunday, five minutes, three questions. This is the single highest-value habit you can build around your training diary.
What went well this week? Not just the numbers. Which sessions felt good? Where did your body cooperate? What conditions produced your best work? Be specific. "Thursday's VO2max session was the best I have done in a month — slept 8 hours, ate properly at lunch, left work on time" is useful. "Had some good rides" is not.
What did not go well? Same specificity. Which sessions fell apart? Where did you miss targets? What was happening around those sessions? Look for the context, not just the outcome. "Saturday's long ride bonked at hour three — had toast for breakfast instead of proper fuelling, started 30 minutes later than planned and rode through the hottest part of the day" tells you exactly what to fix.
What changes next week? This is the question that turns the review from reflection into action. Based on what you have learned, name one or two specific adjustments. Move the VO2max session to follow a rest day. Prepare food the night before the long ride. Protect Wednesday evening sleep. Whatever the patterns say, commit to one change and see if it helps.
If you do nothing else from this post, do this. Five minutes. Three questions. Every Sunday. In six weeks you will know more about how your body responds to training than you learned in the previous six months.
End-of-Block Reviews: The Twenty-Minute Audit
At the end of each training block — typically every three or four weeks — sit down for a proper review. Not five minutes. Twenty minutes. Coffee, diary in front of you, honest assessment.
The question this review answers is simple: did this block produce the adaptation I was targeting?
If the block was a base phase, has your aerobic efficiency improved? Is your heart rate lower at the same power? Is your aerobic decoupling better on long rides?
If it was a build phase, have your interval powers increased? Are you hitting higher peaks in your VO2max sessions? Has your FTP moved?
If yes, carry on. The plan is working.
If no, the diary should tell you why. Was compliance the issue — did you actually do the sessions as prescribed? Was recovery the issue — did accumulated fatigue prevent you from hitting targets in the second half of the block? Was life the issue — did work or family disruption mean the block never really got going?
Each of those causes leads to a different adjustment in the next block. Poor compliance needs a simpler plan. Poor recovery needs more rest days or lower volume. Life disruption might mean the timing was wrong or the block needs to be extended. Without the diary, you are guessing. With it, you have evidence.
The Masters-Specific Angle: Recovery Becomes the Main Character
Everything above applies to every cyclist. But if you are over 40, one shift changes the emphasis of your entire diary practice: recovery tracking moves from supporting detail to the main event.
The physiology is clear and well-documented. As you age, the rate of muscle protein synthesis after training slows. Connective tissue takes longer to repair. Sleep architecture changes. Hormonal recovery from hard efforts is less efficient. None of this means you cannot train hard. It means the gap between hard sessions needs to be wider, and your diary is the tool that tells you whether the gap is wide enough.
Phil Burt, who ran the bike fit and injury prevention programme at British Cycling during their most successful Olympic period, has talked about this on the podcast. The key difference he sees in masters athletes is not that they cannot produce the power. It is that the consequences of under-recovering are more severe and more permanent. A 25-year-old who pushes through fatigue gets tired. A 50-year-old who pushes through fatigue gets injured. The margin for error shrinks, and the diary is what keeps you inside it.
What this means practically: your diary entries about how you feel the morning after a hard session, how long it takes for joint soreness to clear, whether your resting heart rate returns to baseline within 24 or 48 hours — these become the entries you pay most attention to. The power numbers are still useful. But the recovery narrative is where the actionable information lives.
If you notice that your resting heart rate takes three days to return to baseline after a hard interval session instead of the two days it took a year ago, that is not a fitness decline. That is information. It means you need a three-day gap between hard sessions now, not two. And if your plan still has two hard sessions with two days between them, the plan needs to change. The diary told you. Listen to it.
Making the Diary a Conversation
A diary that only you read has a ceiling. Not because your observations are wrong, but because you have blind spots that are invisible to you precisely because they are yours.
The most effective thing you can do with a well-kept diary is share it. With a coach, obviously — a coach reading your diary alongside your training data can spot mismatches between what you think is happening and what is actually happening in about thirty seconds. But also with a training partner who knows your goals and your history.
Stephen Seiler, the endurance physiology researcher, has made the point that one of the underrated benefits of coaching is not the programme design. It is the regular structured conversation about how training is going. The check-in forces you to articulate what you are feeling, and the act of articulating it often reveals things you had not consciously registered.
You can replicate that without paying for coaching. A weekly five-minute conversation with a training partner where you each share your three-question review is remarkably effective. They will ask questions you would not ask yourself. They will notice patterns you have normalised. And the social commitment to doing the review means you actually do it, which is half the battle.
In the Roadman community, we see this regularly. Riders who share their weekly reviews with the group get better feedback and make better decisions than riders who keep their diaries private. Not because the group has secret knowledge, but because twenty pairs of eyes see things that one pair misses.
What a Useful Diary Entry Actually Looks Like
This is not about what to record — we have covered that in the training log guide. This is about what a diary entry looks like when it is built for decision-making rather than record-keeping.
A record-keeping entry: "Tuesday. Sweet spot intervals, 3x15min at 270w. Completed. RPE 7. Slept 6.5 hours."
A decision-making entry: "Tuesday. Sweet spot intervals, 3x15min at 270w. Completed but the third interval was significantly harder than the first two — RPE climbed from 6 to 8 across the set. This is the third week in a row this has happened. Sleep was 6.5 hours again. The Monday group ride was harder than intended — averaged 210w vs planned 180w. Pattern: the Monday ride is eating into Tuesday's session. Action: drop Monday to solo Z2 next week and see if Tuesday improves."
Same ride. Same data. Completely different value. The second entry identifies a pattern, proposes a cause, and commits to a test. That is a diary functioning as a decision-making system.
The Cost of Not Using Your Data
Here is the uncomfortable truth. You are already doing most of the work. You are training consistently. You are recording data. You have the raw material for significantly better decisions sitting in your TrainingPeaks comments, your Strava notes, your spreadsheet, your notebook.
The gap between where you are and where you could be is not more training. It is not a new power meter or a different interval protocol. It is the twenty minutes per week it takes to actually read what you have written, find the patterns, and change something based on what you find.
That is the cheapest, most effective performance gain available to any cyclist at any level. It costs nothing. It requires no new equipment. It takes less time than the post-ride coffee you are already having.
Stop filing your data. Start using it.
If you want a community of riders who actually review their training together and hold each other accountable, that is exactly what happens inside the Roadman Cycling community on Skool. Weekly reviews, shared diaries, honest feedback from riders who understand the work. Come have a look.