When you are sick or on a deload week, the expenditure arithmetic changes less than it feels like, the protein target does not change at all, and the calorie target has three honest settings for the week. That is the whole of what a calculator can say. Nothing here is guidance about eating while ill — what, how much, or whether — which is a question for a qualified professional. This page is the arithmetic only: what the formula sees, what it cannot see, and what each choice about the target costs in planned progress.

Expenditure changes less than you think

The calorie calculator builds TDEE from a formula BMR and an activity multiplier chosen from a short list: 1.2 for no training sessions, 1.375 for 1–3 a week, 1.55 for 4–6, 1.725 for 7 or more, adjusted by −0.05, 0 or +0.1 for daily-life activity. Notice what that list keys on: *sessions per week*, not how hard the sessions were.

Take a 90 kg, 180 cm, 35-year-old male profile with moderate daily activity: BMR 1,855 kcal.

WeekSessionsMultiplierFormula TDEEChange from the normal week
Normal training week4–6, heavy1.552,875 kcal
Deload week4–6, light1.552,875 kcal0 — the formula cannot see a deload
Ill, still moving about0, moderate daily activity1.22,226 kcal−649 kcal
Ill, mostly in bed0, sedentary1.152,133 kcal−742 kcal

The deload row is the point. A deload keeps the sessions and takes the edge off them — in the Zyra Workouts design that is fewer sets, a higher RIR target, or both, and in a generated program it is a marker on the first or last cycle (how to deload has the modes). To a multiplier that counts sessions, nothing has changed. And the real change is smaller than intuition says, because the energy a lifting session adds on top of resting expenditure is modest to begin with and the body offsets part of any change in activity — why exercise burns fewer calories than the tracker says covers that compensation. A lighter week is a difference of a couple of hundred calories a day at most for this profile, and the formula's own error bar is wider than that.

The illness rows are a real drop — 600–750 kcal a day on paper — but for a week. The formula describes a steady state; re-running it for seven unusual days trades one estimate for another that will be wrong again on Monday. What a trend-based estimate does with such a week is hold or absorb it; MacroDiet reads the rate of change over the past three weeks, so one week inside that window shifts it modestly and the effect washes out as the week leaves the window.

In plain terms: a deload is invisible to the calculator; a week in bed is visible but too short to act on.

Protein stays where it is

The calorie target may move; the protein target does not, because it is not computed from calories. The protein calculator sets grams from body weight and a tier — 1.2, 1.6, 2.0 or 2.4 g/kg — plus 0.2 g/kg on a loss goal. For the 90 kg example on the moderate tier during a cut:

  • protein = 90 × (1.6 + 0.2) = 162 g

That figure is the same on a heavy week, a deload week and a week at maintenance. The only way calories touch it is the cap at 50% of the calorie target, which at 2,875 or 2,380 kcal is nowhere near 648 kcal of protein. When the target rises to maintenance for the week, the extra calories arrive as carbohydrate and fat in the diet style's ratio; when the target stays, nothing changes. Either way the protein line on the macro calculator reads 162 g.

What to do with the target for a week

Three settings, all of them honest, each with a cost you can see in advance. On the 90 kg example the moderate-rate loss target is 2,380 kcal against a 2,875 kcal TDEE — a 495 kcal deficit, 0.45 kg a week planned.

OptionWhat the target doesWhat it costsWhen it fits
Keep the targetStays at 2,380 kcal; the plan continuesNothing on paper; the deficit is unchangedA deload in a diet that is going well, or an illness that does not change your activity much
A maintenance weekTarget becomes TDEE, 2,875 kcal, for seven days0.45 kg of planned loss deferred — a 12-week plan becomes 13The common deload convention; any week when the deficit is the thing you would rather not carry
Recompute at the new activity levelTarget re-derived from a lower multiplier — 1,731 kcal at the 1.2 multiplier on this profileRisks a target well below the truth once activity returnsOnly when the change will last a month or more, not for a week

The maintenance week is the same move as a one-week diet break: run the calculator with the maintain goal, or simply treat TDEE as the week's target without touching the goal, and go back to the loss target after. The weekly-budget arithmetic applies as usual, and the calorie floors and 35% cap are untouched because a maintenance target is above any floor by construction.

The third option is where people go wrong in both directions. Recomputing for a week in bed produces a target that is right for four days and wrong for the next forty; not recomputing after an injury lay-off leaves a target built for a body that trained five days a week. The dividing line is duration: a change that will still be true in a month is a new steady state and deserves a new number; a change that will be over by next week is noise.

Whichever you choose, the logging rule from how accurately you need to track still holds: complete days or blank days, never half days. A week of poorly logged illness does more to the estimate than the illness does.

The short version

A deload does not change the calculator's expenditure at all — the multiplier counts sessions, not effort — and a week in bed changes it on paper (2,875 to 2,133 kcal on the 90 kg example) but is too short to re-run a steady-state formula for. Protein is weight × g/kg and stays at 162 g here whatever the calories do. For the calorie target: keep it, take the week at maintenance (about one week of planned loss deferred), or recompute only if the change will last a month. Anything about eating while ill is a question for a professional, not this page.

Educational overview only — not medical advice. Zyra is a training and nutrition tracking tool; the rates, caps and floors on this page describe how the calculator behaves, not what any individual should do.