Should You Skip Today's Workout? A Decision Framework

You wake up and the legs feel like sandbags. The plan says threshold intervals. Somewhere between the first coffee and the kit drawer you make the real decision of the day: do the workout, modify it, or skip it.

Most of us get this call wrong in a consistent direction. The pushers push (always) and fatigue accumulates until something breaks and forces the rest they wouldn't take voluntarily. The folders fold: any rough morning becomes a rest day, and the stress never adds up to an adaptation. Ask yourself which one you are; you already know. The fix for both isn't more discipline in either direction. It's replacing the vibe with a decision tree.

First: is anything actually wrong?

Before the training logic, the medical gate. Chest pain, fainting or near-fainting, severe shortness of breath out of proportion to effort, a sharp or worsening pain, anything neurological, these aren't training decisions. Stop, and get evaluated by a professional. No framework below applies.

Likewise fever, and the classic "below the neck" rule of thumb for illness: symptoms below the neck (chest congestion, body aches, GI) mean rest, full stop. A mild head cold, at most an easy spin, and only if it genuinely feels good.

That gate cleared, it's a training decision. And it runs on signals, not motivation.

The decision tree

1. Multiple nights of poor sleep AND high fatigue? Easy aerobic or full rest, not the hard session. One bad night is noise; two or more combined with feeling wrecked is a multi-day recovery deficit, and stacking threshold work on top of it doesn't build fitness. Adaptation happens when stress lands on a body that can absorb it. This is also the branch where having the signals in front of you changes behavior: a red morning score with the coach proposing the easier session (reasoning attached) is much harder to argue with than a vague sense that you should probably rest.

2. Could you technically complete the workout, but recovery is clearly low? Take the lower-load option anyway. This is the subtlest branch and the most important one, so here's the take stated plainly: completing a session and adapting to it are different things. Grinding out 3×10 at threshold on a deeply unrecovered body earns a green checkmark and collects almost none of the fitness. Full price, fraction of the goods.

3. Fatigue and soreness rising at the same time as training load? Favor the easier day even though nothing has "gone wrong" yet. Two curves climbing together is how overuse announces itself politely, before it announces itself with an injury.

4. One bad day after decent sleep? Warm up and start. Motivation lies more often than legs do, plenty of the best sessions in anyone's log began as "just do the warm-up." The trick that gets you out the door: explicit permission to shut it down after the first interval if the numbers won't come. Athletes who grant themselves that permission almost never use it. Having it is the point.

5. Intervals failing two sessions in a row? Data, not weakness. Check accumulated fatigue first, then whether the FTP setting is honest, failing at a target that quietly drifted too high isn't a fitness problem.

The meta-rules

• Trends decide, days don't. Never overhaul a plan off one rough morning; never inflate one off a single great ride.
• Planned fatigue is not overtraining. A build block is supposed to leave you tired. The question isn't "am I tired?". It's "is relief already on the calendar, and are the recovery signals still inside normal?" If yes to both, hold the plan.
• Felt sense outranks the dashboard. Every readiness score is a heuristic. Feel genuinely awful, dial back without the data's permission. Feel great against lukewarm data, start the session and let the first interval vote.
• A missed workout is not made up. Skipped Tuesday intervals don't get bolted onto Wednesday. Continue the plan, protect the next key session. Cramming two hard days to satisfy the calendar is how one missed session becomes a missed week.

Building the habit

The framework only works with inputs, and this is where training culture has genuinely shifted. Recovery signals that used to live in a coach's intuition now arrive on your wrist every morning; every platform hands out a readiness score. A score alone changes nothing, though. What matters is two minutes of honest inputs and something that acts on them: a wearable filling in sleep and HRV overnight, or a four-question check-in with the coffee, sleep, fatigue, soreness, how hard yesterday actually felt. The day you most need a good call is exactly the day fatigue has compromised your judgment. Recorded signals don't rationalize.

One more habit that pays: write down the outcome whenever you override the tree, in either direction. "Pushed through, session was garbage, cooked for three days" is the entry that converts pushers. "Skipped, felt guilty, crushed the next two sessions" converts the folders.

In Training Signals, this tree runs every morning against your own numbers, the proposal arrives as an easier day, a swap, or a green light, with the why attached, waiting for your confirmation. But it works on paper too. Save it for the next rough Tuesday.