Every runner knows the standoff: the plan says intervals, your legs say otherwise, and you stand in the hallway negotiating with yourself. Push through and you might have a great session — or dig a hole that costs you the week. Skip it and you might be listening to your body — or just to your couch.
The problem isn't weakness or laziness. It's that "should I run today?" is a genuine information problem, and most runners answer it with either blind obedience to a schedule or unstructured vibes. There's a better way: a short, consistent readiness check that turns the daily negotiation into a decision.
Why the schedule can't answer the question
A training plan written last week is a forecast. It assumed a certain amount of sleep, a certain recovery rate, a normal week at work. The forecast is often wrong in small ways — and the cost of ignoring the error compounds. Hard sessions on unrecovered legs produce worse training stimulus, higher injury exposure, and more fatigue to carry into the next day.
The reverse error matters too. Runners who abandon the schedule entirely tend to skip on low-motivation days that were actually fine, and hammer on high-motivation days when they should have rested. Motivation and readiness are not the same signal.
So you need both: a plan for direction, and a daily reading to decide how today executes it.
The five signals worth checking
You don't need lab equipment. Five subjective signals, honestly rated, capture most of what matters.
1. Sleep — quantity and quality
Last night's sleep is the single most useful readiness input available to a runner without instruments. Short or broken sleep degrades coordination, effort tolerance, and glucose handling. One bad night before an easy run is nothing; a bad night before your hardest session of the week is a reason to swap days.
2. Muscle soreness — and where it is
General, symmetric, mild soreness after a hard day is normal adaptation. Pay attention to two variants: soreness that's still strong 48+ hours after the session that caused it, and anything localized or one-sided. The first says your recovery is behind; the second is a potential niggle asking for an easy day before it becomes an injury asking for a month.
3. Energy — mental as well as physical
Life stress and training stress land in the same body. A brutal day at work is physiologically expensive even though it happened in a chair. If you feel drained before you start, the session that builds you up is the easy one, not the hard one.
4. Motivation — as a trend, not a mood
Any single day of low motivation means nothing. Three or four consecutive days of dreading runs you used to enjoy is one of the most reliable early signs of accumulating fatigue. Track the trend, not the day.
5. Yesterday's training — what actually happened
Not what was planned — what happened. If yesterday's easy run turned into an accidental tempo because you felt great, today needs to account for that. This is where synced data helps: when your runs land automatically from Strava, the record is honest even when memory isn't.
Turning signals into a decision
Rate each signal simply — good, okay, poor — and apply a blunt rule:
All good or okay: run the day as planned. Green light.
One or two poor: keep the run, drop the intensity. The planned intervals become an easy run; the easy run gets shorter. You keep the habit and the aerobic work without the recovery bill.
Three or more poor, or any sharp/one-sided pain: rest, or walk. This isn't a failure state — it's the system working. One deliberate rest day is dramatically cheaper than the forced week off you were heading toward.
The crucial discipline is checking in before you decide, every day, in the same way — not only on days you're already looking for an exit. Consistency is what makes the signal readable, because you learn what your personal "okay" feels like.
What this looks like with a coach doing the math
This framework is exactly the loop TempoRun automates. Each day you complete a short check-in about how your body feels; the coach combines it with what you've actually done — your runs sync in from Strava on their own — and picks today's workout to match. Fresh means the quality session goes ahead. Rundown means it moves, and the week quietly rebuilds around the change, so an honest "not today" never turns into being "behind."
That last part is the piece manual readiness checks can't solve: adjusting today is easy, but re-planning the rest of the week around the adjustment is where self-coached runners get lost. An adaptive plan does the re-planning for you, which removes the biggest hidden cost of listening to your body.
Common mistakes with readiness
Only checking in when you feel bad. Then the check-in becomes a permission slip for skipping. Do it daily, including the days you feel great — sometimes the useful answer is "you're fresh, go harder than you would have."
Treating one signal as a verdict. Bad sleep alone rarely cancels a run. It's the combination — poor sleep and heavy legs and flat mood — that means back off.
Confusing discomfort with damage. Readiness training isn't about only running when everything is perfect; some sessions are supposed to be uncomfortable. The check-in decides whether today can absorb hard work, not whether hard work should ever happen.
Overriding every amber. If you notice yourself downgrading the assessment so the plan can proceed, you've rebuilt the rigid schedule with extra steps. The honest answer is the entire value.
The payoff
Runners who train by readiness don't train less — over months, they usually train more, because they lose fewer days to the crashes that follow ignored warnings. The hard days land on fresh legs, so they're actually hard-quality instead of hard-miserable. And the hallway negotiation disappears, replaced by a question you can answer in thirty seconds.
Should you run today? Check the five signals and you'll know. Or let a coach that asks you every morning do the deciding — that's precisely what TempoRun's daily check-in is for.