Counting calories sounds tedious, and done badly it is. But the version that actually works is simpler than most people expect: a kitchen scale, a logging app, and about ten focused days to learn what your food really costs. Get those three things right and you'll never have to guess about your nutrition again. Here's the whole process, start to finish.
What a calorie count is really measuring
A calorie is a unit of energy. Your body burns a roughly predictable amount each day to keep you alive and moving, and your food supplies energy back. Eat less than you burn and you lose weight; eat more and you gain. That's it. Counting calories is just making the invisible side of that equation visible.
The catch is that humans are terrible at estimating food by eye. Studies of self-reported intake routinely find people underestimate what they eat by 20 to 40 percent, and the error grows with bigger portions. You are not exempt, and neither am I. The scale fixes this, which is why it does most of the work here.
Step 1: Find your starting calorie target
You need a number to aim at. Start by estimating your Total Daily Energy Expenditure (TDEE) — the calories you burn in a day. A reasonable shortcut for most people is body weight in pounds multiplied by 14 to 16: use 14 if you sit most of the day, 16 if you're on your feet or training hard. A 170 lb moderately active person lands around 170 × 15 = 2,550 calories to maintain weight.
Then adjust for your goal:
- Fat loss: subtract 15 to 20 percent. For that 2,550 example, a target of about 2,100 calories gives a steady loss of roughly 0.5 to 0.75 lb per week.
- Maintenance: eat at your TDEE.
- Muscle gain: add 10 to 15 percent, so around 2,800, paired with progressive resistance training.
Treat this number as a hypothesis, not a law. It's a starting point you'll correct with real-world data in Step 5.
Step 2: Get the right tools
Two things, and only two are non-negotiable:
- A digital kitchen scale that reads in grams. A $15 model is fine. Grams matter because they're far more precise than cups or "one medium banana," which can vary by 50 percent.
- A food-logging app with a barcode scanner. The FitBot Coach app stores your target, scans packaged foods, and tallies your day automatically so you're not doing arithmetic at every meal.
Measuring spoons help for oils and nut butters, where a small volume hides a lot of calories. One tablespoon of olive oil is about 120 calories; a careless "drizzle" can easily be three of those.
Step 3: Weigh and log, the right way
This is where accuracy is won or lost. The habit to build is weighing raw and weighing on a tared scale.
- Put your empty plate or bowl on the scale and press tare (zero) so the container's weight drops out.
- Add one food, read the grams, and log it. Press tare again, add the next food, log it. One zero-out per ingredient means no mental math and no spillover error.
- Weigh foods in their logged state. Most database entries for meat, rice, and pasta are for the raw weight, because cooking changes water content. 100 g of raw chicken breast becomes about 75 g cooked but still holds the same ~165 calories. Pick one convention and match the database entry to it.
When you choose an entry in the app, favour ones with a verified or official tag over user-submitted guesses, which are frequently wrong. For a packaged item, scan the barcode and trust the label.
Step 4: Handle the messy real-world cases
Perfect weighing breaks down at restaurants and family dinners. Don't let that derail you — get close instead.
- Restaurant meals: log the closest chain entry, or build the plate from its parts (8 oz steak, a cup of mashed potato, a tablespoon of butter). Assume restaurants use more oil and butter than you would and round up.
- Mixed dishes you cooked: weigh every ingredient as it goes into the pot, log the whole recipe, then weigh your individual serving as a fraction of the total cooked weight. Our recipe library lists per-serving calories so you can skip this for those meals entirely.
- Drinks and "zero" extras: count alcohol (a beer is ~150 calories), juice, cream in coffee, and cooking oil. These are the silent budget-killers.
A useful rule: it is better to log something imperfectly than to skip it. An honest estimate beats a blank.
Step 5: Adjust using two weeks of data
Your calculated target was a guess. Your body delivers the real answer. Weigh yourself in the morning, after using the bathroom, before eating, three to four times a week. Daily weight swings 1 to 2 kg from water and food in transit, so ignore single readings and watch the weekly average.
After 14 days, compare:
| What the scale did | What it means | Your move |
|---|---|---|
| Weight trending down ~0.5–0.75 lb/wk (cutting) | Target is correct | Hold steady |
| No change after two weeks | Target is too high (or logging is leaky) | Cut ~150–200 cal/day |
| Losing faster than ~1% of body weight/wk | Too aggressive; muscle and energy at risk | Add ~150 cal/day |
Make one change, then give it another two weeks. Chasing the scale day to day leads to constant over-correction.
You don't have to count forever
Counting is a skill, not a sentence. After a few weeks of weighing, most people can eyeball a chicken breast or a cup of rice within ten percent — that calibration is the real prize. Many use it in cycles: log tightly for four to six weeks when chasing a goal, then coast on the habits they built and only return to logging if progress stalls or drifts.
Pair the count with training that earns those calories. Browse the exercise library to build a routine, and if pre-session fuel is on your mind, see what to eat before a workout. As for the popular worry that eating late ruins everything — the total still rules; whether meal timing actually matters is a smaller lever than the number you've just learned to track.
The five-minute version
- Estimate your target: body weight (lb) × 14–16, then cut 15–20% for fat loss.
- Buy a gram scale and open a logging app.
- Tare, weigh one food at a time, and match raw-or-cooked to the database entry.
- Estimate honestly when you eat out; never skip oils, drinks, or sauces.
- Track your weekly weight average and adjust by ~150 calories every two weeks.
Do this for a fortnight and the guesswork is gone for good. The scale taught you what your food costs — now you get to spend on purpose.
Key takeaways
- Set a starting target with bodyweight (lb) x 14-16, then cut 15-20% for fat loss
- A gram scale plus a logging app does 90% of the work; eyeballing portions doesn't
- Tare the scale and weigh one food at a time, matching raw-or-cooked to the database entry
- Never skip oils, drinks, and sauces; one tablespoon of olive oil is ~120 calories
- Track your weekly weight average and adjust by ~150 calories every two weeks, not daily
Frequently asked questions
Do I need to weigh my food, or can I just use measuring cups?
A gram scale is far more accurate than cups, especially for calorie-dense foods like oils, nut butters, rice, and pasta. Volume measures can be off by 30 to 50 percent. If you only buy one tool, make it a digital kitchen scale that reads in grams.
Should I weigh food raw or cooked?
Either works, but you must match the database entry to how you weighed it. Most entries for meat, rice, and pasta are for raw weight, since cooking changes water content. 100 g of raw chicken becomes about 75 g cooked but holds the same calories, so pick one convention and stay consistent.
How long do I have to count calories?
Counting is a temporary skill, not a life sentence. After four to six weeks of weighing, most people can estimate portions within ten percent by eye. Many log tightly when chasing a goal, then coast on the habits they built and only return to tracking if progress stalls.