How to track what you eat at a restaurant

You cook dal at home and log a katori. You order the same dal at a restaurant and log a katori. Then you wonder why the week did not add up.

The dish had the same name both times. It was not the same food.

Restaurant Indian cooking is a different craft with different economics, and the gap shows up almost entirely in the fat. Once you know roughly how big that gap is, eating out stops being a hole in your log.

Why restaurant food reads so differently

Restaurant food is engineered to taste unmissable on the first bite, and fat is how that is done.

A commercial kitchen has no reason to be restrained with oil. Fat carries flavour, gives gravies their sheen, keeps food glossy under a heat lamp, and makes a dish taste rich enough to justify the price. Nobody at the table sees how much went into the pan.

As a working assumption, a restaurant version of a home dish runs one and a half to two times what your kitchen produces. A home dal makhani simmered with a spoon of butter and a restaurant one finished with cream and a floating knob of butter are not in the same range at all.

What actually goes into a restaurant gravy

Most north Indian restaurant gravies are built from a small number of prepared bases, and this is where the calories live.

• Onion and tomato masala, cooked down in a lot of oil, often held in bulk and portioned out per order.
• Cashew paste, which is what gives korma, malai and shahi gravies their body. Cashews are around 550 to 600 calories per 100 g, and a rich gravy can hold a serious quantity.
• Cream and khoya, added at the end for texture.
• A butter finish, a spoon stirred in or dropped on top just before it leaves the kitchen.

None of that is visible when the bowl reaches you. A butter chicken looks like chicken in an orange sauce. The sauce is most of the meal.

This is also why the range on a restaurant dish is so wide. Two kitchens making the same named dish can differ by hundreds of calories a portion, and neither is doing anything unusual. Anyone quoting you one exact figure for restaurant butter chicken is quoting one kitchen’s recipe and calling it a fact.

The ordering decisions that move the number most

You do not need a rule for every dish. Four decisions carry almost all of the difference.

Tandoori and grilled over gravy. Tandoori chicken, seekh kebab, paneer tikka and fish tikka are marinated in curd and spice, then cooked dry in high heat. The same protein in a makhani or korma gravy arrives with the entire fat load of that gravy attached.

Dry over makhani, korma and malai. Kadai, bhuna, sukka and jeera preparations use far less cream and cashew than their creamy counterparts. Same kitchen, same protein, different order of magnitude on the sauce.

Watch the rice portion, not the rice. A restaurant serving of jeera rice or biryani is often two to three times a home serving. This is one of the easiest adjustments available: order one rice for the table rather than one each.

Count the breads honestly. A plain tandoori roti is a modest thing. A garlic naan or a laccha paratha brushed with butter is a different proposition, and four of them across a meal add up quietly. The roti calories guide has the comparison across the whole bread family.

None of this is a list of things to avoid. It is a list of levers, to pull on the days you feel like pulling them.

How to estimate a restaurant portion without making it weird

Nobody is taking a measuring cup to a restaurant. You do not need one.

Use the same household units you already log in, and estimate from what the bowl looks like:

• A restaurant serving of a main, the bowl one person gets, is usually two katori worth, around 300 to 350 g.
• A shared bowl in the middle of the table typically serves two to three people. Note how many ways it went.
• A plate of biryani is one plate, usually 300 to 450 g, and does not need splitting into components.
• Breads and starters are pieces. Count them.
• Drinks are glasses. A sweet lassi or two beers is not a rounding error.

Do the estimate at the table or on the way home, not at midnight. The memory of how many bowls came and how many ways they split is accurate for about an hour and vague by bedtime.

Chains publish their own numbers, and that beats guessing

Chain restaurants standardise. That is the whole business model: the same recipe, the same portion, in every outlet.

That standardisation is why many chains publish nutrition information for their menu, and why those figures are worth more than any estimate. They come from a fixed recipe with measured quantities, not from a chef adjusting the cream by eye. When a published figure exists for the exact item you ordered, use it and move on.

This is worth knowing when you plan. If you are going to eat out on a day you care about, a chain with published numbers gives you certainty that an independent kitchen genuinely cannot. Sehat carries chain items with the brand’s own published nutrition, marked as such, so you can see when a figure is measured rather than estimated.

For everything else, an estimate with a stated range is the honest option, and it is enough.

Weddings, buffets and shaadi season

A wedding dinner cannot be tracked dish by dish. Stop trying.

Count plates instead. Roughly how many plates did you go through, were the mains mostly gravy or mostly tandoori, how many pieces of dessert, how many drinks. Log it as one large estimated meal and let it sit in the week.

Two things help more than any arithmetic. Walking one full lap of the buffet before picking up a plate, so the choices are yours rather than the queue’s. And starting at the tandoori and salad counters, because those tend to sit at the far end and everyone arrives there full.

A shaadi season with fifteen functions is not a tracking problem to be solved. It is a stretch of weeks where your average runs higher, which is a fact to be recorded rather than a failure to be hidden.

Log the estimate, not nothing

Here is the mistake that costs people the most, and it looks like diligence.

You cannot find the exact dish. The portion is uncertain. So you skip the entry, and tell yourself you will be careful tomorrow.

A missing meal does more damage to a log than a rough one. A rough entry is wrong by maybe twenty percent. A skipped entry is wrong by a hundred percent, and it is always wrong in the same direction, on exactly the days that were biggest. Three skipped restaurant meals a month and your log now describes a person who does not exist.

So log something. Log restaurant butter chicken, two katori, and move on. This is the same principle behind most of the other quiet leaks collected in the piece on calorie tracking mistakes.

Eating out fits in a normal life

Nothing here is an argument for staying home.

Restaurants, weddings, office lunches and Sunday dinners with the family are not obstacles to a plan. They are the reason to have a plan that survives contact with a normal Indian calendar. A system that only works when you cook every meal yourself is not a system, it is a holiday from your own life.

Order what you want. Estimate it. Write it down. The weekly average is patient, and it absorbs a good dinner without complaint. Where all of this fits together is covered in the guide to counting calories in Indian food.