How to Log Homemade and Restaurant Meals Without a Food Database

Three levels of estimate

Packaged food: use the label and the amount you ate. Home recipe you cook often: estimate the full pot once, divide into the servings you actually eat, and reuse that meal. Restaurant or someone else's cooking: describe the plate, review an AI draft, and live with more uncertainty.

That hierarchy saves work. Weighing every gram forever is not the goal. A one-time estimate for your usual oats, chicken rice bowl or dal makes later logging almost automatic.

• Count rotis, eggs, scoops and familiar bowls
• Name oil, butter, cream, dressings and fried cooking when they matter
• Log the major parts of a mixed plate instead of inventing one fake total

Restaurant meals are supposed to be approximate

You will not know the recipe. Hidden oil and serving size are the usual gaps. Say it was a restaurant, mention extras you can see, and do not treat the saved number as a lab result. The point is to keep the day visible so the rest of the week can adjust.

If every weekend is a restaurant and you skip logging those days, the trend lies. An honest range is better than a missing Saturday.

Reuse household meals

The second time you eat the same breakfast, copy yesterday. Change only what changed. That is how a log stays cheap enough to survive a busy week. CutCompanion is built for that loop: one line or a photo, a draft you edit, a save, then the weekly trend.

Indian mixed plates follow the same rules, with extra attention to ghee, bowl size and recipe variation. That walkthrough lives in the Indian meals guide. The method is the same for pasta, burritos and leftover stir-fry.