How to Count Calories in Batch Cooking and One-Pot Meals
The method, in one paragraph
Add up the calories of every ingredient that goes into the pot, weigh the finished dish, and divide one by the other to get a calories-per-100g figure for that batch. Then log whatever you actually spoon onto your plate by weight, not as "a sixth of it" — because your plate is almost never a sixth of it.
That's the whole technique. The rest of this is the places it goes wrong, and how much those places cost you.
A worked example: one pot of chilli
Here's a batch made with a kilo of 5% beef mince, two tins of chopped tomatoes, two tins of kidney beans (drained), an onion, two tablespoons of olive oil, and spices. Using ordinary published figures of the kind you'd find in USDA FoodData Central:
1 kg lean beef mince — about 1,300 kcal
800 g tinned chopped tomatoes — about 130 kcal
480 g drained kidney beans — about 480 kcal
1 onion, roughly 150 g — about 60 kcal
2 tbsp olive oil — about 240 kcal
Stock, spices, tomato purée — call it 30 kcal
Total: about 2,240 kcal.
Now weigh the finished pot. Weigh the empty casserole before you start, or note the figure stamped on the base, then weigh it full at the end and subtract. Say it comes out at 2,300 g of chilli after an hour of simmering.
2,240 ÷ 2,300 gives about 97 kcal per 100 g. That number is now the only thing you need. A 250 g bowl is about 240 kcal. A 480 g bowl is about 465 kcal.
Notice what you did not do: you didn't decide in advance that it serves six. "Serves six" is a number someone wrote on a recipe card. Grams are a number your scale measured.
Why can't I just use the raw weight?
Because water leaves and enters food during cooking, and water has no calories. The same food weighs differently before and after, so the two weights aren't interchangeable.
Dry pasta is around 350 kcal per 100 g. Boiled, it absorbs water and roughly doubles or more in weight, landing somewhere near 130–160 kcal per 100 g depending on how long it sat in the pan. Log 200 g of cooked pasta against the dry figure and you've recorded about 700 kcal for something nearer 300.
The error runs the other way for meat. A 150 g raw chicken breast loses water in the oven and comes out around 110 g — the calories barely changed, so cooked chicken is more calorie-dense per gram than raw. Rice behaves like pasta: about 75 g dry, roughly 260 kcal, becomes something like 200 g on the plate.
The rule that saves you: pick raw or cooked, check that the figure you're using says which one it is, and never mix them within a dish. For a whole-pot calculation, raw is easier, because raw is when you had the packets in your hand.
What happens to the oil, the marinade and the boiling water?
This is where people either double-count or quietly lose 300 kcal.
Oil used in the pot stays in the dish. The two tablespoons you fried the onion in did not evaporate. They are in the chilli, all 240 kcal of them, and they belong in the total. Frying oil is the single most commonly dropped ingredient in home logging.
Boiling water is discarded, so it takes almost nothing with it. Pasta water, the water you boiled potatoes in, the water drained off rice — a trivial amount of starch, not worth counting.
Marinades are mostly thrown away, but not entirely. If you marinate chicken in 60 ml of oil and honey and then lift the pieces out onto a rack, most of that mixture stays in the bowl. Some clings. There is no honest precise answer here; counting roughly half of a discarded marinade is a defensible guess, and being consistent about it matters more than being right. Same for a joint roasted on a rack, where a good deal of the fat drips into the tray and never reaches your plate.
Tinned liquid counts if you don't drain it. Beans in water, drained, are a different figure from beans tipped in wholesale.
The biggest error is the ladle, not the ingredients
If your ingredient totals are 10% out, that's the sort of error that comes out in the wash over a fortnight. If your portion estimate is 30% out every single time, it doesn't — it's a bias, and biases accumulate in one direction.
And portion estimates are routinely 30% out. The person who cooked usually serves themselves last and generously. In the chilli above, an even sixth is 383 g, or about 370 kcal. A bowl that looks like a normal bowl but weighs 480 g is about 465 kcal — roughly 95 kcal more, unrecorded, every time you eat it.
Eat that batch three times a week for three months and you've quietly unlogged around 3,700 kcal. At about 7,700 kcal per kilogram of body fat, that's most of half a kilo of difference between what your log says and what the scale says — enough to make a slow month look like a stalled one. If your numbers and your weight disagree over weeks rather than days, this is one of the first places to look; where the energy usually hides is rarely mysterious once you weigh it.
So: put the bowl on the scale. Tare it empty, serve, read the number. It adds four seconds.
Do I have to do this for everything I cook?
No, and you shouldn't try. This is a technique for the four or five dishes you make again and again — the Sunday bolognese, the curry, the lentil soup, the tray of overnight oats. Those are the meals where a repeated error repeats.
For a dish you'll cook once this year, an honest description is fine. Calorie counting does not need to be as precise as people assume, and the effort is better spent on frequency than on decimal places.
The up-front work also amortises. The chilli calculation above takes maybe five minutes with the packets in front of you, and it's done — 97 kcal per 100 g is true for every batch you make that way, and the only thing left to do on a Tuesday night is weigh your bowl. Day So Far will keep a meal you've already described and let you re-log it at a different weight, which is the whole reason the five minutes is worth spending: you spend it once and then it's arithmetic.
The same logic applies to dishes with no label at all, where the ingredients list in your own kitchen is a better source than any database entry called "beef stew, homemade".
When the one-pot method breaks down
It doesn't work well for anything where the composition isn't even. A tray bake where the sausages sit at one end and the vegetables at the other is not a uniform substance, and grams-of-the-whole tells you little about what's on your fork. Nor does it work for a roast carved into unequal slices, or a pizza where one half got the extra cheese.
For those, separate the components: weigh the chicken thigh, weigh the potatoes, log them as two things. It's less elegant and about as accurate.
And if the answer is genuinely unknowable — a curry at someone's house, a shared meze, a stew someone else made — estimate it, log it, and move on. A rough number entered today beats a precise one you never got round to.