The two-rep drop in week four is the block working as written

Week four, set three, and the bar stops at six

Week four of a hypertrophy block. Thursday's top set on the squat is the same 275 you moved for eight clean reps last week, and today the bar stalls on rep six. It felt like a 9.5. You rack it, sit on the bench, and the question shows up right on schedule: am I overtraining?

Most lifters answer it with whatever's in front of them. Today's session. Last night's sleep. A watch telling them recovery is low.

So they do one of two things. They bail on the program with a week left, convinced something's broken. Or they grind through with no idea whether the drop means anything, because the app they log in only really shows them today.

Both moves read one data point and call it a trend.

The three-line read

Fatigue accumulation only becomes legible when you read three variables together across a full mesocycle: the load on the bar, the reps you completed, and the RPE you logged. Call it the three-line read.

Any one of those lines will mislead you on its own. Load climbing looks like progress. Reps dropping looks like decline. RPE creeping up looks like you're cooked.

Put them on the same timeline and they tell one story. Load held or nudged up. Reps sliding by one or two in the back half. RPE climbing a little every week. That's the signature of an accumulation block doing what it was written to do, stacking fatigue faster than it clears so the lighter week that follows has something to dissipate.

Read against that shape, a two-rep drop on week four isn't a verdict on your recovery. It's the expected reading.

Why "am I overtraining?" is the wrong question for week four

The overtraining frame gets reached for because it's the scariest explanation available, and because the tools most lifters wear are built to answer questions at the session level. HRV, resting heart rate, sleep staging: they describe how your body looks this morning. They're useful for exactly that. But none of them know you added five pounds to the top set last week, or that your RPE on the same load has climbed three weeks running.

A recovery score can't hold a load trend. It has no idea what's on the bar.

And overtraining syndrome, as the research literature defines it, is a slow condition measured in months. A drop that appears in week four of a planned block, and wasn't there in week two, is a poor fit for that description. Treating it like one pushes lifters out of the exact phase where the program was setting up its payoff.

What the research actually separates

The clearest map is the joint consensus statement from the European College of Sport Science and the American College of Sports Medicine (Meeusen and colleagues, 2013). It treats fatigue as a continuum and sorts performance decrements by how long they take to resolve.

Functional overreaching sits at the mild end: a short-term performance drop that recovers within days to weeks and can be followed by improved performance. A well-built accumulation block visits that zone on purpose. Non-functional overreaching takes weeks to months to recover from, with no payoff. Overtraining syndrome runs for months.

Look at what those definitions lean on. Recovery time, and what performance does after rest. You can't classify any of them from one session, because the answer lives in the weeks around it.

RPE is what makes this readable for lifters. The reps-in-reserve based RPE scale that Zourdos and colleagues introduced for resistance training (2016) turned effort into a per-set number you can log next to load and reps. Once all three sit in the same record, the continuum stops being abstract.

What the pattern looks like across five logged weeks

Take a lifter on a four-week accumulation block with a lighter fifth week, squatting three sets of eight on Thursdays. The numbers below are a worked illustration, not study data. The shape is the thing to recognize.

Weeks one through three look like a program going well. Load goes up five pounds a week, all eight reps land, and RPE rises half a point to a point each time. Nobody panics in week three, but the RPE line is already telling you where week four is headed.

Then week four. Same load as week three, six reps, RPE 9.5. Viewed alone, it's the worst session of the block. Viewed as the fourth point on three lines, it's the continuation of a slope that started in week one.

The lighter week drops load and RPE together. And the week that tells you the most is the one after: the opener of the next block, where the load that stalled at six gets its eight back at a lower RPE than week four. That rebound is the functional-overreaching signature the consensus describes, and you only see it if week four and week six live in the same log.

Grade the block when the block is over

If the three-line read holds, the decision point moves. Week four stops being a referendum on whether the program works, and the useful question becomes whether this block's shape matches the one you expected when you started it.

That makes a few things easier. A single bad Thursday surrounded by normal sessions is noise. Sleep, a stressful workday, a missed meal. The next session answers it. A two-rep slide in the back half of a block, with load held and RPE climbing on a slope that began weeks earlier, is accumulation, and the lighter week is where it gets resolved.

The shape that deserves attention looks different. Reps keep falling even when load comes down. RPE reads high on weights that used to be easy. And the lighter week doesn't bring anything back. That's the point where the longer timescales in the consensus start to apply, and where pushing harder is the wrong instinct.

What a log has to show for this to work

The three-line read has one hard requirement. Every set, with its load, reps and RPE, on one timeline that reaches back at least a full block. Better still, years of blocks, so you know what your week four usually looks like before this one arrives.

Platepusher is built around that timeline. It records load, reps and RPE set by set No. Per-set RPE logging is not live in the current Platepusher build. The RPE and percent-of-training-max controls were deliberately removed from the app's interface, and a lifter can't enter or edit RPE during a workout or in the plan editor. Any RPE values already stored in older plans are kept and carried through sync, but they are not shown or editable, and the feature is parked for a possible future release., and its plateau flag reads the top-set trend across weeks, not the verdict of one session. The watch is where you log the set. The log is where you read the block.

If your history lives in another app, bring it with you. A Strong or Hevy CSV imports as native data, so the comparison starts with every block you've already run instead of week one. It's the same argument we've made about training history before: you've already run the experiment. The data just needs to sit where you can read it.

Next time week four hands you six reps, check the other two lines first. They'll usually tell you it's on schedule.