Complete Your First Sprint Triathlon

Proof required

Submit: (1) Strava activities or GPS logs from at least two open water swim sessions of 500m+ each (activity exports showing map, distance, and date), and (2) a pool swim activity confirming 750m+ completion without stopping.

What gets checked

• Two open water swim sessions are documented with GPS — the activities must show open water (not a rectangle, not a pool shape); map view on Strava or Garmin Connect makes this clear; the distance for each session must be 500m or more
• Pool 750m is completed without stopping — a pool activity showing 750m continuous is required; stopping at the wall for 30 seconds does not constitute stopping; stopping for 2+ minutes to rest does; the 750m should be swum in a single unbroken effort to simulate race conditions
• Open water experience is recent — within 8 weeks of the target race; an open water swim session from 6 months ago does not demonstrate current readiness for a race; recency matters because cold water conditioning is time-sensitive

Common mistakes

• Not practising in open water before race day — the open water swim section of a sprint triathlon causes more DNFs (did not finish) than any other section, not because of fitness but because of panic; the experience of murky water, being surrounded by other swimmers, and the absence of lane lines triggers anxiety in swimmers who have only trained in pools; get at least two open water sessions before race day regardless of pool ability
• Not practising sighting — sighting (lifting the head forward to spot the buoy while swimming) is a technique that pool swimming never requires; untrained triathletes typically swim 200–400m extra distance because they cannot maintain a straight course without lane lines; practise sighting every 10 strokes in both pool and open water sessions; it is a skill that takes time to make automatic
• Entering a triathlon without a wetsuit when conditions require one — most sprint triathlon events take place in waters below 20°C; a wetsuit is required below 14°C and strongly advisable between 14–20°C; triathletes who swim in cold water without a wetsuit lose body heat rapidly and their swimming technique degrades; confirm the race's wetsuit rules and water temperature before race day

Resources

What a verifier looks for

• Check the swim activities for open water — open Strava or Garmin Connect activity links if possible; a pool swim shows a rectangle track; an open water swim shows a natural water body shape; confirm at least two activities are open water
• Verify the 750m pool session is without a stopping rest — a Strava or Garmin pool swim showing 750m as a single effort passes; a session showing 10 × 75m with rests between is pool fitness but not race-simulation swimming
• Ask about wetsuit use and water temperature — 'what was the water temperature at your open water sessions?' and 'will you use a wetsuit on race day?' helps confirm race preparation is realistic

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

Proof required

Submit: Strava activity links or GPS exports for at least three brick sessions (each showing a bike segment followed immediately by a run segment on the same day, with dates). The final brick should be close to sprint race distances (15km+ bike, 2km+ run).

What gets checked

• Three distinct brick sessions are documented — each session must show both a cycling and a running activity on the same day; they do not need to be in the same Strava 'multi-sport' activity but both activities should share the same date; three sessions on three separate days across at least 2 weeks
• The final brick approaches sprint race distances — a final brick of 15km+ cycling followed immediately by 2km+ running simulates the race segment; a final brick of 5km cycling and 500m running is insufficient preparation for the race legs; the distances should progressively build toward race distances
• Sessions are post-bike run, not pre-bike run — a 'brick' is specifically cycling then running; a run followed by cycling is not a brick and does not produce the brick legs adaptation; confirm the activities are in the correct order

Common mistakes

• Not doing bricks and planning to 'manage the run' on race day — experienced triathletes who skip brick training in a training block consistently report that the run leg is worse than expected; brick training is not optional; it is the specific adaptation that makes the run leg possible; three sessions over 3 weeks is the minimum required
• Using a turbo trainer (indoor bike) and not doing outdoor cycling — turbo trainer sessions improve aerobic fitness but do not simulate the demands of cycling on a road or triathlon course (weather, terrain variation, bike handling, cornering); at least one brick session should include outdoor cycling on terrain similar to the race course before race day
• Not practising transitions — the T1 (swim to bike) and T2 (bike to run) transitions are timed in a triathlon and account for 1–3 minutes of total race time; untrained transitions involve fumbling with gear, shoes, helmets, and racking the bike; practise the transition at least once before race day, including the sequence of putting on the helmet before unracking the bike (penalty if violated at TRIUK/BTF events)

Resources

What a verifier looks for

• Confirm each brick session shows both cycling and running on the same date — check that the bike and run activities share the same date in Strava or the GPS export; a brick session where the run was done the next day is not a brick
• Check the final brick distances against race distances — the final brick before the race should be at least 15km cycling and 2km running; a final brick of 5km is undertraining for the sprint race bike leg of 20km
• Ask about transition practice — 'have you practised T1 and T2?' is a useful question; a competitor who has not rehearsed the transition will cost themselves time and potentially a penalty on race day

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

Proof required

Submit: (1) the official chip-timed result from the event (link to the official results page showing your name, race number, and finish time with splits), and (2) a 100+ word post-race reflection covering what the race experience taught you that training could not prepare for.

What gets checked

• Official chip-timed result is present — a link to the official results page (e.g. ChronoTrack, Race Roster, BTF results portal) or a screenshot showing the student's name, bib number, and finish time with swim/bike/run splits; a screenshot of a personal GPS watch showing total time without an official result does not pass
• Reflection is 100+ words and specific to the race experience — a reflection that could have been written without competing ('triathlon is hard and I felt tired') does not pass; the reflection should name specific moments, unexpected challenges, or observations about the race that training could not simulate; the swim start chaos, the brick legs at T2, the last kilometre of the run when energy is depleted — any specific moment that reveals something training did not prepare for
• Race is at a registered sprint triathlon event — the event must be organised by a recognised triathlon federation (BTF, Triathlon Ireland, Triathlon England) or a registered event organiser; a 'triathlon' organised by a local running club that is not officially sanctioned does not produce the results documentation required

Common mistakes

• DNF (Did Not Finish) and treating it as a finish — a DNF is not a finish; if the race was not completed (exited the water, withdrew from the bike leg, stopped running before the finish line), the milestone is not met; a DNF is not a failure as an experience but it does not satisfy the milestone requirement; register for a subsequent sprint triathlon after addressing what caused the DNF
• Using a GPS watch time as the official result — personal GPS watch totals differ from chip times due to the distance between the start timing mat and the swim start, and the precision of GPS tracking through the water; the official chip-timed result from the event timing service is the only accepted documentation
• Not writing the reflection until long after the race — post-race reflections written 3 weeks after the event are typically more generic than ones written within 48 hours while the specific sensations are fresh; write the reflection the day after the race while the swim start chaos, the brick legs, and the run finish are still specific in memory

Resources

What a verifier looks for

• Verify the result on the official results page — the link or screenshot should show the student's name, bib number, finish time, and split times; a GPS watch screenshot without an official result does not pass
• Confirm the event is a registered sprint triathlon — search the event name; it should appear on BTF, Triathlon Ireland, or an equivalent national federation's registered event list; an unregistered 'fun triathlon' does not produce the results documentation required
• Read the reflection for race-specific observations — ask 'what was the hardest moment and what caused it?' if the reflection is too generic; a specific answer ('the swim start when 60 people went off at once and I got knocked' or 'the last 500m of the run when I had nothing left') demonstrates genuine completion

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