You might've started tracking your calories with the best intentions. You weighed your food, logged every snack, maybe even the creamer in your coffee. Then one day you eat out, or somebody else cooks, or you just can't remember what you had for lunch, and you can't log it the way you want to. So you don't log it at all. And the next day doesn't seem as important either. Some call it laziness. I call it a dangerous form of perfectionism.
If that sounds familiar, you're not alone. In one study of a free food journaling app, only about 2.6% of the 189,770 people who downloaded and used it at least once kept using it actively. That app was photo-based too, so logging was supposed to be the easy part.
When I first started tracking, I weighed almost everything I ate. I lasted a few months like that. What ended it was a Hershey pie I couldn't find in my app's database, so I scrapped the entire day (I wrote more about that here). There were close enough equivalents I could've estimated from. I just didn't want an estimate.
That all-or-nothing thinking is a big part of why people stop, and there's actual research on it, which I'll get into. This post covers why people quit, what the research says about staying consistent, and the rules I follow now to keep logging even when I can't measure everything.
Why do people quit calorie tracking?
A 2015 study surveyed 141 people who were either tracking their food or had stopped, and analyzed 5,526 posts from food journaling community forums. Respondents described journaling as "too much effort," "time-consuming," and "tedious." I'd agree, especially the first month when you don't know any of your portions yet.
The reasons I hear most often, and the ones I've run into myself:
- Effort: Searching the database for every ingredient, then picking which of the fifteen "chicken breast" entries is the right one. Perfectionism really shows in a lot of people here.
- Meals you can't measure: Restaurants, a friend's cooking, a work potluck. Most of where I eat out is local taco trucks and restaurants with no nutrition information at all, so this one hit me constantly until I changed how I log those meals (which I go over here).
- Perfectionism: Covered above. One meal you can't log accurately and the whole day "doesn't count."
- The scale not moving yet: Water weight swings a lot in the first few weeks, so it can look like nothing is happening.
- Problems with the app: The same study found inaccurate database numbers, missing foods, and duplicate entries for the same food. Some people were also discouraged when friends on the app stopped journaling, or were losing more than they were. Comparison is the thief of motivation for this one.
Most of these can be worked around. The database gets easier once you've saved the foods you eat every week, and you learn to wait out the scale. Perfectionism is what got me, so that's what most of this post focuses on.
Is it better to estimate or skip a day?
Estimate. Almost every time.
A skipped day isn't neutral. The days people tend to skip are the ones they'd rather not see (a birthday party, or the night you ordered takeout and finished all of it). So when you skip them, your weekly average looks lower than it actually is, and you end up wondering why the scale isn't moving.
Say you eat 2,000 calories six days of the week and 3,000 on the seventh. Your real average is about 2,143 calories per day. If you skip the 3,000 day, your log says 2,000, which is 143 calories per day too low. If you estimate that day instead and you're 25% under (2,250), your log says about 2,036, so you're only 107 low. And 25% under is a bad estimate. When I go back and check my own estimates, I'm usually within a hundred calories or so. But even a bad estimate gets you closer for the week:
The bigger cost of skipping is the habit, though, not the numbers. Now if I can't weigh something, I estimate it, and if I can't remember a whole day, I estimate the whole day. I keep my streak going in the app either way.
Does logging often matter more than logging perfectly?
There's research supporting that it does. In a 2019 study of 142 people in a 24-week online weight loss program, the amount of time people spent logging didn't differ between those who lost more weight and those who lost less. How often they logged did. People who lost at least 5% of their body weight logged in about 2.4 times per day on average, compared to about 1.6 for those who lost less. Time spent logging also dropped from about 23 minutes a day in the first month to about 15 by the sixth.
Note, this is a correlation, and most of the participants were women with obesity, so it doesn't prove that logging more often caused the weight loss. But it lines up with what I've seen myself.
So a quick log you'll actually keep doing is likely worth more than a detailed one you'll stop in two weeks. That's the main reason I log with photos and voice, and use "Estimate" mode when a restaurant posts its nutrition information. I go over how accurate AI logging actually is in another post.
That being said, faster logging doesn't fix everything. The app from the first study was photo-based, and most people still stopped. If you're going to quit over a meal you can't measure, a faster app won't stop you from doing it. Mindset matters too.
What happens if you miss a day?
Not much, as long as it's one day.
In a popular 2010 study on habit formation, 96 people picked a new daily habit (like eating a piece of fruit with lunch or going for a run) and reported how automatic it felt. The median time for it to feel automatic was 66 days, with a huge range between people, from 18 to 254 days (anything past the 84 days they were actually followed was estimated). So the "21 days to form a habit" idea doesn't really hold up. More importantly, missing a single opportunity didn't materially affect forming the habit. Being very inconsistent did.
There's also research on the all-or-nothing mindset itself. A 2015 survey of 241 adults found that thinking about food in black and white terms (foods are "good" or "bad," a day is either on track or ruined) helped explain the link between restrictive dieting and regaining weight.
So the rule I'd go by is to never miss twice. If you miss a day, the next one matters a lot more than the one you missed. It's common for me to have long streaks only to miss a day then go back. I used to always let it drift, which didn't help with my goals at all.
How to stay consistent with calorie tracking
- Log before you eat when you can: You won't have to remember it later, and you can figure out how the food you're going to eat will shift your calorie or nutrient count so you can adjust portions or ingredients ahead of time.
- Estimate instead of skipping
- Keep a minimum log for busy days: On my busiest days, I tend to use my app's describe food feature to explain most or even sometimes my entire day of eating into one log. Even just the main meals and anything calorie dense is better for data than nothing, as long as it's not grossly wrong.
- Save the meals you eat a lot: My usual taco truck order (4 chicken or al pastor tacos on double corn tortillas) is a custom entry now. It took one time to set up. I also have eggs nearly every single day. I have that one on repeat.
- Weigh the dense foods, eyeball the rest: Oils, butters, nut butters. Not the lettuce. (More on that here.)
- Never miss twice or at least get back to the habit as soon as possible. The sooner you start, the stronger your habit will have retained.
- Judge your results over weeks, not days: A single weigh-in tells you very little. If you want to see what a few weeks of your log is actually saying, this post walks through finding your real maintenance calories from your own data.
TLDR
Overall, a lot of people who quit tracking quit over a day they couldn't log perfectly. Research suggests how often you log matters more than how detailed it is, and one missed day doesn't break a habit (missing a lot of them does). So estimate when you can't measure, keep a minimum log for busy days, and try not to miss twice.
I still estimate more of my food than I'd like to admit, and I'm still on track.