Race readiness checklist

What readiness is

The readiness page (/admin/race/<race_id>/readiness/) is a discipline-by-discipline audit of how fresh the athlete's threshold metrics are. Each metric is tagged fresh, stale, expired, or missing based on how long ago it was last tested. The page shows the overall readiness as a percent (fresh / total).

What it checks (by discipline)

Swim

• CSS pace.
• Swim HR threshold.
• Sweat rate (general).

Bike

• Critical Power (CP).
• W' (kJ).
• FTP.
• CdA.
• Bike HR threshold.
• Bike speed threshold.
• Sweat rate (bike).

Run

• Run threshold pace.
• Run HR threshold.
• Run Critical Power.
• Run W' (kJ).
• RSI.
• Sweat rate (run).

Physiology

• VO2max.
• Gross efficiency.
• Weight.
• Body fat.
• RMR.

How freshness is computed

Each metric has its own age band that defines fresh / stale / expired. The thresholds live in core.models.metric_history.metric_freshness. Newer is better; older starts producing warnings.

What you see for each metric

• Status label (fresh, stale, expired, missing).
• Current value if present.
• Date it was logged and age in days.
• Source (which assessment or calculator produced it).
• Retest link that opens the appropriate calculator if you want to rerun the test.

Why it matters

The race planning wizard pulls these threshold values to project pacing, fueling, and finish time. If FTP is 8 months old, the bike plan is built on a number that no longer reflects reality. The readiness page is the early-warning system.

When to retest

A common rule of thumb for an A race:

• Swim CSS within 60-90 days.
• Bike CP/FTP within 60-90 days.
• Run threshold pace within 60 days.
• Weight within the last 30 days.

You can still run the wizard with stale metrics; the readiness score just flags how much projection drift you should expect.

What it does NOT check

The readiness page is intentionally narrow: it audits metrics, not equipment, course files, fueling plan completeness, or athlete acknowledgement. Those live elsewhere in the workflow.