How PacePartner Makes Training Decisions

Endurance athletes now have more data than most coaches had a decade ago. Fitness score, fatigue score, form, HRV, resting heart rate, sleep duration, soreness, training load, workout compliance, race countdown, and readiness scores can all appear before the athlete has even warmed up.

That creates a tempting product shortcut: turn everything into one number and tell the athlete what to do.

We think that shortcut is wrong.

The body is not one score. A load model is not the same as a nervous-system signal. A nervous system signal is not the same as tissue soreness. A good-looking chart does not know about a terrible night of sleep, a stressful work week, or the athlete saying, “this feels wrong.”

So PacePartner starts with a different question: what kind of evidence are we looking at, and how much authority should it have over today’s decision?

The problem with one readiness score

A single readiness score feels useful because it removes ambiguity. The problem is that it often removes the exact ambiguity a coach needs to see.

Sleep, HRV, resting heart rate, training load, and soreness are not independent signals. Poor sleep can lower HRV, raise resting heart rate, increase perceived effort, and worsen mood. If an app collapses all of those into one score, it can punish the athlete multiple times for one underlying stressor.

The opposite can also happen. A positive form score can make the athlete look fresh because the recent training load is low, while the athlete is actually exhausted from illness, travel, life stress, or under-fueling. Load math cannot see total life stress unless the athlete or another signal brings it into the decision.

Our rule is simple: a metric can frame the question, but it should not erase the evidence category it came from.

The PacePartner decision stack

When PacePartner evaluates a training decision, we think in layers. The exact recommendation depends on the athlete, plan, and available data, but the order matters.

Load metrics are useful, but they are not biology

CTL, ATL, and TSB are useful because they compress training history into something readable. CTL gives a rough view of longer-term training load. ATL reacts faster to recent stress. TSB shows the gap between the two.

That makes them excellent for understanding whether the athlete is building, maintaining, recovering, or tapering. It does not make them direct measurements of mitochondrial adaptation, glycogen status, immune function, tendon tolerance, motivation, or sleep debt.

This distinction changes the product logic. A moderately negative TSB during a build phase can be exactly what training is supposed to produce. If the app automatically reduces training every time form goes slightly negative, it can prevent productive overload and keep the athlete stuck near maintenance.

At the same time, deeply negative form, rapid load spikes, high monotony, and poor hard/easy rhythm are not harmless. They are prompts to inspect the plan. They become more serious when they line up with subjective fatigue, poor sleep, elevated RPE, HRV suppression, or recurring soreness.

That is why PacePartner treats load math as context first. It explains the pressure the athlete has been under. It does not get the final vote alone.

Why HRV and resting heart rate need baselines

HRV and resting heart rate are closer to the athlete’s current physiological state than CTL or ATL, but they still require caution.

HRV is highly individual. A raw number that is excellent for one athlete may be normal or poor for another. Resting heart rate also moves with hydration, temperature, alcohol, illness, stress, travel, measurement timing, and sleep quality. One morning is noisy. A trend is more useful.

The reports behind this article reinforce the same practical stance we use in the app: compare the athlete against their own baseline, not a population table. Look for patterns such as HRV falling while resting heart rate rises, or HRV becoming unusually high with very low resting heart rate and the athlete reporting systemic exhaustion.

That last case matters. Higher HRV is not always better. In heavy endurance overload, an unusually high HRV combined with unusually low resting heart rate and heavy subjective fatigue can reflect parasympathetic saturation, not readiness. A simplistic score may call that green. A coach should ask why the athlete feels so flat.

Subjective feedback is not soft data

Many athletes trust devices more than their own perception because subjective feedback feels messy. The research base does not support dismissing it.

Self-reported fatigue, soreness, stress, sleep quality, mood, and motivation often respond reliably to training load and recovery status. They also capture things no watch sees well: localized pain, emotional stress, appetite changes, motivation collapse, and the strange “I’m coming down with something” feeling that shows up before a bad session.

In PacePartner, this means athlete feedback can override the chart. If the training load looks easy but the athlete reports severe fatigue and poor sleep, the app should not blindly push. If the chart looks loaded but the athlete reports deep sleep, normal HRV/RHR, low soreness, and strong workout execution, the recommendation can be less alarmist.

The goal is not to romanticize feel. The goal is to stop pretending feel is separate from physiology.

Hard rules, soft warnings, and coaching explanations

One of the most important software design choices is deciding what kind of rule a training concept deserves. Not every sport-science idea should become a hard-coded command.

This is the difference between decision support and decision theater. A product should be strict when strictness protects the athlete. It should be flexible when the evidence is probabilistic. It should be educational when the metric is useful but not decisive.

What happens when signals conflict?

Most interesting training decisions involve conflicting data. Here are the patterns PacePartner is designed to reason through.

The chart says tired, but the athlete looks ready

A deeply negative TSB can appear during a productive build block. If HRV is stable, resting heart rate is normal, soreness is low, sleep is strong, motivation is high, and the athlete is hitting workouts cleanly, the right answer may be to proceed with the plan instead of panicking.

The app should still mention the load. It should not pretend the athlete is fresh. But it should treat this as controlled overload, not automatic failure.

The chart says fresh, but the athlete feels wrong

This is the silent-strain problem. TSB can look positive because the athlete has trained less, but the reason for training less might be illness, poor sleep, work stress, under-fueling, or a brewing injury.

Here, subjective feedback and physiology win. A fresh load chart does not overrule severe fatigue, worsening symptoms, heavy legs, poor sleep, or a clearly elevated easy-run heart-rate response.

HRV is high, but the athlete is exhausted

For some endurance athletes, very high HRV with unusually low resting heart rate can be a confusing signal during heavy load. If the athlete also reports systemic exhaustion and lack of desire to train, PacePartner should not interpret the high HRV as a simple green light.

This is a good example of why the app must preserve the reasoning. “Your HRV is high” is not enough. The decision depends on the full pattern.

Race week makes the numbers noisy

Pre-race arousal can lower HRV and raise resting heart rate even when the athlete is physically fresh. If the athlete feels springy, soreness is low, and the workout is a short opener or race, the app should avoid turning normal race nerves into a false alarm.

What this means inside the app

The decision framework shows up across PacePartner in several ways:

• Daily coaching weighs wellness data and planned workouts, but should explain whether the recommendation came from load, physiology, symptoms, or plan context.
• Weekly plan reviews look beyond today and ask whether hard days, easy days, race proximity, and total load make sense together.
• Missed workout decisions do not automatically chase lost stress. They ask whether the session was high value, whether the week can absorb it, and whether moving it would compromise the next key session.
• Time-crunched workout rewrites preserve the intent when there is enough time and downgrade or skip when fatigue, race proximity, or equipment constraints make the rewrite low value.
• Taper guidance uses load reduction and intensity preservation, but adjusts for race priority, health, fatigue, travel, heat, and event duration.
• Coach directives take priority when an athlete is connected to a human coach, because software should support that relationship rather than compete with it.

The common thread is transparency. The athlete should know whether PacePartner is saying “rest” because of symptoms, because HRV and RHR are trending badly, because the week is overloaded, or because today’s workout is the wrong stress at the wrong time.

The foundation rule

PacePartner’s foundation rule is this:

Use training load to understand the plan, physiology to understand response, subjective feedback to understand lived cost, and safety rules to set the boundary.

That is less tidy than one readiness score. It is also more honest.

Good endurance coaching is not the removal of judgment. It is the discipline of asking the right question in the right order. The rest of this blog series will show how that plays out in the specific decisions athletes face most often: whether to train today, how to review a week, what to do after missing a workout, how to salvage a short session, how to taper, and how to fuel the work.

Evidence Base

This article is based on internal PacePartner research reports covering multimodal readiness, overload and recovery monitoring, fatigue thresholds, and software evidence standards. The most useful external references behind those reports include:

• Saw, Main, and Gastin on subjective athlete monitoring.
• ECSS/ACSM consensus statement on overtraining syndrome.
• Systematic review and meta-analysis of HRV-guided training.
• Narrative review on HRV for monitoring training adaptation and recovery.
• The training-injury prevention paradox.
• Conceptual and methodological pitfalls in training-load injury prevention.
• Sports Technology Research Network quality framework.