How to get your athletes' watch data into your programming
Your athletes already record every run and ride on a watch. Getting that data into your coaching (and your sessions onto their wrists) removes double logging and makes interval work far more precise.
By Loadout5 min readWearables, Endurance, Garmin, Programming
Ask a group of endurance athletes how they log a run for their coach and you will hear three answers. Some copy the numbers from their watch into the coaching app. Some send a screenshot. Some do not bother, because the coach "can see it on Strava". Each of these costs someone time, and none of them puts the numbers next to what was prescribed.
The watch is the best logging device your athletes own. This guide covers the two directions data needs to travel (session to watch, activity back to session) and how to write sessions that survive the trip.
Two directions: push and pull
Push means your session reaches the athlete's watch as a structured workout: warm-up, each rep, each recovery, cool-down, each with a target. The watch counts the reps, times the recoveries and alerts when the athlete drifts off target. The athlete does not have to remember anything.
Pull means the activity the athlete recorded comes back to your coaching tool and lands on the session it belongs to, with distance, duration, pace and heart rate. Nobody types it.
Most setups have one direction at best. Coaches get the full benefit only when both work, because then a cardio session goes from your builder to the wrist and back without a human touching it.
The routes that exist
Watch ecosystems differ in what they accept and from whom. In practice, coaching software reaches athletes' watches through a few routes:
- Directly to Garmin. A structured workout scheduled on the athlete's Garmin calendar syncs to the watch.
- Through intervals.icu. A workout placed on an athlete's intervals.icu calendar can be forwarded by intervals.icu to Garmin, Wahoo and Zwift, which covers indoor riders and athletes on other head units.
- Activities back from Garmin, Strava and intervals.icu, and from the phone's own health store (Apple Health on iPhone, Health Connect on Android) for athletes whose watch syncs there.
- A file upload as the fallback for any device: most watches and platforms export a TCX file.
Before you choose software, list which watches your athletes actually wear and check which of these routes it supports. On Loadout, sessions are pushed to Garmin and intervals.icu, and activities come back from all five sources plus TCX. The details are on the sessions on the watch page.
Write sessions a watch can run
A watch is a literal reader. It needs every step to have a length and, ideally, a target. Coaches who write for humans tend to leave gaps a watch cannot fill. Some habits that help:
Give every step a length
"Warm up, then 6 x 800 m" leaves the warm-up open. "Warm-up 10 min" gives the watch a step. If you want the athlete to decide, say so: "warm up until ready" can become an open step the athlete ends with the lap button.
Separate work from recovery
"6 x 800 m @ 3:30 with 2 min jog" is two steps repeated six times: 800 m at a target pace, then 2 min of jogging. Writing it that way, with the recovery explicit, is what lets the watch alternate them.
Pick one kind of target per step
Pace, heart rate zone, power or effort. A step that says "3:30 pace, zone 4" gives the watch two things to alarm about. Choose the one that matters for that rep and put the other in your notes.
Use distance for track work, time for terrain
Distance reps make sense where distance is exact. On hills, trails or in wind, time-based reps with an effort or heart rate target are more honest, and the watch handles them just as well.
Say what happens if it goes wrong
"If the pace drops by more than a few seconds on two reps in a row, stop and cool down" is a coaching instruction that belongs in the notes. The watch will run the steps; the athlete still needs your judgement in their head.
Make pull-back do the logging
Once activities flow back, the matching rule matters. The simplest reliable rule: an activity on the same day as a single prescribed cardio session that has not been logged yet completes that session. When the athlete does two runs in a day, or a run on the wrong day, a person should be able to reassign it in a tap.
Set expectations with athletes: "Your runs will log themselves. If one lands on the wrong session, move it." That is a two-second job, compared with typing up every run.
Use the history, not just today's session
When an athlete connects a watch account, the most useful thing to come with it is often the past: months of runs and rides. That is a better baseline than any questionnaire. Before you write a new athlete's first block, look at:
- How many sessions a week they have actually been doing, not what they told you.
- Their longest recent session and how often they have done one that long.
- How consistent the last eight weeks have been, and where the gaps are.
A first block built from real history avoids the most common early mistake: programming for the athlete they described rather than the one who turns up.
Recovery data is watch data too
Many watches and phones also record sleep, resting heart rate and heart rate variability overnight. When that arrives alongside the training, it can sit next to the athlete's daily check-in and give you context before you change a load. How to use it without overreacting is covered in autoregulating load from readiness data.
A checklist for your roster
- List each athlete's watch and the platforms it syncs to.
- Ask every athlete to connect once, at the start of a block, and confirm the first session arrives.
- Rewrite your standard cardio sessions as explicit steps with one target each.
- Tell athletes they no longer need to log runs, and how to reassign a wrong match.
- Check the first week of matched activities yourself, then trust it.
FAQ
Can I send workouts to an athlete's Garmin watch?
Yes, if your coaching software supports pushing structured workouts to Garmin, or through intervals.icu, which forwards workouts to Garmin, Wahoo and Zwift. The athlete connects their account once.
What about athletes on other watch brands?
Check whether their watch syncs with intervals.icu or Strava. Activities from those come back automatically; for anything else, a TCX upload works.
Do athletes still need to log strength sessions by hand?
Yes. Watches are good at cardio and poor at counting sets and loads. Strength is best logged in the app, ideally one tap per set.
Put the session on the wrist
Write one interval session in Loadout and see it arrive on a connected Garmin or intervals.icu calendar. Free for up to two active clients: start free.