Open your phone after a run and you’ll find two truths waiting. Your plan, written weeks ago, told you it was a tempo day. Your tracker, freshly synced, tells you that you ran it — the splits, the map, the kudos. Two apps, two jobs, both done well. And yet the question you actually carry up the stairs afterward isn’t answered by either of them: how did that land?
It’s an easy gap to miss, because the two tools you own look so complete. One tells you what to do. The other records that you did it. Between them they seem to cover everything. They don’t — and the thing they leave out is the only thing that’s actually alive.
The plan is a guess made before today existed
A training plan is a prediction. A good coach or a good app writes it from your history and your goal, and it’s genuinely valuable — structure is most of what separates training from just running. But every plan is authored in the past tense about a future it can’t see. The person who wrote “5×1km at threshold, Thursday” didn’t know you’d sleep badly Tuesday, that work would unravel Wednesday, or that Thursday morning would arrive thick and humid.
The plan can’t know those things because they hadn’t happened yet when it was written. It’s a map drawn before the weather. Useful, necessary — and blind to the day you’re actually standing in.
The log is a gravestone
Your tracker has the opposite problem. It’s flawless about the past and silent about everything else. Strava records the run beautifully — every split, the elevation, the segment you stole back — and the moment you stop the watch, that record is finished. Accurate, permanent, past tense.
Even the cleverer version of this — the new wave of post-run AI summaries that read your activity file and describe it back to you in plain English — is still describing the run. It’s a more articulate gravestone. It tells you about a session that’s already over, from the data the session left behind. What it can’t do is look at the living system that produced the run and is still, right now, recovering from it.
“The plan describes the run you were meant to do. The log describes the run you did. Neither describes the runner — and the runner is the only part that changes.”
The data that matters lives outside both
Here is the part most training stacks quietly miss. The information that actually explains a run — why it felt heavy, whether you absorbed it, whether tomorrow is safe — mostly isn’t in the run at all. It’s in the body around it.
Your overnight HRV, taken hours before you laced up. Your resting heart rate, trending across the week. How you slept. The dew point you ran through. What you ate the day before. And the slow patterns that only appear across months — the fuelling that precedes your best long runs, the load that precedes your worst. None of that is a split. None of it lives in a Strava file. Most of it happens while you’re asleep or eating dinner, nowhere near the run it ends up explaining.
That’s the layer. Not a better plan, not a better log — a reading of the organism the session happened to, drawn from everything your watch and your ring quietly gather and nothing else bothers to connect.
Three jobs, three layers
The plan tells you what to run. Written ahead of time, fixed.
The log records what you did. Written after, finished.
The read interprets how your body took it — HRV, sleep, weather, fuel, and the trend underneath. Rewritten every single day, because you are different every single day.
Why it has to be a separate thing
You might reasonably ask why this can’t just be a feature bolted onto the plan or the log. The answer is in the tense. A plan is fixed the moment it’s written; a log is fixed the moment you stop. Both are still objects. Your physiology is not an object — it’s a process, and it doesn’t hold still. It moves with every night of sleep, every stressful day, every hot morning, every meal, every session still being absorbed. Reading something that changes every day is a continuous job. A static plan and a past-tense log were never built to do it, because neither of them is allowed to change once it exists.
So the read has to be its own layer — one that wakes up with your overnight data, revises itself against the day in front of you, and is honest enough to say something different tomorrow than it said today. It doesn’t sleep, because your nervous system doesn’t. It changes constantly, because you do. It’s less a dashboard than a mirror that’s always on — the same shape every morning, a different reflection every time you look.
Keep everything. Add the read.
None of this is an argument to abandon what works. Your plan is still where the structure comes from. Strava is still your log, your history, your Sunday-morning social feed. Those tools earned their place and they keep it. The read isn’t a replacement for either — it’s the connective layer that sits underneath both and finally answers the question they were never built to: not what should I run or what did I run, but how is the body that has to run it.
Add that, and the stack is finally whole. The plan points forward. The log looks back. And the read holds the middle — the living, shifting present tense of you — steady, attentive, never quite the same two days running.
Kovr is the read. Keep your plan, keep Strava.
Kovr connects through Apple Health to your Apple Watch, Garmin, or Coros — reading the HRV, sleep, weather, fuel, and 90-day patterns your plan and your log never see. It doesn’t touch the Strava API, doesn’t ask you to switch, and doesn’t sleep. Every morning it tells you how the body actually took the work — and what today is asking of you.
Join the Kovr waitlistLaunching soon · Garmin, Apple Watch & Oura Ring
Frequently asked questions
Do I need another app if I already use Strava and a training plan?
A plan and a tracker tell you what to run and record what you did. Neither reads how your body absorbed the work — HRV, sleep, weather, fuelling, and the patterns across months. That interpretation is a separate job. Kovr fills it without replacing either; you keep both.
Does Kovr replace Strava?
No. Strava stays your log and social feed. Kovr sits alongside it and reads your physiology through Apple Health — including the HRV and recovery data Strava never sees. It doesn’t depend on the Strava API, so the two simply coexist.
What does Kovr see that Strava and my plan don’t?
The data around the run rather than in it: overnight HRV, resting heart rate, sleep, the dew point you trained in, your nutrition, and the trends across 90 days. The file describes the activity; Kovr describes the body it happened to.
Why does the body need a separate layer at all?
Because your plan was written before today happened and your log is finished the moment you stop the watch — both are fixed. Your physiology isn’t. It shifts with sleep, stress, heat, fuel, and load every day. Reading that moving target is a continuous job neither a static plan nor a past-tense log can do.