DataFrame.fit vs TrainingPeaks

DataFrame.fit is not a TrainingPeaks replacement and not a coaching CRM. If your coach writes plans in TrainingPeaks, keep that calendar. DataFrame.fit sits on top of Garmin - and can import TP plans and TP-only sessions without double-counting rides that also land in Connect.

DataFrame.fit is not a TrainingPeaks replacement or coaching CRM. Keep TP for coach plans if you use them. DataFrame.fit adds Garmin-native depth, recovery-aware plan checks, hybrid sports, share cards, and free Google sign-in.

DataFrame.fit calendar with Garmin and TrainingPeaks plans in one week — Keep TrainingPeaks for coach plans if you use them. DataFrame.fit sits on Garmin and can import that calendar.

Keep TrainingPeaks for

Coach communication, structured plan delivery if that is how your coach works, and the TP athlete calendar. DataFrame.fit does not try to be a full coaching business tool.

What DataFrame.fit adds

Garmin-native depth: recovery-aware plan checks, quality-block compare, week compare, brick fade, hybrid sports (HYROX and CrossFit), nutrition, and share-ready cards. Sign in is free with Google. You can still pull TrainingPeaks into the same week view.

Free Google sign-in - no paid plan
Garmin wellness plus today's plan check
Compare weeks and quality-block compare across sessions
Import TP coach plans and TP-only sessions (deduped against Garmin)
Hybrid sports and brick fade that TP does not centre on
Activity, day, and week share cards

Using both

Link Garmin as the primary source, then TrainingPeaks in Settings if you need coach plans or indoor sessions that only exist in TP. MyWhoosh rides can replace matching TP-only copies when both are connected.

More about DataFrame.fit

This project is currently fully supported by Scope (www.scope.mt).

DataFrame™ is a non-commercial personal project. It is not affiliated with, endorsed by, or connected to Garmin, TrainingPeaks, Peaksware, or other fitness brands.