📊 Key Performance Indicators (KPIs)

🧮 Domains Load · Fitness estimate · Execution · Recovery · Stress 🔎 Window Mar–May
Domain KPI Current / Recent Peak / Low (Mar–May) Interpretation
Load Acute load (7d sum) 909.1 (2026-05-08) 40.8 (2026-03-25) → 1244.9 (2026-05-07) Very large ramp from late March; still a big week even after a rest day.
Load Chronic baseline (28d avg) 837.2 (2026-05-08) 358.9 (2026-04-08) Chronic rebuilt extremely fast (≈+133% in ~30 days). Good fitness return, but ramp risk exists.
Load ACWR (7d/28d) 1.09 (2026-05-08) 2.15 (2026-04-18) Now close to “balanced”; mid-April spikes were substantial.
Load TSB (freshness) -8.7 (2026-05-08) +46.0 (2026-03-23) / -67.6 (2026-04-26) You’ve moved out of the deepest fatigue zone; still slightly negative (normal in build phases).
Load Monotony (7d) (not stated for 5/8) 1.83 (2026-05-07) Early May week was high + repetitive—plan more variability next block.
Load Strain (7d) (not stated for 5/8) 2275.8 (2026-05-07) Confirms “big week” impact; treat as a peak load week that needs consolidation.
Fitness estimate Run VO₂max 62 (flat) 61–62 Algorithm is not reflecting the big load changes; use performance markers (pace/power at HR, races) to track run progress.
Fitness estimate Bike VO₂max 64 (2026-05-06) 61 → 64 Clear positive trend—bike fitness estimate is improving.
Run execution Tempo / “comfortably hard” 12.18 km @ 4:40/km, 147 bpm, NP ~409 W (2026-05-07) Strong controlled tempo: stable power, gradual HR rise = good pacing and aerobic support.
Run execution Long run endurance 21.5 km @ 5:12/km, 139 bpm (2026-04-12) Solid Ironman-relevant durability signal; ability to finish faster suggests good reserve.
Bike execution Endurance ride (outdoor) 2:19:50, NP 211 W, Avg HR 140 (2026-05-02) Good “ride to power” control outdoors; internal load higher outdoors vs indoor at similar power.
Bike execution Interval session (trainer) NP 272 W, IF 0.949, repeated ~343 W blocks (2026-04-17) Purposeful high-intensity work; strong ability to execute structure.
Swim Session volume / pace range 2.1–2.6 km, 1:34–1:48/100m Volume consistent; pace variability suggests different session intents (interval vs aerobic/technique).
Recovery Sleep duration Most days ≥7h (50/57) 4.23h (2026-03-22) Generally strong base; acute short nights are your main recovery disruptor.
Recovery HRV (sleep) 80 ms (2026-05-08) 38–103 ms Usually balanced (70–96); late April showed suppression despite decent sleep scores.
Recovery Sleep RHR typically low-40s 38–47 bpm Low baseline suggests strong aerobic conditioning; watch for upward drift when fatigued.
Stress Stress avg 11 (2026-05-08) >40 spikes on 3/21, 3/22, 4/4, 4/26 Stress avg aligns well with HRV/RHR disruptions—use it as a practical fatigue flag.

Data caution (important): repeated daily_load = 0.0 days may reflect true rest or unrecorded training; HR artifacts exist in a few activities; hydration intake logging appears invalid (often 0.0 L).

🔬 Deep Dive

📈 Load story 🏃 Run 🚴 Bike 🏊 Swim 🫀 Physiology ⚠️ Risk

1) 📈 Training Load Story: From March Reset → April Surge → Early May Peak

Phase shift and ramp

  • Mid–late March: near-stop/start training signal with many zero-load days (e.g., 2026-03-14 to 2026-03-23). Acute load bottomed (acute_ewma 16.2) and freshness peaked (TSB +46 on 3/23).
    Meaning: you were fresh, but detrained (or under-recorded).
  • Early April → early May: rapid accumulation. Chronic load bottomed 4/05 and then climbed steadily to early May highs (e.g., chronic_ewma ~52 → 131, and chronic_28d_avg ~359 → 837).

Spikes vs sustained loading

  • Mid/late April spikes: ACWR hit 2.15–2.53, with a very deep fatigue trough on 2026-04-26 (highest single-day load 503, acute EWMA max 182, TSB min -67.6).
    Meaning: there were days/weeks where short-term stress was far above what your then-current baseline supported.
  • Early May peak week (ending 5/07): not just high volume—also high monotony (1.83) and high strain (2275.8).
    Meaning: the week was big and relatively repetitive (less day-to-day variability), which tends to increase systemic stress for the same total load.

Current state (5/08): improved balance

  • After a 0-load day, your indicators moved quickly toward “manageable”: TSB -43 → -8.7 and ACWR 1.51 → 1.09.
    Practical takeaway: you now have room to either (a) sharpen for the sprint with reduced volume or (b) consolidate without losing the chronic baseline immediately.

2) 🎯 Execution Quality by Discipline

🏃 Run

Two clear “gears” with good control

  1. Steady aerobic cruising: ~5:00–5:12/km with HR in the mid-130s (e.g., 11.5 km @ 5:07/km, 136 bpm; 21.5 km @ 5:12/km, 139 bpm).
  2. Sustained tempo / comfortably hard: ~4:40/km at upper-140s/low-150s HR, with stable power and smooth splits (12.18 km @ 4:40/km, 147 bpm, NP ~409 W).

Signs of endurance + efficiency

  • The long run (21.5 km) finishing faster (last ~3 km closer to ~4:56–5:02/km with only moderate HR rise) suggests durable aerobic support and decent pacing discipline.
  • A notable marker: 10 km @ 4:52/km with 132 bpm avg (2026-05-06). Even allowing for sensor variability, that combination implies that when fresh you can run at a strong clip without high cardiovascular strain.

How this connects to load + physiology

  • Your best “quality” run (5/07 tempo) occurred during the peak week—yet execution remained controlled. That supports the idea that you’re handling training stress, but it also increases the importance of managing the next week so you don’t stack fatigue.

Run VO₂max staying flat (62) is not inconsistent with real improvement—Garmin-style estimates often fail to move when conditions vary (terrain, pacing style, warm weather, sensor noise). In your case, pace/power at given HR and race outcomes will be more trustworthy progress markers.

🚴 Bike

Two distinct archetypes—both useful

  1. Endurance/tempo rides with good pacing
    • Outdoor example (5/02): Avg/NP 202/211 W, IF 0.743, HR 140 with stable lap power despite speed changes → strong “ride to power” skill.
    • Indoor examples: ~196–198 W with low HR ~120–124 → controlled steady work.
  2. Stochastic interval sessions with real intensity
    • Trainer intervals (4/17): Avg/NP 237/272 W, IF 0.949, repeated ~343 W work blocks. NP much higher than Avg → you’re doing purposeful, structured intensity.

Indoor vs outdoor HR: important planning constraint

  • Indoors at ~198 W your HR was ~120–124 bpm, while outdoors ~202 W showed HR ~140 bpm. This can be cooling, position, terrain micro-variability, or sensor differences—but the coaching implication is consistent:
    • Anchor bike training to power, and
    • Treat HR targets as modality-specific (indoor HR will often read lower for the same external work).

Adaptation signal

  • Cycling VO₂max rose from 61 → 64, which aligns with the presence of structured intervals and sustained volume. Bike is currently your clearest “fitness estimate uptrend” in the data.

🏊 Swim

  • Session volume is consistent (~2.1–2.6 km), while average pace varies (1:34 to 1:48/100m).
  • That variability is often a good sign—likely different intents (technique/aerobic vs interval sets). Without set details, the best actionable point is to ensure you’re deliberately covering:
    • one technique/aerobic-focused swim weekly, and
    • one threshold/interval-oriented swim weekly (especially for Olympic prep).

🔁 Brick / Multisport specificity

  • The 4/26 multisport is a strong specificity indicator:
    • Run1: 4.88 km @ 3:33/km, HR avg 165 (max 183)
    • Bike: HR avg 173 (max 186)
    • Run2: 2.58 km @ 3:34/km (power still high; HR reading likely artifact on average)
  • Meaning: you can run fast off a very hard bike—excellent for sprint/Olympic racing.
  • Cost: this is systemically expensive and it coincides with your largest single-day load and lowest TSB. Treat sessions like this as key workouts with planned recovery around them.

3) 🫀 Physiology & Recovery Response (How your body is tolerating it)

Baseline: strong and stable

  • Sleep RHR consistently 38–47 bpm (mostly low-40s).
  • HRV mostly in your balanced band 70–96 ms (with normal fluctuations).

This is the profile of an athlete with good aerobic conditioning and recovery capacity.

Your clear limiter: acute sleep disruption / stress spikes

  • The standout “red” day (3/22): 4.23h sleep, score 31, HRV 38, RHR 47, stress avg 43.
  • You rebounded in ~24–72 hours (HRV back to 84–103; RHR back to ~40).

Meaning: your autonomic system is flexible, but you pay an immediate cost for short/fragmented sleep.

Late April: subtle but important strain signature

  • Late April showed suppressed HRV (e.g., 59–71 ms) even when sleep scores were good (e.g., 4/27 HRV 59 with score 86).
  • That timing overlaps your highest-load period (spikes + brick day).

Interpretation: sleep score alone may look “fine,” but HRV + load context suggests accumulated strain. This is exactly when “hold steady / add recovery” tends to beat “push more.”

Right now: good rebound signal

  • 5/08 shows low stress avg (11) and HRV (80) in balanced range. Combined with the improved TSB/ACWR, this is a strong sign you’re ready to sharpen rather than survive.

4) ⚖️ Risk / Opportunity Assessment (Integrated)

Opportunity

  • You’ve rebuilt a high training baseline early enough to meaningfully prepare for:
    • Olympic (June 7): you already have speed and bike structure; needs race-specific stamina and consistent swim quality.
    • Ironman (July 26): you have time (~11 weeks from now) to turn this baseline into durable long-course specificity.

Key risks to manage

  1. Overuse / fatigue risk from spikes
    • ACWR >2 and TSB <-60 events (mid/late April) are the “watch list” pattern. You handled it, but repeating it raises injury/illness odds.
  2. High monotony weeks
    • High weekly load + repetitive day-to-day structure is a common setup for persistent fatigue and suppressed HRV.
  3. Sleep-driven performance volatility
    • Your physiology is telling you: one bad night can noticeably reduce readiness for 1–3 days.

Data risks (so you don’t overreact to noise)

  • Several 0-load days could be unrecorded training, which would exaggerate ramp/spike signals.
  • Some HR readings look implausible (e.g., very low cycling HR, Run2 HR in multisport). Use chest strap for key sessions if possible and prioritize pace/power + RPE.

5) 🏁 Race Readiness Outlook

🏃‍♂️ Sprint (C) — 2026-05-17 (9 days away)

You’re likely well-positioned for a strong sprint because:

  • You have demonstrated high-end run speed off the bike (4/26).
  • You have recent tempo control (5/07).
  • Recovery has moved closer to neutral (5/08).

The key between now and race day is not adding fitness—it’s arriving with fresh legs and sharp neuromuscular feel.

🚴‍♀️ Olympic (B) — 2026-06-07 (30 days away)

Biggest performance levers:

  • Bike-to-run durability at controlled Olympic intensity (less “all-out brick,” more “steady-hard brick”).
  • Swim quality consistency: maintain volume + add at least one session that targets sustained efforts/turnover.

🏊‍♂️ Ironman (A) — 2026-07-26 (79 days away)

The next 6–8 weeks must shift from “load accumulation” to specific endurance + fueling + pacing discipline, while preserving one weekly intensity touch to keep VO₂/threshold from sliding.

🛠️ Recommendations (Brief, Actionable)

🎯 Goal: sharp sprint → stable Olympic build → durable Ironman block

A) ⏳ Next 9 days (to Sprint 2026-05-17): Consolidate + Sharpen

  1. Reduce volume, keep intensity touches
    • Target: ~30–40% less total load than the peak week, but keep 2 short quality stimuli (one bike, one run).
    • Avoid another monotony-heavy week: include at least one very easy day and one full rest/near-rest day if needed.
  2. One key brick only (optional), and make it “controlled”
    • If you do a brick: short bike with a few race-intensity efforts → short run with 4–8 minutes total at race cadence/pace.
    • Purpose: coordination and confidence, not exhaustion.
  3. Sleep continuity is the #1 priority
    • If you see: sleep <6h or HRV <65 with RHR elevated → immediately downshift the next day to easy or rest.
  4. Sensor/metrics sanity for race week
    • Use a reliable HR strap for key sessions if possible.
    • Don’t chase “vigorous minutes”—use pace/power + RPE.

B) 📆 Post-sprint → Olympic (May 18 to June 7): Build specificity without spikes

  1. Structure weeks to reduce monotony
    • Mix day-to-day stimulus: easy aerobic days truly easy; quality days separated by recovery.
  2. Bike: keep one interval day + one longer steady day
    • Interval day maintains the VO₂max/threshold trend you’re seeing on the bike.
    • Longer steady ride builds Olympic durability (and feeds Ironman prep).
  3. Run: one tempo/threshold focus + one longer aerobic run
    • Your tempo execution is strong—keep it, but avoid stacking it immediately after your hardest bike days repeatedly.

C) 🏁 Toward Ironman (June–July): Durability + fueling

  1. Progress long sessions gradually
    • Extend long ride/run duration in small steps; avoid repeating April-style ACWR spikes.
  2. Practice race fueling now
    • Hydration intake data is missing/invalid—start logging fluids/carbs/sodium so you can connect fueling to HRV, sleep, and performance.
  3. Keep bricks strategic
    • Use them for pacing and fueling practice (Ironman-relevant), not frequent all-out efforts.

D) 🧠 Simple monitoring rules (to operationalize the data)

Use these as “decision triggers,” not as rigid laws:

  • If ACWR trends >1.5 for several days and HRV is suppressed → reduce load 1–2 days.
  • If HRV <65 for 2 consecutive nights or RHR +3–5 bpm above your usual → shift the next session to easy aerobic or rest.
  • If monotony is trending high (lots of similar days) → add variability: one true recovery day and one different modality (swim/skills) day.

✅ Bottom line
You’ve successfully rebuilt fitness fast, with clear bike fitness gains and strong run execution markers, and your recovery profile suggests you can continue progressing—provided you manage spikes, monotony, and sleep disruptions. The next best move is a controlled consolidation to arrive sharp for the sprint, then a more structured, less spiky specificity build into the Olympic and Ironman.