Your weekly volume is math. Missing sets turn it into fiction.

Eighteen sets in the squat rack. Fourteen in the log.

Picture week four of a quad-focused mesocycle. Across two sessions the lifter ran hack squats, a back-off set of high-bar squats, leg extensions and walking lunges, and by Friday the knees feel like wet sand. Eighteen working sets for quads.

The log says fourteen.

Four sets went missing in the usual places. One was a back-off set done while someone waited for the rack. Two were leg extension drop sets that felt too awkward to enter between mini-sets. The last was a lunge set finished at 7:40 p.m. with the gym packed, and the phone was in a bag on the far side of the floor. None of it felt important at the time.

Then Sunday comes. The lifter opens the weekly totals to plan the next block and reads a number that's wrong by more than a fifth.

The capture gap: sets performed minus sets logged

Call it the capture gap. Every volume framework a serious lifter uses runs on one input, hard sets per muscle per week, and that count comes from the log. Sets performed happen in the gym. Sets logged are the only ones the math ever sees.

The volume debate assumes those two numbers match. Threads in r/naturalbodybuilding and the r/JeffNippard community argue 10 versus 20 sets a week, whether indirect work counts as a full set or half of one, whether the top of the range is worth the recovery bill. Good arguments, all of them. And every one quietly treats the weekly total as a measured fact.

For most lifters it's an estimate with a hidden bias. Four sets missing out of eighteen is a 22% undercount. An error that size puts you somewhere else on the curve.

Missing sets cluster on the hardest work

The comfortable assumption is that logging misses are noise. A set here, a set there, and it washes out over a block.

The misses aren't random, so they don't wash out. Look at where sets go unrecorded. Drop sets and myo-reps, where typing a number between mini-sets feels absurd. Back-off sets at the end of a session, when the lifter is gassed and the phone is across the room. Supersets, where two movements share one rest period. Peak-hour sessions, when someone is hovering for the station and the app wants several taps before it'll take the next set.

Every item on that list sits at the high-fatigue end of training. So the log undercounts the exact sets that generate the most fatigue, and it does it most in the late weeks of a block, when sessions run long and sets pile up. Noise averages out over a mesocycle. Bias points the same direction every single week.

Noise averages out over a mesocycle. Bias points the same direction every single week.

How do you track training volume accurately?

Renaissance Periodization's volume landmarks were never meant as universal numbers. MEV, MAV and MRV are individual, and the RP approach locates them by running blocks, reading soreness, pump and performance, and adjusting sets week to week. Stronger By Science has written at length about the dose-response relationship between weekly sets and hypertrophy, and about how individual responses spread around any group average.

Both approaches share a dependency that rarely gets said out loud. Individual calibration means your landmarks get estimated from your own records. Autoregulated set counts mean the program sheet can't tell you what you did, because the sets changed in the gym. That leaves the log as the measurement instrument. If it undercounts, every landmark you estimate from it inherits the error.

So the accurate answer to this question starts before any counting rule. Pick one rule for indirect work and keep it constant. Count working sets only. Capture every set at the moment it ends. The third step decides whether the first two mean anything.

One mesocycle, walked through

Run the opening scenario across a whole block. The lifter starts at 12 working quad sets and adds two a week as recovery allows, a standard ramp. The gap grows by one set each week, because each added set lands later in the session or inside a drop-set cluster, right where capture breaks down.

By week four the log shows 14 while the lifter performed 18. Across the block, 60 sets happened and 50 got recorded. One set in six never existed as far as the math knows.

Now the Sunday planning session. Week four felt brutal, so the lifter marks it as the edge of recoverable volume and writes down an MRV of about 14 sets. The next block caps there. But the volume this lifter actually survived was closer to 18, so the new block opens well under demonstrated tolerance and the growth it was supposed to buy comes slower. And the error now lives inside the landmarks, so every block planned from them carries it forward.

Capture speed belongs to the program

If the capture gap is real, the order of operations changes. Arguing 12 versus 16 weekly sets is premature until your log can tell those two numbers apart.

A one-week audit shows where you stand. Keep a paper tally of every working set as it ends, in a notebook left on the bench or the floor, and keep logging the way you normally do. At the end of the week, compare the tally to your weekly totals per muscle. A gap of more than a set or two on any muscle means the volume math you've been running is off, and now you know which way.

Then look at where the gap lives. If it's drop sets, find a way to enter the cluster as one record. If it's peak-hour sessions, the bottleneck is the seconds between racking the weight and having the set recorded. Every bit of friction there is a set that might not make the log. And a set that isn't in the log doesn't count toward MEV, MAV or MRV, whatever your quads have to say about it.

Where Platepusher fits

Platepusher was built around this exact moment. A gym log for lifters with years of history is only as good as its capture, so the first design question is how fast a working set goes from racked to recorded, including from the Apple Watch when the phone is in a bag across the floor. Weekly totals, history and plateau flags all sit downstream of that one moment.

The log doesn't tell you what MRV to chase. It records what you did, completely enough that the landmarks you estimate from it describe you. And if years of training live in another app, they import as native history, so next block's volume math starts from your full record instead of from zero.