Your Volume Methodology Will Change. Your Log Shouldn't Have to Start Over.

Article · 4 min read

Log the atoms, not the analysis: your methodology will change.

Serious lifters swap volume frameworks as they learn. A raw log of sets, reps, weight, and RPE survives every switch. An aggregate total doesn't.

The number you tracked for three years might be the wrong number

Three years of tonnage sits in your training app, and the volume video you just watched says tonnage was the wrong thing to count. You've got MEV/MRV curiosity now, or a hard-set-counting itch, and you want to know what your last three years actually looked like under the new frame. So you open the app. It hands you a weekly tonnage line and nothing else. The sets are gone, folded into a total the moment they were saved. Your history is intact and useless at the same time, because the app kept the answer to a question you no longer care about.

Log the atoms, not the analysis

One rule survives every framework change: log the atoms, not the analysis. The atoms are the irreducible facts of a set, the exercise, the weight, the reps, the RPE, and whatever effort note you scribbled. Tonnage, hard-set counts, MEV/MRV, fractional volume: every one of them is a calculation you run over those atoms. None of them is data. They're all just a query. Store the atoms and you can run any query, today's or the one you'll believe in two years. Store the query's output and you've thrown the atoms away. The methodology is a lens. The log is what the lens points at, and lenses get swapped a lot faster than a training career ends.

Why 'which volume metric wins' is the wrong fight for log design

Scroll r/weightroom or Stronger By Science on any given week and the argument is always the same shape: which volume metric predicts hypertrophy best. Tonnage people cite total work. Hard-set people say tonnage rewards junk reps you were nowhere near failure on. Fractional-counting people say a hard set isn't even a clean unit. It's a good argument, and it's the wrong one to base your logging on. You aren't going to settle a debate that Examine.com and a stack of PhDs haven't. What you can settle, on your own, is whether your log can answer that debate whichever way it lands. The metric is contested. Sets, reps, weight, and RPE are true no matter whose model wins, and they're the input to all of the models.

MEV/MRV, fractional sets, tonnage: same log, different query

Line up the frameworks actually in play and look at what each one demands from a log. Renaissance Periodization's MEV/MRV model (Mike Israetel's work) counts hard sets per muscle per week against a recoverable ceiling, so it needs set counts, a proximity-to-failure marker, and a muscle mapping. Simple tonnage needs weight and reps per set and nothing else. Stronger By Science's discussion of fractional set counting goes the other way, giving partial credit to indirect work, so it needs per-exercise muscle involvement on top of the raw sets. Different questions, same source data. Every row below reduces to sets, reps, weight, RPE, and exercise. The log that stored those can compute any of them. The log that stored a weekly total can compute none.

FrameworkSourceUnit of analysisFields it needs from the log
TonnageClassic strength literatureSets × reps × weightWeight, reps per set
Hard-set countingSchoenfeld-era hypertrophy researchHard sets / muscle / weekSet count, RPE or RIR, muscle group
MEV / MRVRenaissance Periodization (Israetel)Recoverable hard sets / muscle / weekSets, RPE/RIR, muscle group, week-over-week performance
Fractional volumeStronger By Science (Nuckols)Weighted set fractions / muscleSets, RPE, per-exercise muscle involvement
Every framework is a different query over the same raw fields. Store the fields, run any query.

What a methodology switch actually costs

Take a concrete case. A lifter runs a tonnage-based hypertrophy block for three years, chest tonnage climbing on a clean line, and feels stalled while the number keeps going up. He works through the hard-set material and realizes his tonnage was inflated by high-rep cable work he was well short of failure on. Now he wants to recount those three years as hard sets per week, to see where chest volume really sat when growth was happening versus when it stalled. If his log kept every set with an RPE, that's a filter and a recount, an afternoon's work, and he's got three years of hard-set history to read the stall against. If his log kept weekly chest tonnage, he's got a number that already baked in the reps he now knows don't count. The experiment ran. The record of it didn't survive contact with a better question.

The log is the experiment. The methodology is one pass over it.

The design question for a strength log isn't which volume model to build around. It's whether the log stays raw enough to outlive the model you build around today. A log that computes MEV/MRV for you is helpful right up until you stop believing in MEV/MRV, and then it's a cage. The honest shape is boring: keep every set as its own row, keep RPE and effort notes attached, and let the analysis pass be something you re-run, not something baked in at write time. This is the whole reason a raw export matters, and why it should be free at every tier. Not because you'll migrate next week, but because the export is proof the log is yours to re-interrogate. Platepusher stores the atoms and hands them back on request, in the exact column shape a spreadsheet or the next app can read. The methodology stays yours to change.

The trap: aggregate-at-write-time

If an app persists your weekly tonnage total or a computed hard-set count instead of the raw sets, the atoms are gone the moment you save. You can always compute an aggregate from raw sets. You can never recover raw sets from an aggregate. Check what your tracker actually stores before you trust it with three years.

What we're watching next

The volume debate keeps splintering rather than settling. Fractional-counting and hard-set camps are diverging, and newer arguments about stimulus-to-fatigue ratios and effort proximity are adding fields nobody was logging five years ago. Every one of those new models will ask the same thing of your history: did you keep enough raw signal to answer me. The lifters who kept sets, reps, weight, and RPE at the atomic level get to say yes to models that don't exist yet. When the field itself hasn't settled, that's the only future-proofing there is.

Keep the atoms. Log every set raw with Platepusher, so your training history outlives whatever volume framework you're running now.

Platepusher keeps every set as its own row, the exercise, weight, reps, RPE, and your effort notes, and hands the whole log back as a CSV in Strong's column shape at every tier, free. Whatever volume model you believe in this year, the raw record is there to re-run under the next one.