Context, not verdict
Recovery-aware training keeps multiple signals in the frame.
Recovery data can be helpful, but one poor-looking morning value does not explain the whole training state. RunPT can consider available sleep, HRV, resting heart rate, readiness or stress, recent running, and the current phase together.
The comparison is personal. A value can be unusual for one runner and normal for another, which is why baseline and trend matter more than a universal green or red threshold.
Available inputs
What can inform the recovery picture.
Sleep
Available sleep duration and related provider context can help frame the morning, but they do not decide a session alone.
HRV
Heart-rate variability is most useful against the runner's own baseline and trend, not a population ranking.
Resting heart rate
A meaningful departure from personal norms can add context alongside recent running and other available signals.
Readiness or stress
Provider scores may be available on supported connections. They remain inputs from another system, not diagnoses from RunPT.
Recent training
Completed volume, intensity, long-run demand, and consistency help distinguish a recovery signal from the work that preceded it.
Personal baseline
RunPT considers what is normal for the runner rather than treating one universal threshold as readiness for everyone.
Missing stays neutral
You do not need a perfect data stream to have a plan.
RunPT can build and maintain training from goals, schedule, profile, and completed workouts. If a watch is not worn overnight, a provider omits a metric, or a connection pauses, missing recovery data is not interpreted as poor recovery.
Device and permission differences mean the available metrics vary. The integrations matrix therefore separates completed-run import, recovery import, and planned-workout export.
Planning response
A recovery signal can prompt review; it does not command the plan.
When recovery context changes materially, RunPT can review upcoming work alongside recent load and the purpose of the week. That review may support an easier session, a moved quality day, a reduced demand, or no change at all.
The aim is not to reward perfect scores or punish imperfect ones. It is to avoid making a planning decision from less context than is available.
FAQ
Recovery questions.
Straight answers about what RunPT does, what data helps, and where its guidance stops.
01Do I need a watch for recovery-aware training?
Yes. RunPT needs a compatible running watch, or Apple Watch data through Apple Health, to sync completed training and use available recovery context.
02What happens when recovery data is missing?
Missing data is treated neutrally. RunPT does not interpret an unworn watch, paused connection, or unavailable metric as poor recovery.
03Can RunPT tell whether I am injured or overtrained?
No. RunPT does not diagnose injury, illness, or overtraining. Wearable data can be incomplete or wrong; pain, symptoms, and health concerns require appropriate professional care.