Restaurants are where most tracking attempts quietly fall apart — not because the food is worse, but because there's no nutrition label on the table. Here's how to order, estimate, and log a restaurant meal without either guessing wildly or skipping the log entirely.
The order matters more than the tracking
The biggest lever you have at a restaurant isn't your logging accuracy — it's what you order before any of that starts. A grilled protein with a starch and a vegetable side is close to home-cooked in macro terms. A dish described as "loaded," "crispy," or "smothered" usually means it's carrying calories in the preparation, not just the ingredients.
Four menu words worth reading twice
You don't need the exact number — you need a defensible estimate
Perfection isn't available when someone else cooked the meal. What's available is a reasonable estimate, logged consistently, which beats a perfect number logged occasionally. A few habits that get you close:
- Log before you eat, not after. Committing to an estimate before the plate arrives keeps you from anchoring to how full you feel afterward, which has nothing to do with the actual calorie count.
- Round up on sauces and oil. Restaurant kitchens are far more generous with both than a home kitchen — when in doubt, assume more, not less.
- Use the closest match, not the exact dish. A dish that isn't in any database is still close enough to "grilled chicken, rice, vegetables" for tracking purposes.
This is exactly what a photo log is for
No menu database required — point the camera at the plate in front of you and PlateAI estimates from what's actually there.
One meal doesn't undo a week
The most common failure mode isn't a single big restaurant meal — it's the decision to stop logging entirely because that one meal felt "off plan." A dinner out that runs 400 calories over your target is a rounding error against a week; a week you stopped tracking because of it is not. Log it, move on, and let the next few days average it out.