Running injuries follow patterns a coach can read
Almost every runner I coach deals with a running injury at some point. In more than ten years of this work, the ones that end a season are almost never the ones that showed up out of nowhere. They are the ones that whispered for a week, got ignored, and then shouted. The pattern I watch for is not the pain itself. It is what the runner did the day after they first felt it.
This page is the short version of what I tell my athletes when something starts to hurt, and the long version of where to go next if you want more on a specific injury. Nothing here is a diagnosis. It is how a coach reads the signals, decides whether tomorrow is an easy run, a cross-training day, or a phone call to a PT, and keeps the rest of the training honest while a body figures itself out.
That line is the one I keep coming back to. Most of the common running injuries I see are not freak events. They are small complaints that the runner tried to outrun, right at the point where backing off a week would have cost almost nothing.
The three questions I ask first
When an athlete texts me that something is sore, I ask the same three things before I give them any plan. They are not clever, but they sort nine out of ten complaints into the right bucket fast.
- Does the pain stay or get worse as the run goes on? Normal post-run soreness, and even most low-grade niggles, warm up and fade in the first ten to fifteen minutes. A real injury does the opposite. It gets worse as the miles stack.
- Is it there in the hours after a run, or the next morning walking around? If you feel it going down stairs, getting out of bed, or standing after a long drive, the tissue is loaded past what it can handle, not just annoyed.
- Are you changing your stride to protect it? A limp, a shortened stride, a landing you are reaching for on the other foot. If yes, you are now feeding a second injury on top of the first.
A yes on any of those is a sign to back off that day, not a sentence. A yes on two or three, especially the third, and we are not running that day at all.
When to keep running, when to back off, when to stop
Most decisions after a complaint sort into three buckets. Pick the right one and the injury almost always settles. Pick the wrong one and you buy weeks.
| Signal | What I usually do |
|---|---|
| Warms up in the first mile and fades | Finish the run easy, cut any planned workout, see how it reads tomorrow |
| Stays flat through the run, no worse | Shorten the run, drop the pace, no workouts for a few days |
| Builds through the run, or you are compensating | Turn around and go home, even if it is less than planned |
| Sharp, localized, or hurts walking the next day | No running. Cross-train. Call a PT or doctor if it is not better in a week |
That "turn around and go home" line comes from an old piece of advice I still give. If the discomfort is there a few minutes into the run, see if it fades. If it does not, head back to where you started, even if you planned eight miles and have done two. Best case, the pain disappears on the way back and you add a loop on the end. Worst case, you took thirty minutes off a session that was going to hurt you anyway.
None of this replaces a professional eye. For anything sharp, anything that got worse quickly, or anything that is still there after a week of careful behaviour, see a physical therapist or a doctor. You cannot read a stress reaction out of a training log, and I am not going to try.

The early signs I tell athletes to watch for
Most of the injuries that take a season out announce themselves a week or two before they stop you. The runners who stay healthy are not the lucky ones. They are the ones who treat the first whisper as the message, not as noise. The signals I ask about, in rough order of how often they predict trouble:
- A pain that shows up at the same point in every run. Mile three for one person, forty minutes in for another. The body is telling you something is loaded past what it can take at that duration.
- A spot that is sore getting out of bed. Plantar fascia is the classic. If it is quieter after the first ten minutes of walking around, that is the one to warm up before running, not to ignore.
- Sleep that drops for no reason, or resting heart rate that jogs up for a week. Overtraining and infection show here first. I would rather cut a week than coach you through a chest cold you tried to run off.
- Any strength that disappears. You cannot finish strides that felt easy last week. You cannot drive a hill you drove two weeks ago. Fatigue is a signal, not a character flaw.
- A new way you are landing. Watch your own shadow on the sidewalk. If one foot is reaching and the other is thudding, the chain upstream is tired and something downstream is about to pay for it.
The runners I coach learn to text me these before they turn into something I have to write around. Most do not need a diagnosis. They need one or two easy days and permission to take them.
The boring things that prevent most of it
I wish the honest answer were more exciting. The injuries I see least often are in the athletes who do three dull things well, almost regardless of mileage.
First, easy days that are actually easy. Most of the overuse I see is runners accumulating damage on the days that were supposed to be building a base. If you are running every day at the same medium effort, your tissues are never getting the recovery dose they need.
Second, two short strength sessions a week. Twenty minutes each. Single-leg work, hips, hamstrings, core. This is the thing runners skip first and pay for most. A weak chain upstream is why most knee and shin complaints show up where they do.
Third, a sane build. Volume does not go up more than about ten percent in a week, and takes a cutback every fourth week. Long runs climb in ones and twos, not fours. If you need a plan that does this for you, the marathon and half marathon templates on this site are a good starting point. The beginner plans are the same idea at a smaller scale.

When running stops, training does not
The worst mistake an injured runner makes is treating "no running today" as "no training today". Fitness does not care which engine you use. It cares that the engine runs. Most of the injured athletes I coach keep almost all of their aerobic base through a layoff because they stay on the bike, in the pool, or on an elliptical for the time they would have spent running, at roughly the same effort. An hour spinning at an easy aerobic heart rate is not a replacement for an hour of running, but it is an eighty percent one, and eighty percent for two weeks beats zero.
Two rules make this work. First, match the duration, not the distance. If your week was going to be five hours of running, make it five hours of something else, in the same session shapes. One longer effort, one with some tempo, the rest easy. Second, keep the strength work in. The window where a runner cannot run is the window where they can finally get in two real sessions a week of hips, single-leg work, and core without it compromising a workout. The athletes who come back fastest from a break are the ones who come back stronger than they left.
When to call a doctor or PT
I am a coach. I am not a physical therapist and I am not a doctor, and this site does not pretend to be either. There is a line and it is not fuzzy. Call a professional for:
- Pain that is sharp, specific, and does not warm up or ease at all
- Anything that got significantly worse quickly, especially overnight
- Anything still there after a week of careful behaviour, cross-training, and honest rest
- Any swelling, bruising, visible change, numbness, or pain at rest
- Anything in a bone, not a muscle or tendon, that you can press and reproduce
A good runner-specific PT is one of the best investments in a career. They see the mechanical cause a coach cannot read from a watch file, and a smart PT and a smart coach together are how injured athletes get back to real training faster than either alone.
Every injury and recovery guide on this site
The posts below go deeper on the specific injuries I see most, the return to running after one, and the recovery habits that keep seasons together. I will keep adding to this as the blog grows.
- How to avoid running burnout before it derails your training
- IT band syndrome in runners: what actually heals it
- Legs hurt after running: the four kinds of pain and what to do with each
- Marathon recovery: what the four weeks after 26.2 should look like
- Return to running program: a coach's six-week protocol
- Runner's knee: the real cause and the protocol that heals it
Want this read by someone who has seen it a thousand times?
When you work with me, a complaint in your training notes gets a decision the same day: run, back off, cross-train, or call someone. The plan bends around your body instead of asking your body to bend around the plan.
Book a free intro callGet the next training note
A short series from me over three weeks, then one email a week when a new post is up. Pacing, plans, and the patterns I watch for. No spam, unsubscribe anytime.
