Back-to-Back Long Runs: How to Use Them Without Getting Hurt

How back-to-back long runs work, the day-two duration ratio that keeps them safe, how often to schedule them across a build, and why they teach something a single very long run can't.

Gianluca Belloni 5 min read

The short answer

Back-to-back long runs are two long training runs on consecutive days, used to teach your body to keep moving well on already-fatigued legs - the core skill of ultrarunning. Keep the second day at 40-50% of the first day's duration and run it easy, schedule three to five across a build spaced at least three to four weeks apart, and use them only once you have a solid weekly volume base, not as a substitute for one.

Key takeaways

  • The purpose is fatigue exposure, not extra volume. Day two should feel noticeably harder than its short duration suggests, because you're starting it already tired.
  • Keep day two at 40-50% of day one's duration and genuinely easy. Making it long or hard defeats the point and adds injury risk for no extra benefit.
  • Three to five back-to-back weekends across a build is plenty. More than that compounds fatigue faster than most runners recover from it.
  • A back-to-back is not a substitute for one very long run - each teaches something the other doesn't, and a full build usually needs both.
  • Don't start using them until you have a genuine weekly volume base. They compound an already-inadequate base rather than fixing it.

Ask most first-time ultra runners what worries them about race day and they'll describe the distance. Ask anyone who has actually finished one and they'll usually describe a specific hour - late in the race, legs already wrecked, still needing to move well for several more hours. That hour is what a back-to-back long run trains, and it's the closest thing to genuine race rehearsal you can build into a normal training week.

What it actually trains

A single long run, however long, only ever asks your body to perform on fresh-that-morning legs. An ultra never does that past the first hour.

Running a second long effort the day after the first means starting with glycogen stores that never fully refilled, muscle fibres already carrying eccentric damage from yesterday's descents, and a nervous system that has to find efficient movement patterns despite all of it. That combination - not distance, not elevation - is the actual skill ultrarunning demands, and it's very hard to train any other way.

It also rehearses something less physical and just as important: what your own fatigue actually feels like, and that it's survivable. Runners who've never run tired on purpose tend to catastrophise the first real bad patch in a race. Runners who've done it in training recognise it, and keep moving.

The ratio that keeps it safe

Keep day two at 40-50% of day one's duration, and run it genuinely easy.

A 3:00 long run on Saturday pairs with a 1:15-1:30 easy run on Sunday - not another long run, not a hard effort, just enough time on tired legs to get the adaptation without turning the weekend into an overreach.

The temptation, especially as a build progresses and confidence grows, is to push day two longer or faster "because it felt okay." Resist it. The stimulus you're after happens in roughly the first 45-90 minutes of day two, when your legs are working out how to move well despite yesterday. Extending day two well past that doesn't add much training effect - it mostly just adds recovery cost you'll pay for later in the week.

Day oneDay twoRatio
2:000:50-1:00~45%
3:001:15-1:30~45%
4:001:45-2:00~45%

How often, and when

Three to five back-to-back weekends across a full build is plenty, spaced at least three to four weeks apart so you fully absorb one before attempting the next. Stacking them more frequently compounds fatigue faster than most runners' recovery can keep up with, and it's one of the more reliable routes to an overuse injury in a build - tired tissue doing eccentric work is exactly the combination that produces tendon and bone-stress problems.

Don't start them until you have a genuine base. If your current weekly volume doesn't comfortably include one long run already, a back-to-back weekend is compounding an inadequate base rather than fixing it. The first 50K training plan places the first back-to-back around week seven of a sixteen-week build, once foundation and terrain work are established - that timing isn't arbitrary.

They matter more as the target distance grows. A 50K rarely needs more than three or four back-to-back weekends in a build. A 50 mile or 100K, where the race itself will ask your body to move for twelve, eighteen, or twenty-four hours straight, benefits from more deliberate exposure to compounding fatigue, and from occasionally running day two later in the day to rehearse the timing your race will actually demand.

What a good back-to-back weekend looks like

Day one: your normal long run - full length, race-relevant terrain, full fueling rehearsal, deliberate descending if your race has it.

Between the two runs: eat a real meal with carbohydrate and protein within the first couple of hours, get off your feet, and don't treat the evening as a chance to "bank" extra activity. Sleep is doing more of the adaptation work here than almost anything else you can do.

Day two: easy, on softer terrain if you have the option - legs are already carrying eccentric damage from yesterday, and a second dose of hard descending on top of that is where the injury risk actually concentrates. Fuel this run too, even though it's short. Skipping fueling on day two "because it's only ninety minutes" undermines the point, which is teaching your gut and your legs to work while depleted.

I had an athlete building for a mountain 100K two seasons ago whose recurring problem, in three previous ultras, was a specific collapse around the seventy-kilometre mark - not injury, just a total loss of drive and pace that she couldn't explain from her fitness numbers. We built four real back-to-back weekends into her block, the last one deliberately timed so day two started in the evening, mimicking where that seventy-kilometre mark would fall on race day. She told me afterward that the moment in her actual race that always broke her arrived on schedule - and for the first time, didn't. She recognised the feeling, expected it, and kept moving. That's the entire value of the session in one result.

Not a replacement for one very long run

Back-to-backs and a single very long run train genuinely different things, and a full ultra build usually wants both rather than one instead of the other.

A single long run teaches sustained pacing, fueling over many continuous hours, and mental persistence within one effort. A back-to-back teaches recovery-and-repeat - the specific skill of performing again after incomplete recovery, which is what every ultra actually demands past the first checkpoint.

Neither substitutes for base volume. Both assume you already have it.

The mistakes

  1. Making day two long or hard. The stimulus lives in the first hour of tired-legs running. Past that you're mostly adding fatigue, not training effect.
  2. Doing them too often. More than about five across a build, or closer together than three to four weeks, tends to produce accumulating fatigue rather than accumulating fitness.
  3. Skipping fueling on day two because it's short. The depleted-gut rehearsal is part of the point.
  4. Using them before you have a base. They amplify an inadequate foundation rather than building one.
  5. Choosing the same easy terrain for both days. If day one doesn't include real descending, you're not rehearsing the damage your race will actually cause.
  6. Ignoring what happens between the two runs. Sleep and a proper meal do more of the adaptation than the runs themselves.

If a back-to-back weekend keeps producing the same breakdown point every time, that's usually a fitness or fueling gap worth diagnosing properly rather than training through repeatedly - the kind of pattern 1:1 coaching exists to catch.

Frequently asked questions

What is a back-to-back long run?
Two long training runs on consecutive days, used to teach your body to move well on already-fatigued legs. It's a core ultra-training tool because it rehearses the actual demand of racing - performing again with incomplete recovery - far better than any single long run can.
How often should I do back-to-back long runs?
Three to five times across a full training build, spaced at least three to four weeks apart. More frequent than that tends to compound fatigue faster than most runners can recover from it, raising injury risk without adding proportional benefit.
How long should the second day of a back-to-back be?
Roughly 40-50% of the first day's duration, run genuinely easy. A 3:00 long run on Saturday pairs well with a 1:15-1:30 easy run on Sunday. The training stimulus happens mostly in the first 45-90 minutes of tired-legs running; extending day two much further adds recovery cost without much extra benefit.
Are back-to-back long runs better than one very long run?
They train different things, not a strictly better or worse version of the same thing. A single long run builds sustained pacing and fueling over continuous hours; a back-to-back builds the specific skill of performing again after incomplete recovery. A full ultra build typically benefits from both.
Can beginners do back-to-back long runs?
Only once they have a genuine weekly volume base, including a comfortable single long run already. Attempting back-to-backs before that base exists compounds an inadequate foundation rather than fixing it, and meaningfully raises injury risk.

About the author

Gianluca Belloni - Level 1 Trail Running Coach (CONI-recognised), based in Lecco, Italy.

I coach trail and ultra runners from first 50Ks to hundred-mile finishes, and I write these guides the way I'd explain them to an athlete. More about me.

Want this applied to your training?

Articles give you the framework. Coaching bends it around your week, your terrain, and your race. The intro call is free and low-pressure.