Is Your Bulk PR Actually a Relative Strength Regression?

Article ยท 5 min read

A 20-lb squat PR on a 20-lb bulk is not a PR.

A 20-pound squat PR on a 20-pound bulk can leave you weaker per pound than you were in June. Most logs never say so, because they only track the top half of the fraction.

You added 20 pounds to the bar and 20 pounds to yourself

Sixteen weeks of a deliberate surplus. You started the block at 185 and squatted 405 for a hard triple. You finished at 205 and squatted 425 for the same triple, same depth, same belt, roughly the same RPE. The app logged a PR. Green highlight, new record, well done.

Now run the ratio. 405 at 185 bodyweight is 2.19 times bodyweight. 425 at 205 is 2.07. To hold the number you were carrying in June, you needed about 449 on the bar, not 425. The bar went up 4.9 percent. You went up 10.8 percent. Somewhere in those sixteen weeks, per pound of you, you got weaker, and nothing in your log said a word about it.

The missing denominator

Call it the missing denominator. Every strength number in your log is the top half of a fraction, and the bottom half is you. Move the denominator and the number on the bar stops meaning what it meant last month.

A pound of bodyweight isn't free. It gets carried through the unrack, the descent, the sticking point, and it gets carried up the stairs at work for the rest of the block. When load rises 5 percent and bodyweight rises 11 percent, the honest reading is that absolute output improved and strength per pound fell. Both things are true at the same time. Only one of them made it into the record.

Why absolute load became the default

Absolute load is the easiest thing a tracker can render. One number, one direction, one highlight color. It needs no second data series and no arithmetic, and it produces a celebration event every few weeks, which is what most fitness software is built to produce.

Bodyweight, where it appears in this category at all, tends to live in a separate wellness tab next to sleep and steps. Charted on its own timeline, against its own goal, never touching the lift history. Two series, two silos, and the one calculation that would connect them gets left to the lifter with a phone calculator between sets.

So the default read on a gaining phase is structurally optimistic. Bar goes up during a surplus. Of course it does. Some of that is neural, some is technique, some is leverage from a fuller torso and a bigger arch, and some is real tissue. The log reports all four as the same event.

Powerlifting already solved this at the sport level

Competitive powerlifting has never accepted absolute load as the measure of the better lifter. That's what weight classes are for. And when the sport needed to compare lifters across classes, it built coefficients to do it: the Wilks formula, developed by Robert Wilks of Powerlifting Australia, and the IPF's own scoring system, now IPF GL Points. Best Lifter awards run on those numbers, not on the heaviest total in the building.

Those formulas exist because the relationship between mass and strength is real and predictable enough to correct for. A heavier lifter is expected to move more weight. The correction says how much more, so the comparison means something.

None of it transfers down to the gym lifter, who has no class, no meet, no coefficient, and no scoreboard except an app that only knows what was on the bar. The sport built the correction eighty years into its history. The consumer tracker never inherited it.

Why the sport formulas curve instead of just dividing

Strength doesn't scale one to one with bodyweight. Muscle force tracks roughly with cross-sectional area, which rises with the square of a linear dimension, while mass rises with the cube. That's the geometric-similarity argument behind allometric scaling, and it's why a coefficient beats naive division when you're comparing a 165 lifter to a 275 lifter. For comparing you to you across a 20-pound swing, plain load divided by bodyweight is close enough and far easier to read.

Reading a full gain-and-cut cycle

The read takes one comparison: percent change in load against percent change in bodyweight over the same window. Load moved more, the ratio improved. Bodyweight moved more, it didn't, whatever the record banner said.

Same lifter as the open, same squat, same triple, same depth, across a full 24-week cycle.

Week 8 is the row that matters. The bar had already moved, the app had already fired a PR, and the ratio was already down 2.8 percent from baseline. Nothing was wrong with the block. But a lifter reading only the left half of that table concludes the surplus is buying strength faster than it's buying mass, and it isn't. Week 24 is where the block actually pays out: 420 at 193, essentially the ratio they started the year with, now carrying 15 more pounds on the bar. That's the win. It landed eight weeks after the app stopped congratulating them.

Point in cycleBodyweight (lb)Top triple (lb)Load / bodyweightWhat the log showed
Week 0, pre-bulk1854052.19Baseline
Week 8, mid-bulk1954152.13PR banner. Ratio down 2.8%.
Week 16, end of bulk2054252.07PR banner. Ratio down 5.3%.
Week 24, post-cut1934202.18No PR. Ratio back to baseline.
Illustrative arithmetic on one worked example, not survey data. Same lifter, same lift, same triple across a 24-week gain-and-cut cycle. Ratio is top-set load divided by bodyweight on the day.

What changes if you read it this way

Treat an absolute PR set during a gaining phase as unverified until you've checked the ratio. That's the whole shift, and it moves three decisions.

When to end a bulk. If the ratio has fallen for eight straight weeks while the rate of load gain flattens and the scale keeps climbing, the surplus has stopped buying strength and started buying the other thing. That's a readable signal weeks before the mirror gives you one.

What counts as a win on a cut. Holding 420 while dropping 12 pounds is one of the largest relative strength improvements a trained lifter can produce, and almost nothing will mark it, because the bar number went sideways. A good share of the cut phases that feel like failure are ratio PRs nobody logged.

Whether the program is doing anything at all. Across a year of gaining and cutting, the absolute curve is a sawtooth driven mostly by scale weight. The ratio curve is the one that shows whether the training worked.

This is not an argument against gaining weight

Mass is a legitimate driver of absolute strength, and a temporary ratio dip during a deliberate surplus is expected, often correct, and sometimes the entire point, especially for a lifter moving up a class or chasing a total. The failure isn't the dip. It's spending four months inside one without knowing, because nothing in the log could have told you.

Both numbers have to live in the same history

None of this is computable unless bodyweight and the lift log sit on one timeline. That's a storage decision more than a feature. One history, so any set from any block can be read against what the lifter weighed the week they hit it, without exporting two files and joining them by date in a spreadsheet.

Platepusher keeps them together for exactly that reason. Bodyweight is part of training history rather than a separate wellness corner, and years of prior lifting import as native data, so the ratio reads backward across blocks you ran long before you installed anything. The math describes what happened. It doesn't tell you to cut, and it won't hand you a plan.

One rule for the next block: before you write down a PR, write down what you weighed. The second number is what makes the first one mean anything.

Keep bodyweight and the bar on one timeline, and read the ratio across every block you've already run. Platepusher for iPhone and Apple Watch.

Platepusher was built for lifters with multi-year logs, which means it was built for lifters who have already been through several gain-and-cut cycles and watched their PR history turn into a sawtooth. Bodyweight lives inside training history, not beside it. Existing history imports as native data, so the relative strength read works on blocks you ran years ago, not just the ones you log from here.