Athletes

Setting zones and thresholds

Set a default zone model for every athlete, then override it for individuals when needed.

The default zone model

Every training zone in Wyder can be anchored to something physiological, such as LT1, LT2, FTP, CSS, or heart rate, instead of being based on a single fixed metric. Anchoring zones to a real threshold is what makes a prescribed intensity mean the same physiological effort for every athlete it's assigned to, so training actually produces the adaptation you're aiming for, instead of quietly over or undershooting it.

LT1 and LT2 are both available as separate anchors, so you can set each one directly rather than approximating one from the other.

Set this default model once, per sport, from Your account -> Zones. It's what every athlete's zones are built from until you override something for them specifically.

The default zone model for running, showing pace and heart-rate zones each built from an anchor and its resulting range

Overriding it for one athlete

Two separate things can differ per athlete, and both live on that athlete's own row under Your account -> Athletes.

The first is their own threshold numbers: Max HR, LT1, LT2, FTP, CSS, whichever apply, entered from the Thresholds tab on their row. Any zone model, default or overridden, resolves against these numbers, so this is what actually personalizes a prescribed intensity to this specific athlete's physiology. Set or adjust them whenever it's useful, whether that's on day one or much later, as their fitness changes.

Entering an athlete's own thresholds, with their zones recomputing automatically

The second is the zone model itself, a genuinely separate scheme for this one athlete, not just different numbers plugged into the shared default. If an athlete's training calls for zones structured differently from everyone else, build that from the Running, Cycling, or Swimming tab on their own row. Until you do, they simply use the default model from your account, resolved to their own thresholds.

Zones without an anchor, when you'd rather work in raw numbers

Not every zone scheme needs to start from a physiological anchor. Build one directly in pace or power instead, entering the exact ranges you want for each zone rather than deriving them from LT1, LT2, FTP, or CSS.

Use whichever fits how you actually think about a session: anchor to a threshold when you want every athlete's numbers to scale automatically to their own physiology, or work in raw pace and power when you already know exactly what you want prescribed.

While workout templates are typically built based on intensity anchors linked to training zones, Wyder also allows you to build workouts with an intensity structure freely expressed in pace or power values. That way you don't have to bother converting zones into efforts whenever you don't want to, as covered in Building workouts.

Was this article helpful?

Wyder uses cookies and similar technologies to keep the site running, for analytics, and to measure ads. By clicking “accept” you agree to this as outlined in our Privacy Policy.