How to Peak for a Race: My Training, Taper, and Race-Week Plan

How to peak for a race: I finish building fitness early enough to absorb it, reduce training volume while preserving small doses of familiar intensity, protect sleep and routine, and arrive with a tested execution plan. I am not trying to become fitter in race week. I am trying to uncover the fitness I already earned without letting coordination, confidence, or race rhythm go quiet.

That distinction changes which work I keep and which work I stop during race week.

Across 12 years of running and 36 races from 5Ks to a 50K, I have learned to judge a peak by the decisions I can control: the last costly workout, the recovery runway, familiar race rhythm, and an opening pace I can defend. I do not require a magical feeling during the final shakeout.

I treat peaking as six decisions: Build → Prove → Absorb → Sharpen → Protect → Execute. The taper is the middle of that process, after race-specific work has been completed.

My 60-second peak decision

When I am two or three weeks from a goal race, I ask six questions:

1. Is the fitness already built, or am I still trying to rescue the block?
2. Which final session must prove race readiness without becoming a race?
3. How much fatigue am I carrying from mileage, long runs, hills, strength, work, and travel?
4. Which small dose of intensity keeps my stride familiar?
5. What can still improve the outcome: recovery, logistics, fueling, pacing, or weather adaptation?
6. What can only make the outcome worse now: extra volume, novelty, soreness, panic testing, or a goal change?

If the block is complete, my bias shifts from gaining fitness to preserving access to it. If the block is incomplete, I accept current fitness and still taper. I cannot compress delayed adaptation into five days, but I can easily carry fresh fatigue onto the start line.

My race-week rule is blunt: if a session cannot make me fitter by race day, it must justify itself through rhythm, confidence, or routine—and cost very little.

My race-readiness control panel

I do not let one watch metric, one restless night, or one heavy jog decide whether I am ready. I use a panel of signals and look for a pattern across several days.

Dial	Green	Yellow	Red	My response
Easy-run effort	Familiar and conversational	Slightly heavy but stable	Rising effort or altered gait	Shorten; investigate illness, pain, heat, or fatigue
Stride feel	Crisp, relaxed, coordinated	Flat but improving after warm-up	Forced, painful, or mechanically different	Skip intensity; protect health
Soreness	Mild and fading	Persistent in one area	Focal, worsening, or changes movement	Stop testing; assess the problem
Sleep trend	Broadly normal across the week	One or two disrupted nights	Several poor nights plus declining function	Reduce optional load and decisions
Mood and urge to train	Calm or pleasantly eager	Restless, irritable, doubtful	Compulsive need to prove fitness	Follow written plan; no test workout
Resting data	Near personal range	One unusual reading	Multi-day change with symptoms	Use context; respond to the whole pattern

The panel prevents two errors. First, it stops me from calling normal taper weirdness a crisis. Second, it stops me from dismissing a real problem because the calendar says “race week.”

Peaking begins before the taper

I cannot reveal fitness that was never built. Before I reduce anything, I define what the race asks me to sustain and what is most likely to break that performance.

My one-sentence race demand looks like this:

On race day, I need to sustain this effort for this duration on this terrain, while managing this personal limiter.

For a flat 5K, the limiter may be early pace control and the ability to tolerate the final third. For a half marathon, it may be threshold durability and fueling simplicity. For a marathon, it may be muscular durability, carbohydrate availability, and restraint. For a trail race, climbing economy, downhill tolerance, footing, and equipment may dominate.

That sentence decides the final six weeks better than the vague instruction to “get sharp.”

Build: I create capacity that can tolerate specific work

Early in the block, I want repeatable easy volume, a reliable long run, enough strength to tolerate training, and a small number of high-value sessions. I do not rush race pace onto an unstable base.

Easy mileage does not look dramatic, but it lets me complete specific sessions without turning each one into a recovery emergency. My easy-run rules keep this foundation genuinely easy. If I need to separate effort from weather-driven pace, I use my effort-based training guide instead of forcing yesterday’s numbers into today’s conditions.

Prove: I answer the race’s hardest question

The last meaningful race-specific session should answer a question, not advertise my fitness. Depending on the event, I might test pace control, fueling, hills, late-run mechanics, or sustained threshold rhythm.

I finish that session with information and recoverable fatigue. If I need four ruined days to prove I can survive it, the session was too expensive. The workout should reduce uncertainty while leaving the block intact.

For 10K preparation, the specific work arrives inside a broader progression, as shown in my intermediate 10K plan. For longer road racing, my intermediate half-marathon plan and intermediate marathon plan place the biggest rehearsals early enough to absorb them.

The hinge of the peak: finish the last costly work on time

The most common peaking error I see is not tapering too little or too much. It is putting the final costly session too close to race day.

“Cost” is not just miles. I include:

• muscular damage from a long or downhill run;
• glycogen depletion from sustained work;
• tendon and joint stress from speed;
• soreness from strength training;
• mental stress from a workout treated as a test;
• travel, poor sleep, work deadlines, and long periods standing.

I schedule backward from the recovery cost I know, not from a universal graphic. A high-mileage marathon runner and a lower-mileage 5K runner do not need identical tapers. Even two marathoners may absorb the same long run differently.

My final-key-session filter

Before I approve the session, I ask:

Question	Pass	Fail
Does it match a real race demand?	Pace, terrain, fueling, or rhythm is specific	It is hard only because hard feels reassuring
Have I done its ingredients before?	Familiar duration, surface, shoes, and fuel	New workout, new shoe, or novel eccentric load
Is there enough recovery runway?	My normal response fits before race day	I am hoping recovery will be unusually fast
Can I stop with one repetition available?	Controlled finish and clean mechanics	Chasing a watch prediction or personal best
Will the result change the plan safely?	It can refine pacing or logistics	It can only provoke panic or overconfidence

If the workout fails this filter, I simplify it. Race readiness is not proven by creating a second race before the first one.

Absorb: I reduce fatigue without erasing routine

Once the last meaningful overload is complete, I stop adding. My goal becomes removing enough volume for fatigue to fall while keeping the movements and intensities that make running feel familiar.

I usually reduce duration before frequency. A runner accustomed to six days may feel better keeping several very short runs than taking four unexpected days off. Another runner who normally uses frequent rest may respond well to more complete recovery. I respect the routine the body already knows.

The same principle applies to workouts. I keep the signal and remove the cost:

• fewer repetitions;
• shorter work segments;
• longer recovery;
• no extra fast finish;
• no depletion goal;
• no soreness accepted as proof.

A runner used to six mile repeats does not need six more in race week. A few controlled repetitions can remind the legs of cadence and rhythm. I finish knowing I could do another. That unfinished feeling is part of the design.

A taper is not a cutback week

Both reduce load, but their purpose differs. A cutback restores capacity so training can resume; a taper converts a completed block into competition readiness. My cutback-week framework helps me avoid confusing the two.

During a cutback, I may reduce intensity because the next build matters. During a taper, I often preserve brief, familiar race-relevant intensity because the race is the next demand. In both cases, I remove unnecessary volume and watch the response.

My taper starting ranges by event

These are starting ranges, not prescriptions. I adjust them for weekly mileage, accumulated fatigue, age, training history, travel, terrain damage, and how I responded before previous races.

Event	When I usually begin reducing	What I preserve	What I remove first
5K	About 7–10 days	Short race-rhythm work and relaxed strides	Extra easy volume and full interval count
10K	About 7–14 days	Controlled race pace, threshold memory, frequency	Long repetitions, dense recovery, strength soreness
Half marathon	About 10–14 days	Brief threshold or race-pace segments	Long-run duration and workout volume
Marathon	About 14–21 days	Short marathon-rhythm work and normal movement	Depleting long runs, large workouts, heavy lifting
Trail/ultra	About 14–21+ days	Footwork, hiking rhythm, gentle terrain familiarity	Damaging descents, long outings, technical risk

I do not copy a 50% reduction blindly. I first identify the baseline. If the previous week was already reduced because of illness or missed training, cutting 50% again may create unnecessary inactivity. If the final build was unusually large, I may need a stronger reduction.

I judge the curve, not one week’s arithmetic. The direction should be clear: less total work, fewer costly minutes, familiar movement, and improving readiness.

Sharpen: I touch speed without carrying speed-work fatigue

Sharpening is a nervous-system and rhythm reminder, not a hidden workout. I use short bouts at familiar pace with generous recovery and stop while mechanics remain clean.

Strides work well for me because they let me rehearse posture, cadence, and relaxation without accumulating much fatigue. I build smoothly, run fast but controlled, and recover fully. They are not all-out sprints.

For sustained races, I may use brief race-pace segments. For a 5K, I may touch race rhythm or slightly faster running in short doses. For a marathon, I avoid turning “marathon pace” into a large glycogen-demanding workout.

I use my RPE scale for runners to keep the session anchored to sensation when wind or weather distorts pace. If threshold work was central to the block, my threshold-run guide reminds me what controlled means; race week is not the time to turn threshold into a time trial.

My sharpening pass criteria

I approve the session when:

• pace feels recognizable rather than forced;
• mechanics stay quiet and coordinated;
• breathing settles quickly in recovery;
• no focal discomfort grows;
• I finish with appetite rather than depletion;
• the next day’s easy movement feels normal.

If the first repetition feels dull, I do not immediately add more. Flat legs can wake during the warm-up, or they can be asking for recovery. I compare the whole panel before changing the plan.

Protect: race-week recovery is active decision control

Peaking is not lying still and hoping freshness appears. I protect the adaptations by controlling the small stresses that multiply during race week.

Sleep: I build a buffer, not a perfect-night fantasy

I aim for broadly normal sleep across the preceding week. The night before a race may be restless because of nerves, travel, or an early alarm. One imperfect night does not erase months of work.

I move bedtime gradually if race morning requires an earlier wake-up. I prepare kit and logistics before evening. I do not chase sleep with a new supplement, an unusually early bedtime, or anxiety about the clock.

Strength: I preserve familiarity and remove soreness

I reduce strength volume before the race and avoid novel exercises, heavy eccentric work, or tests of strength. Familiar low-volume movements may stay if I know they leave no residue. My guide to balancing running and strength helps me place gym work where it supports running rather than competes with it.

Rest: I place it where it improves the next key moment

I do not add rest days randomly because “more recovery” sounds safe. Some runners feel best after complete rest; others prefer a short shakeout. My rest-day scheduling framework keeps the choice connected to training history and response.

A hard bike ride, long hike, heavy lifting session, expo walk, or day of airport standing is not rest simply because it is not running.

Fuel and hydration: nothing heroic

I keep meal timing predictable and make carbohydrate availability appropriate to the event. For longer races, I use a rehearsed fueling approach. I do not force excessive water, drastically restrict fiber without practice, or introduce a “performance” food that my gut has never seen.

The final days should make the start line easier to reach. They should not create a second competition against the bathroom, the scale, or a hydration target.

My seven-day race-week operating board

Window	Training objective	Logistics objective	Decision I refuse to make
7–5 days	Reduced familiar running; final modest quality touch if appropriate	Confirm travel, weather range, course, shoes, fuel	No fitness test or new goal from one workout
4–3 days	Short easy work; optional controlled strides	Finalize kit, breakfast, transport, backup layers	No novel strength, mobility, or recovery treatment
2 days	Preserve rhythm or rest according to routine	Charge devices, pin bib, organize bags	No panic mileage or aggressive shoe change
1 day	Brief shakeout or rest—whichever is familiar	Reduce standing and decisions	No chasing sleep, hydration, steps, or scale weight
Race morning	Rehearsed warm-up and controlled opening	Execute breakfast, timing, bathroom, gear	No goal rewrite based on adrenaline alone

My full race-week checklist handles the equipment and logistics layer. That frees the peak itself to remain a training decision rather than a packing emergency.

Execute: freshness has value only if I spend it well

A successful peak can make race pace feel deceptively easy at the start. That is useful, but it is also dangerous. Freshness does not change the physiological price of an aggressive opening.

Before race morning, I write three pace or effort guardrails:

1. Opening cap: the fastest effort I will allow before the race settles.
2. Middle checkpoint: the signal that says hold, adjust, or protect the day.
3. Commit point: the earliest place I am willing to spend what remains.

For a stable course and well-calibrated goal, my even-split pacing guide helps prevent early leakage. When conditions and fitness support a controlled progression, my negative-split guide shows how I earn the faster second half rather than promising it.

I distinguish goal fitness from goal execution. A perfect taper cannot rescue reckless pacing, untested fuel, or a weather-blind plan. Peaking gives me access to my capacity; strategy decides how long I keep it.

What I change when the control panel turns yellow

Race week rarely unfolds exactly as written. I use the smallest change that addresses the real problem.

If my legs feel heavy but nothing hurts

I extend the warm-up gently, keep the planned run shorter, and judge the trend over 48 hours. I may retain a few relaxed strides if they improve coordination. I do not run a hard session to force reassurance.

If fatigue is high and not improving

I remove optional volume, strength, and errands. I preserve sleep opportunity and normal eating. If the training block was unusually heavy, I accept that recovery is now the highest-value intervention.

If I feel flat after too much rest

If this pattern is familiar and there are no illness or pain signals, I may use a short easy run with a few relaxed strides. I do not rebuild the missed week. The goal is movement memory, not fatigue.

If illness appears

I stop treating the schedule as the authority. Fever, chest symptoms, systemic illness, or worsening function changes the decision entirely. A race goal does not make hard running medically neutral.

If focal pain changes my gait

I stop the test. I do not use adrenaline, anti-inflammatory medication, or tighter equipment to manufacture a pass. Race-week proximity does not convert a red flag into taper anxiety.

If weather changes

I adjust pace expectations, clothing, warm-up, and fueling—not the months of fitness. Heat, wind, rain, altitude, and technical conditions alter the sustainable output. Effort is the control variable when pace loses meaning.

How my peak changes by race distance

5K: preserve speed familiarity, remove repetition fatigue

For a 5K, I want the stride to remember race cadence without carrying a full interval-session cost. I keep brief fast running, full recovery, and a controlled finish. I protect the opening because fresh legs can make the first 400 meters lie.

10K: keep race rhythm and threshold confidence

The 10K sits close enough to threshold that I value rhythm, but the real capacity was built earlier. I cut the volume of sustained work, not the memory of pace. I arrive eager to complete repetitions I deliberately did not do.

Half marathon: absorb the last durable work

I want the final specific long or threshold session far enough away that it becomes fitness rather than baggage. Race week retains short rhythm and routine. Fueling, shoes, and pacing are already settled.

Marathon: remove depletion, not movement

The marathon peak is heavily about shedding long-run fatigue while preserving normal running. I reduce long-run length, large pace blocks, and strength cost. I do not use one fast taper run to upgrade my marathon goal.

Trail and ultra: unload damage and risk

For trail racing, muscular damage from descending and technical risk can outlast aerobic fatigue. I remove consequential descents and long terrain exposure early enough. I may retain gentle footwork and hiking rhythm, but nothing that can turn one slip into a lost race.

Peaking mistakes I guard against

I do not cram missed training

Fitness responds on its own timeline. Missed work cannot be squeezed into the final ten days without moving fatigue closer to the race. I race the fitness I have.

I do not race the tune-up

A tune-up should confirm rhythm and decisions. If I chase a personal best in training, I spend recovery budget and create an emotional result that can distort the goal.

I do not copy an elite taper by percentage alone

An elite runner’s percentage starts from elite volume, frequency, recovery support, and years of tolerance. I scale from my actual training and my previous responses.

I do not use one biometric as a verdict

Resting heart rate, HRV, sleep scores, and watch predictions are context. Device noise, travel, alcohol, heat, stress, and measurement conditions can move them. I use trends plus how I function.

I do not introduce equipment or therapy novelty

No new race shoes, socks, insoles, fueling products, deep massage, aggressive mobility, or gym exercise enters because extra time appeared. Predictability is a performance asset.

I do not turn every good sensation into more work

The taper may make easy running feel wonderfully light. That is the desired outcome, not an invitation to rebuild the removed volume.

I do not turn every bad sensation into panic

Heavy legs, restless energy, and altered routine can occur during a taper. I look at the control panel, not one moment. Real pain or illness earns action; ordinary uncertainty does not earn a test workout.

My post-race peak audit

Within 48 hours, before the story changes, I record:

1. Date and cost of the final demanding long run.
2. Date, structure, and feel of the final quality session.
3. Weekly running volume across the final three weeks.
4. Strength work, travel, work stress, sleep trend, and illness.
5. Race-week easy effort and stride feel.
6. How the first, middle, and final thirds of the race felt.
7. Whether the failure was fitness, fatigue, fueling, pacing, weather, terrain, or logistics.
8. One element to move earlier, later, increase, reduce, or leave untouched.

I do not judge the taper only by finish time. Weather and race execution can conceal a good peak; exceptional conditions can flatter a poor one. I ask whether I arrived healthy, fresh enough, coordinated, and able to express the fitness the block plausibly built.

Over several races, this audit becomes my personal taper model. My own response history deserves more weight than generic race-week folklore.

Frequently asked questions

How long should I taper before a race?

I usually start with about 7–10 days for a 5K, 7–14 days for a 10K, 10–14 days for a half marathon, and 14–21 days for a marathon or longer race. I then adjust for mileage, fatigue, terrain damage, travel, and previous response.

How much should I reduce mileage during a taper?

There is no useful percentage without a real baseline. I make the reduction meaningful, usually by shortening runs and removing costly work while preserving familiar frequency and brief intensity. The trend toward less total load matters more than hitting one universal number.

Should I stop speed work during race week?

Usually I keep a very small, familiar dose and remove most of the volume. Brief controlled repetitions or relaxed strides can preserve rhythm. I avoid exhaustive recovery, soreness, new speeds, and any session I need days to absorb.

Why do my legs feel heavy during a taper?

Routine changes, reduced training, nerves, sleep disruption, and normal day-to-day variation can all alter sensation. I use a gentle warm-up and watch the multi-day trend. Focal pain, worsening symptoms, illness, or changed gait is a different problem.

Can I gain fitness in the final week before a race?

I cannot expect a major workout’s adaptation to arrive without its fatigue. In the final week, I can improve readiness through recovery, coordination, logistics, pacing, fueling, and confidence—but I do not try to rebuild the block.

Should I rest completely the day before a race?

I choose the option that matches my established routine. Some runners feel best after complete rest; others feel better after a short easy shakeout with a few strides. Neither is universally superior, and race week is not the time for a new ritual.

What should my final hard workout look like?

It should be familiar, race-relevant, controlled, and far enough from the event to absorb. I want it to answer a specific question and finish with clean mechanics—not produce a training personal best.

What if I missed training before the taper?

I accept the fitness I have and taper from the load I actually completed. I may revise the race goal or pacing plan, but I do not cram missed long runs or intervals into the final days.

My bottom line

Knowing how to peak for a race is mostly knowing when to stop building.

I build the needed capacity, prove the specific demand, finish costly work with recovery runway, reduce volume, preserve a small familiar intensity signal, protect routine, and enter the race with pace guardrails. I watch a panel of readiness signals instead of chasing one magical feeling. My running training guide covers the wider build; this plan handles the transition from that work to race day.

The peak does not need to feel perfect. I want to arrive healthy, slightly hungry to run, and free of a final workout I am still trying to recover from. Fitness is already in the account. Race week is when I stop making deposits and prepare to spend it well.