Deload weeks: markers, not the calendar
Every fourth week is a scheduling convention, not a training decision. The signals that actually mean you need a deload, and why one on its own is never enough.
Written while building GETSIXPACK — a training log that scores the session against your range and calls the next load.
“Deload every fourth week” is a scheduling convention. It survives because it is easy to write on a spreadsheet, not because week four is when fatigue arrives.
Fatigue arrives when it arrives. Sometimes that is week three of a hard block after a bad fortnight of sleep. Sometimes you are eight weeks in, eating well, and nothing is stalling. Taking a week off in the second case costs you a week of training for nothing, and the strength you had at the top of the block is not sitting there waiting when you come back.
What a deload is for
Dropping accumulated fatigue far enough that the work starts producing again. That is the whole job.
Which means the trigger has to be evidence of accumulated fatigue. Not the date. Not a feeling on a Monday. Something in the log that says the work stopped producing.
The markers worth reading
Four, roughly in order of how much they tell you.
Stalled or regressing lifts. The most direct signal there is. A lift that has not moved in three outings is one thing; three or four lifts that have all stopped moving in the same fortnight is systemic, and that is what a deload addresses. One stalled movement is a programming problem for that movement — usually a rep range that needs revisiting, or a movement you have simply outgrown.
Effort creeping up at the same load. You are hitting the same reps at the same weight and it is costing you a full RIR more than it did a fortnight ago. This is the cleanest early marker, and it only exists if you have been logging effort per set. A session-level “felt hard” does not survive contact with your own memory two weeks later.
Volume sitting at the ceiling. If a muscle has been at or over its MRV for a couple of weeks, the accumulated fatigue is not a surprise, it is arithmetic. This one is predictive rather than diagnostic — it tells you what is about to happen.
The joints. Elbow, shoulder, low back and knee complaints that were not there four weeks ago. This is a real signal and it is the one that most often gets ignored until it stops being a deload question and becomes a rehab question.
One marker is never enough
Every one of those has an innocent explanation. A lift stalls because the range was wrong. RIR drifts because you slept badly for three nights. A joint complains because of how you set up on Tuesday. Deloading off a single reading means deloading constantly, which is just training badly at a lower intensity.
So: two independent markers have to stack before it is a deload. Two things pointing the same way is signal. One is noise with a story attached.
Where the calendar does belong
Not as a trigger. As a prompt.
If it has been six weeks, that is worth knowing, and it is reasonable for something to say so. What it must not do is decide. “It has been six weeks and two lifts have stalled” is a deload. “It has been six weeks” is a question.
The distinction is the difference between a coach reading your training and a calendar reminder wearing a lab coat.
What a deload actually looks like
Less than people think, and shorter.
Keep the movements. Keep the frequency. Cut the working sets by roughly half and take the load back about 10%, or keep the load and halve the sets — either works, and the second is easier to execute because you are not fumbling with plate math on a week you are supposed to be recovering.
What you are not doing is stopping. A week of nothing detrains more than a week of half-volume and comes back worse.
One week is usually enough. If a week at half-volume has not moved anything, the problem was not fatigue and another week off will not find it.
The short version
Read the log, not the date. Require two markers before you act. Let the calendar ask, never decide. And keep training through it.