The Block-to-Block Pattern Your Log Is Tracking (And Your App Isn't Showing You)

Article ยท 5 min read

Three logged blocks beat any volume landmark someone else calculated for you.

After three logged mesocycles in one movement, your own volume trend beats any population landmark. Here's how to read the slope and program the next block from it.

Block four, and the chest work is going backwards

Block four of the same upper-body hypertrophy template, and the pressing is sliding. You added two sets walking in, because the volume landmarks said there was headroom. The top set that hit 12 at RPE 8 back in block one is grinding to 9 now, and the pump you used to chase feels like wading through it. Nothing in the program is broken. The template is fine. The number you trusted just quietly stopped being about you, and your log has been recording the reason for eleven weeks.

Your volume response has a slope, not a setpoint

Call it the three-block prior. After three consecutive mesocycles logged in the same movement pattern, the direction your volume response has moved across those blocks tells you more than any range derived from a population ever could. Not the average of your sets. The slope. Did your recoverable volume expand between block one and block three, or did it contract, and what moved it. That trend is the highest-resolution programming signal you own, and it doesn't exist for anyone who started their log three weeks ago. It's the one thing a multi-year history gives you that a spreadsheet of this week's sets can't: change, measured against yourself, over time.

Three blocks in the same movement don't give you an average. They give you a slope.

MRV was never a coordinate to locate

The common read treats maximum recoverable volume as a personal constant, a number you find once and then live inside. Add sets until you hit the wall, mark the wall, program under it. But recoverable volume isn't a coordinate. It drifts across a training year and sometimes across a single block, pushed by accumulated fatigue, exercise rotation, sleep, and whatever your life outside the gym is doing to your recovery. A landmark pulled from a group study can tell you roughly where lifters like you tend to land. It can't see your slope, because it was never measured on you across time. So the lifter who keeps chasing a fixed MRV number ends up adding volume into a response that's already trending down, and reads the resulting stall as needing more.

The frameworks already told you to autoregulate

This isn't a knock on the landmarks. Renaissance Periodization popularized the whole volume vocabulary most serious lifters now think in: MV, MEV, MAV, MRV. Stronger By Science, mostly through Greg Nuckols, has spent years publishing on the volume dose-response, and the consistent finding is that the curve is real at the group level and enormously variable at the individual level. Jeff Nippard builds natural-lifter programming off the same ranges. Read any of them closely and the instruction is identical: these numbers are a starting point, then you adjust to the athlete in front of you. The ranges are a prior. They're the right prior when you have zero blocks of your own data. The problem is that most lifters treat the prior as the answer forever, because the tool in their pocket only ever shows them this session and this block, so the trend that would replace the prior never gets surfaced.

A prior, not a verdict

A landmark answers *where do lifters like me usually start*. Your three-block trend answers *which direction have I actually moved, and why*. The first is a guess about a population. The second is a measurement of you. When you have three blocks logged, the second wins.

What three blocks of a horizontal press actually show

Take a lifter running the same upper template through three blocks, same movement pattern, adding volume each cycle the way the landmarks suggest. Look at weekly hard sets against a per-set output proxy, say top-set reps at a fixed RPE. Block one sits at a comfortable baseline. Block two adds sets and output dips slightly, which reads as normal accumulation. Block three adds more sets and output drops hard. Averaging those three blocks gives you a middling set-count that describes none of them. The slope tells the real story: this lifter's recoverable volume for that pattern contracted across the run, it didn't expand, and the added sets were paying negative interest by block three. The likely driver shows up in the same log: an exercise rotation between blocks one and two that changed the stimulus and the fatigue cost. You can only see any of this because three blocks sit next to each other in one record.

BlockWeekly hard sets (chest)Top-set reps @ RPE 8What the slope says
N-21212Baseline response
N-11511Volume up, small output dip: reads like normal accumulation
N179Volume up again, output falling fast: recoverable volume contracted
Illustrative three-block log for one horizontal-press pattern. Same lifter, same template, sets added each block. The average set-count (about 15) describes none of these blocks; the downward slope describes all three.

You write the next block from your slope

If the three-block prior holds, the next block stops starting from the landmark. It starts from the direction you're already moving. A lifter whose recoverable volume contracted across three blocks doesn't add sets going into block four, they hold or cut and change a variable that the log flagged, like the exercise that rotated in. A lifter whose output held steady while volume climbed has genuine room and can push. Same landmark, opposite calls, and the only thing that separates them is three blocks of their own history read as a trend instead of a snapshot. This is what it means for a log to be a programming asset rather than an archive. The blocks you've already trained are the experiment. The slope between them is the result. Re-running the population average every cycle throws that result away and re-zeros you back to a stranger's prior.

The chart is arithmetic, not coaching

Most workout apps are built for week one, not year five. They'll show you today's session and this block's tonnage, and then the block ends and the view resets. The multi-block trend, the one thing that would actually replace the landmark you've outgrown, is the view they don't render, even though the data to draw it is sitting right there in your history. Platepusher's stance on this is deliberately narrow. The log already holds your last three blocks. Plotting set-count against your top-set output across them is arithmetic, and it belongs to you, so the app draws the slope and gets out of the way. No prescription, no chatbot telling you to deload. It shows the direction; you make the programming call, because you know what rotated in and what your life was doing to your recovery. Recognition, not motivation. The instrument hands back what your own work recorded.

What we're tracking next

The open question the worked example raises is exercise rotation. A clean block-to-block slope assumes the movement stayed the same, and the moment you swap incline barbell for a dumbbell variation, you've partly reset the fatigue cost and the stimulus, which muddies the trend. So the next piece looks at how much rotation your log can absorb before the slope stops being comparable, and whether pattern-level volume (all horizontal pressing) reads cleaner across blocks than exercise-level volume when you rotate often.

Keep your blocks in one record and let the slope show up. Get Platepusher.

Every volume framework worth trusting, from RP's landmarks to Stronger By Science's dose-response work, says the same thing in the fine print: the ranges are where you start, then you autoregulate to the athlete. The three-block trend is what autoregulation looks like when you actually have the data to do it. Platepusher keeps that data intact across blocks and years and draws the slope, so the adjustment isn't a guess.