SYNTH-29 · Guide

Ramp and deload

Watch the spike more than the level, and a deload is a response to signals rather than a place in the calendar

C+thin evidenceMostly from recreational to highly trained athletesWritten before October 2026, being re-checked

The decision this framework makes

Whether to add load next week, hold it, or cut it — and on what evidence. Not "which week of the block is it".

1. Two failure modes, and most coaching only guards one

REF-592 (C+, narrative review, team-sport cohorts) states the training–injury paradox plainly: athletes accustomed to high CHRONIC loads have fewer injuries than those training at lower loads, under-training itself raises risk, and excessive, rapid increases in load are likely responsible for a large share of non-contact soft-tissue injuries. The reflex to ramp timidly guards against the spike while walking straight into the other failure — in those team-sport cohorts under-training was itself associated with more injury, so under-loading is not automatically the cautious option (transfer to endurance athletes is inference).

(The same paper promotes the acute:chronic workload ratio as its predictor; that part has since been dismantled — see REF-365 below.)

REF-619 (B, Tier 1, 1-year exploratory prospective cohort, n=874 novice runners) is the largest cohort here, and it is weaker than it is usually quoted: the overall injury rate did not differ between runners progressing <10%, 10–30% and >30% per week; only for "distance-related" injuries did a >30% jump over two weeks show a trend toward more injury (HR 1.59, 95% CI 0.96–2.66, p = 0.07) versus <10%.

A reason for caution with big jumps, not proof that the jump causes injury. REF-623 (B+, prospective cohort, n=261 healthy recreational runners in a 14-week half-marathon build) is the sharper result: runners who raised weekly distance by 20–60% had 22.6 percentage points more injuries at 21 days than those who raised it by <20% (95% CI 0.9–44.3, p = 0.041), with no difference left at 8 and 14 weeks and no protection from having a prior running schedule.

The penalty for a big jump in this one cohort is early, and its size is imprecise. (That this is a load story rather than a static-biomechanics one is inference — neither cohort tested biomechanics.)

2. What the numbers actually are

The "10% rule" is weakly justified. REF-565 (B+, systematic review, 4 studies) looked for it and found "very limited evidence" that a sudden change in load is associated with injury at all, and no difference between a 10% and a 24% average weekly increase (HR 0.8, 95% CI 0.6–1.3). Build gradually; do not fetishize the number, and do not present it to an athlete as physiology.
The defensible red line is wider than 10%: the cohorts start to show cost at a 20–60% weekly jump ([REF-623], significant at 21 days) and a >30% jump over two weeks ([REF-619], a non-significant trend). Not from a study; the base's own practice: we round this to "keep consecutive-week jumps under 20%" — the lower edge of the category that showed cost in REF-623.The ACWR framework that popularised "spike" thresholds does not carry this: REF-365 (C, methodological commentary) concludes there is no evidence supporting ACWR for load management or injury-risk reduction — the ratio is inaccurate, ambiguous and creates statistical artefacts. Treat any ACWR number as a description of how load changed, never as a risk score.
Conservatism is situational, not constant. Most conservative where there is a previously injured site, and after any break — illness, holiday, injury — rebuild progressively over 2–3 weeks. Not from a study; the base's own practice: neither REF-619 nor REF-623 is a return-to-run study, and neither carries a rebuild duration or a prior-injury result.
Gate progression on symptoms, not only on a percentage. Not from a study; the base's own practice, in line with REF-565's conclusion that the evidence is "very limited" and supports no specific safe threshold.

So the honest prescription is a band rather than a rule: add load when the athlete is absorbing it, keep consecutive-week jumps under the 20% where the running cohort starts to show cost (for cycling load this is a house habit, not evidence), and go slower than that when history or a layoff says so.

3. A deload is not free

REF-217 (B, RCT, n=39 resistance-trained young adults, Tier 2) inserted a one-week complete break from lifting at the midpoint of a 9-week supervised resistance programme.

Hypertrophy, local endurance and power came out the same — but isometric and dynamic lower-body strength improved MORE in the group that did not deload, which also reported slightly better readiness to train.

In that lifting trial a scheduled full week off was a small strength cost paid for nothing; the tested deload was total cessation in resistance training, so whether a reduced-volume endurance recovery week costs anything is untested.

That does not make deloads wrong; it makes them a response. REF-139 (C in the base; an animal model — 7 racehorses over 272 days) is the other side: when daily endurance and interval training kept increasing in duration and intensity, the horses became stale — weight loss, irritability, inability to complete the training — while test performance did NOT fall, the adrenal response to ACTH, plasma and red-cell volume and blood chemistry were unchanged, and the only muscle change reported was a smaller ATP decline during maximal exercise; the authors conclude that overtraining is unlikely as long as exhaustive training is alternated with light exercise, and that no single parameter detects early overtraining.

The markers worth watching, by that model, are behavioural and practical: body mass, mood, and whether the session can be completed as written — not a lab number.

4. The signals that should trigger one

RPE creeping up at the same power or pace. Not from a study; the base's own practice — the human analogue of the "inability to complete the training" that REF-139 observed, and the cheapest marker to collect.
A readiness trend, not a bad morning. One poor day is context; a 3-day direction is a signal. Not from a study; the base's own practice — the underlying methodological point (read HRV as an averaged trend, never a single value) is from REF-361; the 7-day rolling figure is from its full text.An HRV trend that has not recovered (not a single morning) means the next hard session's intensity comes down, not that the block is over (house practice; REF-161 measured acute post-exercise HRV in runners, not morning readiness rules).
Sessions that stop being completable as written. Not from a human study; the base's own practice, modelled on the horses of REF-139.
Confirming functional overreaching: REF-208 (B+, 31 experienced male triathletes, 21 overloaded) reports the counterintuitive one — the 10 who developed functional overreaching (−2.1% performance with high perceived fatigue) showed FASTER heart-rate recovery (+8 ± 5 bpm), together with lower peak lactate and catecholamines.Inference, not tested as a rule: REF-208 defines f-OR as a performance drop with high perceived fatigue and says HRR must be read in that context — so faster HRR than baseline together with elevated RPE at the same power (the base's field proxy) supports "this is FOR, deload now" rather than "the athlete is fresh".Do not plan for it as a target: in a taper trial from the same research group, the 11 overloaded triathletes who became functionally overreached gained less over a 4-week taper than the 12 who were only acutely fatigued (REF-1056, B, 33 trained men, split made after the overload), and a narrative review finds the case that overreaching is necessary for supercompensation unsettled (REF-1055, C+).

Practical Application

Add load while the athlete absorbs it and keep week-to-week jumps under 20% (house practice rounded from running-injury cohorts; for cycling load it is a habit, not evidence) — the 10% rule is convention; rebuild over 2-3 weeks after a break (house practice); deload on signals (RPE up at the same power, a 3-day readiness slide — house practice), not on schedule.
Judge the ramp from the athlete's own weekly totals and readiness trend. Blocks deliberately has no CTL/ATL/TSB strip, so use weekly TSS/duration progression plus the readiness instrument — and say which you are reading.
Do not quote "10% per week" as a rule (REF-565). If a number helps the athlete, frame it as a habit that keeps you far from the 20–60% jumps that cost runners in REF-623, not as a finding.
Keep building when the athlete is absorbing it. High chronic load was associated with fewer injuries in team-sport cohorts (REF-592, C+ narrative review; transfer to endurance athletes is inference).
Rebuild over 2–3 weeks after any break, and be most conservative around a previously injured site. Not from a study; the base's own practice.
Trigger the deload on signals — RPE at standard load, a 3-day readiness direction, sessions failing — not on the week number (house practice; neither REF-139, an animal model, nor REF-217, a lifting trial of a scheduled week off, tested signal-triggered deloads).
When you do deload, say what it is for and what would end it, so it reads as part of the plan rather than as a demotion.

What NOT to do

Do not present the 10% rule as evidence. It is a convention (REF-565).
Do not schedule a full week OFF for an athlete who is absorbing the load — it cost strength and bought nothing measurable in the one lifting trial we hold (REF-217). A reduced-volume recovery week (3:1) was not tested there; whether to schedule one is house practice (see SYNTH-24).
Do not treat a single bad morning as a reason to cut the week (house practice; see SYNTH-30).
Do not read faster heart-rate recovery as freshness without checking RPE at the same power — in an overreached athlete it can mean the opposite (REF-208).
Do not "fix" a load-driven injury pattern with cadence or shoes while the ramp stays steep (inference; REF-619 and REF-623 are about load progression, they did not test biomechanics).
Do not steer training by an ACWR "sweet spot" (REF-365).

Limitations

The ramp evidence is in RUNNERS (REF-619, REF-623) where load is bone-and-tendon mediated, and it is observational: one cohort is a non-significant trend, the other a significant but wide-CI early effect.Not from a study; the base's own reading: cycling is mechanically more forgiving, so the injury framing transfers weakly to a rider — for cyclists the ramp constraint is fatigue and absorption rather than tissue damage. Do not quote a running injury cohort at a cyclist as though it were about them.
[REF-217] is a resistance-training RCT, Tier 2, its deload was complete cessation, and its outcome was strength — not endurance performance. Whether an endurance deload (usually reduced volume, not a week off) carries the same small cost is untested here.
[REF-139] is a HORSE study (n=7). It is mechanistically instructive about escalating overload (its authors conclude that alternating exhaustive with light training keeps overtraining unlikely) and its behavioural markers are sensible, but it is an animal model and should never be cited to an athlete as human evidence. Note that its test performance did not fall during staleness — the "performance drops first" idea is not what this study showed.
ACWR has no supporting evidence (REF-365); no percentage rule follows from it, and the band above is our rounding of two running cohorts.
Nothing here establishes an optimal deload FREQUENCY or magnitude for endurance athletes. The trigger logic above is reasoning built on monitoring evidence, not a finding.
How this entry was checked and changed
Why this level

every decision row is house practice or transfer (running-injury cohorts, a lifting trial, a team-sport review, an animal model); regraded 2026-09-27 from B+: the ramp cohort (REF-619) is now B with a non-significant primary result, the ACWR entry (REF-365) is a C-level commentary, the deload trial (REF-217) is B, the training–injury paradox review (REF-592) is a C+ narrative review and the overload model (REF-139) is animal data

Content correction 2026-09-27
"REF-619 (A) — rate of load change is the primary modifiable injury lever, not static biomechanics" -> REF-619 is B: overall injury rate did not differ across progression groups; only a non-significant trend (HR 1.59, p = 0.07) for >30% two-week jumps in novices; biomechanics not tested.
"Avoid 30–40%+ jumps (REF-365)" -> REF-365 (now C) concludes there is no evidence for ACWR and carries no percentage; the red line is re-sourced to REF-623 (20–60% jump, +22.6% injured at 21 days) and REF-619 (>30%, trend).
"Rebuild over 2–3 weeks (REF-619, REF-365)" and "gate on symptoms (REF-619)" -> not in either paper; relabelled house practice.
REF-139: "run time fell while VO2max held; markers = RPE, mood, body mass" -> abstract: test performance did NOT decrease; markers were weight loss, irritability, inability to complete training; no single parameter detects early overtraining. RPE relabelled as the human analogue.
"Morning HRV not recovered → drop intensity (REF-161)" -> REF-161 is acute post-exercise HRV in runners; relabelled house practice with the 7-day-rolling point from REF-361/REF-132.
REF-217: Tier 1-2 -> Tier 2, n=39, deload was complete cessation; REF-208: 31 triathletes, 10 f-OR, +8 ± 5 bpm. Level B+ -> B (regraded).
Sync after the full-base pass: REF-592 is now C+ (narrative review), not B — parenthetical and Level-line reasons updated; "REF-565 concludes individual tolerance varies" -> REF-565 concludes the evidence is very limited and gives no precise threshold (tolerance-varies is not in it).
Cross-references to duplicate stubs repointed to their canonical entries (REF-132->REF-361); the stubs were emptied on 2026-09-27.
Level parentheticals synced to the cited entries' current Level lines: REF-139 B+ -> C.
Resync 2026-09-28: REF-139 "training kept increasing ... with no light days" and "no blood, muscle or adrenal marker moved" -> the entry describes daily endurance/interval bouts increasing in duration and intensity (light days not described); ACTH response, plasma/red-cell volume and blood chemistry unchanged, but muscle ATP decline during maximal exercise was smaller during staleness. Cross-reference and Limitations wording "overload without light days" aligned.
Resync 2026-09-28: REF-208 "faster HRR + elevated RPE at the same power supports 'this is FOR'" stated as a finding -> REF-208 defines f-OR as performance drop + high perceived fatigue and labels the combined reading as inference; relabelled, RPE-at-same-power marked as the base's field proxy.
Resync 2026-09-28: REF-361 "rolling 7-day average" -> the abstract recommends averaging; the 7-day figure is full text (not checked against the abstract); noted.
Resync 2026-09-28: REF-623 "it is not a static-biomechanics story" -> neither REF-623 nor REF-619 tested biomechanics; labelled inference.
Verification 2026-10-01: every number and level parenthetical for REF-592, REF-619, REF-623, REF-565, REF-365, REF-217, REF-139, REF-361, REF-161, REF-208 matches the entries' head blocks and Key Findings (HR 1.59, CI 0.96-2.66, p=.07; 22.6 points, CI 0.9-44.3, p=0.041; HR 0.8, 0.6-1.3; n=874/261/39/31; +8 ± 5 bpm; -2.1%). No NUMBER or LEVEL finding at the citation level.
Verification 2026-10-01: the problems are at the prescription level — the lead, Practical Application and What-NOT bullets drop the qualifiers (runners, lifting, cessation, team sport, horses) that the body and Limitations state correctly.
Verification 2026-10-01: the 2-3 week rebuild, symptom gate, RPE creep and 3-day readiness rules are honestly labelled practice wherever they are argued; the summary Practical bullet labels only one of them.
Verification 2026-10-01: 'Blocks deliberately has no CTL/ATL/TSB strip' is a product statement, not science — owner to confirm it is still true.
Revision 2026-10-03: added REF-1056 (Aubry 2014, B) and REF-1055 (Bellinger 2020, C+) after the 'Confirming functional overreaching' signal: FOR is a deload trigger, not a goal. No rule, default or level changed.