Bites, Licks and Tastes: The Calories You Never Logged
Do bites and tastes actually add up?
Yes, and more than most people expect: three or four unrecorded handfuls a day — nuts while cooking, the last chips off a child's plate, a square of chocolate from the office tin — commonly lands somewhere between 150 and 400 kcal. The important part is not the size but the direction. This eating is missing from the log almost every day, in the same direction, which is the one kind of error that never cancels out.
None of it is a character flaw, and the aim here is not to stop doing it. The aim is bookkeeping.
Why is this the hardest food to record?
Everything that makes a meal easy to log is absent. A meal has a start, a plate, a seat, and a decision — four separate cues that tell your brain this is eating, write it down. Standing at the hob with a spoon has none of them.
Three patterns account for most of it:
Sampling while cooking. A teaspoon of sauce is trivial. The two tablespoons of grated cheese that go in your mouth rather than the pasta are not: cheddar runs around 400 kcal per 100 g in USDA FoodData Central, so 25 g of it is about 100 kcal. Oil is the same story — a tablespoon is about 120 kcal whether it reaches the pan or the bread you used to test the sauce. (The cooking oil and sauces article covers the pan side of that problem.)
Food that belongs to someone else. Finishing a child's plate is eating a second, smaller dinner. Two leftover chicken nuggets and a short handful of chips is roughly 180–200 kcal, and it happens standing up, between clearing the table and loading the dishwasher.
Shared food in shared space. The tin in the office kitchen, the birthday cake on the side, the bowl of crisps at someone's house. A digestive biscuit is about 70 kcal, two squares of milk chocolate about 55, a 15 g handful of crisps about 80. Each one is forgettable on purpose: it was offered, not chosen.
The foods involved are also, unhelpfully, the dense ones. Nuts are the clearest case — about 160 kcal per 28 g, so a generous handful from the bag while you wait for the kettle can be 200 kcal on its own. Nobody grazes on boiled potatoes.
How much does this cost in practice?
Work it through with a figure you can argue with. Say the unrecorded eating averages 300 kcal a day — three of the examples above. That is 2,100 kcal a week. A kilogram of body fat holds about 7,700 kcal, so the missing eating accounts for roughly 0.27 kg a week of weight you expected to lose and didn't.
Put differently: if you planned a 500 kcal daily deficit, you planned for about 0.45 kg a week. With 300 kcal unlogged, the real deficit is 200 kcal, and the real rate is under 0.2 kg a week — slow enough to look like a stall, slow enough to be buried in normal water-weight noise for a fortnight. That is one of the commonest reasons the log and the scale disagree.
If your unrecorded eating is more like 80 kcal a day, it is worth about 0.07 kg a week and you can reasonably ignore it. The point of doing the arithmetic is to find out which situation you are in, not to assume the worse one.
Why doesn't the error average out?
Random error does average out. If you over-estimate your rice on Monday and under-estimate it on Thursday, a two-week average is still roughly right — which is why calorie counting works at all despite being made of guesses.
Unrecorded snacking is not random. It is always absent, never over-stated, so the average of your log sits below the average of your eating by a stable amount. Averaging more days makes the number more precise and no less wrong.
There is one consolation. If the gap is consistent — call it 250 kcal most days — then a target that learns from the scale rather than a formula will quietly absorb it: your apparent maintenance comes out about 250 kcal lower than it truly is, and the subtraction still produces the right weekly result. This is how Day So Far's target works, comparing what you logged against what the scale did over a fortnight. What defeats it is variability: three handfuls on a bad Tuesday and none at the weekend. Then the gap is both invisible and unstable, and no amount of learning fixes it. The same logic applies to finding your real maintenance calories by any method.
What do I log when I don't know what I ate?
Stop trying to itemise. Nobody reconstructs seven separate pinches of cheese, and the attempt is what makes people give up.
Log the occasion, not the item. One entry per episode: "picked at things while making dinner", "finished the kids' plates", "office kitchen, afternoon". Then put one honest number on it. Plain-language entry helps here — being able to type "a couple of handfuls of cashews and two chicken nuggets" and get an estimate is a lot more survivable than searching a database for food you only half remember.
Or keep one catch-all line. A single standing entry — "untracked bites, 200 kcal" — added at the end of each day. It is openly a guess. A guess that is present beats a zero that is wrong, because zero is a claim too, and it is the least likely one.
Count occasions before you count calories. For one week, make a tally mark instead of a log entry. At the end you have a number — eleven, twenty-six — and multiplying by a rough 70–100 kcal gives you a far better daily estimate than memory ever will. It also tells you where they cluster, which is usually a time of day rather than a food.
What actually reduces the invisible eating?
Change the setup, not the resolve.
Portion nuts, crisps and chocolate into a bowl or a small bag. Eating from the container has no end point and no quantity.
Scrape children's leftovers into a tub or the bin while clearing, before you are standing over them with a fork.
Use one tasting spoon, set down between tastes. It gives the tasting a start and a finish, which is all that was missing.
Move shared food out of your sightline where you reasonably can, and when you can't, take a portion onto a plate. A plate makes it a meal, and meals get logged.
And if logging in the moment is realistic for you, do that — the case for logging before you eat is strongest exactly here, because nothing about this eating is memorable ten minutes later.
The goal is a log that is wrong by a predictable amount rather than one that is wrong by an unknown one. That is achievable, and it does not require eating one biscuit fewer than you want to.