Sets per week is a speedometer. Proximity to your volume ceiling is the map.

Sixteen sets, and the log is already lying

Sixteen sets of chest this week. Sixteen last week, sixteen the week before, all the way back to the start of the block. The weekly-volume number has not moved, so the block reads as steady, on-plan, nothing to see. The lifter running it is four days from a session where the same top set at the same load stalls out near RPE 9.5, and the following bench day feels like moving furniture. The set count never warned him. It could not. It was never measuring the thing that had been changing for six weeks.

The speedometer and the map

Sets per week is a speedometer. It reads output at an instant: how much work you did this week, full stop. A speedometer is honest and useless on its own, because it cannot tell you where you are on the road. What a lifter deep in a hypertrophy block actually needs is a map: where you sit on the arc that runs from the least volume that still grows you to the most your body can recover from. That arc has a name in the programming literature, MEV to MRV, and your weekly set count is not plotted on it.

Why the set count lies by staying still

Volume gets treated as the input you dial. Add a set when progress stalls, that is standard advice, and it holds up fine. The error is treating the number you dialed as the number that matters. Set count is what you prescribed. Proximity to your recoverable ceiling is what you got, and the two pull apart the moment fatigue starts accumulating faster than you clear it. Hold sixteen sets constant for six weeks and the prescription is flat while the cost of paying for it climbs every session. A stable input over a moving system is not stability. It is a speedometer pinned at one number while the terrain goes vertical.

MEV MRV explained: what the volume research actually frames

The volume landmarks come from Renaissance Periodization and Mike Israetel: MEV, the minimum effective volume that still drives growth; MAV, the maximum adaptive volume where return per set is best; MRV, the maximum recoverable volume, the ceiling past which you bank more fatigue than you can pay back. Stronger by Science has made the harder, more useful point: these landmarks are individual, they drift within a block, and they move with your sleep, your stress, and how hard those sets actually were. The dose-response work on volume, Schoenfeld and colleagues' 2017 meta-analysis among it, shows more weekly sets tends to mean more hypertrophy, up to a point. The whole game is finding that point, and it keeps moving under you.

How to know when to deload based on volume: a six-week read

Take a lifter on a chest-focused block, sixteen working sets a week, holding a top set of five reps he wants to keep for the mesocycle. Week one, that top set comes in around RPE 7.5 and he is ready to go again after three minutes. He does not touch the set count, because the plan says hold volume and push load or reps. By week three the same top set reads RPE 8, and he is taking closer to three and a half minutes between heavy sets to feel ready. Week five, RPE 8.5, rest creeping past four minutes, the last two sets getting grindy. Week seven, that top set is a 9, rest sits at five minutes, and the reps on his back-off sets are quietly dropping. The speedometer says sixteen, sixteen, sixteen. Flat. The map says he crossed MAV somewhere around week four and has been climbing toward MRV ever since. The deload was due two weeks before the week it finally forced itself.

The speedometer said sixteen. The map said deload, two weeks ago.

What changes when you read the arc instead of the calendar

Deloads stop being something you pencil in every fourth or fifth week by default and become something you read off the trend. Some blocks earn a deload at week four; some hold recovery well enough to push to seven. The set count cannot tell them apart, so calendar-based deloading either pulls the trigger early on a block that had more in it or waits too long on one that was cooked by week five. Reading the MEV-to-MRV arc means the deload lands when the signals converge: rising RPE at fixed load, lengthening rest, back-off reps bleeding. Not when the calendar says so. That is the gap between managing a training block and surviving one.

The arc only shows up at high enough resolution

None of this is visible in a weekly-volume number, and that is the catch. The arc lives in the relationship between set count and everything around it: top-set RPE, rest, load, reps at load, tracked set by set and read across six weeks instead of glanced at one session at a time. Most trackers surface the volume figure because it is the easy one to compute and the satisfying one to watch climb. The signals that actually plot you on the arc take consistent per-set logging and a view that spans a full mesocycle. Platepusher records RPE, rest, and load at the set level and holds them across the block, so the drift shows up as a trend rather than a surprise. The instrument holds no opinion about your deload. It shows the slope you are on and lets you read it, which is what a lifter with a coach or a program already knows how to do once the data is in front of him.

What we're watching

The open question is how much of this can be read from bar speed. Rising RPE at fixed load and lengthening rest are proxies for accumulating fatigue; velocity loss across a set is a more direct one, and velocity tracking keeps getting cheaper. Whether a phone-grade signal is sharp enough to plot the MEV-to-MRV arc on its own, or only good enough to confirm what RPE and rest are already telling you, is the thing worth logging carefully enough to find out.