For runners, TrainingPeaks is primarily a shared workspace for planning, coaching collaboration and completed training. A well-defined workout can reach your watch, the completed recording return to the calendar, and your coach see what happened relative to the target. Basic accounts, Premium analysis and different watches’ sync involve different permissions and technical requirements.

This guide is based on TrainingPeaks documentation checked on 21 November 2026. Rather than our own product test, it uses original operating examples to show how a written workout idea becomes an executable watch task and what to consider when interpreting load figures.

1. Basic or Premium: working with a coach need not require paid access

The Basic–Premium comparison permits both tiers to log workouts, upload supported-device data, view summaries, track equipment and work with a coach or training plan. Premium adds tools for your own future planning, larger libraries, detailed analysis and the Performance Management Chart. Free Basic is therefore more than an empty preview, without being the complete analysis package.

According to the table for coach accounts, a coach can also plan for a Basic athlete. The athlete’s own editing and analysis options remain narrower, however. At the start of collaboration, clarify who moves workouts, updates thresholds and receives changes in your availability. A missing button may concern permissions rather than incorrectly imported training.

Our decision example: if your coach creates the week while you follow it on your watch and give brief feedback, your feature needs differ from independently building multimonth plans and regularly analysing splits. Write three sentences describing what you want to do personally in the interface. Compare plans afterwards, rather than assuming every runner needs the same Premium use.

2. A structured workout is more than typed instructions

The Workout Builder updated on 17 November 2026 describes distance-, time- and intensity-based editing using power, heart rate, pace or perceived effort. Targets may be single values or ranges, adjustable per interval. Device sync requires a structured workout. A clear free-text description of a runner’s task does not automatically become a watch-guided sequence of repeats.

Our editing example: 9 introductory minutes, four repetitions of 3 minutes of work and 90 seconds of recovery, then 7 minutes to finish. This is 9 + 4 × 4.5 + 7 = 34 minutes. Omitting the last recovery gives 32 minutes 30 seconds. The example illustrates block logic rather than personal intensity advice. Check sequence and repetition count first, targets afterwards.

The editor supports work, recovery, warm-up, cooldown and repeating blocks. An open interval ending with the lap button can also be configured for a compatible device. Changing an interval’s target alters the current workout; create a copy first for a separate version. This support detail matters when preserving the same structure separately with pace one time and heart rate another.

3. The same threshold and sport should underlie a percentage

A percentage target becomes a specific task only with its reference value. Percentage of maximum heart rate, reference to threshold heart rate and threshold pace have different starting points. “Easy” or “tempo” in a title does not replace clarification of the selected method. If working with a coach, record the target system and how settings are updated together.

The Garmin AutoSync support explicitly states that the TrainingPeaks threshold for the relevant workout type must be set correctly for targets to appear properly. TrainingPeaks is the primary source for values sent to the watch. A threshold for another sport or an old setting can therefore produce a functioning yet misunderstood watch target. Successful data transfer does not equal a professionally appropriate target.

To check, open a known workout on phone and watch. Do units, target type, repetition count and range match? Kilometre- and mile-based displays can give different impressions if you examine numbers alone. Record threshold-change dates too: later comparisons need to distinguish changed actual difficulty from a changed reference.

A runner completes a controlled interval on the track while a coach observes their agreed target-pace practice.Enlarge image
AI-generated editorial illustration of focused practice at race pace; not a documentary photograph or a performance prediction.

4. Garmin: a rolling fifteen-day window and two sync steps

The Garmin guide says upcoming structured workouts enter Connect’s calendar in a rolling fifteen-day window. Editing, moving or renaming a workout can reach Connect, but the watch then needs separate sync. Edit TrainingPeaks-originated workouts in TrainingPeaks rather than Connect. Later changes to already completed workouts do not re-enter the planned Garmin workout.

Not seeing your entire marathon preparation on the watch therefore need not mean the connection is broken within its stated fifteen-day window. Find today’s or tomorrow’s workout first. Missing distant weeks differs from an absent supported workout scheduled today. Naming the fault precisely shortens investigation and avoids unnecessarily dismantling a working account connection.

The TrainingPeaks compatibility table lists interval types, targets, secondary fields and open steps separately by device. Compare the intended workout with the exact receiver’s capabilities. If a secondary target does not transfer, the main instruction may still work; test this before running. A compatible brand alone does not establish unchanged transfer of every edited field.

5. Apple Watch: native Workout has separate limitations

The updated Apple Watch support describes structured programmes sent to native Workout. By default, today and the next six days transfer; manual sending is also available. RPE-based programmes and purely textual, unstructured tasks do not sync. In indoor running, the pace target’s range does not appear at interval transitions; the current description also does not support secondary targets.

The support page pairs iOS 17.2–18 with watchOS 10.7 or later, and iOS 26 with watchOS 26. Its hardware paragraph also gives a lower watchOS number and does not provide a separate pairing for version 27 systems. We do not turn this into guaranteed compatibility for every old and new combination. For borderline or freshly updated systems, confirm your current phone–watch pair with TrainingPeaks support.

Apple Watch running-power measurement and displaying a TrainingPeaks target are separate questions too: current support names Ultra for running-power targets. The same description says daily Apple Health data, such as sleep or resting heart rate, do not sync through this path. A completed workout arriving therefore does not establish a full daily health-data connection. Try the specific function your use requires.

6. rTSS, hrTSS and power: the letters identify inputs

The TSS explanation requires pace and elevation data over time, plus running threshold pace, for pace-derived rTSS. Heart-rate-based hrTSS uses other inputs: heart-rate data and threshold heart rate. Manually entered TSS may receive an asterisk. Do not call these identical measurements merely because all eventually appear as scores in the calendar.

The guide to unusual running TSS values specifically warns that running-power data introduced through a watch update can also change the calculation source. Check the detailed summary for whether power, pace or heart rate underlies it; the calendar tile’s simple TSS label may not reveal this. After changing method, the appropriate threshold and consistent treatment of previous data matter too.

Our checking situation: your usual half-hour run suddenly gives a very different load score although route and perceived effort are similar. First inspect new data series and the calculation name. A newly available power curve may explain the change; do not immediately assume substantial fitness loss or sudden improvement. Settings changes belong to the log’s history.

7. Pace correction cannot see everything on technical trails

The Low rTSS and Trail Running information says Normalized Graded Pace attempts to account for topography, but surface, wind, short steep sections and technical difficulty may not always be handled appropriately. Comparing heart-rate-based estimates may then be considered with suitable recording and running threshold heart rate. This offers another model’s perspective rather than an automatically flawless substitute measurement.

Our example: one sixty-minute run takes place on a smooth forest dirt road, the other on a rocky trail with frequent stops. Slower average pace does not prove the second was less demanding. Technical attention and route obstacles do not fit entirely into a pace model. Brief written feedback about that day may matter more to a coach than another decimal place in a score.

For a sound comparison, identify the run’s purpose. Reconnoitring a trail-race route may produce valuable navigation and equipment familiarity. Lower TSS returning to TrainingPeaks does not mean adding a harder programme to that day. Supplement the method’s limits with the task’s story, rather than basing tomorrow’s decision on “making up” one indicator.

A runner and coach review a training log together on a laptop facing them in a clubroom.Enlarge image
AI-generated editorial illustration; not a documentary photograph.

8. PMC: find the faulty point before explaining the curve

According to the Performance Management Chart troubleshooting guide, the curve depends on TSS data and Fitness/Fatigue time parameters. An erroneously enormous load score can distort the picture for an extended time. Finding and checking that activity is therefore the first step, rather than rewriting the entire preparation. CTL and ATL are model variables, not direct laboratory measurements.

Our numerical example: six days of 40 points total 240. If one accidentally receives 400, the week totals 600. The difference of three hundred and sixty points is one entry error here, not extra work performed. Before interpreting a graph’s slope, locate the value’s origin in the daily list. Even a plausible-looking smoothed line can be wrong with one faulty input.

Missing runs and scores from different methods can alter the picture less conspicuously too. Daily well-being, work demands or technical difficulty do not fully convert into TSS. Keep workout descriptions and personal feedback available alongside the graph. Load modelling supports shared thinking, but does not permit running through pain or determine health suitability.

9. Coaching notes and subscriptions: organised collaboration

The Notes permissions table separates creating notes from commenting on them: Basic athletes can comment, while creating their own Notes requires Premium. If your coach adds a travel or race-related note, you can respond without possessing every editing feature. Base your division of work on operations actually available.

The guide to upgrading to Premium describes automatic renewal and different purchase paths by platform. Managing web, Apple and Google purchases differs. Before paying, check whether your coach already provides Premium, which period the offer covers and where renewal is controlled. A purchased training plan, coaching service and analysis-account subscription may be separate costs.

In a useful TrainingPeaks system, it is clear who plans the week, which threshold informs the target, which workout starts on the watch and where completed TSS comes from. Initially, check the whole path with one simple workout. Once details make sense, calendars and graphs give you and your coach a concrete shared language, preserving much more of preparation’s story than ticked-off sessions alone.

Sources

Helpful? Pass it on.