Counting calories
Should You Eat Back Your Exercise Calories?
Should you eat back exercise calories? See the 27-93% average device error and the double-count that makes the burn number unreliable.
Guides

You know a calorie deficit is working when your weight trend, averaged over at least three weeks of morning weigh-ins, moves down. No single weigh-in tells you this, and neither does hunger. You cannot feel a deficit from inside your body, so the trend line is the only test, whether or not you log a single meal.
Hunger feels like it should tell you something. It does not, because researchers have measured people eating less without noticing.
In a controlled trial, cutting a two-day menu's energy density by 25% reduced what people ate by about 24%. Hunger and fullness ratings did not change significantly (Rolls, Roe & Meengs, 2006). A 25% cut in portion size alone reduced intake by about 10%, again with hunger unchanged. A real, measured reduction in calories can happen while the body reports business as usual.
The reverse problem is worse. In one study, obese subjects believed they were eating about 1,028 kcal a day and were not losing weight. Doubly labeled water, a method that measures actual energy use over time, put their real intake at 2,081 kcal a day, roughly double what they reported (Lichtman et al., 1992). They were certain a deficit existed. It did not. Confidence is not evidence, in either direction. The only way to check is external: the scale, read correctly.
Because body weight is not just fat. Water, glycogen, salt, and gut contents shift the number daily, often by more than a week of real fat loss.
A large fluctuation study found body weight follows a weekly rhythm. It rises early in the week and falls by the end of it. The average within-week swing is about 0.35% of body weight (Turicchi et al., 2020). At 80 kg, that is close to 0.3 kg, up and down, with nothing to do with fat.
A separate longitudinal study tracked 80 adults over 4,657 weigh-ins across 15 to 330 days. It found the same pattern: weight highest on Sunday or Monday, lowest midweek. The people who were actually losing weight still showed this bounce (Orsama et al., 2014).
This is why a single low or high reading proves nothing. One morning's number sits inside noise that is often bigger than the week's real change. You need enough points to see past it, not a better scale.
Weigh in every morning, after using the bathroom, before eating or drinking. Write down the number. Do this for at least three weeks.
Then stop looking at daily numbers and start looking at a 7-day rolling average: the mean of the last seven mornings, recalculated each day. This smooths out the weekly bounce described above and leaves the underlying direction.
Compare week to week, not day to day. If this week's 7-day average sits meaningfully below last week's, and next week's sits below that, you have a trend. If the averages sit within roughly 0.35% of each other, per the Turicchi et al. noise figure, you are likely still looking at fluctuation, not a result.
Three weeks gives you three averages to compare, which is enough to tell a real slope from noise. If you would rather not do this by hand, paste your weigh-ins into the weight trend calculator. It smooths daily noise into a trend line and tells you whether the resulting slope is a real change or a plateau.
Early changes in eating often shift glycogen and its stored water before any consistent fat trend shows on the scale, which is a separate reason the first several days can look flat. Keep weighing daily and averaging weekly, and let the trend accumulate enough points to separate itself from the noise. A real trend does not need to rush to prove itself.
The daily weights below are an illustrative example, not a measured case. They are chosen to divide cleanly so the averaging is easy to follow.
| Week | Daily weights (kg) | 7-day average (kg) |
|---|---|---|
| Week 1 | 80.4, 80.9, 80.2, 80.6, 80.8, 80.1, 80.5 | 80.5 |
| Week 2 | 80.3, 80.7, 80.0, 80.4, 80.6, 79.9, 80.3 | 80.3 |
| Week 3 | 80.1, 80.5, 79.8, 80.2, 80.4, 79.7, 80.1 | 80.1 |
Each week's daily numbers bounce by up to 0.9 kg morning to morning. That is well inside the roughly 0.35% weekly fluctuation range Turicchi et al. (2020) measured at similar body weights. Reading any single day here, say the 80.9 kg on day two, would look like nothing is happening.
The 7-day averages tell a different story: 80.5, then 80.3, then 80.1. That is a steady 0.2 kg drop each week, three weeks running, in the same direction. A single-day reading could not show this. Only comparing the averages, week over week, separates the trend from the noise sitting on top of it.
Looser clothes and more energy are weak signals, not a replacement for the scale. Clothes fitting differently can reflect water retention or how a garment was worn that day. Reported energy varies for reasons unrelated to eating less.
None of the sources behind this article measured clothes fit or energy as a marker of a deficit. The measured findings point the other way. Rolls, Roe & Meengs (2006) found hunger stays flat during a real intake drop. Lichtman et al. (1992) found people's sense of eating less is unreliable too. Treat non-scale signs as supporting color once the weight trend has already told you something, not as a substitute for it.
A flat trend after three real weeks is information, not failure. It usually means the eating change was smaller than assumed, water is still masking an early trend, or intake has not changed enough yet.
Given the Lichtman finding above, the most common explanation for "I'm eating less and nothing is happening" is that less eating did not actually occur. When that is the concern, it helps to see how counting calories accurately removes the guessing from what "eating less" actually means, before reading the scale any further.
No. The trend test above runs entirely on weight numbers, not on food logs. Weighing every morning and averaging by week works whether or not a single meal has been written down. A food log adds something different: it can explain why a trend moved, by showing what actually went into a day, rather than what was assumed.
Avocalo is a mobile app that lets you photograph a meal or search a food database to log calories, protein, carbohydrate, fat, water, weight, and activity, with statistics over 7 days, 30 days and 3 months. It can hold your weigh-ins alongside your food log in one place, but it cannot confirm a deficit any faster than the plain weight-trend arithmetic above, run by hand or with the free calculator. A photo estimate is a read of the image, not a lab measurement.
If you want that layer, you can download Avocalo and log meals there. If you would rather stick to the scale and a notebook, the trend test above works exactly the same way.
No. A controlled trial found measured calorie reductions of up to 24% with no significant change in reported hunger or fullness (Rolls, Roe & Meengs, 2006). Hunger tracks habit and food composition more than whether you are actually in a deficit that day.
Yes. Body weight follows a weekly pattern, typically highest around Sunday or Monday and lowest midweek, with a normal swing of about 0.35% of body weight (Turicchi et al., 2020). People genuinely losing weight still show this bounce.
Daily, then average by week. A single weekly weigh-in can land on a high or low point in the weekly rhythm (Orsama et al., 2014) and mislead you either way. Daily weighing lets a 7-day average cancel that rhythm out.
No. It is a documented, normal pattern seen across 4,657 weigh-ins in one longitudinal study (Orsama et al., 2014), present in people losing weight, maintaining it, or gaining it. It reflects timing, not failure.
Keep going a third week before concluding anything. Two weeks gives only one week-over-week comparison, which the roughly 0.35% weekly noise band (Turicchi et al., 2020) can easily swamp. Three weeks gives two comparisons in the same direction, a much stronger signal.
This article was written by the Avocalo Editorial Team for Avocalo, published by Petros IT Solutions SRL. See the editorial policy for how sources and calculations are checked. Spotted an error? Write to [email protected].