Training with a Polar: the measurement is world-class, the cycling plan is missing

What Polar actually measures, and how good it is

Better than almost anyone, and with published thresholds rather than a proprietary score. Training Load Pro splits a session into Cardio Load, Muscle Load and Perceived Load, then grades your accumulated strain against your own tolerance on a ratio with four named bands [Polar Training Load Pro]. Very few platforms publish the cut points.

Cardio Load is TRIMP. Polar states the mechanism plainly: it is calculated after every workout from your heart rate and session duration, and it is affected by your physical settings, resting and maximal heart rate, and gender [Polar Training Load Pro]. A typical 60-minute session lands between 70 and 130. Muscle Load is the mechanical side, average power multiplied by session duration, with a typical hour of cycling landing between 360 and 720. Perceived Load is your own 1-to-10 rating. Three numbers, three different questions, and the platform does not pretend one of them answers all three.

The status layer is where it gets genuinely useful. Cardio Load Status is a strain-to-tolerance ratio with published boundaries: below 0.8 is Detraining or Recovering, 0.8 to 1.0 is Maintaining, 1.0 to 1.3 is Productive, and above 1.3 is Overreaching [Polar Training Load Pro]. Compare that to the fitness-and-fatigue charts most platforms show, where the equivalent judgement is left to you and a form number with no documented interpretation. Polar drew the lines and published them.

Nightly Recharge adds an overnight read. ANS charge combines heart rate, heart-rate variability as RMSSD, and breathing rate, measured optically from the wrist during roughly the first four hours of sleep, and compared against your own 28-day baseline [Polar Nightly Recharge]. Sleep charge measures how you slept against your normal pattern. The 28-day baseline matters more than the sensor: it means the number is relative to you rather than to a population, which is the correct design for a recovery metric.

Recovery Pro is the most demanding and the most direct. It needs an H10 or H9 chest sensor and an Orthostatic test on at least three mornings per week, and it returns a short training advice from a fixed set: Train more, Go for it!, Train light, Train light or rest, Rest or train light, Injury and illness risk, and Take it easy! [Polar Recovery Pro]. It runs on the Grit X Pro, Grit X2, Grit X2 Pro, Street X, Vantage M3, Vantage V2 and Vantage V3. That is a daily direction, produced from a real physiological measurement, and it is the closest Polar comes to telling a cyclist what to do.

Read that list again, though. Train light is a direction. It is not a session. Nothing in the measurement stack decides whether today's ride is four by eight minutes at threshold or two hours of endurance, or what next week should look like given the last six. Polar tells you how hard you have been going and how recovered you are. The prescription is left to you.

The split that leaves most cyclists with a half-complete ledger

Cardio Load needs heart rate. Muscle Load needs power. Polar's own definitions make both requirements explicit [Polar Training Load Pro], and most cyclists ride with only one of the two sensors, which means half of Training Load Pro is dark on every ride they do.

Work through the two common cases. A rider doing an indoor session on a smart trainer with no chest strap produces power for every second and no heart rate at all. Muscle Load computes; Cardio Load, which is calculated from heart rate and duration, does not. Now the same rider goes outside with a strap and no power meter, which is the far more common Polar configuration. Cardio Load computes; Muscle Load, which is average power multiplied by duration, does not. Neither ride is wrongly scored. Each is half-scored, and the halves are different halves.

The consequence lands on the status ratio rather than on any single ride. Cardio Load Status compares accumulated strain against tolerance [Polar Training Load Pro], so a training week whose hardest session was a power-only indoor effort contributes almost nothing to the cardio side of that ratio. The chart then reads Maintaining or Detraining after a week that was neither. The metric is behaving exactly as documented. The input was incomplete.

The practical fix is unglamorous and worth stating anyway: wear the strap on the trainer even when the trainer measures power. Cardio Load is the one of the three that feeds the status ratio, and it costs a chest strap you already own. If you ride without power outdoors, accept that Muscle Load will be sparse and do not read its gaps as easy weeks.

This matters beyond tidy charts, because the thing that actually decides whether a training year works is whether the easy rides stayed easy and the hard ones stayed hard [Seiler 2010]. You cannot audit an intensity distribution from a ledger that scores half your sessions on one axis and half on another. Any system reading your Polar data, ours included, inherits whatever holes the sensor setup left.

The plan layer Polar never built for cycling

Polar publishes a page enumerating every training plan it offers. There are five: Flow manual planning, the Running Program, TrainingPeaks integration, the Fitness Program, and FitSpark [Polar Training Plans]. Not one of them is a cycling-specific training plan, and Polar has said in its own words why.

The Running Program is the proof that Polar knows how to build an adaptive plan. It is free, it runs on Flow web, it builds a personalized plan from your race distance and target date, and it schedules two to five sessions a week across nine to twenty weeks [Polar Training Plans]. That is a real training plan by any definition. Asked in its own FAQ why the programs are only for running, Polar answers: we have had the most requests for a running program, so we started with that, and in the future training programs for other sports like cycling are possible [Polar Running Program FAQ]. Polar is not hiding the gap. It is describing a roadmap.

One correction to a claim you will see made carelessly, including by people arguing our side of this. Polar does ship an adaptive program that covers cycling: the Fitness Program, a subscription at 9,99 euro a month, running on four-week periods, which suggests a new level after each period if it detects you have progressed enough or if the level was too demanding [Polar Fitness Program]. You can choose any sport except Multisport. So the honest claim is not that Polar has no adaptive program. It is that Polar has no cycling-specific one.

The distinction is substantive rather than pedantic. The Fitness Program is based on training in the right heart rate zone [Polar Fitness Program]. There are no power targets, no cycling interval structures, and no periodization toward a cycling goal. It is general-fitness cardio that will accept a bike as the vehicle. A rider training for a gran fondo in fourteen weeks is not served by a rolling four-week cardio ladder, and Polar does not claim otherwise.

FitSpark is the fifth option and the one most often mistaken for a plan. It offers two to four ready-made workouts a day chosen against your recovery, fitness level and training history, and its cardio sessions can be completed with any sport profile on your watch [Polar FitSpark]. So it does work on the bike. What it does not do is look forward. A daily suggestion has no memory of a goal date and no obligation to make this week build on the last one, which is the specific job a training plan exists to do.

Getting a structured session onto the watch

Two routes exist and both are real. Build the session yourself as a phased training target in Flow, or let TrainingPeaks push it. Everything else is blocked at the API layer, because Polar's public AccessLink API has no endpoint that writes a workout [Polar AccessLink API].

Phased training targets are the free route and they are better than their reputation. In Flow you add phases, set each one by duration or distance, choose whether phases advance automatically or manually, and select the intensity of each phase based on heart rate, speed or power [Polar Training Targets]. The watch then guides you through the session. This is a genuine structured-workout system and it costs nothing.

The catch is power, and it is narrower than most riders expect. Polar states that power-based phased training targets are currently supported only by Grit X Pro, Grit X2 Pro, Street X, Vantage V2 and Vantage V3 [Polar Training Targets]. Five models. Note who is missing: the Vantage M3 and Grit X2 both run Polar's own Cycling Performance Test to establish your FTP [Polar Cycling Performance Test] and then cannot follow a phase expressed in watts. Heart-rate and speed phases work far more widely, so on those two watches an HR-based build of the same session is the working route.

The TrainingPeaks door is the other one, and it deserves credit rather than a grudging mention. After you link the accounts, every compatible TrainingPeaks training plan and all target workouts sync to Polar Flow automatically once a day, across a device list that runs from the current Vantage V3 back to the M400 and V800 [Polar TrainingPeaks Sync]. It is genuinely a push of structured workouts onto a Polar watch, and we cannot do that. It is also not paywalled: Polar's own wording is that if you are using TrainingPeaks with a premium or a basic account, you can now sync your training plans made in TrainingPeaks to Polar Flow diary [Polar TrainingPeaks Sync]. Basic is TrainingPeaks' free tier.

The sync carries documented constraints worth knowing before you build a season around it. Flow always uses five training zones while TrainingPeaks does not restrict the count, so zones are remapped on the way across. A training target with more than twenty unique phases cannot sync at all. TrainingPeaks does not separate indoor from outdoor cycling the way Flow does. And once a workout is in your Flow diary you cannot edit it in Flow, only in TrainingPeaks [Polar TrainingPeaks Sync].

Everything else is closed, and the reason is architectural rather than commercial. The public AccessLink API exposes read endpoints for exercises, daily activity and physical information, and nothing that creates a training target. That is why no third-party service other than TrainingPeaks pushes workouts to a Polar watch. It is also, read the other way, a guarantee: a service reading your Polar data through the public API cannot alter your Flow account, because the API has no endpoint that could.

FTP on a Polar, and the wall the heart-rate rider hits

Polar's Cycling Performance Test is a proper FTP protocol, offering 20, 30, 40 or 60-minute options and returning FTP in watts along with maximum heart rate and VO2max [Polar Cycling Performance Test]. It also requires a compatible cycling power sensor, which is the wall, because heart rate is this brand's centre of gravity.

The test runs on eight watches: Grit X Pro, Pacer Pro, Vantage V2, Vantage V3, Grit X2 Pro, Vantage M3, Grit X2 and Street X [Polar Cycling Performance Test]. If you own one of those and a power meter, take it. Twenty minutes is enough for a usable estimate, the results sync to Flow and update your power zones, and it is a better anchor than a number you guessed.

For everyone else the requirement is absolute. No power sensor, no test, and no power zones on the watch either. That is a larger population than it sounds, because Polar is the H10 brand and a great many of its cyclists have trained to heart rate for years by preference rather than by accident. It is also worth knowing that Polar is Bluetooth-only for power: its compatible-sensor list annotates the PowerTap G3 entry with the note that Bluetooth-only and Dual models are supported while the ANT+-only model is not [Polar Power Sensors]. A rider who already owns an ANT+-only power meter cannot reach a Polar watch with it.

Threshold from the power curve is the alternative, and it is not a consolation prize. A model fitted to your mean maximal power across durations estimates the same physiological boundary the test is aiming at [Jones et al. 2010], updates itself as you ride, and never asks you to schedule a maximal effort you then have to recover from. The honest limit is that it needs efforts of varying length in your history to anchor against; a rider whose last eight weeks are all steady endurance gives any estimator very little to work with.

Keep the number's precision in proportion either way. Measured against maximal lactate steady state, FTP tracks the group mean closely but its 95% limits of agreement run to roughly 9% [Borszcz et al. 2019]. A test result and a modelled estimate that differ by fifteen watts are not in meaningful disagreement, and neither justifies rebuilding a training plan around the delta.

What has to sit on top of the hardware

Everything above is measurement and delivery, and Polar does both unusually well. The vacancy is the layer that decides: nothing in the ecosystem looks at the last six weeks of your cycling, writes the next eight, and rewrites them when the week falls apart. Polar's own plan menu is the evidence [Polar Training Plans].

The honest read on the alternatives. TrainingPeaks has the deepest structured-workout builder in the sport and genuinely pushes sessions to your watch, which is a real advantage over us. Its calendar does not restructure itself when you miss Tuesday and ride four hours on Saturday instead. The Fitness Program adapts, within a general-fitness cardio scope that was never meant to periodize a cycling goal. FitSpark answers today well and has no opinion about the twelve weeks after it. Each is good at what it was built for.

That gap is the layer AdaptCycling occupies. We read your rides from Polar, estimate threshold from your power curve rather than asking you to schedule a test [Jones et al. 2010], build a plan from what you have actually been doing, and rebuild it when the week goes sideways. The Polar data is unusually good raw material for this: Cardio Load and Muscle Load are computed against your own settings, and Recovery Pro's advice is grounded in a real orthostatic measurement rather than an activity-ring guess.

Three limits stated plainly, all of them ours. First, we cannot send a workout to your watch, because the public API has no endpoint that writes one [Polar AccessLink API], so the plan lives in our app and the phased-target route above is how you put a session on the wrist. Second, connecting Polar gives us no history. Polar's API returns only exercises uploaded to Flow in the last 30 days, and only those uploaded after your account was registered with our client [Polar AccessLink API] — both conditions at once, which at the moment you connect means nothing at all. Polar is a live feed from today forward, not an archive, so a rider with years of history should connect Strava as well and let Polar handle the new rides.

Third, the sensor gaps from the section above are inherited rather than solved. If your rides carry heart rate and no power, our plan anchors to heart rate, and the estimates it makes carry the wider error bars that implies. We would rather say that than imply a power-grade plan from data that has no power in it.

Quick answers

Sources cited in this guide

1. 01
   Polar Training Load Pro. Training Load Pro. Polar Support.
2. 02
   Polar Nightly Recharge. Nightly Recharge recovery measurement. Polar Support.
3. 03
   Polar Recovery Pro. Recovery Pro. Polar Support.
4. 04
   Polar Training Plans. Which Polar Training Plan Is Right for You?. Polar.
5. 05
   Polar Running Program FAQ. Polar Running Program FAQ. Polar Support.
6. 06
   Polar Fitness Program. Polar Fitness Program FAQ. Polar Support.
7. 07
   Polar FitSpark. FitSpark daily training guide. Polar Support.
8. 08
   Polar Cycling Performance Test. Cycling Performance Test. Polar Support.
9. 09
   Polar Training Targets. How do I create a training target in Polar Flow web service?. Polar Support.
10. 10
    Polar TrainingPeaks Sync. Using Polar Flow with TrainingPeaks. Polar Support.
11. 11
    Polar Power Sensors. Which third-party power sensors are compatible with Grit X/Pacer/Street X/Vantage?. Polar Support.
12. 12
    Polar AccessLink API. Polar AccessLink API. Polar Developers.
13. 13
    Jones et al. 2010. Critical power: implications for determination of VO2max and exercise tolerance. Medicine & Science in Sports & Exercise.
14. 14
    Borszcz et al. 2019. Is the functional threshold power interchangeable with the maximal lactate steady state in trained cyclists?. International Journal of Sports Physiology and Performance.
15. 15
    Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.

Specific questions inside this topic

Focused reads — each answers one question end-to-end.

1. 01

   Does Polar have a cycling training plan?

   Polar's own plan menu lists five options and not one is cycling-specific. What each actually does on a bike, and what Polar says about the gap.

   →
2. 02

   TrainingPeaks workout not syncing to Polar Flow?

   Polar documents the rules that silently block a structured workout: a 20-phase cap, zone remapping to five, sport-type mismatch, and once-a-day sync.

   →
3. 03

   Polar FTP without a power meter: what still works

   Polar's Cycling Performance Test needs a power sensor and runs on eight watches. What an HR-only Polar rider can anchor training to instead.

   →
4. 04

   Polar Flow to Strava sync: what it carries and drops

   Flow's automatic Strava sync skips every ride recorded before you linked, drops calories, and needs sample data. What that costs a training app.

   →
5. 05

   Training with just a Polar H10 and no watch

   An H10 and a phone is a complete free training stack for a cyclist. What Polar Beat records, what the strap's memory does, and where it stops.

   →
6. 06

   Is Polar FitSpark any good for cyclists?

   FitSpark cardio sessions run in any sport profile, so they do work on the bike. Why a daily suggestion is still not a cycling training plan.

   →

Related guides

• Training with a Hammerhead Karoo: a self-coached guide →
• FTP without a test: estimating threshold from real rides →
• Adaptive cycling training plans that survive real life →