Run 5K Under 20 Minutes

Proof required

Submit an official chip-timed 5K result under 25:00 from a parkrun, road race, or athletics club open event, with your name and event date visible. If this was submitted for a previous outcome, a link to that result is sufficient.

What gets checked

• Official chip-timed result under 25:00 from a publicly verifiable event
• Current VO2max estimate from a GPS watch or fitness tracker (if available) — Garmin, Polar, Apple Watch, Fitbit all provide this; a value above 45 mL/kg/min correlates with sub-20 potential
• 12-week plan with two quality sessions per week identified before starting

Common mistakes

• Starting sub-20 training from a 27-minute base — the gap is too large for a single mesocycle; consolidate sub-25 first
• Not tracking VO2max trend over training — it should rise 1–2 mL/kg/min per 8-week block when training is working
• Choosing a 12-week plan without periodisation (easy week every 4th week) — accumulation without recovery stalls adaptation

Resources

What a verifier looks for

• Verify the sub-25 baseline result is from an official chip-timed event — same standard as sport-run-5k-under-25min M3
• Check that the 12-week training plan includes at least two quality sessions per week (intervals or tempo) and one easy week every 4 weeks
• A VO2max estimate is optional but valuable — if provided, above 45 mL/kg/min correlates with sub-20 potential at the right fitness

You'll sign in first, then come straight back here.

Proof required

Submit a Strava or GPS app export showing 12 weeks of training with at least 24 quality sessions (labelled or paced as intervals or tempo runs), average pace on quality sessions in the 4:45–5:50/km range, and weekly mileage of at least 25 km. Include a 200-word reflection on how your quality session paces changed from week 1 to week 12.

What gets checked

• At least 24 quality sessions (intervals or tempo) over 12 weeks with GPS data
• Quality session pace averaging 4:45–5:50/km for interval efforts visible in the data
• 200-word reflection naming specific sessions where pace improved and where form broke down

Common mistakes

• Running quality sessions too fast (under 4:30/km) and accumulating fatigue that prevents completing the next session — sub-20 pace is 4:00/km; train at 4:45–5:10 to stimulus-adapt without burning out
• Skipping easy days and replacing them with moderate effort — 'junk miles' at medium intensity neither build aerobic base nor stimulate speed adaptation
• Not recording every session, so the 12-week pattern cannot be documented as proof

Resources

What a verifier looks for

• Count quality sessions in the GPS archive — at least 24 sessions at interval or tempo pace across 12 weeks
• Check average pace on quality sessions — should be 4:45–5:50/km for a sub-20 candidate; faster than 4:30 suggests overtraining, slower than 6:00 suggests aerobic runs mis-labelled as quality
• The 200-word reflection should name specific sessions (week X, Y×Z intervals at W/km) — generic answers do not confirm the training was real

You'll sign in first, then come straight back here.

Proof required

Submit the official race result URL or screenshot showing your name, event name, date, and finish time under 20:00. A parkrun result page at parkrun.org.uk showing your finisher page is accepted and preferred.

What gets checked

• Official chip-timed 5K result under 20:00 from a publicly searchable event
• Result includes your name — not an anonymous time
• A sub-20 chip result from parkrun can be cross-verified by searching the runner's name on parkrun.org.uk

Common mistakes

• Arriving at race day without a 2-week taper — interval training within 10 days of goal race leaves residual fatigue that costs 30–90 seconds
• Going out at 3:50/km for the first kilometre and dying in the final two — sub-20 requires consistent 3:58–4:02/km across all five kilometres
• Choosing a course with significant elevation gain — sub-20 requires a flat or net-downhill certified course; hilly parkruns can add 60–120 seconds

Resources

What a verifier looks for

• Official chip-timed result required — a GPS watch showing 4:00/km average on a training run does NOT satisfy this milestone
• For parkrun: search the submitter's full name on parkrun.org.uk results to cross-check the time and date
• For road races: event name + date + finish time should appear on the race timing service (Sport:80, RunThrough, Athletics Data, Active.com, etc.)

You'll sign in first, then come straight back here.