Train for and Run a Trail Race

Proof required

Submit a Strava or GPS app export showing at least 8 weeks of running with at least 24 sessions, weekly elevation gain of at least 200m in most weeks, and at least one run per week of 10km or more. The activity type should be 'Trail Run' or equivalent where possible.

What gets checked

• At least 24 sessions over 8 calendar weeks visible in GPS data
• Weekly elevation gain of 200m or more in at least 5 of the 8 weeks
• At least one run per week exceeding 10km shown in the data

Common mistakes

• Training entirely on flat roads and expecting trail performance to transfer — ankle proprioception and downhill technique require actual trail and hill time
• Running the long run at the same pace as road running — trail and elevation slows pace significantly; running by effort rather than pace prevents early dropout
• Not recording sessions in a GPS app that shows elevation — without elevation data, the vertical gain claim cannot be verified

Resources

What a verifier looks for

• Elevation data must come from GPS tracking — Strava segments or manual entries without GPS cannot confirm vertical gain
• Check that at least 5 of the 8 weeks show 200m+ elevation gain — a single high-elevation week does not constitute trail training
• At least one 10km+ run per week: check the weekly long run distance in the GPS data for each of the 8 weeks

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

Proof required

Submit either: (A) an official trail race finish certificate or result listing your name, race name, distance, and finish time; or (B) a GPS recording showing a single continuous effort of 15km or more on trail with 400m+ elevation gain, date visible, and a 100-word reflection on pace management and trail conditions encountered.

What gets checked

• Option A: official race result with name, distance ≥10km, and finish time from a publicly verifiable event
• Option B: single GPS-recorded effort of ≥15km with ≥400m elevation gain as one continuous activity
• Option B also requires a 100-word reflection — not just a GPS record

Common mistakes

• Choosing a race with a course cutoff shorter than your expected finish time and being timed out — check historical finish times for the race before entering
• Attempting the long effort on a day with poor weather and abandoning halfway — a failed DNF does not satisfy this milestone; check conditions and choose a backup date
• Not downloading the GPS recording immediately after the effort — auto-sync failure on the day means a lost proof record

Resources

What a verifier looks for

• Option A: trail race result must be from a publicly findable event — search the race name and year online to cross-check the result
• Option B: GPS recording must show a single continuous activity (not stitched) of ≥15km with ≥400m elevation — check for unusual elevation spikes that might indicate GPS error rather than real climbing
• The 100-word reflection (Option B only) should mention specific trail conditions and pacing decisions — generic effort descriptions without trail detail suggest indoor or road running re-labelled

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

Proof required

Submit your official race finish result (result URL, finisher certificate, or photograph of the results board with your name visible) for a trail race of at least 15km with 500m+ elevation gain. Include a 200-word race report covering: pre-race goal vs. actual result, the hardest section of the race, and one thing you would train differently for the next race.

What gets checked

• Official finish result showing name, race name, distance ≥15km, and finish time
• 200-word race report covering pre-race goal, hardest section, and one training change — not a generic 'it was great' summary
• Race must be on trail terrain with ≥500m elevation gain — flat road race with 'trail' in the name does not satisfy this

Common mistakes

• Not building a taper (reducing volume 10–14 days before race) and arriving fatigued — trail races with elevation are harder than road races of the same distance; taper matters more, not less
• Not filing a race report in the 48 hours after finishing while the experience is fresh — reconstruction from memory two weeks later produces generic responses that fail the quality check
• Choosing a race where online results are not published and no finisher certificate is issued — the external result verification must be available

Resources

What a verifier looks for

• Search the race name and year online to find the official results page — the submitter's name should appear with finish time
• The 200-word race report must mention a specific section by name (e.g. 'the second climb after kilometre 8') — generic reports without course-specific detail suggest the race was not run
• Check that the race distance is ≥15km and the course has ≥500m elevation gain — many events labelled 'trail race' are flat park runs; confirm from the race website

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