The long run trains four things at once, and it's worth being specific about them: aerobic capacity (the engine that lets you process oxygen for hours), mental endurance (the part of you that has to keep going when the run stops being interesting), fueling practice (gels, fluids, what your stomach tolerates after two hours), and time on feet at a sub-marathon effort that teaches your legs to keep firing when they're tired. This guide is for recreational marathoners somewhere between “my longest is 8 miles” and “my longest is 18 miles” who want to build to marathon distance without breaking. This is not elite training material, and it is not a starting plan for someone who ran twice last month. What it can do is give you a framework for safe progression. What it cannot do is read your body week to week. The long run is the most important workout in a marathon block, and the easiest one to get wrong.
The Kenyan view on the long run
In the Rift Valley, where most of the camp's long runs happen, the road climbs and falls over packed dirt above 7,500 feet, and the air gives back less oxygen than what you're used to. The long run is run as a group, and the group sets the rule that nobody breaks: the first half is slower than the second. That's not a slogan. It's the discipline. The runners who win marathons here learned how to walk before they ran (pole pole, slowly slowly), and the long run is where that lesson is repeated every Sunday.
“If you finish the long run thinking ‘that was easy, I had more in me,’ good. That is the run. The day you finish proud of how fast you went, you've lost three days of training to recovery you didn't need.”
— Coach Martin Karoki Muriuki
Western marathon plans tend to treat the long run as a distance to be conquered. The Kenyan view is the opposite: the long run is a controlled aerobic exposure. You are not proving anything. You are building the system that will let you race twelve weeks from now. The temptation to “race” the long run (to chase a pace, to feel strong by mile ten, to push the last three miles because you've got the legs) is a common way recreational marathon blocks fall apart.
Long run progression by current distance
The honest way to think about progression is not in weeks but in where you currently are. A runner whose longest run is 9 miles and a runner whose longest is 18 miles are in completely different physiological territory, and the advice that fits one will hurt the other. Find your current bracket and work from there.
From 8 miles → 12 miles · still building base
Where you are: You've been running consistently for at least eight to twelve weeks. You can finish 8 miles without walking. Your weekly mileage is probably somewhere in the 20 to 30 mile range, and the long run is the longest single thing you do.
Progression rate: Add roughly a mile every one to two weeks. Some weeks the jump is half a mile. Some weeks you repeat. There is no exact number. The right rate is the one your body absorbs without the day-after feeling like punishment. Over time, you are adding about 8 to 12 minutes a week, not 20.
Effort: Easy enough that the run is boring. If you have a heart rate monitor, you are in the lower aerobic range, but the better signal is that you could hold a conversation in full sentences the whole way.
What often goes wrong here: Runners at this stage haven't yet built the connective-tissue durability (tendons, ligaments, joint cartilage) that catches up to aerobic fitness more slowly. The lungs feel fine well before the Achilles, the knees, and the hips are ready. The failure mode is jumping from 9 to 12 in one week because the run "felt easy." It felt easy because your cardiovascular system was ready. The rest of you wasn't.
From 12 miles → 16 miles · building toward marathon-specific
Where you are: You've held a 12-mile long run for at least two or three weekends without unusual soreness. Weekly mileage is settling somewhere around 30 to 40. You're starting to think about fueling on the run: gels, fluids, something solid before you head out.
Progression rate: Still about one mile every one to two weeks, but now the time on feet matters more than the mileage number. A 14-mile run at easy effort is well over two hours for most recreational runners. That two-hour mark is where fueling stops being optional and where your form starts revealing itself.
Effort: Same easy aerobic effort. The temptation to push starts here because you feel like a real marathoner. Resist it. This is the bracket where pace inserts can begin to be useful, but only at the end, only short, and only on a run that started easy.
What often goes wrong here: Skipping cutback weeks. Every third or fourth week, the long run should come back down by about 25 to 30 percent. Runners who don't cut back accumulate fatigue invisibly. The signal that you skipped one is the long run four weeks from now feeling impossibly hard for no obvious reason.
From 16 miles → 20 miles · the peak block, most marathon-ready territory
Where you are: This is the bracket where most recreational marathon plans live. Weekly mileage in the 40 to 55 range. You've fueled mid-run multiple times. The long run is a significant Sunday event that affects what you can do on Monday and Tuesday.
Progression rate: Slower now. Jumps of one mile every two weeks, with a real cutback week every third week. Some runners do well topping out at 18 miles. Some need to see 20 once before race day. There is not a universal answer, and anyone who tells you there is hasn't coached enough runners.
Effort: This is where the Kenyan negative-split discipline pays. First half slower than the second half. If you can hit 20 miles having spent the first 10 at a properly restrained effort, the back half teaches you something about marathon pacing that no track session can.
What often goes wrong here: Going for 20 too early in the block, before the body has progressed through 16, 17, 18. The 20-miler is a checkpoint, not a launchpad. The other failure is running 20 miles at race pace because a pace chart said you should. That is a race, not a long run, and the cost in recovery is roughly a week of training.
From 20 miles → 22 miles · only for runners with deep history
Where you are: You've run marathons before. Weekly mileage is 55+, sustained for months. Your body has a long-run history measured in years, not weeks. You are not trying this because the internet said elite runners do 22-milers. You are doing it because you have a specific reason: a hilly race, a goal time you've been close to, a known weakness in the final hour.
Progression rate: This bracket is barely a progression. It is one or two attempts at 21 or 22 miles in a full block, on perfect days, with a full week of recovery built around them.
Effort: Conservative throughout. The risk-to-reward at 22 miles is unfavorable for most recreational runners. The additional aerobic benefit over a well-executed 20-miler is small. The injury and fatigue cost can be large.
What often goes wrong here: Doing it because someone else's plan said to. The 22-miler is not a badge. If you don't have a specific reason it serves you, do a 20 with a marathon-pace insert instead.
Marathon-pace inserts · when and how to add pace work
A marathon-pace insert is a section of a long run, usually 3 to 8 miles, run at the effort you intend to hold on race day. Done right, it teaches your legs to hold pace on tired aerobic muscles. Done wrong, it turns the long run into a workout and costs you days.
When to add them: not before you've held a 14–16 mile easy long run for at least two cycles. Not on the same week you increased the long run distance. Not on a cutback week.
How to add them: start the long run easy: 6, 8, sometimes 10 miles at the same restrained effort as always. Then insert the pace section in the middle or toward the end. Finish with at least a mile of easy running, never a hard final push. The point is to feel marathon pace on legs that are already tired, not to time-trial.
“A marathon-pace section inside the long run is the closest thing we have to race rehearsal. If you run it correctly, you finish thinking ‘I could have held that for longer.’ That feeling is the goal. Chase it.”
— Coach Martin Karoki Muriuki
How to actually pace a long run
Effort, not pace. This is the part of Kenyan training philosophy that translates least well to runners who came up on GPS watches, and it is the part that matters most.
The talk test is the best free tool you have. For the first 70 percent of a long run, you should be able to speak in full sentences without breaking them up to breathe. If you are breathing every three or four words, you are going too hard. The mistake is reading a number on the watch (a pace you “should” be hitting based on a calculator) and chasing it on a day when your legs are tired, the wind is up, or last night's sleep was short.
If you must use heart rate, the long run lives in zone 2 territory: aerobic, sustainable, the zone where you could keep going significantly past the planned distance if you had to. But even heart rate lies. It runs higher in heat, higher when you're dehydrated, higher when you're stressed. The body's own signal (that you could hold this for another hour) is more reliable than any wrist data.
GPS pace is the least reliable signal of all on a long run. Pace is affected by terrain (every roll of the road), heat (a 2:00 mile in 80°F is a different effort than the same mile in 50°F), wind, humidity, and accumulated fatigue across the week. A long run that runs 15 seconds per mile slower than “expected” is not a bad long run. It is a long run on the day you had.
The honest pace target for a long run is: slower than you think. If you finish and your first thought is “I had more,” you ran it correctly.
The progression mistakes that derail marathon blocks
There are a small number of named failure patterns that explain most of the marathon blocks that fall apart, and they are worth recognizing by name.
The 10% rule is not a rule. It is a defensive heuristic invented to keep beginners from doing something stupid. It ignores recovery state, sleep, life stress, weather, and the difference between a runner with twenty years of base and a runner in their first block. Some weeks you should add nothing. Some weeks you should cut back. The 10% number is a ceiling at best, never a floor.
Cutback weeks are not optional. Every third or fourth week, drop the long run by 25–30 percent and reduce overall mileage. The runners who skip cutbacks because they “feel fine” are the runners who, six weeks later, cannot understand why a 14-miler feels brutal.
Running the long run too hard. This one shows up in almost every block that falls apart. The long run is an aerobic stimulus, not a fitness test. Run it at the effort that lets you finish thinking “I could have gone further,” and you will be a faster marathoner than the runner who proves something every Sunday.
Increasing distance and intensity in the same week. If the long run goes up, the workouts during the week stay flat. If you add a new track session, the long run holds. One stress at a time. The body adapts to one new thing better than two.
Ignoring the day-after signal. The Monday after a long run is the most honest data you have. Heavy legs are normal. Sharp pain is not. A heart rate that runs ten beats higher than usual on Monday is the body telling you the long run was harder than you registered. Listen to Monday more than you listen to Sunday.
“If your long run feels like a workout, it was a workout; now you have one less easy run in your week.”
— Coach Martin Karoki Muriuki
What this guide can and can't do
A static guide can give you a framework. That is what this is. It can tell you, roughly, how to think about progression, what the common failure modes look like, and what effort is supposed to feel like.
It cannot read your body's signals on a Tuesday morning. It cannot tell you whether the ache in your left calf is normal training noise or the beginning of something you should rest immediately. It cannot adjust when you miss a week to a head cold, or when work travel breaks the rhythm, or when your sleep falls apart for ten days. It cannot tell you whether your specific body needs to see 18 miles or 20 miles before race day, because that depends on your history, your injury record, your goal, and how you've responded to the last six weeks.
A guide is a map. A coach is the person reading the road in front of you. They are not the same tool.
Closing
If you want a coach inside your block reading the week-to-week response, not a static guide, KenyanRunning matches you with a professional Kenyan coach for $79 a month. Real 1:1 coaching, adjusted to what your body actually tells you between Sundays. Take the free coach-match quiz to get started, or check your current fitness against the marathon readiness score. When you're closer to the start line, the race-week guide is where to go next.