The short answer
A marathon tune-up race is useful only when it has one clear job and the surrounding training can absorb it. Use a shorter race to rehearse logistics, practise controlled pacing, or collect a current performance signal. Do not insert it merely because the calendar has an event.
The tune-up result does not prove a marathon finish time. Half-marathon and marathon pacing research describes population patterns, while performance-prediction studies retain individual error.1 Use the result alongside long-run durability, training consistency, fueling, recovery, course, and conditions.
Give the race one primary job
Choose one:
- Logistics rehearsal: breakfast, travel, kit, warm-up, corrals, and aid decisions.
- Controlled workout: complete a planned training effort in a supported setting.
- Performance check: race hard enough to update fitness assumptions, with recovery space.
- Pacing practice: execute a restrained opening and deliberate finish.
- Confidence through process: complete the plan correctly, independent of the clock.
If the race has all five jobs, it has no priority. A maximal half marathon, new breakfast, new shoes, pace test, and next-day long run is not one useful experiment.
Choose the distance by cost, not prestige
| Tune-up | Potential use | Main recovery cost |
|---|---|---|
| 5K | pace control, warm-up, race logistics | high intensity and soreness if raced maximally |
| 10K | sustained pacing and restraint | can disrupt the next quality session |
| Half marathon | endurance, fueling, course execution | larger fatigue and injury exposure |
| Local low-key event | supported controlled workout | temptation to race the field |
A shorter distance is not automatically low stress. A maximal 5K can create substantial neuromuscular and musculoskeletal load. A controlled half marathon can sometimes fit better than an all-out shorter race, but only when the training history supports it.
Recovery consensus emphasizes that recovery needs depend on the athlete and the preceding load.3 No table can assign an exact number of easy days.
Place it by working backward
Mark the marathon date, taper, final long-run block, travel, and known life load. Then ask:
- Does the tune-up replace a workout or add to the week?
- Is there time for normal function to return before the next key session?
- Does it collide with the final long run?
- Is the course or climate so different that the result will be hard to interpret?
- Will travel cost more recovery than the event itself?
Use a conservative default: the harder and longer the tune-up, the more separation it needs from the marathon and from other high-load sessions. That is a planning principle, not a universal week count.
Endurance taper research supports reducing training load before the goal competition while maintaining useful intensity and frequency in context.4 It does not mean every tune-up needs a full marathon taper. Reduce only enough to perform the assigned job, and avoid sacrificing the main build to chase a secondary result.
Use three effort formats
Format A: controlled throughout
Run at a pre-set effort below maximal racing. This is useful for logistics and pacing practice. The success metric is stable execution, not placement.
Format B: progressive finish
Open conservatively, hold the middle, and increase only if the plan remains green. This tests restraint and late decision-making without promising a negative split on marathon day.
Format C: performance check
Race hard only when health, training, and recovery space make the information worth the cost. Do not pair it with an unrehearsed food, shoe, or pacing change.
Large half-marathon pacing studies commonly find slowing across the race and differences between performance groups.1 Systematic pacing reviews also show substantial heterogeneity.6 Use these findings to avoid a thoughtless opening surge, not to impose one split pattern on every athlete.
Build a pre-race green, amber, red gate
| Signal | Green | Amber | Red |
|---|---|---|---|
| Health | ordinary | minor symptoms, uncertain trend | fever, chest symptoms, significant illness |
| Pain | no altered movement | mild and stable | worsening or changes gait |
| Recovery | normal daily function | several signals off baseline | profound or worsening dysfunction |
| Training | recent load repeatable | disrupted but stable | repeated failure to recover |
| Logistics | routine rehearsed | one manageable uncertainty | unsafe travel or missing essential plan |
Green supports the assigned job. Amber usually means reduce ambition or convert the event into a controlled session. Red means do not use a race to diagnose readiness.
Overtraining and recovery literature warns against interpreting fatigue from one symptom alone.3 A checklist cannot diagnose illness, injury, or overtraining. Concerning symptoms require qualified assessment.
Make the result interpretable
Record:
- official and watch splits;
- course elevation, turns, surface, and congestion;
- weather and wind;
- pre-race food and fluid;
- in-race intake;
- perceived effort by segment;
- pain or gastrointestinal symptoms;
- sleep and travel context;
- next-day and forty-eight-hour function.
Then separate facts from inference.
Fact: the runner completed a hilly half marathon in a given time and conditions.
Inference: current flat-marathon capability may be within a range.
Unsupported claim: the tune-up guarantees an exact marathon time.
Performance-prediction research can help frame likely outcomes, but equations depend on the input effort, athlete, distance relationship, and conditions.2 Use the race time predictor as a scenario, not a promise, and the marathon pacing guide to turn current evidence into guardrails.
Protect the week after
For the first twenty-four to seventy-two hours, prioritize ordinary recovery:
- easy movement or rest according to symptoms and experience;
- normal meals and hydration rather than a supplement rescue;
- sleep opportunity;
- no repayment workout;
- assessment of focal pain, illness, and normal daily function.
An endurance-recovery umbrella review found that strategies and evidence vary.8 The practical implication is not that nothing matters; it is that no gadget replaces load management, sleep, food, hydration, and symptom-aware decisions.
Resume the next key session only when the movement and effort needed for it are normal enough to perform the session's job. If the tune-up raced harder than planned, adjust the week instead of pretending the load did not happen.
Keep it out of race week
Race week is not the time for a maximal tune-up. A short organized event can sometimes serve as familiar movement, but crowds, travel, hard surfaces, and competitive effort add risk and decision load. Prefer a short, controlled primer already present in the plan.
Do not chase a confidence result after a missed workout, poor long run, or anxious taper. The marathon fitness is already largely built; one late race cannot safely repair the block.
Frequently asked questions
How many weeks before a marathon should I run a half marathon?
There is no universal number. Place it early enough that the expected recovery, travel, and any disruption do not collide with final long runs or taper. The harder the effort and the less experienced the runner, the more conservative the separation should be.
Should I race the tune-up all out?
Only if a maximal performance check is the primary job and the training plan can absorb it. A controlled or progressive effort often provides better marathon-specific information with lower cost.
Can I predict marathon pace from a half marathon?
Use the result as one input to a range, not an exact promise. Course, conditions, pacing, fueling, durability, and training volume all affect how shorter-distance performance transfers to the marathon.
What if the tune-up goes badly?
Classify the cause before changing the marathon goal: early pacing, conditions, illness, pain, logistics, fueling, or accumulated fatigue. Protect recovery and use the broader training record. One poor race is data, not a diagnosis.
Safety boundary
Do not race through chest pain, fainting, confusion, severe breathing difficulty, fever, major illness, or pain that changes normal movement. Stop and seek appropriate medical or event support for concerning symptoms.
This guide is educational and not medical advice or an individualized training prescription. It cannot diagnose readiness, injury, illness, overtraining, or determine a safe race effort.
26weeks.ai adapts marathon training around completed work, recovery, tune-up races, and disrupted weeks while keeping the main finish line visible. Start training now.
References
- Santos-Lozano A, et al. Pacing profiles of 208,760 half-marathon finishers. 2024. (PubMed)
- Feng Z, et al. Half-marathon performance prediction in recreational runners. 2024. (PubMed)
- Kellmann M, et al. Recovery and performance in sport: consensus statement. 2018. (PubMed)
- Bosquet L, et al. Scientific bases for precompetition tapering strategies. 2007. (PubMed)
- Wang Z, et al. Effects of tapering on performance in endurance athletes: systematic review and meta-analysis. 2023. (PubMed)
- Casado A, et al. Pacing behaviour in endurance running: systematic review. 2024. (PubMed)
- Meeusen R, et al. Prevention, diagnosis, and treatment of overtraining syndrome: joint consensus statement. 2013. (PubMed)
- Li S, et al. Recovery strategies in endurance athletes: umbrella review. 2024. (PubMed)