How to choose a goal race time you can actually hit

Know your current fitness level

Before picking a target, run a 5K time trial on a measured route in race-like conditions—flat, well-rested, morning start. This single data point matters more than weeks of easy-run data. If you don't have a recent 5K, use your last genuine race effort at any distance as your benchmark. Software can estimate VO2 max from that, but raw numbers are more honest than calculations.

Use the 5K rule to project longer distances

A reliable shortcut: take your 5K time and multiply by these factors to estimate potential at other distances. These are approximations based on typical aerobic capacity, not guarantees, but they give you a realistic range.

• 5K to 10K: multiply by 2.05–2.15
• 5K to half-marathon: multiply by 4.5–4.8
• 5K to marathon: multiply by 9–9.5

If your 5K is 25 minutes, a half-marathon projection would be roughly 112–120 minutes (1:52–2:00). That band is where you should hunt for your goal.

Apply the safety margin

Subtract 5–10% from your projected time. This accounts for race-day variables: fuelling gaps, heat, wind, navigational errors, and the simple fact that fitness forecasts are rarely perfect. For that 2:00 half-marathon projection, a 7% margin means aiming for 1:56 instead. That feels conservative, but it's the difference between crossing the line proud and crossing it disappointed.

Build in the impact of training load

A goal time only works if your training plan gets you there. Check whether your schedule includes enough tempo work, long runs, and speed sessions to support the pace you're targeting. If you're aiming for a 1:56 half-marathon but averaging only 25 miles per week with no structured speed, that's a red flag. Either adjust the goal downward or extend your preparation window.

Account for the distance factor

Longer races expose weaknesses that shorter ones hide. Your 5K fitness might be sharp, but marathon fitness demands base-building that takes months. If you've never run the target distance before, be especially conservative. A first marathon goal should sit comfortably within your capability, not at the edge of it.

Test your goal pace in training

In the six to eight weeks before race day, run a hard session at or just below goal pace. A 90-minute run with the middle 40 minutes at race pace, or a tempo effort at goal marathon pace, tells you whether the number is real or fantasy. If you struggle at that pace in training, revise the goal. If it feels controlled, you're in the zone.

Adjust for course profile and conditions

A goal time on a pancake-flat course is quicker than the same time on a hilly route. Wind, altitude, heat, and terrain all shift what's realistic. If you're chasing a specific time on an undulating course, add 30–60 seconds per mile to your flat-ground projection. Check the course profile early and adjust accordingly.

Data-driven goal-setting with adaptive coaching

The most effective approach merges your baseline fitness data—5K time, recent race results, weekly mileage—with a clear-eyed training plan. Apps that track your workout paces, heart rate, and progression help you spot whether you're on track or drifting. Rather than guessing, you can refine your goal as training unfolds: if six weeks in you're consistently hitting paces ahead of projection, you can raise the bar. If you're falling short, you lower it without shame. Adaptive coaching that responds to real data beats rigid targets set months in advance.

Write your goal down and stick to it

Once chosen, commit to it in writing. Vague aspirations don't focus training. A specific number—'1:56 for the half-marathon on 15 June'—channels every session. You'll train differently knowing exactly what you're chasing. And on race day, that clarity becomes your anchor when doubt creeps in.