Run a Marathon Under 4 Hours

Proof required

Submit your official half marathon chip time from a registered race. Acceptable sources: official race results URL showing your name and chip time, a finisher certificate from the race app, or a race bib photo alongside the official results page. GPS watch time from a solo run is not accepted for this milestone.

What gets checked

• Official chip time from a registered half marathon race — not a solo GPS run or a 'virtual race' unsupported by a race organisation
• Race name and date are visible in the evidence
• Time is plausible as a sub-4h marathon predictor: finishing times up to 2:20 are realistic for someone early in their marathon training

Common mistakes

• Running the half marathon too hard and compromising the training block — a blown half-marathon 10 weeks before the goal race leaves the athlete in a recovery hole during peak training weeks; race it at controlled effort, not all-out
• Using a solo GPS run as a substitute for a registered race — race conditions (hills, weather, late-mile pressure) differ significantly from training runs, and the chip time is the non-falsifiable proof standard
• Not registering for the half until the milestone is approaching — popular half marathons sell out weeks in advance; registration should happen at the start of the training block

Resources

What a verifier looks for

• Evidence type check: an official race results URL, finisher certificate, or bib-plus-results photo. A GPS watch screenshot from a solo training run does not satisfy this milestone.
• Time plausibility: half marathon times under 1:20 suggest significantly more running background than the outcome implies. Times up to 2:30 are realistic for a runner who started training specifically for this outcome.
• Virtual race check: if the athlete submits from a 'virtual' race, verify it was organised and timed by a race organisation — self-organised virtual marathons with no independent timing are not accepted.

Proof required

Submit GPS watch data from a continuous 20-mile (32km+) training run including total distance, total time, and average pace. Acceptable formats: Garmin Connect or Strava activity screenshot, or a Strava public activity link. The average pace must be within 45 seconds per mile of stated goal marathon pace.

What gets checked

• Distance ≥ 20 miles (32.2 km) confirmed in GPS data — not estimated or manually entered
• Average pace within 45 seconds of the stated goal marathon pace; a 20-miler significantly faster than 9:09/mile for a sub-4h goal indicates over-pacing that increases late-race injury risk
• Run completed in a single continuous session — the distance must not be split across two separate runs on the same day

Common mistakes

• Running too fast — the most common error; the 20-miler must be run at goal marathon pace, not the pace the athlete feels good at on fresh legs; 30 seconds per mile too fast over 20 miles compounds into significant over-exertion and a longer recovery than the taper allows
• Skipping mid-run fuelling practice — at 3+ hours, glycogen depletion is a race-day variable; the 20-miler is the one opportunity to test the fuelling strategy (gel timing, type, water volumes) that will be used on race day
• Scheduling the long run too close to race day — it must complete 3–4 weeks before the race to allow a proper 2–3 week taper; a 20-miler two weeks before race day leaves no taper window

Resources

What a verifier looks for

• GPS data must show ≥20 miles as a single continuous session — check that it is not two separate activities added together
• Pace check: for a sub-4h goal, the long run should average 9:00–9:45/mile. A 20-miler run at 7:30–8:00/mile indicates a substantially stronger athlete than the goal implies, which may affect readiness assessment
• Strava and Garmin both show 'moving time' vs 'elapsed time' — verify the split map covers the full 20 miles; an elapsed time with long walk-stop gaps may indicate multiple sessions
• Walk breaks are permitted and expected in an endurance long run; the milestone requires a single continuous session, not unbroken running

Proof required

Submit your official chip time from a registered marathon race. Acceptable sources: (1) official race results URL showing your name and chip time ≤ 3:59:59, (2) a finisher certificate from the race app showing chip time, or (3) a race bib photo alongside the official results URL. The time must be chip time, not gun time.

What gets checked

• Official chip time ≤ 3:59:59 from a registered marathon race — gun time, GPS watch time, and virtual marathon self-reported times are not accepted
• Race is a registered, timed marathon (USATF-certified, UK Athletics-certified, AIMS-certified, or equivalent national athletics body) — not a 'virtual marathon'
• Name and chip time are visible in the submitted evidence without manual image editing

Common mistakes

• Finishing in 4:01–4:10 after a strong training block — this is the most common outcome for a first sub-4h attempt, often caused by positive-splitting (running the first half faster than the second); the right response is to enter the next race with a conservative early-race pacing plan
• Blowing up at mile 20 by over-pacing miles 1–15 — the euphoria and crowd energy of a large marathon reliably produces a first-ten-mile pace that is 15–20 seconds per mile faster than goal pace; the only defence is a pace band on the wrist and a commitment to ignore early-race energy
• Selecting a hilly or hot course for a first sub-4h attempt — the outcome is achievable on any course, but the risk-adjusted approach is a flat, well-supported, cool-weather certified course

Resources

What a verifier looks for

• Verify the evidence shows chip time specifically — finisher certificates and official results pages both display chip time separately from gun time; accept chip time only
• Race legitimacy check: all registered marathons with official timing produce a results URL within 24–48 hours of the event; ask for the official results page if only a finisher certificate is submitted
• Virtual marathon check: self-organised 'virtual marathons' without independent timing do not satisfy this milestone; the race must have chip timing administered by a timing company
• If the submitted time is 4:00:00 exactly, this is the chip time — it does not satisfy the sub-4:00:00 standard; only 3:59:59 or faster counts