Why a Fixed Plan Stops Working, and What Reading Your Logbook Changes

A fixed plan tells you what to do on Tuesday. It cannot tell you whether Tuesday is the Tuesday your body is ready for.

Every session is a dose, and a dose only means something relative to the state it lands on: what you are still carrying from last week, whether the three hardest sessions of the block have all fallen inside the same seven days, and what a missed Thursday did to the run of training behind it. Training response is not a constant, so a schedule obeyed for twelve weeks is answering a question that stopped being true around week four.

None of that is an argument against plans. A plan beats improvising when you are starting out. It is an argument about what a plan has to do once it has met your logbook.

The context

A static plan is a mapping from a position on the calendar to a prescribed dose. Week three, session two, this much. That mapping was a good arrangement: you did not have to think, and thinking was the thing that stopped people training.

What the mapping leaves out is the input. The state you are in on the day is not on the plan anywhere. It lives in your logbook: in how the third session of last week felt, in a week where the hard sessions landed on top of each other. Which is why a plan can be followed exactly and still stop working. Nothing about the plan changed. What changed is the rower on the other end of it.

The core idea

Training response is not a constant, and a plan has no way of finding out where you are on it. Three findings do the work here.

The same session is not the same stimulus. The fitness-and-fatigue model treats every session as two things at once: an impulse that raises fitness and decays slowly, and one that raises fatigue and decays fast. Performance is the difference between the two ([1] Banister 1980). The same work lands differently on a fresh rower and on a tired one, and the plan, which can only write the work, cannot tell which kind of Tuesday it is for.

More is not monotonically better. When six untrained volunteers trained over five weeks, the relationship between daily training and performance was not a straight line but an inverted U ([3] Busso 2003). A dose that would be right in week one can be past the top of your curve in week twelve, and the plan cannot tell which side of the top you are on.

The curve belongs to you. In that same study, a model fitted to each volunteer separately predicted that volunteer's performance better than the same model run on the group's average parameters ([3] Busso 2003). The population average is not the rower, and a plan written from it is a plan written for somebody else.

The three things a fixed plan cannot do

It cannot see how you responded to last week's volume. Consider a week you know: three sessions of thirty minutes at the plan's easy pace, and the third one was a fight, the breathing wrong by the middle and the last five minutes survival. The plan has already written this week and has no field for what happened. That happened in your logbook, and only there if you wrote it down.

The practical way to make it visible is the one the monitoring literature settled on: rate the whole session on a ten-point scale, then multiply by the minutes it took. That product was validated for quantifying training load across both steady-state and interval work, and it needs nothing but a memory and a logbook ([2] Foster 2001). One number per session, comparable week to week, which is the thing a calendar cannot do.

Then read the trend rather than the session. One hard Tuesday means very little. Three Tuesdays in a row at the same effort on the same duration means your fitness has not moved underneath you, or you have not recovered, and the plan's assumption that it has is the thing to doubt.

It cannot notice that the three hardest sessions all landed in the same week. The plan's week four might hold a threshold session, an interval session and a long piece. So does every other week, and that is the point: the plan has already spread them out. Your week four held a deadline at work and a car that needed a garage, so the threshold session moved to Thursday, the intervals to Saturday, and the long piece stayed. Three hard sessions, one week. From the plan's side week four was ordinary and week five was fresh. From yours, the block's load arrived all at once.

The evidence says this bites faster than most people expect. In trained cyclists put on an intensified training block, a state of overreaching could already be induced after seven days of intensified training with limited recovery: maximal power fell, time-trial performance slowed, and perception of effort rose by 8.6 per cent, with nothing changing in substrate, efficiency or lactate ([8] Halson 2002). No single session in that week was too much.

How long the recovery takes is where the honest answer is less tidy. The same group of researchers put the overtraining literature together and found that recovery from overreaching takes about two weeks while overtraining syndrome can take months to years, and they are careful about the edge between them: acute fatigue cannot currently be discerned from overreaching, the continuum may oversimplify, and there is no evidence overreaching necessarily comes first ([7] Halson & Jeukendrup 2004).

The consensus statement on the same subject gives the recipe rather than the timeline: successful training has to involve overload and avoid the combination of excessive overload with inadequate recovery, and none of the available markers currently meet the criteria that would make their use generally accepted ([6] Meeusen 2013).

It cannot adapt when you miss one. You miss Thursday. The plan's Friday is the third hard session of the week, and the plan does not know Thursday happened, so Friday arrives at full size.

What a missed week costs depends on who you are. With less than four weeks of insufficient training stimulus, maximal oxygen uptake and blood volume fall quickly, along with glycogen levels and lactate threshold, in the well-trained, though the same review notes those changes are more moderate in recently trained individuals ([9] Mujika & Padilla 2000). If you are a beginner, the fitness you stand to lose is close to nothing, and what a break costs is continuity. If you have trained hard for years, a week off is a real physiological event.

Either way the plan's instruction is wrong in the same way: it treats the week as a container of sessions rather than as a run of training that a gap interrupts. A missed session is not a paused session.

What the evidence does not settle

What monitoring can and cannot tell you is the honest limit of all of this.

The review usually quoted for practical advice found that very few of the available markers have strong scientific evidence behind them, that there is not yet a single definitive one, and that the importance of individualising load monitoring cannot be over-emphasised. Its advice for designing a monitoring system is that it has to be intuitive and able to report simple, scientifically valid feedback ([5] Halson 2014). That last clause matters for a rower with a logbook: a system that is hard to use does not get used, and an unused system measures nothing.

One result runs against the intuition that the objective measurement should win. In a systematic review of monitoring methods, subjective and objective measures generally did not correlate, and the subjective measures reflected both acute and chronic training load with better sensitivity and consistency than the objective ones ([11] Saw 2016). How hard the session felt, and how the week has felt, is not a soft substitute for a sensor. It is a different signal, and it resolves more.

And there is one trial in which adapting beat prescribing, the closest thing to a direct test of the whole idea. Forty recreational endurance runners were assigned either a heart-rate-variability-guided prescription or a conventional one for an eight-week intensive block. The guided group completed significantly fewer moderate and hard sessions, 13.2 against 17.7 on average, and improved its 3000 m running time significantly, by 2.1 per cent, where the conventional group's gain of 1.1 per cent was not significant ([4] Vesterinen 2016). Same idea, less total work, a better result.

Three limits on that. The runners were runners, on a treadmill, and the signal was morning heart rate variability, which an indoor rower usually does not have. The trial is one trial of forty people. And it is not evidence that any particular coach beats any other one. It is evidence that changing the prescription to fit what the athlete is showing is not a worse use of a training week than following a fixed one.

The how-to

1. Log the effort of every session, not just the result. Session rating of perceived exertion multiplied by the minutes it took is the load product validated for tracking training across steady and interval work, and the one thing a logbook produces without a sensor ([2] Foster 2001).

2. Track the rolling average, not the single session. One hard Tuesday is weather. A week of the same session at the same effort is a finding, and it is the finding the plan cannot make for you.

3. When you have to cut something, cut volume before intensity. Eighteen experienced rowers trained for twelve weeks either entirely at or below lactate threshold or on a mixture of threshold and above-threshold work, and the 2000 m time and maximal oxygen uptake improved by the same magnitude in both groups ([10] Ingham 2008). The mixed sessions were not doing work the easy ones were not. Keeping the hard session and shortening the easy one is a defensible trade. The reverse is not.

4. Count the hard sessions in a rolling seven days, not in a calendar week. Three is a cluster. If this week has already produced two, the third is the one to move.

5. Treat a missed week as a week. Do not resume at the session the plan had in store. Re-enter at the point your actual fitness is and build back from there.

6. Tell your coach the things the logbook cannot show. The coach reads your logged sessions, your goal and your load trend, and weighs them against what you have told it in chat. It does not know you slept four hours, that your back is sore, or that work has been eating your week — those are inputs you bring back through chat, and the synthesis only works when both sides share them. What it reads is set out in how MyNextRow reads your logbook; how the data behind it is handled is covered by our privacy notice.

The trade-offs

Two honest limits.

First, almost none of this literature is about indoor rowers: the fitness-and-fatigue model comes from swimmers, the dose-response work from six untrained volunteers, the overreaching studies from trained cyclists, and the adaptive-prescription trial from runners. The mechanism is sport-agnostic, which is why this article argues about what a plan can and cannot see rather than what a rower should be prescribed.

Second, a static plan is not the villain. For someone doing three sessions a week in their first year, a plan is better than improvising, and the rowing trial above is a reason to keep structure rather than chase novelty. The failure mode is the plan's refusal to be adjusted once it has met your logbook.

What to do tomorrow

Open your logbook and write down two numbers for each of your last five sessions: the minutes, and the effort on a ten-point scale. Multiply the two and you have a load number you can compare across weeks. Then count the hard sessions in a rolling seven days rather than a calendar week, and if the answer is three, the next one is the one to move. And when you miss a week, re-enter rather than resuming at the session the plan had in store.