When I Tell An Athlete To Skip A Workout

The easiest thing I can do as a coach is program workouts. With great communication, understanding of time to train and performance goals, the athlete expects it. Nobody questions it. I send it, the athlete does it, the session gets recorded and uploaded, and we move forward. Clean, simple, uncontroversial.

The harder call - the one that actually separates human coaching from A.I. or canned plans - is sending this instead: "Don't train today".

That message can sometimes cost something. It may cost the athlete's confidence in the process. It may cost time they feel they can't get back. It can sometimes cast doubt in the relationship, at least temporarily, because athletes who are wired to train don't want to hear it. And it could cost me, because if I'm wrong, I've pulled them off a session that might have been fine. The accountability runs both directions.

But when I make that call, it's not a random decision. I'm looking for the convergence of a few things.

First: Physiological markers that don't lie. HRV suppressed below an athlete's rolling baseline. Resting heart rate elevated or unusual heart rate (high or low) during training that wasn't expected. Sleep quality tanked despite adequate duration. Poor watts, pace or times during structured sessions when expectations were different.

These aren't feelings, they're data points. I'm looking at the numbers before I'm listening to what the athlete tells me, because athletes are optimists by nature and will frequently talk themselves into a workout their body is telling them to skip.

Second: Life load the workout can't account for. Training stress and life stress draw from the same recovery pool. A plan built during a normal week doesn't know about the cross-country flight, the difficult conversation, the two nights of broken sleep. When external load is high enough, the physiological cost of a hard session stops being productive and starts being extractive. These become clear when good communication exists between the athlete and myself. I'd rather pull the session than spend two weeks managing the fallout.

Third: What's downstream. The calculus changes entirely depending on where we are in the training plan. If we're in a build block with a key race six weeks out, a missed tempo session is a rounding error. If we're ten days from an A-race, I'm making a different calculation. The value of any single workout is relative to everything surrounding it.

Here's what most coaches don't say out loud: how an athlete responds to being told to rest can be diagnostic on its own. The athlete who pushes back hard, who tries to negotiate, who needs to be talked down from doing something anyway - that's an athlete with a relationship to training that we might need to address separately from the workout in question. The rest day becomes a different kind of work.

The athlete who says, "Thanks, I needed to hear that." usually didn't need the rest day as badly. They were already listening to themselves. I just gave them permission.

I'm not managing fitness. Fitness is managed by the cumulative load across a season. What I'm managing in this moment is the athlete's long-term relationship with training - their ability to stay in the process, stay healthy, and show up to the starting line with something left. And that requires the athlete to learn that balance between Drive and Gratitude. My goal is to continually improve their ability to advocate for themselves when they're honest with themselves.

A skipped workout is not a hole in the plan. Sometimes it's the plan working exactly as intended.

Gratefully,

Mark

Team MPI