Should I train today? A decision framework

It’s 6:15am. Alarm went off fifteen minutes ago. The legs feel heavier than yesterday, sleep was OK not great, the plan calls for intervals. What do you do? Every amateur endurance athlete faces this decision three mornings a week. Here’s a framework that makes the call faster, with less regret in either direction.

The goal isn’t to train harder. The goal isn’t to rest more, either. The goal is to make the same call a good coach would make from your data, most mornings, in under 60 seconds.

Three inputs, in order of trust

Good decisions come from three signals, weighted like this:

1. Subjective feel after 10 minutes of light movement— 50% of the decision. Not the 6:15am “I want to go back to bed” feel — that’s noise. The “I’ve been moving for ten minutes, legs are unpacking” feel.
2. Training readiness score — 30%. A grounded reading of where you are on the objective load-recovery axis.
3. Scheduled session type — 20%. A prescribed easy day is tolerant of a mediocre readiness; a prescribed interval day needs both subjective green and objective green.

The ordering matters. When subjective and objective disagree, subjective wins — your body is better at detecting pre-illness and systemic fatigue than any algorithm reading your TSB. Conversely, when subjective says “I feel great” but readiness is capped at 50 because monotony is 2.1, trust the data: you’ve been lured by the grey zone before.

The four common cases

Case 1 — Green subjective, green readiness (≥65)

Train as planned. Hit the prescribed session. This is the easy case and honestly the most common one — two-thirds of mornings for most athletes. Don’t overthink it.

Case 2 — Green subjective, yellow readiness (45–64)

Downshift one level. If intervals were planned, do tempo instead. If tempo, do steady Z2. If steady Z2, keep it — Z2 is pretty forgiving.

The reason this happens: your legs feel OK but the data shows you haven’t recovered from recent load. Pushing intensity on this day is the classical way to dig the overreach hole deeper. Downshifting maintains the volume without driving new fatigue.

Case 3 — Yellow subjective, green readiness

Start the warm-up and reassess at 10 minutes. If the legs unpack, proceed with the planned session. If they don’t, downshift one level.

This is the classic “didn’t want to get up” scenario. Sometimes it’s real fatigue, sometimes it’s just morning inertia. You can’t tell until you’ve moved a little. Give yourself 10 minutes before deciding, but commit to honesty after.

Case 4 — Yellow or red subjective, yellow or red readiness

Rest or recovery spin only. Don’t intellectualize it. When both signals are off, the body is telling you something — don’t spend an hour deciding. Either take the day off completely or do 30 minutes very easy. No intensity. No “just threshold for 10 minutes”. Take the recovery.

When to override

Two legitimate overrides:

• Race-week taper.If you’re within 7 days of an A-race, err heavily on the side of rest. The fitness is already banked. No training session in race week significantly improves your race; many significantly compromise it. Cut volume aggressively even when readiness is green.
• A specific tune-up.You booked a B-race or a hard group ride. Readiness says yellow. You do it anyway — you know what you’re trading. That’s fine. The frame is: you’re informed, not surprised.

Two overrides to avoid

• “The plan said intervals, so intervals.”Discipline is good; rigid discipline produces injuries. The plan exists to serve you; you don’t exist to serve the plan. When objective data and subjective feel both say no, the plan is wrong about today — rewrite today and keep the week’s intent.
• “The weather is nice / I have time.” Opportunity-based training leaves recovery on the floor. Your calendar feels full; your body has its own calendar. Answer to the body first.

How ZoneTwo helps (and where it doesn’t)

The readiness score handles the objective side. A glance at the dashboard tells you whether the data says green, yellow, or red. The AI chat handles the nuanced second layer — “readiness is 55, I’ve got 4×8 min at FTP on the plan, what should I actually do?” Answer: see case 2 above. The coach will often cite your recent TSB and monotony and suggest the specific downshift.

Where we can’t help: the subjective read. That’s yours. No algorithm sees inside your body. Trust your 10-min warm-up feel, and learn to read it honestly over months — the skill compounds.

Related reading: training readiness, training monotony, ZoneTwo AI chat.