Calories of Indian home food for clients: IFCT 2017, oil and the katori problem

Calories for an Indian home-cooked meal are estimates when the nutritionist knows only a dish name and a household portion. IFCT 2017 by ICMR-NIN is a named Indian food-composition reference that can inform calculations, but it does not tell you exactly what went into a client's dal or how full their katori was. Recipe, cooking oil, ingredients and serving size all affect what a number represents. Explain the assumptions and keep the client's meal at the centre of the discussion.

What a food-composition reference can do

A food-composition reference gives information about foods described in its entries. It can help nutritionists work with Indian food examples using a recognised local reference. IFCT 2017 by ICMR-NIN is one such reference. The important distinction is between the composition information in a reference and a particular meal prepared in someone's home.

A home-cooked dish is not automatically identical to a reference entry. Recipes differ between households, cooks and occasions. Ingredients can be substituted, water content can vary, and the final preparation may be more or less concentrated. A named food provides a starting point for an estimate, not direct evidence about the exact nutrients in a client's serving.

When describing the result, say that the value is an estimate informed by the available food description and portion. Do not say that ICMR-NIN confirmed the calories in the client's lunch. The authority belongs to the reference, while the estimate for the individual dish depends on details the reference cannot know.

Why the katori problem matters

“One katori” is a useful household phrase, but it does not name one standard vessel. Katoris have different shapes and sizes; people fill them to different levels. The client may also use the same word for a serving bowl and a smaller personal bowl. Without knowing which one they mean, the portion is uncertain.

Ask the client to describe the vessel and how full it was. A photo of the bowl beside a familiar object may help clarify the description, if the client is comfortable sharing it. Even then, the food's density and preparation can differ, so visual comparison does not automatically produce an exact gram weight.

Clarify whether the client means food served or food eaten. In a family meal, a serving may be shared or replenished. “One katori rice” could describe the first serving, the total eaten, or the amount placed on the table. A follow-up question can distinguish these without asking for false precision.

Cooking oil is difficult to infer from a dish name

Oil may be used during cooking, added in a tadka, or poured at the table. The amount can vary by recipe and serving size. A photo may show the finished dish but not how much oil was used in the pot or how the total was divided among servings. The client may not have prepared the meal or know the quantity.

Ask what the client knows in a non-judgemental way: “Do you know how it was prepared, or is that something the cook would know?” If they do not know, keep the cooking detail uncertain. Do not infer an amount from appearance or imply that the client should have monitored the cook.

The same care applies to ghee, coconut, peanuts, cream or other additions. A dish name may not reveal every ingredient. Ask about details only when they are relevant to the conversation, and accept that some meals cannot be reconstructed precisely after the fact.

A practical way to build an estimate

Start with the client's description, then clarify the details most likely to change your interpretation. This is not a requirement to collect every ingredient for every meal. It is a way to make the assumptions explicit.

1. Name the dish as the client remembers it. For example, dal, poha or rajma chawal.
2. Clarify the serving. Ask about the household measure, fill level and whether the amount was served or eaten.
3. Ask about preparation only when known. Record that the client does not know if the recipe details are unavailable.
4. Identify the reference and assumptions used. Do not suggest that the reference measured the actual meal.
5. Present the result as an estimate. Use wording that matches the uncertainty in the input.

For a meal with several parts, keep components separate where the client can describe them. “Rice and rajma, about one serving each” may carry more useful context than one broad label. If parts were mixed or portions cannot be recalled, record that honestly.

Avoid precision that the entry cannot support

A number with several decimal places looks precise even when the meal description is approximate. Match the displayed detail to the quality of the information. If the serving is “2–3 roti, I think,” preserve that range or discuss which value feels more likely. Do not silently replace uncertainty with an exact amount.

The same rule applies to daily totals and comparisons. If only some meals are logged, the total cannot represent the full day without additional information. If a week has gaps, do not make a complete weekly claim from the recorded entries. Name the coverage and explain what is missing.

The purpose of an estimate is to support the nutritionist's conversation where a number is useful. It does not need to be included for every dish. Sometimes the most accurate statement is that the recipe or portion is not known well enough to provide a meaningful figure.

Explain estimates without undermining trust

Clients do not need a technical lecture to understand that home recipes vary. A simple explanation is enough: “This value is an estimate based on the dish and serving you described. Your recipe or bowl may be different.” That language is honest and gives the client a chance to add context.

Avoid framing uncertainty as a defect in the client's memory. The nutritionist also does not know every ingredient or amount. Shared meals are ordinary; the person eating them may not cook them. A respectful estimate acknowledges the limits on both sides.

If a client asks why the displayed number differs from their expectation, walk through the dish match and serving assumption. Invite them to correct the entry. Do not defend a value merely because software or a reference produced it. The estimate should remain open to revision when the underlying description changes.

A home-food example

Dr Meera Iyer and Priya S. discuss a lunch of dal, rice and sabzi. Priya remembers one medium katori of rice and a smaller bowl of dal, but her mother cooked the meal and she does not know how much oil was used. Meera can record the portions as Priya describes them, leave the cooking detail unknown, and explain that any calorie or macro figure is an estimate.

If Priya later remembers taking another serving, the entry can be updated. If she does not, the uncertainty stays. Meera can still use the meal to understand how Priya describes lunch and what she wants to discuss. The value of the conversation does not depend on producing an exact number for every home recipe.

How Shellel helps

Shellel gives nutritionists a place to review food descriptions and portions with clients. Estimates can support that discussion when useful, with recipe and household-measure limits kept clear. Learn about the nutritionist workflow at /nutritionists. For a deeper look at household portions, read katori, not grams.