Before a hard session I want to know one thing: should I go deep today or back off? Not a vague feeling. A quick check — am I actually recovered, or am I just caffeinated? The point isn't to use readiness as an excuse to skip intervals. It's to develop a sense for your body and then validate it with numbers. Over time you calibrate: "I feel good" starts to mean something measurable.
Three values. That's it.
Ready is a recovery percentage from your wearable — HRV, resting heart rate, sleep, and whatever else it tracks. The details vary by device. The number is what matters: high means your nervous system has bounced back.
Sleep score is how much of your sleep need you actually covered. Not just hours in bed — it accounts for debt, strain, baseline. A better question than "did I sleep 8 hours" is "did I sleep enough for what I did yesterday."
Form is CTL minus ATL — fitness minus fatigue, basically. Positive means rested. Negative means you're carrying load. It uses yesterday's training data so the number reflects your state going into the ride, not the ride itself.
The color thresholds are my cutoffs based on what correlates with how I feel on the bike. They're not medical ranges. Your green might be different — but these are a reasonable starting point.
I put these on the planned workout card.
Color-coded so you can glance and move on. If everything's green and you feel good — go. If there's orange or red, check in with yourself. Does it match how you feel? If yes, maybe dial it back. If you feel fine despite a low number, ride and learn from the mismatch. The point is the conversation between the data and your body, not a traffic light telling you what to do.
Open a completed ride and the same three numbers appear for that day.
On a past ride, readiness is context. It explains why a session felt heavy or why you surprised yourself. Pattern recognition, not excuses.
Readiness was on the profile page initially. Removed it. A readiness score without a ride is just a number. It belongs where there's a workout to decide about or a ride to contextualize.
I considered adding HRV and resting heart rate as separate values. Decided against it. They're already inputs to the readiness score. Showing the ingredients and the result is redundant. Three numbers is enough. If something is orange or red, that's your cue to look deeper in your wearable app.