Three disciplines, one plan.

Separate tools for each sport give you three separate verdicts that rarely line up. Your running app says your ramp is fine, your cycling app says fitness is climbing, your swim log looks boring, so all-green, push harder. Two weeks later you’re flat.

The failure is structural: none of those tools see the other two. So nobody is computing the only number that matters — how hard you’re training overall. ZoneTwo computes it.

Combined CTL, combined ATL, combined TSB. Combined Foster monotony. Combined strain. Cross-discipline rule checks. It’s one athlete getting coached, not three.

A recent example, 42-year-old male, Olympic-distance target 8 weeks out:

• Summary: 3 weeks of productive build (CTL 40 → 47). Swim volume lagging primary-sport declaration.
• Concerns: DISCIPLINE_NEGLECT (0 swim sessions last 14 days); monotony 1.6 trending up.
• Next block: 3-week build → peak. 2 rides, 3 runs, 2 swims, one brick. Hard days Tue + Sat, 48h apart. Week 3 = deload before race-specific work.
• Progression: Week 1 as template. Week 2 Saturday long ride +20 min. Week 3 deload, drop Thursday intervals.
• Red flag response: Two swim sessions added back in immediately, acknowledged discipline neglect in the rationale.

Set your race date in your profile and the coach computes weeks-to-race for every block:

• 8+ weeks out: base or early build, volume matters.
• 4–8 weeks: build with race-specific intensity. Brick workouts start appearing.
• 2–4 weeks: peak. Race-pace efforts, sharpening.
• 1–2 weeks: taper. Volume drops 40–60%, intensity stays.
• Race week: short sharp openers only.

None of this is a rigid 16-week plan locked in September. The coach re-evaluates every Sunday based on what actually happened. Missed a hard week because of travel? The block shifts. Added a new long ride that wasn’t prescribed? The next review notices and adjusts.