How to log meals you didn't cook

Most calorie advice assumes you're cooking. Weigh the chicken. Measure the oil. Hit "save" on the recipe. That works at home. It falls apart the moment you sit down in a restaurant, open a takeout bag, or fill a plate at someone else's table.

This is the situation where most people quit tracking. The food is opaque, the ingredients are guesses, and the math feels impossible. So the whole day gets a shrug and a "I'll start again tomorrow."

You don't have to. Here's how to log meals you didn't cook without pretending you can do it precisely.

Start with the plate, not the recipe

When you can't see the recipe, see the plate. Estimate by what's actually in front of you:

• Protein: how big is the portion compared to your palm? One palm ≈ 100 g cooked.
• Carbs: how many fistfuls? One closed fist ≈ 150 g cooked rice, pasta, or potatoes.
• Fats: how much added oil, butter, or cheese can you see? A thumb tip ≈ 5 g.
• Vegetables: barely matter for calories. Don't over-account.

You don't need to be right. You need to be in the right neighborhood. A 600 kcal estimate that's off by 100 is still vastly better than a 0 kcal estimate because you "didn't have the data."

The hidden fat rule

Restaurants cook with two to four times the oil you'd use at home. That's most of the calorie surprise. If the dish glistens, add 100–150 kcal mentally before you start estimating.

This isn't paranoia — it's how kitchens get food to taste good fast. Once you internalize this, your estimates for restaurant food jump in accuracy overnight.

The goal isn't precise numbers. The goal is a tracking habit that survives a Friday night.

Use a tool that accepts vague input

The whole point of describing food in plain language — "two slices of veggie pizza and a beer" — is that a decent estimator can resolve it. You don't need to break it into ingredients yourself.

If you're using Excaloricate or anything similar, type what you ate the way you'd describe it to a friend. The estimate will land in the right range. If the dish is unusual (regional specialty, mystery sauce), add the one detail that matters most — "fried" vs "grilled", or "cream-based" vs "tomato-based".

What to log when you genuinely don't know

Sometimes you just don't know. The party had four kinds of dip and you grazed for two hours. The rule:

1. Log something, even if it's wrong. A 700 kcal placeholder beats a blank.
2. Round up, not down. When you're guessing, your brain underestimates by roughly 20%. Bias toward overestimation and you'll be approximately right.
3. Don't double-count the day. One sketchy meal doesn't ruin a week. Log it. Move on.

The week is what matters

Look at your seven-day average, not yesterday. A single 1,000 kcal estimate that's off by 300 either way disappears into the week's noise. What kills progress isn't a bad estimate — it's three days of zero logging because the estimating felt too hard.

Imperfect tracking, sustained, beats perfect tracking, abandoned.