Exporting planned weeks (TrainingPeaks, .zwo, device .fit)

On the training calendar, tick one or more week checkboxes and a bulk bar appears with three export buttons. They serve three different destinations — pick by where the workouts need to end up.

Export to TP ↗ — the TrainingPeaks calendar

Downloads the selected weeks as dated files (.fit + a .txt description per session) plus a CSV, for putting the prescribed sessions onto an athlete's TrainingPeaks calendar on the right days. Use this when the athlete lives in TrainingPeaks and wants the plan to appear on their TP calendar.

Bike .zwo ↗ — the TrainingPeaks Workout Library

Downloads a .zip of .zwo files — cycling only — for TrainingPeaks → Workout Library → ⋮ → Import Workout. .zwo is the only format that library accepts, and only for power-based cycling, so runs and swims are skipped. These are reusable structural templates, not dated calendar entries.

Device .fit ↗ — straight onto a Garmin / Wahoo / Polar

Downloads a .zip of structured-workout .fit files — one per bike / run / swim session in the selection — for loading directly onto a device, no TrainingPeaks in the loop. This is the batch version of the .fit button on a single workout.

Load them on:

• Garmin (USB): unzip, then copy the .fit files into the GARMIN/NEWFILES folder while the device is plugged in. They show up under Training → Workouts after it syncs.
• Garmin Connect / Express, Wahoo, Polar: import the .fit files through the app's workout import, then push to the device.

Power targets are encoded in watts at the athlete's Grepiac FTP on each session's date — check the device/app FTP matches, or the target watts won't line up. Where no FTP is on file, the steps are timed with no power target (open). Run and swim files carry the same %-of-threshold structure as watts, so they're most useful with a power meter (e.g. Stryd).

Which one?

All three are coach-only, and all use the same week selection.