The race planning workflow end to end

The 7 steps

The Hub structures race planning as a deterministic workflow. Run it the same way every time and the saved race plan stays consistent.

1. Add the race

Athlete or coach creates the race at /my-races/ (athlete side) or /coach/race/new/ (coach side). Required: athlete, name, date, sport / distance. See Adding a race.

2. Tag priority and periodization

Set the priority (A, B, or C; see A vs B vs C race tagging) and pick the periodization approach for this race build (linear, reverse linear, block, undulatory). Periodization is a property of the race, not of the macrocycle. See Choosing a periodization model.

3. Check readiness of underlying metrics

Open /admin/race/<race_id>/readiness/. Look at how fresh the athlete's CSS, CP / FTP, run threshold, weight, and other metrics are. Retest anything expired or missing before running the wizard. See Race readiness checklist.

4. Run the planning wizard

Open /admin/race-planning-wizard/<race_id>/. Work through the seven calculator steps (CSS, CP, CdA, bike plan, finish time, calories, fueling). Each step saves a CalculatorResult linked to this race. See Race planning wizard tour and The race plan: where saved outputs live.

5. Race week and race day

Use the saved wizard outputs (bike target watts, run pacing, hour-by-hour fueling) as your race day plan. Print or screenshot the calculator outputs you want trackside.

6. After the race: import results

Open /admin/race/<race_id>/import-results/. Paste timing or upload the race FIT. The Hub builds the post-race comparison against the saved wizard targets. See Importing race results.

7. File a race recap

Athlete fills /my-races/<race_id>/recap/. The coach reads the recap alongside the imported timing and the race FIT to close the loop on this race and inform the next one. See Filing a race recap.

Skipping steps

You can skip steps but each one improves the next. A race with no priority falls into the planner with default rules. A race with no readiness check still runs the wizard but with the projection drift you accept by ignoring stale metrics.