Why home-cooked food is the hardest thing to track — and how to estimate it anyway

Open any food log and look at what people actually record. Four biscuits: 220 calories, exact, straight off the label. Then lunch: “home food”, no number at all. The effort went into the product that came in a packet, and the meal that decides the day went in as a word.

That is not laziness. Packaged food is easy to count because somebody already did the counting. Home cooking is hard for a specific set of reasons, and once you can name them, most of the difficulty goes away.

A katori is not a unit

Katoris come in every size between 100 ml and 250 ml, and in most kitchens “one katori” means “that bowl, filled to where it looks right”. The same katori of the same dal can be 7 g of protein or 15 g, depending on how thick it is and how high it was filled. Both are honest servings. One is twice the other.

This is the single biggest source of error in Indian home-cooked logging, and the fix is smaller than it sounds: measure your own usual katori with a measuring cup once, and remember the number. Ours is 150 ml. Now “a katori of dal” is a real quantity instead of a bowl.

Oil leaves no trace in the log

Nobody writes down the tadka. It is a spoon that goes into a pan, and by the time the dish reaches the table, the 80 calories in it look exactly like the rest of the sabzi.

We measured what that costs in the post on cooking with less oil: a normal day of home cooking, no frying, no restaurant meals, carries somewhere around 300 calories of oil. That is a fifth of an average day’s intake, invisible to any log that records dish names.

The same dish is never the same dish

Your mother’s rajma and your rajma are different foods. Yesterday’s and today’s are also different foods, because the tomato was bigger and you used a little more ghee because the pan was dry. This is a feature of home cooking, not a flaw, but it means there is no stable database entry to look up — and it is why the estimate should be built from components rather than from a recipe you found online.

How to estimate without weighing anything

Five rules, in the order they help:

1. Log components, not dish names. “Dal” is unloggable; “one katori of dal, two rotis, bhindi sabzi, curd” is four estimates you can actually make.
2. Give oil its own line. Count the teaspoons you added, multiply by 40 calories. It is usually the most accurate part of the whole log.
3. Divide by the pan. If you cooked for four people and ate a quarter of it, you know your portion better than any “1 serving” definition.
4. Round to sensible bands. “About 250 calories” beats “237”. The false precision is what makes logging exhausting, and it buys you nothing.
5. Accept plus or minus twenty per cent. That is close enough to see whether you are 400 calories under or 400 over, which is the only question a log needs to answer.

If you do only the first and second consistently, your estimate gets good enough to be useful within a week. You do not need a kitchen scale, and we would not recommend one for home-cooked Indian food — the variation between cooks is bigger than the precision a scale would give you.

Watch “5 mistakes stopping your weight loss” on YouTube

The three numbers worth knowing

You can log every nutrient and learn nothing. In our own cooking we watch three things:

• Total calories, roughly. Not to hit a target exactly, but to know which side of it you are on.
• Protein. Because it is the one that decides whether you are still hungry two hours later, and it is the one Indian home cooking most often misses — the numbers are in how much protein you actually need.
• Fibre, loosely. If most meals have a pulse, a vegetable and something raw, you are fine. If none of them do, that is worth fixing before anything else.

Everything else — the exact grams of carbs, the micronutrient percentage, the breakdown by meal — is information you can have without acting on it, and tracking only pays off when it changes a decision.

When tracking stops helping

Worth saying plainly: if logging makes you skip meals, feel guilty about food, or eat less than you meant to in order to make a number look better, stop. The point of writing food down is to replace a guess with an estimate, not to turn dinner into a test. Anyone with a history of disordered eating should not use a food log at all, and that is not a caveat we tack on at the end — it is the reason this site never nags.

Where the app comes in

The reason HealThaali records components rather than dishes is this post. Food memory, quick logging and the plate camera on the features page exist so the estimate takes a few seconds instead of an evening, and so the answer to “was today roughly right?” is on one screen. The app is still in development; what is ready today is the cooking, on the recipes page.

Next in this series: what to change before you cut rice. The other side of the same problem is the meal somebody else cooked to a recipe you cannot see, which is what eating out and ordering in does to a week — and the packaged half of it, including the label on those four biscuits, is in the post on sugar in an ordinary day.