Your Realistic Half Marathon Goal Pace, From Data

You need a goal pace for race day, and you're stuck between an old PR, an aspirational number, and whatever your training has actually shown you lately. Your realistic goal pace comes from the last 6-8 weeks of training, not a PR from a year ago or a number you've picked aspirationally. Pull three data points — your threshold-run pace, your best recent tune-up race, and your long-run pace at controlled effort — check whether they agree, and below is the exact rule for which one wins when they don't, plus how to adjust for treadmill, hilly, or hot-weather training.

Pick the wrong number here and the damage doesn't show up until mile 9, when a goal your training never actually supported starts unraveling in front of everyone tracking you. Runners rarely blow up because they trained wrong — they blow up because they raced a number their own data was quietly telling them not to trust.

The Direct Answer: Audit Your Last 6-8 Weeks, Not Your Best-Ever Race

Six to eight weeks of consistent training data tells you far more about your current fitness than a race time from twelve months ago. Fitness moves — up and down — and last year's PR doesn't know about this year's training.

Pull three numbers from your recent log: your threshold-run pace, your best recent tune-up race, and your long-run pace at controlled effort. If those three roughly agree, you have a trustworthy goal. If they don't, you need a rule for which one wins — and that's the part almost nobody gives you.

Reading Your Threshold Runs

Threshold pace is a strong starting estimate, but the conversion to half marathon goal pace shifts depending on your speed. For a sub-90-minute half marathon, threshold pace is close to a direct goal-pace estimate — the two efforts sit near each other for well-trained, faster runners.

For a 1:30-2:00 finisher, add 10-20 seconds per mile to your threshold pace. For a 2:00-2:30 finisher, add 30-45 seconds per mile. The slower the finishing time, the bigger the gap between a threshold effort and a sustainable 13.1-mile race effort.

Using a Recent Tune-Up Race to Cross-Check

Race a 5K or 10K four to six weeks out from your half marathon and convert the result using a standard equivalency calculator, such as a VDOT-based tool. This gives you a second, independent number to compare against your threshold-pace estimate.

Treat this tune-up result as a ceiling check, not a replacement for your threshold-based estimate. A short race benefits from fresher legs and adrenaline that a 13.1-mile effort simply doesn't get to lean on in the same way.

What to Do When Your Data Sources Disagree

This is the exact hierarchy I apply when an athlete's three data sources disagree, stated as a direct rule rather than a hedge. If threshold pace, tune-up race, and long-run pace all land within 10 seconds per mile of each other, trust the average — you have genuine agreement.

If the tune-up race predicts a pace more than 15 seconds per mile faster than your threshold runs support, trust the threshold number. Race-day adrenaline inflates short-race predictions more than people expect. And if your long run consistently falls apart at the predicted pace, that's the overriding veto — drop the goal to match what the long run can actually sustain, full stop.

The long run beats every other data source when it disagrees, because nothing else you do in training simulates 13.1 miles of fatigue as honestly.

Downgrading a Goal Without Shame

If your data says slower than you hoped, that's the plan working as intended — training data exists to correct ambition, not just confirm it. A downgraded, data-backed goal you can execute beats an aspirational one you blow up chasing.

I've had more athletes blow up chasing an aspirational number their training never supported than I've had athletes regret trusting the data and running a smart, slightly conservative race. Let that settle the argument with yourself before race week, not during it.

Adjusting for Treadmill, Hilly, or Hot-Weather Training Paces

Treadmill paces at a 1% incline roughly match outdoor effort — use that data as-is once the incline is accounted for. If you trained predominantly on hilly routes, add back 10-15 seconds per mile to estimate your flat-course equivalent pace, since your legs have been working harder than the raw number shows.

If you trained predominantly in heat — 25°C/77°F or above — subtract 10-20 seconds per mile from your training pace data before using it to estimate a cooler race-day goal. I coached an athlete who trained an entire block on a hilly home route and initially thought his fitness had stalled, until the flat-course conversion showed he was exactly on track. The raw numbers were lying to him; the adjusted numbers weren't.

Using GPS Watch and App Race Predictors as a Sanity Check

Garmin and Strava race-predictor features, built on critical power or VO2 trends, are a reasonable secondary sanity check. Cross-reference the predictor against the three-source method above rather than trusting it alone — it's a useful second opinion, not a primary data source.

Setting a Goal Pace Range, Then Locking It In

State your final output as a 10-15 second per mile range, not a single number. Reserve the fast end of that range for good-weather, good-taper conditions on race day.

Lock the final number in the last week before race day, once taper fatigue has genuinely cleared. Committing to a specific pace too early risks anchoring to a fatigued training-block number that undersells the fitness your taper is about to reveal.

Frequently Asked Questions

What if my threshold pace and long-run pace disagree?

If your long run consistently falls apart at the pace your threshold runs suggest, the long run wins — that's the overriding veto. Drop the goal to match what the long run can actually sustain, since that's the closest simulation you have to race demands.

How many weeks of training data are enough to trust a goal pace estimate?

Six to eight weeks. That's enough to smooth out one-off bad sessions and see a genuine trend, without leaning on a PR from a year ago or a number picked aspirationally.

Should I trust a recent tune-up race or my best-ever time?

The recent tune-up race, every time. Race a 5K-10K four to six weeks out and convert it using a standard equivalency calculator, then treat that number as a ceiling check against your threshold-pace estimate, not a replacement for it.

Does treadmill training data translate directly to outdoor race pace?

Roughly, yes, provided the treadmill was set to a 1% incline throughout your training — that offsets the missing wind resistance and keeps the effort comparable. Without that incline adjustment, treadmill paces run slightly optimistic.

What if I missed key workouts during my training block?

Base your goal on the workouts you actually completed, not the ones you planned. A goal pace built on three solid threshold sessions and a consistent long run is more trustworthy than one built on a training plan you didn't fully execute.

How does training in heat or on hills skew my pace data?

Both make your training pace slower than your flat, cool-weather fitness actually is. For consistently hilly routes, add back 10-15 sec/mile to estimate flat-course equivalent pace. For training predominantly in heat above 25°C/77°F, subtract 10-20 sec/mile before using the data to set a cooler race-day goal.

Can I just trust my GPS watch's built-in race predictor?

Use it as a secondary sanity check, not your primary data source. Garmin and Strava predictors, built on critical power or VO2 trends, are reasonable cross-references against the three-source method — threshold pace, tune-up race, long-run pace — but shouldn't override it alone.

Should my goal be a single pace or a range?

A range — 10-15 sec/mile wide — not a single number. Reserve the fast end of that range for good-weather, good-taper conditions, and lock the final number in the last week before race day, once taper fatigue has cleared.

How close should my hardest training effort feel to actual race effort?

Your threshold runs should feel comfortably hard, not race-day maximal — race effort over 13.1 miles is sustained in a different way than a shorter threshold session. That's exactly why you cross-check threshold pace against a tune-up race and your long run rather than relying on any one number alone.

When should I lock in my final goal pace?

In the final week before race day, once taper fatigue has cleared and you're feeling the freshness the taper was designed to produce. Locking it too early risks anchoring to a fatigued-training-block number that undersells your real fitness.

Some Other Pages You May Like