12 calorie-tracking mistakes that stall weight loss

Most stalls are a few small under-counts repeated daily. Here is where they hide and how to close each one.

By the Cal.AI Team · Published October 25, 2026 · 4 min read

Short answer The mistakes that stall weight loss are mostly small, repeated under-counts: unlogged cooking oil, eyeballed nuts and cheese, skipped weekends, wrong serving sizes, raw weights logged as cooked, inflated exercise calories eaten back, and targets never updated after losing weight. Each has a simple fix, and together they explain most stalls.

Which calorie counting mistakes stall weight loss?

Almost all of them are under-counts. Tracking rarely fails because someone logged too much; it fails because a few hundred daily calories never got logged. In the best-known study on this, people who could not lose weight on a reported low intake were under-reporting food by 47% on average and over-reporting exercise by 51% (Lichtman 1992). The twelve mistakes below are the usual sources of that gap, each with its fix.

Mistakes 1 to 4: the food you did not log

Not logging cooking oil. One tablespoon of olive oil is 13.5 g and 119 kcal (USDA). Two unlogged tablespoons a day is 239 kcal, or about 1,670 kcal a week. Fix: weigh the bottle before and after, or log a tablespoon per pan as a default.
Eyeballing nuts and cheese. A "handful" of almonds might be 30 g (174 kcal) or 50 g (290 kcal, USDA). Fix: weigh them every time, or pre-portion into bags once a week.
Forgetting drinks. A 12 fl oz can of cola is 155 kcal, a 5 fl oz glass of red wine 125 kcal, a can of beer 153 kcal (USDA). Fix: log drinks first, before the food.
Ignoring sauces, dressings and spreads. One tablespoon of mayonnaise is 94 kcal and a 30 g serving of ranch dressing is 129 kcal (USDA). Fix: treat condiments as food and scan the bottle.

Mistakes 5 to 8: the numbers that were wrong

5. Wrong serving sizes. The label says 30 g per serving; the bowl holds 80 g. Fix: weigh the portion and log grams, not servings.
6. Logging raw as cooked, or cooked as raw. USDA lists dry oats at 379 kcal per 100 g and cooked oatmeal at 71. Pick the wrong one and a 60 g dry portion is logged as 43 kcal instead of 227. Fix: match the entry to the state you weighed.
7. Picking the wrong database entry. "Chicken" can mean breast meat only (165 kcal per 100 g) or wings with skin (254), and "Greek yogurt" can be nonfat (59) or whole milk (97) per 100 g (USDA). Fix: read the full entry name, and scan barcodes for packaged food.
8. Trusting labels as exact. U.S. rules allow a product's measured calories to run up to 20% above the label (21 CFR 101.9). Fix: treat label numbers as a floor, not a ceiling, and leave a small buffer in your target.

Mistakes 9 to 12: the plan that drifted

9. Skipping weekends. Five tracked days at 1,700 kcal and two untracked days at 2,800 average out to 2,014 per day, not 1,700. Fix: log the weekend first, even roughly. The weekly average is what the scale responds to.
10. Eating back inflated exercise calories. Watches and machines estimate burn, and self-reported exercise ran 51% high in the Lichtman study. Fix: eat back none or at most half of estimated exercise calories, and let the weight trend decide.
11. Not updating targets after losing weight. A 90 kg (198 lb) man who reaches 80 kg (176 lb) needs about 100 kcal less per day at rest by Mifflin-St Jeor (10 kcal per kg × 10 kg), and more once the activity multiplier is applied. Fix: recompute at every 5 kg (11 lb) lost.
12. Logging perfectly for three days, then quitting. More frequent self-monitoring is consistently linked with greater weight loss (Burke 2011). Fix: lower the bar. A rough log every day beats a precise log twice a week.

Worked example: how 500 kcal a day goes missing

This is what a "clean" 1,800 kcal day can look like once the small misses are added back, using USDA values.

Miss	Logged	Actual	Gap
Oil for eggs and dinner, 2 tbsp (27 g)	0	239	239
Almonds, logged 30 g, ate 45 g	174	261	87
Cheddar, logged 1 slice (28 g), ate 2	113	226	113
Ranch dressing, 2 tbsp (30 g)	0	129	129
Total	287	855	568

The logged day reads 1,800 kcal. The real day is 1,800 + 568 = 2,368 kcal. If maintenance is 2,400, the planned 600 kcal deficit has shrunk to 32 kcal, which is a stall. None of the four misses is large on its own. Together they erase the deficit.

What to do next

Weigh oil, nuts, cheese and nut butter for one week. These four fix most of the gap.
Log drinks and condiments before the meal, not after.
Log weekends, even with photo estimates. Cal.AI's photo scan plus Fix Results takes seconds and keeps the weekly average honest.
Do not eat back exercise calories until the trend proves your estimate.
Recalculate your target every 5 kg (11 lb) lost.
Read how accurate AI calorie counting is so you know where estimates are strong and where to correct them.

Close the gaps with Cal.AI Cal.AI is free on iPhone, Apple Watch and Android. Snap a photo, scan a barcode or search any food, then fix anything the AI gets wrong.

Frequently asked questions

Which calorie counting mistake matters most?

Unlogged cooking oil and eyeballed calorie-dense foods such as nuts, cheese and nut butter. Each tablespoon of oil is about 119 kcal (USDA), and a generous handful of nuts can be double what you logged. These are small per item and large per week, which is why they stall progress without feeling like overeating.

Should I eat back exercise calories?

Be cautious. Device and machine estimates are often high, and in a well-known study people over-reported their activity by 51% (Lichtman 1992). A safer rule is to eat back none or at most half, then let the weekly weight trend tell you whether your real deficit is what you think it is.

I track everything and still do not lose weight. What now?

Weigh instead of estimating for two weeks, log weekends, and recheck your target at your current weight. If the trend is still flat after four weeks of careful logging, your maintenance is lower than the formula estimate and the target needs to come down by 100 to 200 kcal.

Is it a mistake to use photo scans instead of weighing?

No, as long as you correct them. A photo gives a fast estimate of what is on the plate. For dense foods, open Fix Results and set the portion to the weight from your scale. Using the estimate for everything and never correcting it is the mistake, not the photo itself.

Sources

Lichtman SW, et al. Discrepancy between self-reported and actual caloric intake and exercise in obese subjects. N Engl J Med. 1992;327(27):1893-1898. PubMed
Burke LE, Wang J, Sevick MA. Self-monitoring in weight loss: a systematic review of the literature. J Am Diet Assoc. 2011;111(1):92-102. PubMed
21 CFR §101.9(g) — nutrition labeling compliance (the 20% tolerance). eCFR
U.S. Department of Agriculture. FoodData Central. USDA

Cal.AI TeamWe build Cal.AI, an AI calorie counter for iPhone, Apple Watch and Android. Every number in this article links to its source; see how we research and fact-check. This is general nutrition-tracking guidance, not medical advice.