Indian food databases, household portions and honest estimates

What IFCT and INDB refer to

The Indian Food Composition Tables, commonly called IFCT 2017, are a reference publication about the composition of foods analysed for that work. INDB is the Indian Nutrient Databank, a separate resource that brings food and nutrient information together. These resources can support research and reference work, but a database entry is not a measurement of every dish made at home.

When choosing software, ask which source or method applies to each food and how the product handles a dish that does not map neatly to a reference item. A vendor should be able to describe its approach without suggesting that every recipe, brand or serving matches one fixed value. Reference material has a scope and should be read in that context.

Why the same dish can have different values

Dal can vary by pulse, thickness, added oil and serving size. A roti changes with flour and diameter. A katori is a familiar household measure, but bowls do not all hold the same amount. A plate can mean a single dish or several portions. These details affect any estimate created from a general food description.

That is why calorie and nutrient values should be presented as estimates. A useful record tells the nutritionist what the client meant and lets them clarify the recipe or portion when needed. It should not imply that a single number captures every version of a dish or establishes a health outcome.

Household portions can make logging easier

Many people describe meals in ways that fit daily cooking: two rotis, one katori of curd, a serving spoon of rice or half a plate of sabzi. Requiring a scale for every entry can add work and may not reflect how meals are served in the household. Familiar measures make a diary more approachable, even when they are approximate.

The trade-off should be visible. A household measure may be less specific than a weighed amount, and two clients can mean different things by “one bowl.” A good conversation can refine the description where it matters. The purpose is to understand the record well enough to discuss it, not to suggest false precision.

How Shellel presents food estimates

Shellel lets clients describe Indian meals in English, Hindi or Hinglish, or add a photo. It uses the available description to create a diary entry that the client can review and correct. The nutritionist sees entries that the client has chosen to share, which can make it easier to ask about the dish and portion during a consult.

Values shown for foods are estimates. They are not attributed as exact results from IFCT or INDB, and they cannot fully account for a home recipe or serving that has not been described. A photo can add context but may not show hidden ingredients, oil or the full amount eaten. Treat the entry as a record to discuss, not an authority on its own.

Questions to ask about any database

• Does the product explain which food reference or estimation method it uses?
• Can a client specify a recipe, brand or household portion when relevant?
• Can the client review and correct the food description before sharing it?
• Does the interface say clearly that nutrition values are estimates?
• Can the nutritionist see the description behind the number and ask a follow-up?

Use the number as a starting point

A nutrition estimate can help organise a food diary, but it should be interpreted with its uncertainty. If a client’s entry says “dal and rice,” ask what kind of dal, how it was prepared and what portion they had when those details matter to your review. Do not infer a person’s condition, progress or outcome from an approximate database match.

If you are comparing tools, test the same familiar meal in each one and see what description it returns. Check how corrections work and whether the nutritionist can see the client’s wording. To explore how that works in Shellel, review the meal-planning guide or book a demo with sample people.