Filing a race recap

What a recap is

A RaceRecap is a short post-race reflection logged by the athlete (one per race). It captures the subjective side that timing data alone cannot: how the race felt, what worked, what did not, what you want to do differently next time.

Where to file it

Open /my-races/<race_id>/recap/. The link appears on the race detail page after the race date passes.

Fields on the form

Overall feel

Pick one of five labels:

• Great: better than expected.
• Good: on plan.
• Mixed: some highs, some lows.
• Rough: below plan.
• Disaster: DNF or very off plan.

Overall rating

A 1 to 10 score (1 = terrible, 10 = best race ever). One number, independent of the label above.

Three narrative questions (free text)

• What went right: pacing, fueling, mental, technical.
• What went wrong: cramps, GI, weather, gear, mental.
• Lessons: what would you do differently next time.

Gear notes

Free text. Bike setup, shoes, wetsuit, kit: what worked, what did not.

Fueling notes

Free text. Pre-race meal, in-race calories and fluids, hydration. GI issues if any.

Weather notes

Short field for temperature, wind, rain, heat, but only if it materially affected the race.

What the coach sees

The recap appears on the coach side immediately. Combined with the imported timing (see Importing race results) and the activity FIT, the coach can compare:

• The plan (race plan targets (saved wizard outputs))
• The execution (actual data)
• The athlete's experience (recap)

This three-way comparison is the input for the next race planning cycle.

When to file it

Within 48 to 72 hours of the race. Earlier is better while the race is fresh. If it has been more than a week, you will still remember the broad strokes but the granular details fade.