How activities connect to workouts and races
When you record a session on your watch (Garmin, Coros, Suunto, Wahoo, Polar, Apple Watch, Rouvy, Strava…) and it syncs to Good Coach App, the app tries to put it in the right place on your calendar:
- attach it to the workout plan it was meant for, or
- connect it to the competition (your race) you had that day, or
- keep it as a standalone activity if it doesn't clearly belong to either.
This page explains, in plain language, how the app makes that decision — so you know what to expect, and when you'll still need to connect something yourself.
The app only connects things when it is confident. Anything unclear is left for you to connect by hand, and you can always change what the app did.
The short version
When an activity syncs, the app looks — in this order — for the best home for it:
- An exact match to a planned workout. If your device sent the workout back with its plan name or id (for example a structured session you pushed to your watch), the activity attaches to exactly that plan. This is a certain match, so it always wins.
- A race on the same day. If you had a competition on your calendar that day and the activity looks like that race, the app connects it to the race.
- A planned workout of the same sport. If there is a single open workout of the same sport that day with nothing recorded yet, the activity attaches to it.
- Nothing fits — the activity is saved on its own as a recorded activity.
Putting races ahead of the "same sport" step matters: an easy shake-out run you had planned for race morning won't steal your actual race file.
Connecting an activity to a race
Athletes very often forget to link their race-day file to the competition on their calendar — or their watch was set to the wrong sport. So the app does this for you when it is confident it is really the race, and otherwise leaves it for you.
It compares your same-day competition to the activity. The distance is the main signal; heart rate and GPS location only help confirm a borderline case.
✅ Connected automatically as finished
- The activity covers essentially the whole race distance (for example a 42.8 km file for a marathon, or a 10.2 km file for a 10K).
- If the race has no set distance, a clearly race-sized effort (roughly 20 km or more) still connects — nobody trains that far on race day.
The competition is marked finished and your file (pace, heart rate, splits) is shown on the race.
🟠 Connected as DNF (did not finish)
- The activity is more than half but clearly short of the full race — a sign you started and dropped out.
- Or you covered a substantial distance and GPS shows you were at the race, even if it is under half the distance (an early drop-out).
Because a DNF is something you will see, the app only marks it when there is supporting evidence — your GPS start being at the race, or a race-like heart rate for that distance. Your file is still connected, so your coach can see exactly where and how the race unravelled.