The standard advice for tracking your food is a purity test. Buy a scale. Weigh the chicken raw. Log the cooking oil. Don't estimate — estimating is how people fail. Underneath it sits an assumption that sounds obviously true: the more accurate your log, the better your results.
The research does not support that assumption. It supports a much less flattering one, which is that accuracy is not the variable doing the work. Frequency is. And the accuracy obsession is one of the main things destroying frequency.
The finding nobody quotes
In 2019, researchers led by Gabrielle Turner-McGrievy at the University of South Carolina went looking for a definition of "adherence" that actually predicted outcomes. They pooled participants from two six-month randomized weight-loss trials — people using calorie-tracking apps, a photo-based meal app, and a wearable bite counter — and tested every plausible measure of tracking behavior against weight change at six months.
The winner, published in the Journal of the Academy of Nutrition and Dietetics, was almost embarrassingly crude: the number of days on which the participant logged at least two eating occasions. Across all completers (N=91), that one variable explained more of the variance in six-month weight loss than any other adherence definition tested — R²=0.27, P<0.001.
Read that again with the emphasis in the right place. Not calories logged. Not accuracy against a food scale. Not whether the entries were complete. Two eating occasions, on a day, counted as a day. Log breakfast and lunch, eat an unlogged dinner at your sister's, and by the measure that best tracked real-world results, you had a good day.
There's a dose-response curve, and its bottom end is ugly
A 2024 analysis went further and asked how many days per week you actually need. It found a graded relationship in the direction you'd expect — and one result that should genuinely change how you think about part-time tracking:
- At a threshold of 1–2 days per week, participants showed significant weight gain.
- At 3–4 days per week, weight was roughly stable — no meaningful change.
- At 5 or more days per week, participants lost weight, with the largest benefits at the 5–6 day thresholds.
- For long-term maintenance, ≥3 days per week was enough to correlate with less regain.
The bottom of that curve is the interesting part. Tracking a couple of days a week isn't a diluted version of tracking every day — it lands in the same territory as not tracking at all. That is almost certainly not because two days of logging causes weight gain. It's because "two days a week" is what the collapse of a tracking habit looks like from the outside: the Monday-and-Tuesday pattern of somebody who restarts each week and quits by Wednesday.
Why perfectionism is the thing eating your streak
Now look at what adherence actually looks like in the wild. A 2021 systematic review in Obesity examined digital self-monitoring across weight-loss interventions — studies where people were explicitly instructed to log daily, often with paid research staff checking in. Among interventions asking for daily dietary self-monitoring, only 58% reached logging on even half the days. Just 11% reached three-quarters of days.
Eighty-nine percent of supervised, motivated, enrolled participants could not hit the frequency the evidence says matters. The binding constraint isn't knowledge, motivation, or database quality. It's friction, accumulated one entry at a time.
And every accuracy rule you add is friction. Weighing raw adds a step. Finding the correct database entry among fourteen near-identical listings for "chicken breast" adds a step. Logging a restaurant meal you can't decompose adds a decision you're likely to resolve by not logging it. Each rule is defensible on its own; together they raise the cost of an entry to the point where skipping is the rational choice on a busy day — and then the skipped day becomes two, and you're at the bottom of that curve. We've written before about the specific way tracking habits die, and it is essentially always this: not a decision to quit, just a gap that never closed.
But doesn't accuracy matter at all?
It matters, and it's worth being precise about how. Estimation error is real: people routinely underreport by 20–30%, restaurant portions run over their published figures, and photo-based estimates drift badly on mixed dishes. In the same 2019 pilot work, the group using a calorie-tracking app lost significant weight while the group using a photo-only meal app did not — so some quantification beats none.
But here's the thing about a consistent error: it mostly cancels. If you underestimate by 15% every day, your log is wrong in absolute terms and still perfectly useful as a relative signal — Tuesday versus Thursday, this week versus last, the week you ate out four times versus the week you didn't. You adjust based on the trend and what the scale does, not on the absolute number. Consistency, not correctness, is what makes the number actionable. An imperfect log you keep beats a perfect log you abandon by a margin that isn't close.
Sustained monitoring matters more than exhaustive monitoring. The habit is the intervention; the numbers are just how it's expressed.
Four seconds is a low enough bar to clear every day
If frequency is the variable that matters, the only design question worth asking is how cheap you can make a single entry. VoiceLog's answer: say it out loud. "Two eggs, toast and butter, black coffee" — spoken, transcribed on-device, filed with calories and macros before you've put the phone down. No database search, no portion dropdown, no six-tap ritual. It's fast enough to do while walking to the car, which is exactly the day you'd otherwise have skipped.
Get VoiceLogA protocol built around frequency
If you're going to optimize for the variable that the data actually rewards, the rules change:
- Two eating occasions is a complete day. Not a partial day, not a failure. If breakfast and lunch are logged, close the app and go about your life.
- Estimate out loud, immediately. "Big bowl of pasta, maybe a chicken breast's worth of meat." A rough entry made in ten seconds beats an exact entry made never.
- Never leave a day blank because you can't be exact. The restaurant meal you can't decompose is the single most common cause of a broken streak. Log your best guess — and if you want to guess well, there's a method for that.
- Aim for five days, not seven. Building in two forgiving days keeps a missed Saturday from reading as failure, which is what turns one gap into six.
- Judge yourself on days-logged, not on accuracy. Count check marks on a calendar. It's the metric with the R² behind it.
None of this is permission to be careless about food. It's permission to be careless about bookkeeping, on the specific grounds that bookkeeping perfectionism has a measurable body count in the adherence literature. The person who logs roughly, six days a week, for a year will end up further along than the person who weighed everything to the gram for eleven days in January.
The one number to watch
At the end of a month, don't grade your average daily calories — you don't know it as precisely as your app implies, and neither does anyone else. Count the days with at least two entries. If it's twenty or more, the behavior that predicts the outcome is in place, and the rest is just time. If it's eight, no amount of food-scale rigor is going to rescue that month, and the fix isn't to try harder next time. It's to make each entry cheap enough that trying isn't required.
Log by talking. Keep the streak that actually predicts results.
VoiceLog turns one spoken sentence into a filed meal with calories and macros — and does the same for workouts, expenses, and anything else you'd otherwise forget. Transcription runs on your iPhone, so your food diary isn't sitting in someone else's database, and you can point Claude or ChatGPT at your own logs through MCP when you want to ask what actually changed. Free to start, and fast enough to survive a bad week.
Get VoiceLogFrequently asked questions
How many days a week should I track calories to lose weight?
The evidence points to five or more days per week for weight loss, with the largest benefits seen at 5–6 day thresholds. Around 3–4 days per week is associated with weight stability rather than loss, and — counterintuitively — thresholds of only 1–2 days per week have been associated with weight gain, most likely because that pattern reflects a tracking habit that has already collapsed. For maintaining a loss you've already achieved, 3 or more days per week correlates with less regain.
Do I have to log everything I eat for tracking to work?
No. In a 2019 analysis pooling two randomized trials, the adherence measure that best predicted six-month weight loss was simply the number of days on which participants logged at least two eating occasions (R²=0.27, N=91) — not calorie accuracy or completeness. Logging two meals a day, most days, is the behavior the outcome data rewards. Treat a two-meal day as a success rather than a failed seven.
Does it matter if my calorie estimates are wrong?
Less than you'd think, as long as you're wrong consistently. A systematic bias mostly cancels out when you're comparing days and weeks to each other, and that relative signal is what you actually act on alongside the scale. Quantifying something does beat quantifying nothing — in one pilot trial, calorie-app users lost significant weight while photo-only meal loggers didn't — but chasing gram-level precision usually costs more in missed days than it buys in accuracy.
Why do I keep quitting calorie tracking after a few weeks?
Because each entry costs too much. Even in supervised research settings, only about 58% of interventions asking for daily food logging saw participants log on half the days, and just 11% reached three-quarters of days. Habits don't end with a decision to stop; they end with one skipped day that becomes three. The durable fix is reducing the per-entry cost — voice entry, rough estimates, no database search — rather than trying to want it more.
Is it better to track loosely every day or precisely a few days a week?
Loosely, every day — or at least most days. The dose-response data consistently favors frequency: five-plus days of rough logging sits in the weight-loss range, while one or two days of meticulous logging sits in the range associated with weight gain. Precision has no mechanism for helping on days you didn't log at all.
