You don't learn anything from this week's set count on its own. You learn something when you put it next to last block's.
This is the practice of comparing training volume block to block: what to log, how to line two blocks up so the comparison is honest, and the two patterns that actually mean something changed. If you want the framework behind how much volume to run in the first place, that's volume landmarks — this page is only about the comparison.
A block only produces one clean comparison if you record the same things, the same way, every week inside it:
At the end of the block, average each number across its weeks and set it next to the same average from the block before. A single week's numbers are close to noise — they move for reasons that have nothing to do with the training. A block's average is the first number worth trusting, which is the entire reason blocks exist instead of one long stretch of training with no checkpoints.
Fourteen sets of chest last block and fourteen this block looks like a flat line. It is only a flat line if the effort behind each set also held steady. Push those same fourteen sets a rep or two closer to failure and you have quietly run a harder block while your spreadsheet reports no change at all.
How close to failure a set is taken is its own studied variable, not a rounding error — a 2023 systematic review from Refalo and colleagues and a 2024 series of meta-regressions from Robinson and colleagues both treat proximity-to-failure as a variable that changes the outcome, separate from the raw set count. Neither paper hands you a rule for how much it matters. What they establish is that it does, which is reason enough to log it every week rather than assume it stayed put.
Without that number, a rising set count and a rising habit of skipping the last rep look identical on paper.
Once two or three blocks are lined up, only two shapes in the data actually call for a decision.
Volume went up, performance didn't follow. More sets, same or worse top-set numbers, at a matched effort. Fatigue is outrunning what you're adapting to. That's the pattern behind pulling a deload forward instead of waiting for the calendar date — the block-over-block comparison is what surfaces it, days before it would otherwise show up as a bad session.
Volume held flat across two or three blocks, and so did performance. That's not a volume problem, and the instinct to just add sets to a flat trend usually adds fatigue to a flat trend instead of a result. The block is asking for a different driver — a different rep range, a different lift order, a different emphasis — which is a planning decision, not a volume one.
Both patterns are invisible from inside a single block. They only exist in the comparison.
The comparison only pays off if you act on it, not just file it. A plan written in week one is a guess about what week five will look like. The block-over-block comparison is how you find out whether the guess was any good, in time to still do something about it.
That's the entire argument for keeping the record. Reading it back is part of what makes a plan worth following.
Fire Your Coach counts sets per muscle group, logs the effort behind each one, and keeps your top-set numbers — every week, tied to the block it happened in. That's the raw material the comparison above needs, and it's exactly what a spreadsheet tab from six weeks ago rarely gives back cleanly.
When the next block starts, last block's numbers are still there. You are not reconstructing a spreadsheet tab from six weeks ago. The reasoning carries forward into the block after this one, too.
At the end of each block, not week to week. A single week moves for reasons that have nothing to do with training - a missed session, a rough night of sleep, an exercise swap. Line up the full block's average against the block before it and the noise mostly cancels out.
Three numbers, the same three every week: working sets per muscle group, the effort each set was taken to (RIR or RPE), and the load and reps on your top set. Miss the effort number and a higher set count next block might just mean you stopped leaving reps in the tank, not that you did more work.
Volume and performance have decoupled, which usually means fatigue is outrunning what you are adapting to. Check your effort log first, since a hidden drift toward training closer to failure can make set counts look identical while true stimulus rose. If effort held steady and performance still stalled, that is a signal to bring the deload forward rather than wait for the calendar date.
That is a stagnation pattern, not a volume problem, and adding more sets on top of a flat trend usually just adds fatigue to a flat trend. Change what the block is asking for instead - a different driver, a different rep range, a different lift order - and record the new baseline before you judge it.
Not directly. Sets per week describes resistance training; conditioning load is better tracked by session count, pace and heart-rate zone, which is a different comparison. If you are running both, track each on its own terms rather than forcing one number to describe both.