Your old shoulder tweak is still programming your bench.
Fitness apps log around an injury and then forget it happened. A joint that flared three years ago should still shape today's volume and exercise selection.
The same shoulder, three years apart
Take a lifter four years into structured training. In year two, the left shoulder started catching at the bottom of a paused bench. They pulled heavy pressing for a couple of weeks, swapped in floor press, eased back, and by the end of the block the log shows top sets right where they'd been. As far as the app knows, that's the end of it.
Then the shoulder catches again. Same lift. Same spot in the range.
So they scroll back to see what happened last time. The log has every set, every rep and every date. It has no marker saying this is where it started, or this is when they were back. If a note survived, it says "shoulder." The questions that matter (how much weekly pressing was in that block, whether they'd just added a second bench day, which grip they were running) all have answers somewhere in the data. Nobody pinned those answers to the flare-up, so finding them means rebuilding a two-year-old block from memory.
The missing column
Every serious log tracks the same variables: load, reps, sets, RPE, date, exercise. Injury history behaves like one of those. It changes what you can load, how much weekly volume a joint tolerates, and which variations you quietly stop programming. It just never gets a column.
Call it the missing column. An old injury keeps acting on training long after the pain stops, and a log that only records the interruption throws away the part that keeps mattering.
The shoulder that flared in year two is a standing input to every pressing block that comes after it. The log should carry it forward like one.
Why logging around an injury loses the record
The standard advice for training through a tweak makes sense as far as it goes: modify, keep moving, log what you can do. Most tracking apps support exactly that and little more. The injury shows up as a gap in the chart, a substituted exercise, or a note you remember to write on one session.
The trouble is how success gets measured. Recovery counts as done once you're back to the old top set, and then the episode is closed. But getting back to the same numbers under the same conditions is also how you recreate whatever came before the first flare-up. And a gap in a chart reads as missing data, which every trendline smooths over.
Run the audit below against your own log. The left column is what a lifter ends up asking years later.
The question, three years later
What a typical log can answer
What the log needs to answer it
What was my weekly pressing volume in the block before it flared?
Yes, if you can work out which weeks to look at
The flare-up date pinned to the record, so the block is easy to find
Which variation and grip was I running?
Yes, buried in individual sessions
The same data, filtered to the weeks before the flare-up
Which joint, side and part of the range hurt?
Only if a free-text note survived
A consistent entry: joint, side, movement, range
How long did the return take?
Guessable from gaps and substitutions
A marked start and end of modified training
Has this joint flared before, and how many times?
No
Every flare-up for that joint, in one list
The missing-column audit. Run it against your own log.
Does a previous injury raise the risk of another one?
Prior injury is one of the most consistently reported risk factors in sports injury research. In a 2006 study of elite footballers published in the British Journal of Sports Medicine, Hägglund, Waldén and Ekstrand found that players with a previous hamstring injury, groin injury, or knee joint trauma were two to three times more likely to suffer an identical injury. ([source](https://pubmed.ncbi.nlm.nih.gov/16855067/)). Football isn't lifting, but the direction of the finding is hard to ignore.
Closer to the barbell, Keogh and Winwood's 2017 review in Sports Medicine pulled together injury epidemiology across the weight-training sports. They report the shoulder, lower back, knee, elbow, and wrist/hand were generally the most commonly injured sites. ([source](https://pubmed.ncbi.nlm.nih.gov/27328853/)). Those are the joints you load on every squat, bench and deadlift day.
Put those together and the picture is uncomfortable. The joint you've already hurt is a prime candidate for the next injury, and you train it several times a week. Population studies can't tell you where your own threshold sits, though. Your record can, but only if it knows when the flare-ups happened.
This is about the record. Rehab is a separate job.
Nothing here is a return-to-training protocol. A log describes what came before a flare-up. A physio or physician diagnoses it and decides what you load. Take sharp or worsening pain, numbness or swelling to a clinician before you put it in a spreadsheet.
What the last three flare-ups look like on the record
Rerun the opening scenario with one change. Each time the shoulder flared, the lifter added a dated entry in the same shape: joint, side, movement, position in the range, what they changed. It takes five seconds to type.
Three years later the shoulder catches again, and this time the question has an answer: what was I doing the last three times this joint flared up?
Suppose the answer looks like this. Each flare-up landed a few weeks into a block where weekly pressing sets had been climbing. Two of the three came after close-grip work went in as a second heavy day. The return took longer each time. That's a pattern the lifter can see for themselves, and one a physio would probably want to hear about. Explaining it is still the physio's job.
What to do with it stays the lifter's call. Maybe the next block caps pressing volume a little below where the trouble started. Maybe close grip moves to a lighter day. The log stays descriptive. It hands back what the lifter's own training already recorded.
A training log worth keeping lets you ask what you were doing the last three times this joint flared up.
If injury is a variable, the comeback stops being a reset
Treat injury history as data and a few things change.
Exercise selection gets a reason. The variation you've drifted away from for two years either has a dated flare-up behind it or it doesn't, and you'll know which.
Volume gets a ceiling with a source. A lifter who can see that a joint has complained at a particular weekly load has a number to plan under, and it comes from their own record.
And a comeback no longer wipes the slate. Right now, hitting your old top set again reads as the end of the story. With the flare-up on the record, it's one point in a longer series, and that series can tell a lifter in year five something they couldn't have known in year one.
Most apps are built around the week in front of you. Injuries play out over years, and that's the timescale the log needs.
Keep the years where the first flare-up lives
Every one of those questions depends on the history still existing. Lifters who switch apps or abandon a spreadsheet often leave behind the very years their first injury sits in. A log that starts fresh can't tell you what came before something it never saw.
Platepusher imports a CSV from Strong or Hevy, so every lift, set and date arrives as native data. The block before that first flare-up comes with you. Full history stays on the free tier, and CSV export is free at every tier, so the record stays yours either way.
Until your log has a real injury column, give it a consistent note: joint, side, movement, where in the range, what you changed, and the date you were back to normal training. Use the same shape every time so it's searchable later. It's the cheapest training data you'll ever record, and three years from now it's the entry you'll most want to find.
Log the injury the way you log the load.
Bring your whole training history into Platepusher, including the blocks your old injuries came out of.
Platepusher imports multi-year training histories from Strong or Hevy as native data, with every lift, set and date intact. Full history stays on the free tier and CSV export is free at every tier, so the blocks that came before your old flare-ups stay on the record and stay yours.
