How to start counting calories: your first week, step by step

Here's what to actually do, day by day.

Before day 1: get a rough target, then forget about it for a week

Most calorie apps (Bocco included) will estimate a daily target from your age, sex, height, weight, and activity level in under a minute, using a standard formula like Mifflin-St Jeor. Get that number and move on — don't refine it, don't research it further. It's a placeholder you'll adjust in two or three weeks based on what actually happens, not a number to get exactly right on day one.

Day 1: log today exactly as you'd normally eat it

This is the step people get wrong first: they start a diet and a tracking habit on the same day. Don't. Day one is a baseline — eat what you'd normally eat, and just write it down. If you change your eating before you know your starting point, you'll never know what "normal" actually cost you, and the number you adjust from later will be fiction.

You don't need an app open at every meal. Log it after, from memory, even roughly. The goal isn't accuracy yet — it's seeing your actual pattern for the first time.

Days 2–3: pick a logging method you'll still be using on day 10

This is the decision that determines whether the whole thing survives past a week. You have a few options, roughly in order of effort:

• Read the label on anything packaged — no estimating needed.
• Estimate by hand — a palm of protein, a fist of vegetables, a cupped hand of carbs. We cover this in more detail in a full guide to estimating without a scale.
• Photograph the meal and let AI estimate it — the fastest option for home-cooked or restaurant food, since there's nothing to look up or type. Here's how that works.
• Weigh it, if you want a calibration check for a day or two — not a requirement, and usually the first thing people abandon.

Pick whichever one survives a rushed Tuesday lunch. The method you'll actually keep using beats the one that's technically more precise.

Days 4–5: catch the calories that hide

By day four you've probably noticed the food is easy. The stuff that quietly inflates the total is almost never the meal itself — it's the extras nobody thinks to log:

• Cooking oil and butter — a tablespoon of olive oil is roughly 120 calories, and most home cooking uses more than one.
• Drinks — juice, soda, a latte, a glass of wine. None of it registers as "food," so it's the easiest category to log-blind.
• The bites off someone else's plate, the handful of chips on the way past the bowl, the taste while cooking. Small individually, real by the end of the day.

You don't need to eliminate any of this. Just start logging it — that's the whole point of days four and five.

Days 6–7: look at the week, not any single day

Don't judge the plan from Tuesday. Weigh yourself once, look at the whole week of logs, and ask one question: did anything surprise you? Most first-week surprises are one of the categories above — oil, drinks, or a meal you underestimated the size of.

This is also the moment to decide if your logging method survived. If you weighed food on day one and gave up by day four, that's useful information — it means the method, not you, was the problem. Switch to something lighter-weight for week two.

First-week mistakes that quietly end the habit

• Changing your diet and your logging habit at the same time. Pick one. Log first, adjust eating once you have a real baseline.
• Chasing precision on day one. Nobody logs perfectly in the first week — a rough, honest log beats a precise one you gave up on by Wednesday.
• Treating one missed meal as a reason to quit the whole log. It isn't. Log the next one.
• Choosing the most accurate method instead of the one you'll keep doing. A 2011 systematic review of self-monitoring and weight loss found that how consistently people tracked mattered more for results than which specific method they used — the frequency of logging was the strongest predictor across the studies reviewed, not the precision of any single entry.

In our experience building Bocco, this is the mistake that kills more first weeks than anything about the food itself: people spend day one perfecting their target number and day two arguing with a database search bar, and by day three there's nothing left logged at all.

What happens in week two

Once you've got seven honest days behind you, week two is where you actually use the data: compare your logged average to your target, and nudge your eating — not your logging — if you want the number to move. That's the full method, laid out in detail in our beginner's guide to counting calories. Week one's only job was getting you real numbers to react to.