Training Around Pain and Returning After Injury

Scope, stated first. This document covers how a training programme should behave when an athlete reports pain or is coming back from an injury. It is not a diagnostic guide and does not substitute for assessment by a qualified clinician. Diagnosis, rehabilitation prescription, and clearance to return are medical decisions. What follows is about the programme: what to modify, what to remove, how to progress load back, and — most importantly — when to stop programming and refer.

The reason this matters for automated programme design is specific: an athlete reporting pain is the situation where a plan is most tempted to improvise, and improvised medical advice is worse than no advice. The correct behaviour is narrow and conservative.

Key Principles

1. Some presentations are not training problems. Refer, do not modify.

Stop programming and direct the athlete to a clinician when any of the following is present:

• Pain following significant trauma — a fall, a collision, a sudden pop or tearing sensation.
• Inability to bear weight, or a joint that gives way.
• Visible deformity, significant swelling that appears rapidly, or extensive bruising.
• Numbness, pins and needles, or weakness radiating into a limb.
• Pain that wakes the athlete at night, or that is unrelated to activity.
• Pain accompanied by fever, unexplained weight loss, or general illness.
• Chest pain, breathlessness disproportionate to effort, dizziness or fainting during exercise.
• Any pain that is worsening week on week despite reduced load.

These are not cues to reduce volume. They are cues to stop and refer. A programme that responds to them with "reduce sets by 20%" is doing harm.

2. Below that threshold, modify rather than stop entirely

For the common presentation — a familiar ache, a joint that objects to one specific movement, mild soreness that lingers — complete rest is usually the wrong response. Tissue adapts to load, and removing all of it deconditions the area and everything attached to it.

The order of preference:

1. Change the exercise — same pattern, different execution. Painful barbell back squat → goblet squat, split squat, or leg press.
2. Change the range — work in the pain-free portion of the movement and expand it over weeks.
3. Change the load or tempo — lighter, slower, more controlled.
4. Change the volume — fewer sets before fewer sessions.
5. Remove the movement, keeping everything else training.
6. Rest the area entirely, which is the last resort and rarely the first.

Whatever the athlete can do without pain, they should continue doing. An injured knee is not a reason to stop training the upper body.

3. Pain during training is information, and the threshold is usable

For persistent, non-acute musculoskeletal pain, a widely used practical rule is that mild pain during exercise is acceptable provided it settles quickly and does not worsen the following day. Working definitions in common use:

• Pain up to roughly 3 on a 0–10 scale during the exercise: acceptable.
• Pain that returns to baseline within roughly 24 hours: acceptable.
• Pain above that, or still elevated the next morning: the load was too high. Reduce and retry.

This is a rule for known, chronic, non-alarming presentations, applied under professional guidance — not a licence to push through unfamiliar pain.

4. Return is progressed by load, not by time

"Six weeks and back to normal" is not a plan. Returning athletes progress through criteria: pain response, range, control, and demonstrated capacity at each stage before moving to the next.

A useful sequence for a returning limb or region: pain-free range → controlled load through that range → progressive strength → speed and reactive qualities → sport- or task-specific demands. Each stage is entered when the previous one is tolerated, not when a date arrives.

5. The most dangerous week is the one after it stops hurting

Symptoms resolve before capacity returns. An athlete who feels fine at week four has a tissue that has not yet regained the strength it had at week zero, and the reinjury rate reflects it.

Programmes should assume that the return progression continues past the point where the athlete feels ready, and should reintroduce the highest-risk qualities — maximal speed, maximal load, change of direction — last and deliberately.

6. Load rises gradually, and the previous fortnight is the reference

The strongest single predictor of a load-related problem is a sharp increase relative to what the athlete has recently been doing. Weekly increases in the region of 10% are a conservative and widely used ceiling for volume, and the same logic applies to intensity, distance, and vertical gain.

Returning athletes have a low recent load by definition. The comparison is with the last two or three weeks, not with what they could do before the injury.

Guidelines & Recommendations

Modifying a session, by region

• Lower back: remove loaded spinal flexion under fatigue and heavy axial loading. Retain hip-hinge patterns at reduced load, trunk anti-extension and anti-rotation work, and all upper-body training. Walking is usually well tolerated and worth keeping.
• Knee: reduce range before reducing load; box squats and partial-range work often permit continued training. Retain hip and hamstring work. Avoid high-volume deep flexion under load and impact until controlled.
• Shoulder: remove overhead pressing before removing all pressing; horizontal work at reduced range is often tolerated. Retain scapular and rotator cuff work at low load, and all lower-body training.
• Achilles and calf: remove plyometric and sprint work first — it is the highest-risk load and the least necessary. Retain heavy slow resistance work, which is generally well tolerated.
• Hamstring: most sensitive to high-speed running. Remove sprinting entirely, retain progressive eccentric loading, and reintroduce speed last, in small doses.

Communicating a modified programme

A programme that modifies for pain should say so explicitly and say why: which exercise changed, what it was replaced with, and what would need to be true to go back. Silent substitution leaves the athlete unable to tell whether the plan noticed.

It should also state plainly that it is not a diagnosis and that persistent or worsening pain warrants assessment.

What a programme must not do

• Diagnose. "This is patellar tendinopathy" is a clinical judgement.
• Prescribe a rehabilitation protocol for a specific diagnosed injury.
• Recommend medication, injections, imaging, or any medical intervention.
• Advise pushing through pain that fails the criteria above.
• Set a return date.
• Interpret pain that meets any of the referral criteria as a load-management problem.

Key Takeaways

• Recognise the presentations that require referral, and stop programming when they appear.
• Below that threshold, modify before removing and remove before resting entirely.
• Keep training everything that does not hurt.
• Mild pain that settles within 24 hours is usually acceptable for known, chronic presentations.
• Progress the return by demonstrated capacity, not by the calendar.
• Expect symptoms to resolve before capacity does, and keep progressing past the point of feeling fine.
• Compare load with the last two or three weeks, not with pre-injury baseline.
• Never diagnose, never prescribe rehabilitation, never set a return date.