Back to back long days, and when they stop paying

Long run Saturday, longer than you would like. Then up on Sunday morning, on legs that want no part of this, and out again.

Back to back long days. The block everybody swears by, and with good reason: short of running the race itself, it is probably the most specific thing you can do for a long day in the mountains. It is also the block that quietly ends more seasons than any other, because the cost curve turns nasty without much warning.

Why it works

It teaches you to run on tired legs, which is the actual skill. Nobody’s hundred kilometre race is decided in the first thirty. It is decided at hour seven, on legs that are already cooked, when the terrain gets awkward and your form starts to fall apart. You cannot rehearse that in a fresh state. The whole point of Sunday is that you begin it already fatigued, which is the condition you will be racing in.

It also buys you a long time on your feet without one enormous session. Five hours Saturday and three hours Sunday gives you eight hours of specific work. One eight hour run gives you the same total with a deeper hole afterwards and more mechanical stress in a single dose. The split version buys most of the benefit at a lower price.

And Sunday morning is when yesterday’s nutrition strategy submits its report. Under fuel on Saturday and Sunday will tell you, unambiguously. That is a lesson far better learned in February than at kilometre sixty of your race.

There is a fourth, less measurable one. Getting out of the door on Sunday when everything hurts is a rehearsal for the part of the race where you want to stop.

When it stops paying

Back to backs are not linearly better. There is a range where they are the most valuable session in your week, and a point past which the recovery cost grows faster than the adaptation, and every additional one is a withdrawal.

The problem is that the point moves. It depends on your training age, your recent block, your sleep, your life, the terrain, and how much vertical is involved. Anyone who gives you a fixed number is guessing.

What you can do is watch for the signs that you have crossed it.

Sunday is not getting easier across the block. The whole premise is adaptation. If back to back number four feels exactly as grim as number one, you are not adapting to them, you are absorbing them.

Monday and Tuesday are wrecked. A back to back should cost you a day. If it is costing you the first half of the week, every time, then your weekly total is being eaten by a single session and the rest of your training is being sacrificed to it.

Your easy pace at a given heart rate is sliding across the block, not just after each one. Some slide is expected in a big block. A steady one, week on week, that does not recover on the down week, is a different message.

Niggles that show up on Sunday and are still there on Wednesday. Sunday soreness is the price. Sunday soreness that outlives the week is a bill.

Sleep getting worse across the block. Common, easy to attribute to something else, and one of the more reliable indicators that the load has gone past what you are absorbing. This is the one that gives you weeks of warning before your legs make the argument for you. If your back to back block coincides with your sleep sliding and your resting heart rate drifting up, you have your answer, and you did not have to wait for an injury to get it.

The two failure modes

The hero block. Six back to backs in six weeks, because that is what the plan on the internet said. This is the one that produces stress fractures and Achilles problems, and the runner is always surprised, because every individual session was completable. That is the trap. Completing them is not the test, absorbing them is, and there is no in-session feedback that tells you which one you did.

The too easy back to back is the opposite failure and looks nothing like it. Sunday’s run is so short and so gentle that it is not really the second half of anything. Three hours Saturday and forty minutes Sunday is a long run and a jog. There is nothing wrong with that as a week, but it is not the specific stimulus.

A common shape is Sunday being somewhere around half to two thirds of Saturday. The principle is more useful than the ratio: Sunday has to be long enough that the last part of it is genuinely hard work on tired legs.

How to run a block that pays

Put them in blocks with a real break. Two or three back to back weekends, then a proper down weekend. Not a slightly smaller weekend. A genuinely easy one, where the point is to let the adaptation land.

Build the Sunday, not the Saturday. If you are progressing the stimulus, add to the second day first. That is the day doing the specific work. Adding to Saturday mostly adds fatigue.

Match the terrain to the race, and count the descent. If your race has 4000 metres of descending, your back to backs need descending, because the eccentric damage is a large part of what wrecks people late in a mountain race. Descent is also where most of the mechanical cost lives. This is the axis where blocks most often go wrong: runners progress distance carefully and let vertical run away.

Treat the following week as part of the session. If Monday and Tuesday need to be very easy, that is the session’s actual footprint rather than a failure of discipline. Plan it that way instead of being disappointed by it.

And go into them rested enough to do them properly. A back to back off an already dug hole is just a big week with extra steps.

What we cap, and one we got wrong

There is a cap on how much of a jump a long run can take from one week to the next, and back to backs are counted as the pair rather than as two separate runs, because treating Sunday as an independent medium run is exactly how the total sneaks up on you.

The correction: an early version of the plan generator would, under certain race and block combinations, produce back to back weekends with more vertical in the recovery weeks than in the build weeks. Not more distance. More climbing. That is the sort of error that never looks wrong on a calendar, because the distances all descend politely while the thing that actually hurts you goes the other way. It is fixed, and there is now a check that fails rather than shipping a deload that climbs more than the week it is deloading from.

I mention it for the same reason I mentioned the taper bug in another note. These systems are only worth trusting if the people building them will tell you what they found when they went looking.

Watch Sunday getting easier across a block. Watch what Monday and Tuesday cost. Watch your sleep. When those turn, the correct response is a genuinely easy weekend rather than one more heroic one.

Trailwise is not a medical device. Neither is it a replacement for a doctor or a physiotherapist. Trailwise flags what is worth a conversation. It does not diagnose, and it will tell you when it does not know.