Tracking calories when one pot feeds four people

Calorie apps are built around a plate: one person, one portion, one entry. Most of the world does not eat that way. Food arrives in a pot, gets served in rounds, and what ends up on your plate is neither measured nor equal to anyone else's.

This is the case that makes people give up. It has a method, and the method is less work than it sounds because it is done once per dish rather than once per meal.

Log the pot, not the plate

The move is to calculate the whole dish and then take your share.

Count what goes in. Every raw ingredient, by weight where possible. Two hundred grams of toor dal, one onion, two tomatoes, four tablespoons of oil, a teaspoon of ghee for the tadka, spices, salt. Spices and salt are nutritionally negligible and can be ignored.

Total it. That is the calorie content of the entire pot. For a typical family dal it might come to 1,100 kcal, of which nearly half is the oil and ghee.

Divide by the servings it actually produced. Not the servings the recipe claimed. If it filled six katoris, divide by six.

Save the number. One katori of your dal = 185 kcal. Use it every time.

The full worked example is in how to calculate the calories in a recipe you cooked.

Why the fat dominates, and why it must be counted

In almost every home-cooked dish, the largest single line in the calculation is the cooking fat. Lentils, vegetables and spices are cheap in calories. Oil is 9 kcal per gram.

A dal made with one teaspoon of oil and the same dal made with four tablespoons differ by about 500 kcal for the pot — which is 80 kcal per serving, every serving, forever. That difference is invisible on the plate and it is bigger than most people's entire margin for error.

If you take one thing from this: measure the oil going into the pan. Nothing else in home cooking repays measurement as well. How much oil is actually in your curry has the numbers by dish.

Serve yourself with a calibrated vessel

Once the per-serving number exists, the remaining variable is how much you serve yourself. A katori filled to the brim and a katori filled two-thirds are not the same portion.

Pick one bowl. Weigh it full of dal, once. From then on "my katori" is a fixed quantity you can log in one tap, which is what a household serving means in practice. Details in how to track calories without a food scale.

Uneven eaters and the honest share

Dividing by the number of people assumes everyone ate the same, which is often untrue — the person who trains hard eats more, the child eats less.

When shares are genuinely uneven, weigh the finished dish and log by grams. Total calories divided by total grams gives you calories per gram; multiply by what you served yourself. It is one extra step and it makes the number yours rather than the household average.

Build a small library, then stop calculating

Here is the part that makes this sustainable. Most households cook from a repertoire of fifteen to twenty-five dishes. Once each has a saved per-serving number, logging dinner becomes recall.

Do one or two dishes a week. After two months the common ones are all done, and the calculation work drops to whatever is genuinely new. Compare that with searching a database at every meal and choosing between eleven strangers' guesses, which is the alternative and the reason most people quit.

When someone else cooks

At a parent's house, a relative's, a friend's, you have no ingredient list. Ask one question: how much oil went in. That single answer resolves most of the uncertainty, and people are generally happy to tell you.

Then estimate the rest from the closest dish in your own library and add a margin. A generous estimate is closer to the truth than a generic database entry, because generic entries are built from recipes far leaner than most home cooking, which is part of why two apps give the same roti different calories.

Cooking for a household that is not dieting

A common worry: does this mean the family eats diet food? It does not, and the version where it does tends to fail within a month because nobody else agreed to it.

The two changes worth making are invisible. Measure the oil rather than pouring it, which usually cuts a third of it without anyone noticing a difference in taste. And serve the protein first, the vegetables second and the rice or roti last, which changes the ratio on your plate without changing what is on the table.

Everything else — what you personally take, how many rotis, whether you go back for a second katori — is a portion decision, not a recipe decision. Keeping it that way is what lets one pot feed a person losing fat and a teenager who is not.

Logging your own plate from a shared pot

There is a shortcut worth knowing when you did not do any of the calculation. Weigh your own plate before and after, if that is practical, and log the difference against a close database entry with a generous fat allowance.

It is cruder than the pot method and still better than picking "1 serving chicken curry" from a list. The reason is that the plate weight is real and yours, so the only thing being estimated is calories per gram rather than both quantity and density at once. Halving the number of guesses roughly halves the error, which is the same reasoning behind how accurate are calorie counts, really.

What this buys you

A per-serving number for your own food, in your own servings, that does not change week to week. That is a more reliable basis for tracking than any packaged food you could buy, and it comes from the meals you were going to cook anyway.