Key takeaways
- Self-logged diets routinely under-report intake by 20–40% — almost always unintentionally.
- Cooking oil, drinks, and untracked weekends are the three biggest single leaks.
- Two untracked weekend days can cancel five weekdays of a 400 kcal deficit.
- You do not need to weigh everything forever — two weeks recalibrates your eye.
When someone says “I’m eating 1,600 calories and not losing weight,” the plan is rarely the problem. The log is. Research comparing self-reported intake against objective measurement has found gaps of 20–40% again and again — not because people lie, but because calories hide in perfectly ordinary places. Here are the eight most common, and what each one costs.
1. Cooking oil and fats
The biggest single leak in most kitchens. A tablespoon of olive oil is roughly 120 calories, and almost nobody pours a level tablespoon. A generous glug into a hot pan is easily two, and if you cook twice a day that is 200–400 calories entirely unlogged — the size of an entire moderate deficit.
The fix: measure oil with a spoon or weigh the bottle for two weeks. Not forever — just long enough to know what your actual pour looks like. Most people are shocked once.
2. Liquid calories
Drinks bypass the mental category of “food” almost completely, and they do very little for satiety, which makes them the least efficient calories in the diet.
| Drink | Typical serving | Calories |
|---|---|---|
| Large latte, whole milk | 16 oz / 470 ml | 220 |
| Orange juice | 250 ml | 115 |
| Beer | 1 pint / 568 ml | 210 |
| Wine | 175 ml glass | 160 |
| Sports drink | 500 ml | 125 |
| Blended coffee drink | 16 oz / 470 ml | 380 |
Two of these a day is 400+ calories that never feel like eating.
The fix: log every drink that is not water, tea, or black coffee for two weeks. Many people find their entire missing deficit here.
3. Skipping the weekend
Weekday discipline followed by two unlogged days is arithmetically self-defeating, and it is the most common pattern we see.
−2,000
Weekday deficit
400 kcal below maintenance, Monday to Friday
+2,000
Weekend surplus
Two relaxed days at 1,000 kcal above maintenance
0
Net weekly result
A month of perfect weekdays, and the scale does not move
The fix: your body settles up weekly, not daily. Log weekends even roughly — a rough estimate you record beats a perfect one you skip. If weekends are social by design, plan a slightly larger weekday deficit and treat it as a weekly budget.
4. Bites, licks, and tastes
The spoonful while cooking, the crusts off a child’s plate, three chips from someone else’s bowl, the handful of nuts while making dinner. Individually trivial, collectively 100–300 calories a day for a lot of people.
The fix: log them as one estimated entry — “bites, 150 kcal” — rather than trying to capture each one. An approximate entry is infinitely better than the zero you are currently recording.
5. Trusting bad database entries
Crowd-sourced food databases contain a great deal of wrong data. Entries with implausible values, missing fat, or portion units that make no sense are common, and picking the first search result is a coin flip.
- Prefer entries with a verified or brand-official marker where your app offers one.
- Scan the barcode instead of searching by name — it maps to the manufacturer's own data.
- Sanity-check anything that looks too good: cooked chicken breast is not 60 kcal per 100 g.
- Save a corrected version of foods you eat weekly so the error does not repeat.
Fewer steps, fewer places to go wrong
2BIB logs from a barcode, a nutrition label, or a photo of the plate — and returns a per-item breakdown you can correct. Recurring foods can be set to log themselves daily, so the meals you always eat stop being a source of error.
6. Logging raw, eating cooked (or the reverse)
100 g of raw chicken becomes about 75 g cooked as water is driven off — the calories stay put but the weight falls, so logging 100 g cooked when your database entry is raw under-counts by roughly a third. Rice and pasta run the opposite way: 100 g dry becomes roughly 250–300 g cooked, so logging cooked weight against a dry entry can triple the real number.
The fix: pick one convention and check the entry matches it. Weighing rice and pasta dry is usually the simpler habit.
7. Eyeballing calorie-dense foods
Portion misjudgement scales with calorie density. Being 30% out on broccoli costs you eight calories. Being 30% out on peanut butter costs eighty.
| Food | What people log | What it usually is | Difference |
|---|---|---|---|
| Peanut butter | 1 tbsp / 16 g | 2+ tbsp / 35 g | +110 kcal |
| Cheese | 28 g | 50 g | +90 kcal |
| Cooked rice | 1 cup | 1.5 cups | +100 kcal |
| Cereal | 40 g | 70 g | +110 kcal |
| Salad dressing | 1 tbsp | 3 tbsp | +130 kcal |
The two-week calibration
You do not need a food scale forever. Weigh everything for two weeks and your eye recalibrates — most people discover their default portions were 30–50% larger than they assumed. After that, weighing only the calorie-dense items (oils, nut butters, cheese, grains) captures most of the benefit at a fraction of the effort.
8. Logging after the fact
Reconstructing a day at 10 pm relies on memory, and memory systematically drops the small stuff — which is exactly the stuff that adds up. Retrospective logs are consistently lower than real intake.
The fix: log at the meal, or better, before it. Photographing the plate before you eat takes two seconds and preserves the evidence even if you complete the entry later — and a pre-meal scan is also the most accurate kind, as the accuracy research shows.
Putting it together
A two-week accuracy audit
Do not change your diet. For fourteen days: weigh cooking oils, log every drink, log weekends, add a daily “bites” entry, and scan barcodes rather than searching by name. Then compare the new average against what you thought you were eating. That gap is your answer — and it is usually larger than any plan change you were about to make.
If your weight has stalled, run this audit before cutting calories further. In most cases the deficit did not stop working; it stopped existing. The plateau guide covers what to do once the log is honest again, and the TDEE calculator gives you the target to measure against.