4-Hour Marathon: Why Fixed Pace Fails and How to Choose

According to Marathon Handbook, a 16-week marathon plan is 112 days—enough time to train physiology, but not enough to justify a fixed 4:30 pace band. In biomedical informatics, a decision-support system uses the patient's current measured state; a population average would be rejected. A fixed pace band is an order set written for an average runner, applied to every runner.

The better decision rule is an LT2-derived zone plan. Instead of prescribing a single pace per mile, it sets zones from a measured threshold and tells the runner when to stay controlled and when to push. The 16-week plan includes early base work before specific marathon blocks; the Thursday marathon-pace block is a repeated clinical stress test. Too many runners make the common mistake of thinking about marathon pace too early and shortening the base phase.

For a 4:30 goal, the individualized approach matters most late in the race. Glycogen is depleted and core temperature elevated; the pace band that felt easy in the early miles is no longer valid. A 20-week plan gives more time to adapt, while a 16-week plan spanning 112 days or 4 months can work if the decision rule is personalized. The sample week is an orienting framework, not a rigid law—and the taper protects adaptation, with Week 16 volume at 35 miles.

Mechanism

The arithmetic baseline is unforgiving: a fixed target time may be expressed as a single average pace, but the real metabolic cost depends on grade, economy, and environment. Every undulation, every footstrike inefficiency, every headwind adds a metabolic surcharge that the fixed pace target cannot absorb. The runner who locks onto that number is not following a plan; they are following a population average that assumes a perfectly flat, perfectly efficient, perfectly still day.

The controlling variable is critical speed—the asymptote of the speed-duration curve. A 4:30 finish requires a current critical speed that keeps the anaerobic capacity above critical speed in reserve, because that capacity is a finite reservoir. Spend it in the opening minutes of too-fast running, and the final stretch becomes a survival shuffle, not a race. Critical speed is not a number you inherit; it is a state you earn and re-earn as the training block progresses. Because it is expressed in pace zones, the plan's states are Z2 (aerobic), Z3 (threshold), and VO₂max intervals. A fixed pace band collapses these distinct physiological states into a single average-pace number, removing the feedback that tells the runner when a workout is too hard. The runner cannot hear the signal because the instrument has been taped over.

The feedback signal is the decoupling relationship. If pace stays constant while heart rate rises more than expected over a sustained period, the workout is no longer Z2—it has drifted into a higher zone, and the runner is accumulating fatigue without adaptation. The corrective action is immediate: shorten or walk the next interval, then lower the zone slightly at the next session. This is not a failure; it is data. The plan's closed-loop rule operationalizes this: repeat the LT2 field test periodically, and change all zones only when LT2 pace or LT2 heart rate has changed meaningfully. According to Marathon Handbook's 16-week plan, the schedule includes daily workouts and pace guidance, but the guide itself notes it "should not be set in stone." That caveat is the entire mechanism in miniature.

The 16-week plan, published March 25, 2026, is designed for beginner to intermediate runners and aims to get them to the finish line in 4 months. But the finish line is not the goal; the goal is the finish line at the target time. The runner who re-tests periodically and adjusts zones only on meaningful changes is running a closed-loop system. The runner who holds a fixed pace from the first week to week 16 is running an open-loop system, hoping the original estimate was correct. One of those systems adapts to a threshold shift; the other ignores it. The mechanism is not about the pace band—it is about the feedback that the pace band suppresses.

The Evidence

Faude, Kindermann and Meyer's Sports Medicine review quantified why a fixed marathon pace band fails before the first workout: the usual lactate-threshold convention is a population average, not a biological constant. Across individuals, LT2 varies widely. A runner at the low end reaches threshold at a fraction of the work a runner at the high end can absorb, so a pace calculated for "threshold" mis-targets anyone off the mean. That variability alone disproves one-size-fits-all pace bands.

The measurement side dictates the retest cadence. Poole, Burnley, Vanhatalo, Rossiter and Jones, in Medicine & Science in Sports & Exercise, reported that critical power/speed estimated from a short all-out test carries good precision. That precision is what makes a periodic retest decision defensible: the field test is stable enough that a pace change between tests reflects physiology rather than instrument error.

That precision matters more, not less, for runners who will see smaller threshold shifts. Kenney's training-induced shift is documented in previously recreational adults; a more seasoned runner's LT2 moves less over the same block. At that smaller signal size, good precision is the difference between detecting a real change and guessing. A longer interval would risk carrying a stale pace into the highest-volume weeks; a shorter one would drown in noise.

Buchheit, in Clinical Physiology and Functional Imaging, set the lower bound on retest frequency. Supine resting heart-rate variability has a day-to-day typical error. Test too frequently and you are sampling autonomic noise; the retest interval is the shortest window in which a genuine threshold shift can be separated from that noise floor.

According to Kenney, Wilmore and Costill's Physiology of Sport and Exercise, a block of endurance training shifts the lactate threshold to a higher percentage of VO₂max in previously recreational adults. A 16-week marathon block — 112 days, per Marathon Handbook's "112-day physiology" — falls squarely inside that window. The target will move, and materially, in the time it takes to train. Locking a pace band in the first week means running the final month on a number from a physiology that no longer exists.

Stack the evidence and the direction is unanimous: the inter-individual spread dwarfs the test's measurement error, which sits above the biological noise floor, while the 16-week block (112 days) is exactly the duration over which LT2 shifts most. A fixed pace band loses on every one of those axes. The only defensible plan: set every workout from a current LT2 field-test pace, re-test periodically, and let the target pace be recalculated — because the physiology it tracks will not stay still.

Decision Framework

When you choose a pace-setting method for a 16-week sub-4:30 block, you are not choosing a number; you are choosing an update policy. A fixed pace band is a static policy: it assumes your threshold physiology at the start is identical to day 112. That assumption fails precisely where the marathon is won or lost—late in the race, when accumulated fatigue has shifted your lactate threshold upward relative to your heart rate, and a pace you could hold early is now too hot. The decision framework below compares the viable methods against the criteria that actually matter for the training block.

Jack Daniels' VDOT table deserves a specific role: a calibration seed for the first week. The table converts a race result into training paces, but it rests on an assumption of average running economy. According to Saunders et al., running economy varies among runners with the same VO₂max. Two runners with identical aerobic capacity can differ substantially in the oxygen cost of running at the same speed—meaning the VDOT-derived pace for one is a recovery jog for the other. That is why the table should seed the first week's zones, then yield to your own LT2 field-test data for the remaining weeks.

The decision-support frame for any zone method reduces to a few criteria: actionable, timely, and individualized. A fixed pace band is actionable—you can run it from memory—but it fails timeliness (no updates) and individualization (no personal data). The VDOT table is timely only after a race, which in a 16-week block might happen occasionally, and it is not individualized because it assumes average economy. The LT2 retest protocol satisfies all of them: it is actionable because it produces concrete pace zones; it is timely because you re-test periodically; and it is individualized because the zones come from your own chest-strap test, not a population curve.

There is an equipment gate for the winning method, and it is non-negotiable. The LT2 field test requires a chest-strap HR monitor that records ECG-derived R-R intervals. Wrist optical sensors cannot be relied upon at threshold intensity—the very intensity where the test operates—because motion artifact and perfusion changes corrupt the signal precisely when you need accuracy. This is why the plan uses pace zones derived from the test, not watch HR during workouts: the test gives you a reliable threshold pace, and you execute that pace, not a live optical HR reading.

Rule 1: If you have not done an LT2 field test recently, do one before the first week. Use the resulting pace to set your zones. Do not use a stale race result.

Rule 2: At scheduled retest points, re-test. If your LT2 pace has improved meaningfully, adjust all zones upward. If it has not changed, keep zones identical—do not chase a faster number.

Rule 3: If your current LT2 pace is fast enough to support the target, keep 4:30 as the goal. If it is not, the goal is not viable; reset to a pace band derived from your actual LT2, not the calendar.

Rule 4: If you are using a wrist optical sensor for the test, stop. Borrow or buy a chest strap. The test is invalid without ECG-derived R-R data.

Rule 5: If you are in week 16 and your long run is 26 miles, treat it as a dress rehearsal for the LT2 pace you set at the last retest—not the pace from the first week. The sample week is an orienting framework, not a rigid law.

What the Data Doesn't Tell You

Before you trust a single workout prescription from your LT2 field test, you need to see where the data is structurally blind. The protocol I've described—recalculate every zone from a current LT2 test periodically—is the most reliable route to the target, but "most reliable" is not the same as "guaranteed." Here is what the data does not tell you, and how to keep the system honest when it lies.

A one-off field test is noisy. Day-to-day LT2 pace varies in the same runner under identical conditions. Add a hot morning, a stiff headwind, or a night of poor sleep, and the test can read slower than your true threshold. That is the difference between a workable and an unworkable prescription—a full pace zone shift that would derail the entire 16-week block. The fix is not to trust the first number. Baseline should be the more conservative of two tests performed on separate days. The slower value is more likely to reflect your sustainable threshold, not a transient environmental or physiological spike.

The retest is not the only cause of improvement. Stöggl & Sperlich in Frontiers in Physiology demonstrated that polarized training—with no individualized zone recalibration whatsoever—still produced substantial race-performance improvements. This is the counter-evidence you must hold in mind: the act of training hard and easy, with a clear structure, drives adaptation even when the zones are population averages. The LT2 retest is a precision instrument, but it is not the sole engine of progress. If you skip the retest and simply run a polarized plan, you will still get faster. The retest's value is in avoiding the plateau and the injury that come from mis-prescribed intensity—not in manufacturing adaptation from nothing.

Responder variance is the hard ceiling. Bacon et al. in PLoS ONE meta-analyzed interval-training studies and found VO2max responses varied widely. That spread is enormous. A low responder—someone at the low end—can follow the protocol perfectly, re-test periodically, and still not manufacture the target marathon. The zone algorithm is a necessary condition, not a sufficient one. If you are a low responder, the plan will keep you honest and efficient, but it cannot override your biology. The target is only viable if your current LT2 is fast enough; if the retest shows you are not there, the goal must shift, not the protocol.

Wrist-based heart rate is not a reliable proxy for threshold. Gillinov et al. in Annals of Thoracic Surgery measured consumer wrist monitors against ECG and found meaningful mean absolute errors during exercise. In a threshold zone, a small error can shift you a full pace zone—meaning you could be doing tempo work at recovery effort, or worse, redlining into VO2max territory. The LT2 field test is pace-based for a reason: pace is ground truth, wrist HR is an estimate. Use the HR data as a sanity check, never as the primary control loop.

Recovery has a blind spot. HRV can look completely normal for days after a hard long run before the dip appears. If you check Monday's numbers and see a green HRV, you might be tempted to push the scheduled Friday taper run. That is a mistake. The dip is coming; it just has not shown up yet. The protocol's periodic retest cadence is designed to absorb this lag, but only if you respect the schedule. Monday's HRV should never cancel a Friday taper run that the plan calls for. The data is a lagging indicator, and treating it as a leading one will cost you the adaptation you are trying to build.

The protocol fails cleanly at the edges: when the test is noisy, when you are a low responder, when the hardware lies, and when recovery data lags. None of these invalidate the canonical rule—re-test periodically, set zones from current LT2, and keep the target only if LT2 is fast enough. They simply define the conditions under which the rule is trustworthy. In every case, the fix is more data, not less: a second test, a pace-based check, a longer recovery window. The rule holds; the data around it just needs to be handled with the same rigor as the training itself.

Worked Case

Maya’s initial LT2 field test is the anchor for everything that follows: a measured threshold pace and heart rate, with post-test blood lactate near the conventional threshold, set against a recent race best and a laboratory VO₂max test. Her initial zone card is derived from that exact LT2, not from a population table: distinct zones for recovery, tempo, marathon pace, and VO₂max repeats. The LT2 value does not yet support the 4:30 goal by the decision rule; the whole point of the next 16 weeks is to see whether retests move that number.

The skeleton is deliberately periodized. The early weeks are easy runs plus a long run. The middle weeks add tempo work and extend the long run with a marathon-pace finish. The late weeks keep that structure with a reduced volume, and the final weeks taper to easy runs and short strides. According to Hahnertwins, the plan’s value is the clear transition between build, stabilization, and taper; the Marathon Method book presents the same broad 16-week structure (Grokipedia). A published Week 16 schedule mirrors the taper at three 3-mile runs and 35 total miles (Blogspot).

Retests are where this case earns its conclusion. At subsequent retests, Maya’s LT2 pace improves and her heart rate drops, reaching the gate that keeps the target viable. So every zone on her card shifts downward after the later retest: recovery, tempo, marathon pace, and VO₂max. She never trains by her initial zones again. A fixed pace band would have frozen her at the old relationship; the recalculated card makes the final build responsive to the threshold that actually exists.

Her race plan shows how to use the updated zones rather than chase them. She runs the first half conservatively, deliberately not at her updated marathon-pace window. That is not a contradiction of the retest data; the updated window is a ceiling supported by her latest LT2, not a starting pace. Holding the first half in reserve keeps the final miles below that ceiling. The projected finish is the target time.

Maya’s worked case is the canonical rule in motion: the fixed pace band would have kept her aiming at a one-time initial estimate for the entire block, while the retest protocol lets her finish at the target time precisely because her training zones moved when her LT2 moved.

How to Choose Well

In clinical decision support, a rule fires only when its trigger condition is met; trigger on the wrong variable, and the intervention is noise. A sub-4:30 marathon block runs on the same logic: the trigger for every goal decision is your initial LT2 field test, not the race date on the calendar. A fixed pace band is a population average with no trigger at all — it never re-fires, so it cannot adapt when your threshold shifts. The rules below are the decision tree that replaces it.

Rule 1 — Set the goal from the initial LT2 test, not the calendar. If the tested threshold pace is fast enough, target 4:30. If it is not, choose a slower goal consistent with the test. A calendar tells you when the race happens; it tells you nothing about the threshold pace your aerobic system can sustain on race day. The test does. This mirrors a clinical alert that triggers on a lab value rather than on the date of the patient's next appointment.

Rule 2 — Re-test the same field test periodically, on the same flat loop, same time of day, after an easy day and no hard workout the day before. The standardization is the mechanism: a different loop introduces elevation error, a hard day before the test leaves lactate carryover, and a different time of day shifts heat and circadian state. Any of those can move the result more than a real threshold shift would, and a rule built on a biased reading will propagate that error into every zone for the next training block.

Rule 3 — Keep the intensity split heavily skewed to easy volume. In a typical week, only a small share of total mileage should be hard; the rest must feel genuinely easy. The cap is by volume, not by session count. The easy miles are not filler; they are the recovery substrate that allows the hard miles to raise your threshold instead of just accumulating fatigue.

Rule 4 — When zone plans conflict, protect the long-run progression over an extra tempo session. The segment that matters is the long run with the final miles at marathon pace. The Hahnertwins plan puts early base work before specific marathon blocks precisely to set up this run, because the long run is where threshold work is integrated under real fatigue. The sub-4:30 decision is made in the late miles: if marathon pace holds there, it holds; if not, no Tuesday tempo can rescue it.

Rule 5 — Do not change the goal because of one noisy retest. If a scheduled LT2 test comes back slightly slower but the LT2 heart rate is unchanged, repeat the test soon before touching the original zone card. The unchanged HR is the discriminant: pace dropped but the cardiac cost held, so the threshold likely did not move — the reading is noise from sleep, weather, or cumulative fatigue. In clinical decision support, an out-of-range reading triggers a re-test, not a new treatment. The Hahnertwins plan names the matching error: responding to every fatigue day with extra ambition. Acute signals are real but local — the Week 4 session log in the Marathon Training series shows an interval workout going off plan after a twinge, and it was adjusted at the session level, not the goal level. The Week 16 plan's 26-mile long run is where the goal is finally confirmed, not before.