Fall Marathon Training in Summer Heat: The Two-Phase Plan¶

Your "marathon pace" run felt like a tempo effort. Your heart rate came in 12 beats above the zone the plan expected. Your splits are 60 seconds per mile off goal, and you are three weeks into a structured block with a real number on the wall.

The watch is not wrong. It is measuring something real — just not what you think.

You are not undertrained. You did not lose fitness over the winter. You started a goal-pace performance standard in early summer, which is the wrong standard for early summer. The problem is not your fitness. It is the mismatch between what the plan asks you to prove in July and what peak heat will allow you to demonstrate.

Berlin is September 27. Chicago is October 11. NYC is November 1. If you are holding a bib for any of those races, your 16–18 week training block has already started. Here is the structure that makes it work.

Where You Stand Right Now¶

Before anything else, orient to the week number. Generic training plans often skip this step. Here it is specific to the three fall majors and today's date:

If you are a Berlin runner on an 18-week plan, you are five weeks in. If you are an NYC runner who picked up a 16-week schedule, you started last week. Neither of those numbers is a problem — unless you have been scoring each run against a goal-pace standard in peak July heat. In that case, you have been reading the wrong column.

The week number matters because everything that follows depends on it. Where you are in the block determines which performance standard applies, and that determines whether the data you are seeing is a fitness problem or a structural one.

Why Weeks 1–8 Feel Wrong¶

Heat creates a specific and predictable set of failure signals on marathon-paced workouts. If any of these look familiar, you are reading thermodynamics, not fitness:

• Pace 45–90 seconds per mile slow versus goal, at what feels like the correct effort level
• Heart rate 10–15 bpm above the target zone for a given pace, including on runs that should feel easy
• RPE-to-pace ratio inverted: the effort that used to produce marathon pace is now producing what looks like garbage miles

These numbers are not evidence that your goal time needs revision. They are evidence that summer exists. The full dew-point math — what specific humidity thresholds do to pace, and by exactly how much — is in our summer pace breakdown. If you want to understand why heat stress is also a productive physiological stimulus (it is, and it is working in your favor right now), that is covered separately. This post is about the upstream structural decision: how to set up the block so weeks 1–8 produce real fitness instead of anxiety and bad data.

The core issue is that standard marathon training plans are written with a single set of performance targets from week one through race week. They assume conditions are roughly stable. July conditions are not stable. Running a plan that was designed for October temperatures in July heat will produce failure signals on every quality session for eight weeks straight — not because the training is failing, but because the plan's measurement system has no accommodation for the environment it is being executed in.

The Two-Phase Framework¶

A 16–18 week fall marathon block is not one continuous structure. It is two distinct phases with different performance standards, different success metrics, and different questions to ask after each run.

The summer phase exists because heat makes pace an unreliable proxy for effort. Your cardiovascular system is working at exactly the right training intensity — the aerobic adaptation is accumulating as planned — but the pace readout is distorted by the thermal load. Evaluating a summer quality workout by split time is like judging a wind-assisted 400 by the clock: the number reflects the conditions, not the performance.

The fall phase works because, starting around weeks 9–10, temperatures drop enough that pace becomes honest again. A threshold run at 8:10/mi in 54°F October air reflects your actual fitness. The same pace in 78°F July air at a dew point of 68°F does not.

Where the phase boundary lands for each race:

Berlin runners currently on week 5 of an 18-week plan have a summer phase through approximately week 8 — roughly late July. The fall phase begins around week 9 (late July to early August) and runs through race week, with taper beginning in the final two to three weeks. For taper structure specifically, the marathon taper guide covers it in full.

Chicago runners on week 4 have a summer phase through week 8, with the pace-based fall phase beginning in early August — right as midwest humidity breaks into the lower dew points that make pace data useful.

NYC runners entering weeks 1–3 have the longest summer phase runway: effort-based training through week 8, with the pace-based phase beginning in early-to-mid August and running through a November 1 race day.

None of this requires modifying the plan's structure. The training sessions — easy runs, quality sessions, long runs — stay identical. What changes is the measurement system used to evaluate them.

What "Effort-Based" Actually Means in Practice¶

The summer phase is not "just run easy." Every session type in the plan still happens: easy recovery runs, quality days, the long run. The volume targets stay. The structure stays. What changes is the performance standard you use to decide whether each session was a success.

Here is what that means in practice:

1. Replace pace targets with RPE or heart rate targets on every non-recovery run. If your plan calls for a tempo at 7:45/mi, your summer-phase execution is "tempo at RPE 7–8" or "comfortably hard effort in zone 4." Run the right effort. Do not chase the number.

2. On long runs, target time — not distance. Heat adds 10–15 minutes to a typical 18-mile effort. A 3:15 long run in July heat is a 3:15 long run regardless of how many miles the GPS logs. That is the aerobic stimulus you are after. The split is not the point; the time on feet is.

3. Define workout success as effort completion, not pace outcome. You ran 45 minutes at a controlled moderate effort. That is a completed quality session. The pace it printed is information about today's conditions. It is not a score.

4. Log effort alongside splits in your training notes. NavRun's weekly report and Strava's notes field both accept text input alongside data. Write down how each run felt — the words matter. When you review a week of July training, effort notes are what tells you whether training is on track. Pace-only logs in summer produce a record that looks like six weeks of regression and nothing else.

5. Keep the full structure intact. The same number of weekly runs. The same easy-quality-long distribution. The same mileage targets where conditions allow. The summer phase modifies the measurement system. It does not modify the training plan.

When Phase 2 Starts and How You'll Know¶

Do not wait for a calendar date to flip from effort-based to pace-based training. Watch for two specific signals instead:

• Weeks — approximately week 9 for all three races. For Berlin this is roughly the last week of July. For Chicago and NYC it lands in early-to-mid August. These weeks roughly coincide with regional dew points dropping below the thresholds where they dominate running performance — but the calendar is an approximation, not a trigger.
• Data signal — your easy-pace runs return to within 20–30 seconds per mile of your spring easy pace at the same heart rate. When the heat penalty shrinks to that range, pace is telling you something honest again. This is the observable marker. The dew-point thresholds for determining when conditions have normalized are covered in the summer pace piece if you want the specific numbers.

When both markers align — roughly week 9, roughly late July to mid-August depending on your race — shift your quality sessions back to pace targets and structure your next long run with the final 4–6 miles at goal marathon pace. That first successful pace-based long run is confirmation that the fall phase has started and your summer aerobic base is ready to be tested.

The Mistake That Kills Training Blocks Before They Start¶

Some runners solve the summer-pace problem by waiting. They decide that heat training is not productive — because every split confirms it — and plan to start serious work in September when conditions improve. For a Chicago or NYC race, this feels like six weeks of lost time that can be recovered.

It cannot. The math is unforgiving: a 16-week plan crammed into 10 weeks requires roughly 1.6× the normal weekly mileage ramp rate to reach equivalent peak volume. The standard evidence-based guideline caps weekly mileage increases at 10%. A compressed ramp of that magnitude does not produce marathon fitness in six weeks; it produces tendinopathy and stress fractures in weeks three through five.

The summer phase is not junk miles. Effort-based training at controlled heart rate zones in July heat produces real aerobic adaptation — it just does not produce split times that confirm it. The fitness is accumulating in your cardiovascular system even as your pace log looks like a steady decline. Start the block on time. Measure with the right tool. The data will make sense in September.

How NavRun Tracks This for You¶

Two features map directly to the two-phase structure.

AI Training Plan generates a 16–18 week marathon block that accounts for the current week you are in. If you are a Berlin runner on week 5 who has not structured a formal plan yet, entering your race and current week produces a remaining-block schedule that labels the summer-phase sessions by effort rather than pace and shifts automatically to pace targets in the fall phase.

Weekly Report surfaces effort-versus-pace trends across your recent training — exactly the data pattern that distinguishes "I am behind" from "heat is doing its job." When pace is slow but effort data is consistent week over week, the report shows consistency. When pace is slow and effort is also deteriorating, that is a different signal that needs a different response. The two read very differently in July.

If you are a Berlin, Chicago, or NYC runner and your block structure is not set yet, the AI plan generator takes about four minutes.

For the dew-point math behind summer pace adjustment: Your Summer Pace Is a Lie: The Dew-Point Adjustment. For the physiology of heat as a training stimulus: Heat Acclimation for Runners.