Hi Riccardo,
Are you adding a RACE event in Calendar? (as opposed to workout) for both 28 June and 5 July.
For example these would then show as following when asked show all planned events
| Date |
Event |
Type |
Duration |
Priority |
| Jun 28 |
A Race |
Ride |
120m |
Priority |
| Jul 5 |
A Race |
Ride |
120m |
Priority |
Then you can ask to plan for these races. Show a preparation plan for these races
Does this achieve what you want?
Here is a race-specific preparation plan for your two A races:
June 28
July 5
This is a 3-phase build → taper → race → recover → sharpen model, aligned with your current state (aerobic strong, VO2 slightly drifting, intensity clustering risk).
MACROCYCLE STRUCTURE
Phase Map
- Now → June 8 → Aerobic + VO2 rebuild
- June 9 → June 22 → Race-specific sharpening
- June 23 → June 28 → Taper → Race 1
- June 29 → July 5 → Recovery + Race 2 peak
PHASE 1 — BUILD (NOW → JUNE 8)
Objective
- Maintain aerobic dominance
- Reintroduce clean VO2 stimulus (without clustering)
- Improve fatigue resistance
Weekly Structure (ideal)
| Day |
Session |
| Mon |
OFF / Recovery |
| Tue |
VO2 (4–6 × 4–5min) |
| Wed |
Z2 Endurance |
| Thu |
Tempo / Sweet Spot |
| Fri |
Easy / OFF |
| Sat |
Long Ride (3–4h) |
| Sun |
Endurance (low stress) |
Key Fix (from your data)
No more stacking: VO2 → Long → Threshold
Instead:
- Always insert low day after VO2
- Keep 2 hard days max per week
PHASE 2 — SHARPEN (JUNE 9 → JUNE 22)
Objective
- Convert fitness → race performance
- Increase race-like intensity + repeatability
- Reduce volume slightly
Weekly Structure
| Day |
Session |
| Mon |
OFF |
| Tue |
VO2 (shorter, sharper) |
| Wed |
Z2 |
| Thu |
Threshold / race simulation |
| Fri |
Easy |
| Sat |
Race simulation / hard group ride |
| Sun |
Endurance |
Key Workouts
- VO2: 4x4 / 5x3 (high quality, not exhaustive)
- Threshold: 2x20 or over-unders
- Race sim: stochastic efforts (attacks, surges)
PHASE 3 — TAPER (JUNE 23 → JUNE 28)
Objective
- Reduce fatigue
- Maintain intensity
- Arrive fresh but sharp
Structure
| Day |
Session |
| Mon (23) |
OFF |
| Tue |
Short VO2 (3x3) |
| Wed |
Easy Z2 |
| Thu |
Openers (short efforts) |
| Fri |
OFF |
| Sat |
30–45min activation |
| Sun |
RACE 1 |
Rules
- Cut volume 40–60%
- Keep intensity but very low density
- No long rides this week
BETWEEN RACES (JUNE 29 → JULY 5)
This is where most athletes fail.
Objective
- Recover from Race 1
- Maintain sharpness
- Avoid fatigue carryover
Ideal Week
| Day |
Session |
| Mon |
OFF |
| Tue |
Recovery spin |
| Wed |
Openers (short VO2) |
| Thu |
Easy |
| Fri |
Openers |
| Sat |
30min activation |
| Sun |
RACE 2 |
Critical Rule
DO NOT train fitness this week
You are NOT building anymore — only:
- Recover
- Maintain sharpness
YOUR PERSONAL LIMITER (VERY IMPORTANT)
From your data:
Your limiter is NOT fitness — it’s intensity distribution
So your race success depends on:
- Spacing intensity
- Avoiding hidden fatigue
- Arriving fresh
PERFORMANCE STRATEGY
Race 1 (June 28)
- You should be at peak fitness
- Execute aggressively if needed
Race 2 (July 5)
- You will NOT gain fitness
- Goal = better freshness + execution
FINAL COACHING TAKE
If you follow this correctly:
- You won’t feel “overtrained”
- Your VO2 will come back up
- You’ll convert aerobic strength → race performance
Next Step (recommended)
Say:
“optimize my calendar for this plan”
I’ll:
- Rewrite your actual scheduled workouts
- Fix intensity clustering
- Align everything to peak perfectly for both races
Top tip. Use the word “replace” to update Calendar events (it will use ID if known first and then date if ID not known).
also, btw if you add in RACE style that helps
e.g.
Name: Marmotte 2026 | A Priority | Climbing focus
But now you have me thinking about how to include a Target RACE Events layer inside a report
to complement Adaptive Decisions (ADE). This would be cool.
Clive