Blog Recovery

When does Anneal deload? An autoregulation app, explained

10 min read

Quick answer

Anneal suggests a deload when the training you have already logged shows you need one. It watches seven signals continuously: grinding sets close to failure, effort creeping up across sessions, missed target reps on weights you have handled before, a sharp spike in recent workload, a run of low readiness, and, if you prefer a schedule, a planned recovery week or a simple cadence. When the pattern crosses a threshold it surfaces a suggestion and names the signal that fired. Reading those signals for you is what makes it an autoregulation app, and it is a core feature, free for everyone.

You can feel a deload coming before you can name it. The warm-up that used to feel easy takes more out of you. A weight that moved for a clean set of eight last week grinds to a stop at six. You are still showing up, still working hard, and the numbers have quietly stopped moving. The question is when to actually back off, and most training apps leave you to answer it alone.

Anneal is built to answer it for you. It logs your training like any tracker, then reads that log the way a good coach would and works out when to deload so you do not have to. This post is about the part under the hood: what Anneal watches, when a deload suggestion fires, when it deliberately stays quiet, and why the whole thing runs free. If you would rather make the call yourself, how to know when to deload walks through reading the same signals by hand.

What an autoregulation app actually does

Autoregulation is a plain idea with an awkward name. It means adjusting your training to how your body is actually responding, rather than holding to a plan you wrote weeks ago no matter what the sessions tell you. A coach autoregulates every time they watch a slow rep and say take ten percent off today. You autoregulate when you add a rep because the set felt easy, or rack a set with one clean rep still in the tank.

An autoregulation app does the same job from your training log. It watches the data you are already creating, set by set, and adjusts its recommendations as your numbers move. Anneal autoregulates two things. The first is the weight it pre-fills for your next set: it nudges the load up when you hit the top of a rep range and eases off when you stall. The second, the focus of this post, is when it suggests a deload. If the term is new, what a deload week is covers the why and how to run one; here the subject is the timing.

When Anneal suggests a deload

Under the hood, Anneal watches eight signals. Seven of them run in a single deload evaluator that weighs them together every time you finish a session; the eighth is a separate check for one lift that has stopped moving. None of them fire on a single rough day. Each is built to track fatigue that has accumulated, so one bad session reads as noise and a repeated pattern reads as a pattern.

Effort climbing while the weight stays put

The earliest honest signal is your effort rising on a weight you have not changed. If you log RIR, short for reps in reserve, the number of clean reps you had left when you ended a set, this shows up plainly. Sets that sat at RIR 2-3 a couple of weeks ago now finish at RIR 0-1 on the same load. That is fatigue suppressing your output rather than a sudden loss of strength.

Anneal reads this two ways. Within a single session, if most of your hard sets are grinding to the edge of failure, that is an acute flag. Across several sessions, if your average reps in reserve drifts down and stays down, that is the chronic version, and it is the more trustworthy of the two. RIR logging is optional and stays off until you turn it on, so these two signals sharpen once you start recording effort. They also sit close to failure on purpose: self-reported RIR is most accurate within a rep or two of failure and gets noisier the further out you guess (Zourdos and colleagues, 2016), so Anneal reads the signal where it is sharpest.

Missing reps you used to hit

The next signal is missing your prescribed reps. If your program calls for eight to ten and you are landing on six on a weight that gave you eight last month, that is underperformance worth noticing. Anneal scores the share of your working sets that fell below the rep-range floor and flags the session when too many did.

The trap this avoids is the productive grind. Trading a couple of reps to put more weight on the bar is progression. Going from 100 for 10 to 110 for 7 looks like missed reps on paper, but the estimated one-rep max (the single number that folds weight and reps together, which Anneal computes with the Epley formula) went up, so the lift moved forward. Anneal checks that before it counts a set as a miss. It also holds its fire on a day you are clearly well recovered, where a short set reads as leverage or skill on a heavy attempt rather than a hole you are digging.

A sharp jump in recent workload

Two of the signals look at workload rather than a single set. The first compares your recent training load against your longer-run baseline, roughly the last week against the last month, for each muscle group. When the recent week spikes well above what you have been used to, the jump itself is worth a second look. Sports scientists call this the acute to chronic workload ratio, a heuristic adapted from team-sport research, and it is fair to be upfront that the metric is contested: the exact cut-points are softer than early work suggested, and it needs a few weeks of history before it carries any signal (Impellizzeri and colleagues, 2020).

So Anneal treats a workload spike as one flag among several, never a verdict on its own, and only when your strength is not still climbing. A muscle group that is running hot but still adding to its estimated one-rep max is in functional overreach, the productive kind, so the signal stays quiet. A spike with no progress to show for it is the case that earns a suggestion. When only small muscles are running hot, a little extra curl or calf work, Anneal can pull back just that work and leave the whole-body recovery week alone, once it has enough of your logged history to target a single muscle group.

A stretch of low readiness

The second workload-level signal is readiness. Anneal keeps a running read on how recovered you have been, built from the inputs you log over time. When that read sits low across a stretch of sessions, not for one off day, it counts toward a deload. This is the softest of the signals, and Anneal treats it that way: a prompt to ease off when the wider picture says you are run down, most useful when it stacks with one of the harder signals above.

The calendar, if you want one

Not every deload has to be reactive. If you train in planned blocks, Anneal fires a deload when your block reaches its scheduled recovery week, the way periodization has worked for decades. And as a safety net, if none of the signals above have flagged anything, Anneal will still suggest a deload once your training streak reaches a set cadence, so a recovery week never gets skipped forever. That cadence defaults to a value most lifters land near anyway, around every four to six weeks, and you can set it anywhere from three to twelve. How that baseline shifts with training age is covered in how often you should deload. The schedule fires last, on purpose, so an active fatigue signal always gets to speak first.

One lift that has stalled

The eighth check runs on its own, outside the evaluator. It watches each lift for a plateau: the same best weight and reps, give or take a rep, across a few sessions running. A single stuck session is noise, two could be circumstance, three is a pattern worth surfacing. It is a nudge to look closer at one movement, not a ruling that you are overtrained.

When Anneal stays quiet

Knowing when to hold back is half the value. Anneal stays silent on purpose in several cases:

Each of these exists so a suggestion arrives when it is informative and stays away when it would just be one more notification.

It tells you which signal fired

When a suggestion does fire, it comes with a reason. Anneal names the signal that triggered it, so the prompt reads as an explanation: your sets graded close to failure today, or your workload on this muscle group has spiked. You decide what to do with it. Accept it and Anneal drops your working weights and trims your volume for that week, then steps you back up when it ends. How deep the cut goes depends on the signal that fired; a standard recovery week takes about half your volume off and keeps the top weight a little lighter, enough to shed fatigue while holding on to the strength you built.

Deload detection is free

Reading these signals is the core of what Anneal is, so it is not a paid feature. The deload evaluator, the pre-fill that backs off when you stall, the suggestion, and the recovery week that follows all run for everyone, free, from your first eligible session. There is no tier you have to reach to be told when to back off. An autoregulation app that hid its autoregulation behind a paywall would be missing the point of the category.

Wrap-up

A deload is easy to believe in and hard to time. The signals that say back off are all sitting in your training log: effort climbing on the same weights, missed reps you used to hit, a workload spike with no progress behind it, a stretch of low readiness, or simply enough weeks on the clock. Anneal reads them every session so you do not have to hold them all in your head, tells you which one fired, and runs the recovery week for you when you accept.

Three things to take away:

  1. Anneal suggests a deload from your real session data, weighing seven signals together rather than any single bad day.
  2. It reads effort, missed reps, workload spikes, readiness, and your schedule, and it stays quiet for new accounts, active deloads, and returns from time off.
  3. Every suggestion names the signal that fired, and the whole feature is free.

Common questions

When does Anneal suggest a deload?

Anneal suggests a deload when your logged training shows accumulated fatigue. It weighs seven signals each session: grinding sets near failure, effort creeping up across sessions, missed target reps on weights you have handled before, a sharp spike in recent workload with no strength progress behind it, a stretch of low readiness, a planned recovery week, or a simple cadence you set. When the pattern crosses a threshold it surfaces a suggestion and names the signal that fired.

What is an autoregulation app?

Autoregulation means adjusting your training to how your body is actually responding rather than following a fixed plan written weeks ago. An autoregulation app does that from your training log: it reads your sets, reps, weights, and effort as you record them, and adapts its recommendations. Anneal autoregulates the weight it pre-fills for your next set and when it suggests a deload.

Is deload detection a paid feature in Anneal?

No. Deload detection is a core part of Anneal and runs free for everyone from your first eligible session. The deload evaluator, the suggestion, and the recovery week that follows are not behind a paywall.

Do you have to log RIR for Anneal to suggest a deload?

No. RIR, short for reps in reserve, sharpens the two grinding signals, but Anneal also reads missed reps, workload spikes, readiness, and your schedule, none of which need RIR. Logging RIR is optional and off until you turn it on; turning it on gives the effort-based signals more to work with.

Does Anneal deload on a schedule or by feel?

Both, with feel first. Anneal reads your training signals every session and suggests a deload when they call for one. If none have fired, a schedule you set (defaulting to around every four to six weeks, adjustable from three to twelve) acts as a safety net so a recovery week never gets skipped forever. The schedule fires last, so an active fatigue signal always speaks first.