Short answer: almost certainly not. Pain is very rarely a measure of damage.
Something pulls in your calf on a Tuesday run. By Thursday you have read fourteen forum threads, watched two videos and arrived at a diagnosis that involves the word “tear”. By the weekend you have stopped running entirely and you are checking it every morning to see whether it is still there.
If that is roughly where you are, this is the most useful thing I can tell you: how much something hurts tells you surprisingly little about how serious it is.
Pain is a signal, not a score
It is tempting to treat pain like a fuel gauge — a readout of how much harm has been done, where more pain means more damage. It doesn’t work that way.
Pain is produced by your nervous system as a protective output. It indicates that an area has become sensitive, or that your body wants you to rest and get some help. That is a useful message and worth listening to. It is just not a measurement of tissue.
Think about a paper cut, which hurts far out of proportion to the harm done, or the bruise you find on your shin with no memory of getting it.
What the scans tell us
The clearest illustration comes from imaging studies. Scan people who have no pain at all, and a substantial proportion of them show exactly the findings runners get frightened by — disc changes, tendon changes, joint changes — while going about their lives perfectly happily.
It runs the other way too. Plenty of people in real, genuine pain have scans that look unremarkable.
Structure and symptoms are related, but far more loosely than the language around them suggests. Which is why a report full of alarming nouns is not the same thing as an explanation, and why being told what your scan showed can sometimes make you feel worse without changing anything about your body.
To be clear about what this is not: it is not “the pain is in your head”. The pain is real. It is the meaning attached to it that is usually wrong.
What to actually do this week
- Take 24 to 48 hours off. Rest it and see how it settles. Most things do.
- Keep moving otherwise. Complete shutdown is rarely the answer. Walk, bike, swim — whatever doesn’t provoke it.
- Stop testing it. Prodding the sore spot every morning to see if it has gone tells you nothing and keeps the area sensitised.
- Stop searching. The internet is very good at turning a sore Achilles into a catastrophe by Thursday.
- Still there after a couple of days? That is the point to get it looked at — not because something is broken, but because there is usually a cause worth finding.
Why the fear is worth taking seriously
Not because it means something is wrong, but because of what it does next.
A runner who believes they have done permanent harm stops running, then stops the other things too, and gets gradually less robust. A less robust body is more easily provoked. More provocation means more pain, which confirms the original fear. It becomes self-sustaining, and I see it far more often than I see anything structurally alarming.
Reassurance is not a nicety I offer before the real work starts. For most runners arriving frightened and over-Googled, it is the largest single part of the treatment.
When it does need looking at
None of this means ignore everything. Pain that is not settling after a couple of days, pain that returns to the same spot every time you build your mileage, a joint that gives way or locks, or anything that came with a genuine trauma — those all deserve a proper look.
The point isn’t that nothing is ever wrong. It is that the worst case you arrived at on the internet at half past eleven at night is very rarely the one you are in.
Still sore, and not sure what you’re dealing with? I run online injury assessments for runners — no travel, no waiting list, and you’ll come away with a plan built around your actual training week.
Run happy and injury free.
Leave a Reply