Adaptive vs. Static Training Plans: Why the PDF on Your Fridge Stops Working

I printed a plan once and put it on the fridge. It survived until the Sunday I missed, a headwind that turned an easy 12 into something else, and a night that was not sleep. The paper still said 8×800. I ran it tired. I got very little back.

Most running plans are a week someone else already had. They are written for an average runner in an average week, which is a person who does not exist. The plan is correct the day you download it. Then the week happens.

What the paper cannot see

Miss a run and a fixed plan has no next sentence. You either drop the session and feel like you failed a receipt, or you cram it in and dig a hole. I have done both. Neither one gave me the workout back.

You are wrecked on a quality day. Bad sleep, a week that was already loud, a calf that is not an injury yet and not nothing. The PDF does not know. It still wants the intervals. You can complete them and absorb almost none of it.

You get fitter, or you do not. The paces were set on day one from a race, a guess, or a hope. Six weeks later they are wrong in one direction or the other, and the sheet cannot tell the difference.

The performance-manager idea, the one people shorthand as fitness, fatigue, and the balance between them, is useful here only as a picture. Training raises both. The useful signal is not the kilometres on the page. It is whether the fatigue from what you actually did is still sitting on top of the next hard day. I will not pretend that balance is a number I can read off a fridge. Carl Foster's session-RPE is the version I can use on a Tuesday: how hard the session felt, times how long you were out. A "slow" run into a Dutch headwind can be a harder day than the split suggests. The paper never asks. (Foster et al., 2001, Journal of Strength and Conditioning Research)

What I mean by adaptive

An adaptive plan changes the schedule because of what is true today, not because you edited a cell.

Readiness goes in. Sleep, soreness, how much you want to be there, resting heart rate if you have it, the stress of the recent training. Low readiness and the plan should offer recovery, a hold, or a cut, before "just get it done" becomes the week you stop. That is a coaching judgment sitting on signals, not a diagnosis.

Miss a session and the rest of the week gets rebalanced. The kilometres are not a debt. Doubling up to feel caught up is how easy days stop being easy.

Pace drift is the quieter one. Consistently faster or slower than the target, and the ranges should move toward the fitness you are showing, not the number you started with. One good day is not a new VDOT. A pattern is.

Static plans are simple, and for a runner with a stable week and a modest goal they can be enough. I have used them. They earn less when the life is messy, the goal is a long one, or you have already been hurt by treating a bad morning as a character test.

What Runapt does with that

Runapt builds the plan from your VDOT and the goal, then rewrites the week you are in: readiness before a session that no longer fits, a missed run that does not become two, paces that get re-anchored when the evidence is a pattern. Notes after the run say why, in plain language, so you are not guessing which part of the week moved.

You can see the next week react to the week you had, including the one the wind won. That is the difference between a schedule and something that has looked at you.

If you want to watch a plan move after a real week, not an imaginary one, build the first week free. How that sits next to routes and paces is on features. The short version of how the plan is built in the first place is the plan builder.

Sources

Foster, C., Florhaug, J. A., Franklin, J., Gottschall, L., Hrovatin, L. A., Parker, S., Doleshal, P., & Dodge, C. (2001). A new approach to monitoring exercise training. Journal of Strength and Conditioning Research, 15(1), 109–115. https://doi.org/10.1519/00124278-200102000-00019