The Single Best Workout to Predict Your Marathon Time: A Coach-Backed, Race-Specific Test

Table of Contents

1. Key Highlights
2. Introduction
3. Why a long, effort-based run predicts marathon performance better than pure speed work
4. The workout, step by step: Warm-up, main set, and cool-down
5. Translating “marathon effort” into pace, heart rate, and perceived exertion
6. When to schedule the test within a training cycle
7. How to scale the workout for different abilities and goals
8. Fueling and hydration: treating the test like race day
9. Interpreting the outcome: What success and failure look like
10. Translating the test into a race-day pacing plan
11. Comparing this test with Yasso 800s and other predictive workouts
12. Practical variations: hills, altitude, treadmill, and weather adjustments
13. Monitoring and data: How to use heart rate, power, and GPS during the test
14. Recovery and taper: What to do after the test
15. Common mistakes and how to avoid them
16. Case studies: How runners used the test to adjust marathon goals
17. Implementing the test within a weekly training schedule
18. Mental rehearsal and race-day psychology
19. When the test indicates you should revise your marathon goal
20. A note on injury prevention and session selection
21. How coaches use the test to individualize training
22. FAQ

Key Highlights

• Test marathon readiness by running 90–100 minutes at marathon effort (RPE ~5) three weeks before race day to assess pacing, fueling, and fatigue management.
• Focus on sustained effort in a long run rather than speed repeats; this time-based workout simulates late-race conditions and gives actionable data to set a realistic goal time.
• Use shorter versions early in the training block to establish a tentative range, then fine-tune with the full-length test after peak week; adjust fueling, terrain, and pacing based on the results.

Introduction

Choosing a realistic marathon goal and sticking to it on race day requires more than optimism and a race-day adrenaline surge. Pacing that feels sustainable for a single 10K often blows up after 20 miles. Predictive workouts exist—the famous Yasso 800s among them—but they test speed, not the prolonged, steady effort a marathon demands. A targeted long run that replicates marathon effort under fatigued legs provides far more specific information: can you hold your planned effort while managing fuel, hydration, and mental strain?

Brant Stachel, a USATF-certified endurance coach with Fast and Free Performance Coaching, prescribes a single, simple workout that many runners can schedule three weeks before race day. It’s long enough to simulate late-race conditions and short enough to permit recovery before the goal race. This article explains why that run works, how to implement it for different paces and fitness levels, how to interpret the outcome, and how to translate findings into a practical race-day plan.

Why a long, effort-based run predicts marathon performance better than pure speed work

Marathon performance hinges on maintaining a sustainable effort while the body accumulates fatigue, depletes glycogen, and faces shifting environmental conditions. Short, fast intervals measure speed and VO2max. They fail to reproduce the physiological and psychological stressors that appear after 60–90 minutes of running.

A 90–100 minute steady run at marathon effort recreates key race variables:

• Accumulated muscle and central fatigue from running on tired legs.
• The need for consistent fueling and hydration strategies over time.
• Pacing control under perceived exertion rather than chasing an idealized split.

Testing an athlete when their legs are untapered—the state the workout is performed in after peak training—delivers more realistic information. If you finish the test feeling you could comfortably continue at that effort for a few more hours, the chosen marathon pace likely sits within your sustainable range. If the effort feels unsustainably hard, the test reveals a need to revise expectations and strategy before race day.

The workout, step by step: Warm-up, main set, and cool-down

Structure matters. Stachel’s protocol is simple and reproducible:

1. Warm up: 20–30 minutes easy running
2. Main set: 90–100 minutes at marathon effort (roughly RPE 5 on a 1–10 scale)
3. Cool down: 20–30 minutes easy running

Warm-up purpose: increase blood flow, loosen muscles, and mentally prepare to hold a steady effort. Avoid introducing hard efforts during warm-up; the goal is to arrive at the main set ready to settle into controlled exertion.

Main set focus: monitor effort rather than chasing specific per-mile splits. On a 1–10 rate of perceived exertion, RPE 5 should allow you to speak in short sentences but not hold a full conversation. Heart rate and pace will vary depending on terrain, weather, and individual physiology; effort is the controlling variable.

Cool-down purpose: promote recovery, flush metabolic by-products, and provide a psychological transition back to easy running. The entire session should simulate a long training day—test fuel intake and mid-run adjustments as you would on race day.

Translating “marathon effort” into pace, heart rate, and perceived exertion

Marathon effort is more subjective than a single pace number. Use a combination of cues:

• Perceived exertion (RPE): Target roughly a 5–6 on a 1–10 scale. You should be working, but not sprinting; breathing is rhythmic and controlled.
• Heart rate: Expect values below VO2max effort but above easy runs. For many trained runners, marathon pace sits near lactate threshold; heart rate will typically be a steady zone rather than spiking. Use recent training data—if your marathon pace usually corresponds to a consistent heart rate range during long efforts, aim for that.
• Pace: Use historical training paces as a guide, but don’t force exact splits. Terrain and wind will change mile times; focus on holding even effort.

Real-world example: A runner targeting 3:30 marathon pace (~8:00/mile) might run the 90-minute effort at 7:50–8:10/mile depending on hills and conditions. If, after 100 minutes, the runner feels they could continue at the same effort for several hours, 3:30 is plausible. If they feel drained and pace is drifting dramatically upward, the test indicates a more conservative pace is wise.

When to schedule the test within a training cycle

Timing the workout matters. Place the full 90–100 minute test in one of these spots for best diagnostic value:

• Three weeks before race day: This is optimal for a final reality check. It follows peak volume weeks but allows sufficient time for recovery and a proper taper.
• After peak week: Running the test after your highest-volume training week ensures the legs are fatigued, which mirrors race-day muscle condition.
• Early in the build (optional shorter version): Run 60–70 minutes at marathon effort about two to four weeks into the training cycle to establish a baseline. Repeat the full test closer to race day to confirm adjustments.

Why three weeks? It gives coaches and runners room to tweak pacing, fueling, and taper strategy while preserving recovery time. A test performed one week out risks compromising race readiness due to inadequate recovery.

How to scale the workout for different abilities and goals

The protocol is inherently flexible. Adjust duration and intensity to match training history and race objectives.

• Beginner marathoners: Begin with a 60–70 minute marathon-effort block early in the build to gauge steadiness. As fitness grows, progress to 75–85 minutes, then reserve the full 90–100 minute test three weeks before the target race.
• Intermediate runners: Most can handle the 90–100 minute test as prescribed. If training stress is high, consider 80–90 minutes to reduce recovery demands while still getting meaningful feedback.
• Advanced athletes targeting very fast times: The test still applies. Elite runners may be more precise about pace but should maintain the emphasis on effort and fuel management. Some elites perform similar tests as part of marathon-specific peak weeks, often on course-similar terrain.

Adjustments for ultra-distance or unusual race conditions: For hilly marathon routes or high-altitude events, replicate race terrain during the test or use treadmill runs with gradient to match expected demands. For hot-weather marathons, perform the workout in warmer conditions (or use heat acclimation strategies) to see how exertion and fueling respond.

Fueling and hydration: treating the test like race day

A central advantage of this workout is that it also tests your fueling strategy. Use the session to run a dress rehearsal of race-day nutrition: timing of gels or sports drink, salt intake, and fluid volumes.

• Pre-run fueling: Match your typical pre-race carbohydrate intake and breakfast timing. A familiar pre-run routine reduces variability.
• During-run fueling: Consume what you plan to use on race day—gels, chews, sports drink. Practice stomach tolerance and the rhythm of intake (e.g., one gel every 30–45 minutes). Modify amounts if GI distress occurs.
• Hydration: Carry or plan for fluid consistent with aid station spacing. If you plan to mix your own electrolyte solution on race day, practice with that exact mix.
• Environmental considerations: Sweat rates vary widely. In heat or on hilly routes, you may need more electrolytes. Use the workout data—perceived thirst, urine color post-run, cramping—to fine-tune quantities.

Real-world illustration: A runner training for Chicago decides to practice taking a gel at 30, 60, and 90 minutes during the 100-minute test and drinks 150–200 ml of electrolyte beverage every 20–30 minutes. They experience no GI issues and feel steady; they then adopt the same plan for race day.

Interpreting the outcome: What success and failure look like

Treat the test as diagnostic data, not a verdict.

Signs you’re on track:

• After 90–100 minutes at marathon effort, you feel you could continue at that intensity for several more hours.
• Pace and heart rate remain reasonably steady during the main set; RPE does not drift dramatically upward.
• Fueling and hydration strategy cause no GI distress and help maintain energy.
• Perceived exertion is similar to long runs completed at comparable fitness phases.

Signs you need to adjust:

• Effort becomes markedly harder before the 90-minute mark and remains unsustainable.
• Pace or heart rate shows a rapid drift upward, indicating poor endurance at that effort.
• Repeated bonking, severe fatigue, or GI issues despite trying multiple fueling strategies.
• Mental collapse—if the effort causes panic or catastrophic doubt about maintaining goal pace.

Actionable responses:

• If you pass the test: set or confirm goal pace, fine-tune race fueling, and proceed with taper.
• If you marginally pass but with difficulty: adopt a conservative pacing plan with built-in contingency (e.g., slight negative split or run-walk at the end).
• If you fail: adjust the goal time downward and rework training emphasis on long-run endurance and fuel practice during the remaining weeks.

Translating the test into a race-day pacing plan

Holding marathon effort over 26.2 miles demands precise pacing discipline. Use test results to craft a plan:

• Conservative start: If the test revealed vulnerability late in long efforts, begin slightly slower than target marathon pace for the first 10–15K to bank fitness and stabilize effort.
• Split strategy: Aim for even effort rather than perfect splits. If you judge perceived effort to be steady through the test, mimic that on race day. Rely on RPE and heart rate—not solely on GPS pace—if wind or hills alter immediate pace.
• Aid station integration: Practice picking up fluid and gels without letting pace collapse during the test. On race day, map a rhythm—grab a cup at each aid station and sip while running rather than stopping.
• Contingency planning: If you hit a tough patch between miles 18–23, have a plan: slow to a steady jog for 1–2 minutes to regain composure, switch to run-walk intervals, or reduce power and maintain cadence.

Example pacing translation: A runner’s 90-minute test at RPE 5 yields even splits and confirms a comfortable effort that approximates 8:00/mile. For the marathon, the runner plans to start at 8:05–8:10/mile for the first 10K, then settle into 8:00/mile, aiming to slightly negative split if energy permits.

Comparing this test with Yasso 800s and other predictive workouts

Yasso 800s and similar speed workouts have a role: they reveal speed endurance and correlate with marathon times for many runners. However, they test a different capacity—repeat speed and recovery—rather than the ability to sustain a steady, submaximal effort over prolonged fatigue.

Advantages of the long RPE-based test over 800s:

• Specificity: It mirrors marathon conditions—prolonged effort, fueling, and fatigue.
• Accessibility: Time-based rather than pace-based; useful across a wide range of abilities.
• Holistic feedback: Tests GI tolerance, hydration strategy, and psychological resilience, not just anaerobic speed.

When to still use 800s:

• As part of a training block to develop speed and VO2max.
• To gauge improvement in repeatability and lactate clearance.
• For runners who need a complementary speed stimulus in a balanced program.

Most effective approach: Combine both. Use intervals during marathon builds to maintain speed and economy; use the 90–100 minute marathon-effort test for peaking and pacing verification three weeks out.

Practical variations: hills, altitude, treadmill, and weather adjustments

Replication of race conditions increases test predictive value.

Hilly routes: If the marathon course includes significant elevation changes, perform the test on similarly undulating terrain. Pace will be slower on climbs and faster on descents; effort should remain steady.

High altitude: If racing at altitude, attempt the test at similar elevation if possible. If that’s not feasible, consider heart-rate drift and perceived exertion differences when interpreting results.

Treadmill options: Use gradient to simulate course demands. Treadmill testing can control pace and reduce injury risk for those with limited route options. However, treadmill proprioception differs; be cautious interpreting exact pace numbers.

Hot or humid conditions: Heat elevates heart rate and perceived exertion. If you cannot simulate race-day heat during the test, anticipate slower paces and practice additional cooling strategies (e.g., pre-cooling, ice, sunscreen).

Cold or windy conditions: Wind and extreme cold can depress pace without changing perceived effort. Use effort and heart rate rather than raw pace to judge success.

Monitoring and data: How to use heart rate, power, and GPS during the test

Collecting objective data complements subjective observation.

• Heart-rate monitoring: Useful for steady-state efforts. Watch for steady heart-rate drift; a pronounced upward trend suggests cardiovascular strain or inadequate fueling.
• Running power meters: Power provides an alternative to pace in variable terrain. Maintain consistent power output rather than pace.
• GPS pace: Helpful but sensitive to terrain and signal errors. Use it to log splits, but prioritize RPE and heart rate for effort control.
• Perceived exertion log: Write down perceived feelings at 15–30 minute intervals to capture the mental and physical trend.

Interpreting data:

• Consistent heart rate, power, and RPE through the latter portions of the main set indicate good pacing and endurance.
• Sharp drift in any of these metrics signals underpreparedness or inappropriate fueling.

Recovery and taper: What to do after the test

A properly executed recovery plan minimizes the test’s toll on race-day fitness.

Immediate post-run:

• Cool down and rehydrate with a mix of carbohydrate and protein within 30–60 minutes.
• Refuel with carbohydrates to replenish glycogen stores.
• Gentle mobility work and compression or contrast therapy if desired.

48–72 hours following:

• Reduce intensity and volume; prioritize sleep and nutrition.
• Include one or two easy aerobic sessions if recovery is progressing well; avoid hard efforts that could compromise taper.

One week out:

• Maintain light runs with short pickups but avoid exhaustive sessions.
• Practice race-warm-up and final fueling plan in small dress rehearsals.

If you ran the test three weeks out, schedule recovery over the first week, maintain moderate training the second week, and start tapering the final 7–10 days before race day.

Common mistakes and how to avoid them

Many runners misinterpret the test or sabotage its usefulness through avoidable errors.

Mistake: Treating pace as the primary metric.

• Fix: Focus on perceived exertion and steady heart rate. Adjust pace for hills and wind.

Mistake: Changing fueling during the test to something untested on race day.

• Fix: Use the exact race-day nutrition and fluid plan to identify issues.

Mistake: Performing the test too close to race day.

• Fix: Schedule it about three weeks out. This gives time to recover and adjust while preserving peak fitness.

Mistake: Overextending the test or turning it into an all-out effort.

• Fix: Resist the urge to “race” the workout. It’s diagnostic, not maximal.

Mistake: Ignoring environmental differences.

• Fix: If you cannot replicate race conditions, account for heat, humidity, altitude, or hills in your interpretation.

Case studies: How runners used the test to adjust marathon goals

Case study 1 — First-time marathoner A recreational runner aiming for 4:00 (9:09/mile) completed the 90-minute test three weeks out. They felt increasingly heavy after 70 minutes and struggled with GI discomfort despite planned fueling. Their coach suggested reducing goal pace to 4:10 and practicing a slightly earlier fueling schedule during taper. On race day, they hit 4:08—close to the adjusted target—having avoided bonking through conservative pacing.

Case study 2 — Experienced runner chasing a PR An intermediate athlete targeting 3:10 used the test and found pace and RPE steady through 100 minutes, but heart-rate drift suggested dehydration risk in heat. The runner modified hydration volume and salt intake for the race and executed the plan. They achieved a negative split and a new PR, crediting the refined fueling plan from the test.

Case study 3 — Runner on a hilly course An athlete preparing for a hilly marathon performed the test on rolling terrain. Their average pace was slower than flat training but effort and power data matched their flat marathon-effort targets. They planned a more conservative flat-equivalent pace for race day and practiced downhill running form, reaching the finish strong.

Implementing the test within a weekly training schedule

Example for a three-week lead-in before a marathon:

Week A (peak week, high volume)

• Monday: Easy 45–60 minutes
• Tuesday: VO2 or lactate-threshold session
• Wednesday: Easy 45–60 minutes
• Thursday: Medium-long run 75–90 minutes with pickups
• Friday: Rest or easy 30–40 minutes
• Saturday: Long run 2:00–2:30 with portions at marathon effort (to build stiffness)
• Sunday: Easy recovery 45–60 minutes

Week B (test week)

• Monday: Easy 45–60 minutes
• Tuesday: Short tempo or easy run with strides
• Wednesday: Easy 30–45 minutes
• Thursday: Warm-up + test: 20–30 minutes easy, 90–100 minutes marathon effort, 20–30 minutes cool-down
• Friday: Rest and recovery protocol
• Saturday: Easy shakeout run 20–40 minutes, low intensity
• Sunday: Moderate easy run 30–45 minutes

Week C (taper)

• Monday–Wednesday: Reduced volume with short, race-pace pickups
• Thursday: Easy 20–30 minutes with strides
• Friday: Rest or light jog
• Saturday: Short warm-up and mental rehearsal
• Sunday: Race day

Adjust volume for experience and prior fatigue: novices may require more recovery days between the test and remaining training.

Mental rehearsal and race-day psychology

The long-effort test does more than confirm physical readiness. It builds confidence and clarifies mental strategies for hard mid-race moments.

Use the test to:

• Practice maintaining focus during repetitive miles.
• Identify useful mantras or cues when fatigue arrives.
• Test strategies for breaking the race into manageable chunks (e.g., 5K blocks, aid-station markers).

If the test exposes mental vulnerabilities—such as a tendency to panic when pace drifts—work on breathing drills and visualization techniques in the remaining weeks.

When the test indicates you should revise your marathon goal

Adjust goals if the test shows unsustainable effort or significant physiological red flags.

Red flags:

• Rapid, persistent pace or heart-rate drift.
• Severe GI distress despite testing multiple fueling strategies.
• An inability to maintain even a conservative marathon effort in untapered legs.

If you encounter any of these, revise the goal to a more conservative target and execute a revised race plan with contingencies. Accepting a slower time is better than chasing an unrealistic target and risking injury, blow-up, or negative race experience.

A note on injury prevention and session selection

The test itself is low risk when integrated thoughtfully into the training plan. Still, pay attention to cumulative training stress.

• Avoid inserting hard, high-impact sessions in the days immediately preceding the test.
• Prioritize sleep, nutrition, and minor load reduction the week of the test.
• Address niggles early; a pre-test sports therapist visit can identify modifiable risks.
• If you have recent injuries or chronic issues, consult a coach or sports medicine professional before attempting the full 90–100 minute test.

How coaches use the test to individualize training

Coaches view the test as a rich data point to inform pacing prescription, taper length, and marathon peaking strategy.

• Pace prescription: Coaches translate perceived exertion and physiological cues from the test into a target marathon pace range rather than a single “must-hit” number.
• Fueling plan: Observations of GI tolerance and energy dynamics guide nutrition plans tailored to race day.
• Taper adjustments: If the test suggests incomplete adaptation, coaches might extend or intensify taper elements or modify final-week training.

The test also helps coaches decide whether to add race-specific sessions—such as longer segments at marathon effort with added race-pace miles—in the weeks leading up to the race.

FAQ

Q: How accurate is this workout at predicting marathon finish time? A: The workout is highly informative about sustainable effort and fuel tolerance, which are core determinants of marathon performance. It’s not a mathematical predictor like some interval-based estimates but provides practical, race-specific feedback that often leads to more reliable pacing decisions.

Q: Should I do this workout on a flat course? A: Ideally, replicate race terrain. If the marathon is flat, do the test on flat ground. For hilly courses, choose a rolling route to simulate climbs and descents. When terrain differs, interpret pace accordingly and focus on consistent effort.

Q: What if I can’t do a 90–100 minute block because of time constraints? A: Conduct a 60–70 minute marathon-effort test earlier in the build to establish a baseline. While not as diagnostic as the full-length test, it still provides meaningful feedback on effort and fueling.

Q: Can I use a treadmill for this test? A: Yes. Use incline to mimic road effort and adjust pace and gradient to match perceived exertion you expect on race day. Be cautious interpreting exact pace, as treadmill running mechanics differ slightly from outdoor running.

Q: How should I adjust for heat or humidity? A: Heat increases heart rate and perceived exertion. If you can’t simulate race-day heat, anticipate slower race paces and incorporate heat-acclimation strategies where possible, like shorter runs in heat or sauna exposure. During the test, monitor symptoms closely.

Q: How do I know if my fueling during the test is optimal? A: If you maintain steady effort, avoid GI distress, and feel able to continue beyond the main set, your fueling is likely sufficient. If you experience early energy dips, experiment with carbohydrate timing, concentration, or types (gels vs. chews vs. real food) in subsequent runs.

Q: Should I stop the test if I feel bad early? A: Stop if you experience warning signs like sharp pain, dizziness, chest discomfort, or other non-typical symptoms. If the issue is merely “harder than expected,” slow down and continue to gather information, but prioritize safety.

Q: How much should I adjust my marathon goal based on a marginal test? A: If the test was marginal—with effort trending upward but no catastrophic failure—conservatively lower your time target (e.g., add 1–3% to expected finish time) and plan a cautious race with escape strategies. If the test shows clear unsustainability, revise plans more substantially.

Q: Can I run the test alone or should I have a training partner or coach present? A: Running alone is fine, but having a coach or trusted training partner can help you maintain steady effort, monitor data, and provide objective feedback. Use a coach if available, especially when attempting a time-specific goal.

Q: How do I combine this with interval training and speed work? A: Use intervals earlier in the build to maintain speed and raise lactate threshold. Reserve the full-length marathon-effort test for the peak phase to validate pacing and fueling. Maintain light, targeted speed work through the taper in short bursts only.

This 90–100 minute marathon-effort test gives runners a practical, specific assessment of race readiness. It moves beyond abstract pace estimates to test how you cope with fatigue, fueling demands, and mental strain. Whether you’re chasing a first marathon or a personal best, this single session—scheduled and executed well—clarifies what’s realistic and what needs adjustment before race day.