Restaurant meals can be harder to estimate because you may not know the recipe or portion weights. Start with available information and make the assumptions in your description clear.

So the honest approach is to use what is available, name what is missing, and stop treating the entry as a verdict.

Start with the information you actually have

Before you open the app, check what the restaurant has already told you. Many places publish nutrition information for their dishes, either on the menu, on their website, or through a published calculator. That is a document, and it is better than an estimate.

  • Published nutrition information for the dish you ordered: use it, and check that the portion it describes matches what you were served.
  • An ingredient list you can see on the table: oils, dressings and sauces are usually the missing pieces — note them separately.
  • Nothing published: describe the dish plainly and move on to step two.

One caution worth keeping: restaurant portions vary by kitchen and by the week. A published number for a dish is a description of that restaurant’s standard serve, not a measurement of the plate in front of you.

Identify the dish and the portion you ate

Name the dish as the kitchen would, and add the details that change the numbers: what was on it, what came with it, and what you actually ate rather than what arrived.

  1. Name the components, not the vibe“Chicken, rice, salad, dressing on the side” is workable. “Chicken salad” collapses three entries into one guess.
  2. Describe the portion honestly“Half the plate, which was bigger than a fist” is more useful than “large” and more honest than a number you did not measure.
  3. Note what you leftUnfinished food changes the totals. Recording half a portion instead of a full one helps the entry reflect what you ate.

Note the meaningful extras

Remember additions such as oil, butter, dressing, cream sauce, cheese and drinks. Their quantities can affect the estimate even when they are difficult to see in a photo.

A worked illustration: a mixed plate with a sauce

What I know
  • The dish was served with the sauce in a separate bowl. About a spoonful went onto the plate.
  • The rice portion was about a fistful, which is smaller than the restaurant’s standard side.
  • The vegetables were roasted, and no dressing was added at the table.
What I am estimating
  • Whether the estimate treats the sauce as part of the plate or as a separate line.
  • The cooking oil used on the vegetables.
What that means for the entry
The review step turns the two unknowns into two visible lines, so you can correct them or leave them. Either way, six months later you can see what you assumed — which is the difference between a log you trust and one you quietly doubt.

Review the estimate, then correct it

Open the entry, look at each line, and correct the parts you know: the portion that is off, the sauce that should be separate, the dressing that was not there. Then save. The corrected entry is what your day is built from.

  1. Compare each matched item against the plate you were served.
  2. Split anything combined that you know was separate — sauce, dressing, sides.
  3. Adjust the portion to what you ate, not what arrived.
  4. Save, and leave the remaining unknowns visible.

Treat the entry as information, not a moral grade

A restaurant meal logged honestly is a good entry. It is not a bad choice, and logging it is not an admission of anything. The point of the log is to see patterns across weeks — not to catch yourself doing something wrong.

Treat the entry as information about a meal. You do not need to compensate for eating out. When reviewing a longer period, distinguish complete records from days with missing or uncertain entries.

A lighter approach when tracking gets stressful

If logging has become part of the stress rather than a way out of it, use less of it. Choose a level of tracking that is useful to you, and remember that a partial log is not a complete picture of daily intake.

  • Log one meal a day instead of every meal — the main one, ideally at a consistent time.
  • If you choose to keep only a partial log, avoid treating its totals as your full daily intake.
  • A written description can be another way to record a meal when you do not have a measured portion.
  • Take a break. You can return when tracking feels useful again; missing days remain gaps in the record.

Ask when you are in doubt

Allergies, medical conditions and anything that genuinely affects your safety are questions for the restaurant and for a qualified professional — not for an app and not for a guide on the internet. This article is general education about logging. It is not medical advice and it cannot tell you whether a meal is safe for you.

Common questions

More about this topic.

Does Makro have a restaurant database?

This guide does not establish verified coverage of restaurant dishes. For a specific dish, the restaurant’s own published nutrition information is the better source, and you should check that its portion matches what you were served.

Can I use Makro if I have a food allergy?

Do not rely on it. The app cannot see ingredients, cross-contamination risk or what the kitchen actually did. Ask the restaurant directly, and speak to your clinician about anything that affects your safety.

Should I log a meal I could not even estimate accurately?

Yes, if logging it helps you see a pattern. Mark the unknowns, correct what you can, and treat the entry as a description rather than a measurement. A logged-and-corrected meal is more useful than a skipped one.

What if I eat out most days and my log looks useless?

Your record can still help you review what you entered. Restaurant estimates and missing details limit the conclusions you can draw, so check available nutrition information and keep your descriptions specific.

About this article. General education from the Makro team. Product information checked November 4, 2026. This article is not medical advice or an individual nutrition plan. Written by the team that builds Makro. No restaurant nutrition database was used to write this article.

Sources and further reading