How to Track Meals When Cooking for a Family

Tracking your own calories when cooking for a family feels like solving a multi-variable equation mid-dinner rush. You made a pot of dal for four, a side of rice, and a salad. How many calories did you eat? If you’re eyeballing your portion and searching “dal” in a database, the answer is probably wrong by 30–40%. This guide walks through the correct CalEye workflow for shared family cooking: log the pot once, split by portion, and move on in under 2 minutes.

The key insight is to separate two tasks that most people confuse: logging the recipe (a one-time setup per dish) and logging your serving (the daily 15-second action). Once a recipe is saved, every family dinner becomes a question of one thing: “How much of the pot did I eat?” Answer that question accurately and you have a reliable log without starting from scratch each time.

Step 1: Log the Full Recipe, Not the Serving

The first time you cook a dish, log it as a recipe in CalEye. This takes 4–5 minutes the first time.

Open CalEye → Log Meal → Create Recipe. Name it specifically: “Mum’s Dal Tadka (4 servings)” or “Sunday Chicken Curry.”

Add every ingredient used in the pot:

• All lentils, grains, and starches (weigh raw, before cooking)
• All vegetables (weigh raw)
• All oils and fats (measure by tablespoon or ml)
• All spices and pastes that contain significant calories (coconut paste, tahini, cream)
• Skip pure spices (cumin, turmeric, salt) — their caloric contribution is negligible

Why weigh raw? Cooking changes weight through water absorption or evaporation. Raw weights are consistent and repeatable. CalEye’s recipe engine is calibrated for raw input weights. Cooked rice weighs approximately 2.5× more than raw rice due to water absorption; weighing cooked rice and applying a “raw rice” database entry would undercount calories by 60%. Always enter raw weights and select the raw food database entry; CalEye handles the cooked-yield conversion internally using stored yield factors derived from USDA cooking study data.¹

Set Total Yield to the number of servings you’re making. If the pot makes 4 adult servings, set yield = 4. The app calculates per-serving calories automatically. If yield varies (sometimes you make a larger batch for meal prep), set the yield to the actual number of servings this batch makes — the per-serving calorie calculation adjusts automatically.

Accuracy note: The largest source of error in home-cooked meal logging is oil measurement. A “drizzle” of oil can range from 5 mL (approximately 40 kcal) to 30 mL (approximately 250 kcal). Use a tablespoon measure for oil rather than estimating, and enter the exact measured amount. For recipes with tadka (tempering), measure the total oil before heating — oil does not evaporate in normal cooking, so the amount added equals the amount consumed.

Step 2: Determine Your Portion Using the Division Method

When you plate your meal, you have two choices for estimating your share of the recipe:

Option A: The serving-unit count. If you use a standard ladle and the pot holds roughly 8 ladles, taking 2 ladles = 25% of the recipe. Tap Serving size in the recipe log and set it to 0.25 (25%). This works well when you consistently use the same ladle size and have a reasonably accurate sense of how many portions the batch makes.

Option B: The plate-weight method. Weigh your empty plate. Plate your food. Weigh the plated plate. Subtract the empty plate weight. Enter the gram weight in CalEye’s serving size field (the app converts grams to a fraction of the recipe total based on the recipe’s total cooked yield weight).

Option B is more accurate, particularly for dense dishes like dhal, curries, and stews where ladle volume is variable. Option A is faster and accurate enough for most tracking goals where ±50 kcal precision is acceptable. The plate-weight method is worth using for at least the first 2–3 times you make a recipe, so you learn what your typical ladle portion weighs in grams — after that, the ladle count gives you a calibrated estimate.

The “biggest spoon” problem: Many families serve with a large serving spoon rather than a standard ladle. Serving spoon volumes vary significantly between households — from 50 mL to 200 mL. Before relying on serving-spoon counts, fill your serving spoon with water and pour it into a measuring cup once to establish its volume. For a curry, volume × density (approximately 0.9–1.0 g/mL for most dals and curries) gives you the gram weight per spoon. Log this calibration in CalEye’s recipe notes field for future reference.

Step 3: Log the Rice or Staple Separately

Rice, roti, and bread are logged most accurately as their own entries — not as part of the curry or dal recipe. They have consistent per-gram calorie counts and are easy to measure directly.

Rice: Weigh the dry grain before cooking. Standard yield conversions from USDA data: 1 cup (185 g) dry basmati rice yields approximately 500–520 g cooked rice (3.0–3.5 cups cooked), producing approximately 680–700 kcal total. A 150 g serving of cooked basmati rice contains approximately 195 kcal and 43 g carbohydrate. Log by weighing the cooked portion directly and entering it as “basmati rice, cooked” from the CalEye database — this is more accurate than calculating from dry weight if you’ve already cooked the batch.¹

Roti: Log by piece. One medium (20 cm diameter) whole-wheat roti made from approximately 30 g of dry atta and cooked dry = approximately 82–90 kcal. A roti made with 5 mL of oil during cooking adds approximately 40 kcal (use the “roti with ghee” database entry or add oil separately). If you’re making roti from scratch, weigh the dough balls before rolling — 30 g of raw dough per roti is a consistent reference.

Bread: Barcode scan (fastest) or select from database by brand. Most commercial sliced bread is 70–90 kcal per slice at the stated weight; always check the stated slice weight on the package and confirm you’re not eating larger slices than the label assumes.

Log staples as separate items in the same meal session. Tap Add item within the open meal log before confirming the meal. This keeps the meal log accurate at the component level, which is important for glycaemic load reporting — rice and dal have very different GI values and contribute differently to the meal’s overall GL figure.

Managing Multiple Family Members Eating Differently

If you’re tracking yourself but cooking for others who eat different portions, log only your own portion. Do not estimate others’ portions or log food that others consume. CalEye’s calorie data is per-user and should not include food consumed by other household members.

If a family member is also on CalEye and you share the same recipe, save the recipe as a Shared Recipe (tap the share icon after saving). The other user can access it from their account and log their own portion separately using their own serving size. The recipe’s ingredient list is shared; each person’s individual portion log is private and separate.

For households where two adults are tracking: The Shared Recipe feature eliminates double-entry. One person creates the recipe — typically whoever cooked the meal. Both people log their own portions independently. The recipe updates for both users when either edits it, which means if one person adjusts an ingredient (discovered the oil amount was different this week), the correction propagates to both users’ recipe library. This assumes both users want the same recipe version; if household members modify their cooking differently, saving as separate recipes prevents unwanted synchronization.

Children in the household: Children’s calorie needs are not currently supported in CalEye’s profile system, which is calibrated for adult macronutrient tracking. Do not log food consumed by children in your adult CalEye account — it will systematically inflate your intake data and corrupt your trend analysis.

Handling Last-Minute Changes to the Recipe

Recipes are living documents in home cooking. You ran out of coconut cream and used yoghurt instead. You added an extra tablespoon of oil. The onion quantity doubled because the recipe called for too little. These changes affect the calorie calculation.

Before logging your serving, tap Edit Recipe and update the changed ingredient. This takes 30 seconds and keeps the calorie estimate accurate for all future logs of that recipe. If you edit the recipe after already logging a serving from this batch, CalEye will ask whether to retroactively update today’s log with the corrected ingredient amounts — tap “Yes” to keep your daily total accurate.

If you made a one-off variation that you do not want to replace the original recipe, save it as a Variant with a date or description suffix: “Sunday Chicken Curry — extra cream 2026-06-15.” The original recipe stays intact for the regular preparation; the variant is logged for today’s meal and saved for future reference if you make the same variation again.

The batch-cooking case: If you cook a larger batch than usual (doubled for meal prep), update the Total Yield field before logging. Doubling the batch doubles the total calories in the pot; if yield remains set at the original 4-serving number, the per-serving calorie count will be double the correct value. Always set yield to match the batch size you actually made.

Why Photo Logging Alone Is Less Accurate for Family Cooking

CalEye’s photo recognition is most accurate for clearly separated, individually plated items with visible portion geometry. A shared pot of curry from which everyone takes different-sized servings is not well-suited to photo logging — the photo captures the pot’s appearance, not your serving. For home-cooked shared meals, the recipe method described in this guide will reliably outperform photo estimation by 15–25% in accuracy for total calorie count.

Use photo logging for family meals when:

• You’re eating your own clearly defined plated portion and the photo captures all components
• The meal is a restaurant or takeaway item where recipe logging is not practical
• You’re estimating a single component of a meal (the roti you took from the communal plate, photographed beside your hand)

Use the recipe method when:

• You cooked the meal and know every ingredient
• Multiple people ate from the same pot and your portion is a share of the whole
• You cook the same recipes repeatedly and want accurate data over time

The recipe method takes more setup time than a photo but produces data that is repeatable, auditable, and accurate enough to identify real patterns in your nutrition over weeks and months.

Family Cooking Tracking Workflow Summary

Step	Action	Time
First-time setup	Create recipe with all ingredients	4–5 min
Daily log	Select saved recipe, set portion size	15 sec
Staple side	Log rice/roti/bread as separate item	15 sec
Recipe changed	Edit recipe before logging	30 sec
Second family member	Access shared recipe, log own portion	15 sec

Total daily tracking time once recipes are saved: under 2 minutes per meal. That’s the payoff for doing the setup correctly the first time.

References

1. U.S. Department of Agriculture, Agricultural Research Service. USDA Table of Cooking Yields for Meat and Poultry. USDA, 2012. Also: FoodData Central cooked yield data for grains and legumes. https://fdc.nal.usda.gov/