Race-readiness report — taper-window check

What it is

The race-readiness report is a pre-race version of the post-race recap. Instead of comparing predicted vs actual splits, it scores the state of the preparation across five dimensions and surfaces the underlying data so you can see exactly what's behind each rating.

Designed to be most useful during the taper window (1–3 weeks out from an A-race), but the manual entry point on /my-races/ means coach + athlete can pull it up any time.

Where to find it

• On /my-races/ — each upcoming race card header has an orange "Readiness report →" pill next to the countdown.
• Direct URL: /race/<id>/readiness/

Permissions match the recap page: athletes see their own races, coaches see athletes they coach, superusers see all.

The 5-dimension verdict

Each dimension gets a green / amber / red badge with a one-line "why." Designed to be glanceable for the coach and actionable for the athlete.

Dimension	Green when…	Amber when…	Red when…
Volume	26-wk avg TSS ≥ distance-specific floor	within range but light	well below the amber floor
Specific work	≥3 sessions ≥70% of each leg's target	1-2 sessions in any leg	0 sessions in any leg
Thresholds	CP + run-CP + CSS all on file, ≤ 90 days	present but stale	critical metric missing
Recovery	last week 40–70% of prior 4-wk avg (in taper)	not yet tapering / over-tapered	last week ≥ 100% of prior avg in taper
Fueling	plan saved + ≥3 tested entries logged	plan saved but no logged actuals	no plan at all

Volume floors (auto-applied per race distance):

• Super-sprint: green 200 / amber 100 TSS / wk
• Sprint: green 300 / amber 150
• Olympic: green 450 / amber 250
• Middle (70.3): green 600 / amber 350
• Long (140.6): green 800 / amber 500

These are deliberately lenient floors for the general case. A real coach tunes to the individual athlete — treat the verdict as a starting point for the conversation, not a prescription.

What's in each section

Training volume — last 26 weeks

• Weekly stacked bars — one bar per ISO week, sport segments stacked (swim blue / bike orange / run green). Hover to see the exact breakdown for that week. Auto-scales to your tallest week.
• Monthly cards — 6 month summaries with total TSS + per-sport hours. Cleaner for PDF / print review.
• 4-week block averages — rolls the last 24 weeks into 6 blocks to see the macro-cycle pattern.

Race-specific work

For each leg, counts sessions in the last 6 months whose duration OR distance reached ≥70% of the race leg's target.

• Target distance comes from the race format (90 km bike for 70.3, etc).
• Target duration comes from the goal split.
• The top-3 most race-like sessions per leg are listed with date + %.

Thresholds & race metrics

Latest value + age + 6-month delta for:

• CP / FTP / W' / VO2max power (bike)
• run-CP / run-W' (Stryd)
• CSS pace (swim)
• CdA (lower = better, marked accordingly)
• VO2max / weight / sweat rate

The trend arrow (↑/↓/→) is colour-coded by direction-of-better: green when the change is good for that metric, red when bad. A stale pill (>90 days) or very-stale pill (>180 days) flags data that's overdue for a refresh.

Best performances — last 6 months

• Swim — best pace at standard distances (400 m / 800 m / 1 km / etc), taken from the per-activity best_pace_curve and aggregated to the fastest across all sessions.
• Run — same approach, with /km formatting.
• Bike — top-3 by Normalized Power, top-3 by total work (kJ), top-3 by duration. (We don't compute a full mean-max power curve yet — that's on the roadmap.)
• Longest sessions — top-3 per sport, regardless of intensity. Confirms the volume base.

Predicted splits

Pulls the model prediction from a saved triathlon_finish_time calculator result (same source as the recap) and shows it next to the goal split for each leg + the finish row.

When to run it

• 3 weeks out — first full pass to surface anything red. Time to fix big issues (missing thresholds, no fueling plan, run too short).
• 1 week out — second pass to confirm green. Recovery dimension starts being meaningful (taper window kicks in at day 14).
• Morning of race day — for the coach's pre-race brief / shareable summary.

What it doesn't tell you

• It's heuristic. The volume floors are population averages — your athlete might do well below them or need much more.
• It can't see fatigue from outside training (work, sleep, illness). Cross-reference with wellness logs.
• "Specific work ≥70%" is a coarse threshold — a 4×30min @ race-NP session might count as less specific than a 90-min steady ride at Z2, by this rule. Look at the listed top-3 sessions, not just the count.
• No PR / pacing-strategy commentary yet (that's the recap's job after the race).

See also

• Post-race recap reference
• Race comparison
• Critical Power calculator
• CSS calculator
• Race-day fueling calculator

Model engine + PDF export (May 2026)

The "Predicted splits — model vs goal" section now sources the Model column from the physiology-derived feasibility engine (athlete's current CP, CSS, run pace threshold → projected splits). This is the same engine that powers the green/amber/red feasibility gauge on /my-races/, so the readiness page and the dashboard now agree on what the athlete is realistically capable of.

If the athlete is missing the metrics the feasibility engine needs, the Model column falls back to the saved finish-time calculator result (legacy behaviour). A caption under the section title tells you which engine produced the numbers ("physiology-derived" vs "saved calculator result").

Also new: a [⬇ Download PDF] button in the top-right of the report. Generates a 2-page A4 with the verdict grid, predicted splits, thresholds table, weekly TSS chart, monthly summary, race-specific work, and best performances. Filename auto-generated from race name + date (e.g. readiness-IM-70-3-HAWAII-2026-05-30.pdf).