A deload is a planned cycle of lighter training, and in the Zyra Workouts design it comes in three modes: volume-down (about 40% fewer sets, same load), intensity-down (same sets, +2 RIR) and both (25% fewer sets and +1 RIR). The position is a single choice per program — none, first cycle or last cycle. This page covers when a deload makes sense, what each mode does to a real exercise, which of them the current build writes for you, and how first- and last-cycle deloads differ.
Zyra Workouts is in development and not yet on the App Store; the screens described here may change before release.
When a deload makes sense
Two signals exist in the app, and neither is a calendar.
The first is planned: a generated program with the deload option switched on ends its six-cycle block with a lighter sixth cycle. That is a structural choice made when the program is built — a block that ramps effort for five cycles and then eases.
The second is observed: the dashboard's exercise trajectory. For each exercise it compares the estimated 1RM (e1RM, the one-rep max estimated from a set's weight and reps) of the most recent session against the first session in the last 30 days. If the change is ≤ −2% and the average logged RIR over those sessions is ≤ 1, the label reads Deload needed. The RIR condition is what separates "getting weaker while training hard" from "getting weaker while coasting" — the second is not a deload signal. A drop with higher RIR shows the percentage and nothing else; three or more flat sessions read "Plateau".
Outside those two signals the app does not tell you to deload. The judgement is a training call, and the honest framing is that a deload is a tool you choose to use, not a requirement the app enforces.
The three modes (table)
Take a back squat programmed at 4 sets of 6–10 reps at RIR 2, and a barbell bench press at 3 sets of 6–10 at RIR 2:
| Mode | Rule | Squat, 4 × 6–10 @ RIR 2 | Bench, 3 × 6–10 @ RIR 2 |
|---|---|---|---|
| Volume-down | −40% sets, same load | fewer sets at the same weight (4 → about 2–3; the rounding is not published) | 3 → about 2 |
| Intensity-down | same sets, +2 RIR | 4 × 6–10 @ RIR 4 | 3 × 6–10 @ RIR 4 |
| Both | −25% sets and +1 RIR | 3 × 6–10 @ RIR 3 | about 2 × 6–10 @ RIR 3 |
| Generated last-cycle deload | one fewer set, base + 2 RIR | 3 × 6–10 @ RIR 4 | 2 × 6–10 @ RIR 4 |
Honest status first. The three named modes are the design's; the source does not state how a fractional set count is rounded, so the table says "about" where 40% of 4 does not come out whole. What the current build implements is the last row: the program generator writes sets − 1 (never below one) at RIR base + 2 into the sixth cycle's override when the deload option is on. Any other shape is entered on the cycle cards by hand — which, because the position is a marker and the targets are editable, is a few taps rather than a workaround.
What each mode is for, in plain training terms:
- Volume-down keeps the weights on the bar. The sets that remain look and feel like the block's sets; there are simply fewer of them. It suits a lifter who wants to keep practising heavy loads while doing less total work.
- Intensity-down keeps the session length and the set count but stops each set further from failure. At the same weight that is fewer reps; at the same reps it is a lighter weight. It suits a lifter whose sets have drifted toward failure (the trajectory's RIR ≤ 1 case).
- Both splits the difference — a quarter fewer sets, each one RIR easier.
In plain terms: cut sets, cut effort, or cut a little of each. The load on the bar is not the lever the design reaches for first.
First-cycle versus last-cycle deloads
The position setting has three values and one rule each:
| Position | Which cycle is the deload | Typical use |
|---|---|---|
none | no cycle | continuous training; deload by hand when you decide |
first | cycle 1 of each block | ease into a new block, especially after a break or a change of program |
last | the final cycle of each block | close a block before repeating it or moving on |
A last-cycle deload is the natural end of an RIR ramp: effort climbs for five cycles and the sixth is lighter, and when the block repeats it starts again at the top of the ramp (base + 1 RIR). A first-cycle deload puts the light cycle at the start, which pairs well with a return from time off — the first cycle back is lighter by design, and the ramp follows. The missed-week page goes into the return case.
The position is a marker on the program, and the targets for that cycle are what make it a deload. There is no hidden calculation applied on top of your targets — what the cycle card shows is what the session asks for. If you change the cycle card, you change the deload.
What a deload does not touch
Records, history and weekly-set counts continue as normal — a deload cycle sets no records and removes none. The progression engine keeps reading your last working sets, so the first hard cycle after a deload starts from what you actually lifted in the deload, and the ramp's higher starting RIR is what stops that from reading as a step backwards. If you would rather the engine ignore the deload, the recommendation is one tap to override.
The short version
Three modes in the design — 40% fewer sets, +2 RIR, or 25% fewer sets and +1 RIR — placed on no cycle, the first or the last. The one the current build writes for you is one fewer set at base + 2 RIR in cycle six. The app suggests a deload only when an exercise's e1RM falls 2% or more over 30 days at average RIR 1 or below; otherwise the call is yours. Plan the block first in the program guide.
Educational overview only — training guidance, not medical advice.