You don't learn anything from this week's set count on its own. You learn something when you put it next to your last program's.
This is the practice of comparing training volume from one program to the next: what to log, how to line two of them 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 program only produces one clean comparison if you record the same things, the same way, every week inside it:
At the end of the program, average each number across its weeks and set it next to the same average from the one before. A single week's numbers are close to noise. They move for reasons that have nothing to do with the training. A program's average is the first number worth trusting, which is the entire reason a program has an end instead of running as one long stretch with no checkpoints.
Fourteen sets of chest in your last program and fourteen in this one 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 program 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 programs 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. That usually means fatigue is outrunning what you're adapting to. It's the pattern behind pulling a deload forward instead of waiting for the calendar date, and comparing one program with the last is what surfaces it, days before it would otherwise show up as a bad session.
Volume held flat across two or three programs, 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 next program needs a different driver: a different rep range, a different lift order, a different emphasis. That is a planning decision, not a volume one.
Both patterns are invisible from inside a single program. 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. Lining one program up against the last 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 from what you log, keeps the effort target each set was written at, and keeps your top-set numbers, every week, tied to the program it happened in. That's the raw material the comparison above needs, and it's what a spreadsheet tab from six weeks ago rarely gives back cleanly.
When a program ends, its recap keeps the weekly sets each muscle group got, so the last program's numbers are already lined up when the next one starts. You are not rebuilding them from a spreadsheet tab six weeks old.
At the end of each program, 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 program's average against the one 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 in the next program 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 program is asking for instead: a different driver, a different rep range, a different lift order. Then 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.
Fire Your Coach builds the plan with the lifts and the conditioning in the same week, counts working sets per muscle group from what you log by one rule, and keeps each program's count when it ends.