Your back went and nothing happened

NO INJURY

You bent to pick up a sock. That is the story most people are embarrassed to tell, and it is the most common one there is — the absence of a mechanism is itself informative.

Why nothing has to happen

People expect back pain to be proportionate to its cause, because that is how the rest of the body behaves. Spines do not work that way. A lumbar segment loaded thousands of times a day sits somewhere on a curve of accumulated tolerance, and the sock is not the load — it is the moment the curve was crossed. The event you remember is a timestamp, not a cause.

Three things set where that threshold sits, and none of them happened on the day. The first is mechanical: how much sustained flexion the segment has absorbed and whether the deep stabilizers have any endurance left. The second is metabolic — the disc is the largest avascular structure in the body, fed by diffusion, and insulin resistance and poor glycemic control measurably degrade that supply. Nobody expects a blood draw at a back appointment, and it is one of the more useful things we do.

The third is neither: it is sleep, load at work, and how much of your week is spent in one position you did not choose. A threshold is crossed by everything sitting under it, and a fair amount of what sits under it is not biological at all.

So what actually tore?

Usually nothing. The commonest presentations after a trivial mechanism are a facet joint that has been provoked, a segment guarding hard enough to feel like structural damage, or an annular irritation that produces genuine pain with no neurological deficit at all. A spasm is your back guarding something — the useful question is what.

This is what the literature calls non-specific low back pain, and the label is honest rather than dismissive: in the acute phase a specific structure genuinely cannot be identified in most people, and trying to name one early is how you end up treating a scan.

Why the story matters anyway

Not because it explains the pain, but because of what it does to you. People who cannot name a cause tend to assume the cause is worse, and that assumption is one of the better predictors of how the episode goes. A back that hurt for no reason feels less trustworthy than one that hurt because you lifted a piano, and the fear changes how you move, which changes how it recovers.

It is worth saying clearly: pain arriving without an injury is not evidence of something sinister. It is the ordinary presentation. The short list that does need attention is defined by what comes with the pain — fever, weight loss, bladder or bowel change, progressive leg weakness — not by whether you can explain the onset.

What to do with the first week

• Keep moving. Not through the sharp end of the range, but do not stop.
• Do not go looking for the moment. Reconstructing which lift did it is satisfying and changes nothing.
• Notice what the pain does, not just how bad it is. Worse sitting, worse standing, worse rolling over — each of those points somewhere different, and it is the most useful thing you can bring us. The drive being worse than the walk is a finding, not a detail.
• Give it six weeks before drawing conclusions, and less than that if anything is becoming weaker.

If it has not settled by then, the question stops being what caused it and becomes which structure is sustaining it — and that one has a testable answer.