Why do food journals stop after a few weeks?
Not for lack of numbers. They stop because writing them down is a chore repeated at every meal, for months: weigh, search a database, pick among ten entries for one food, fix the portion, repeat.
The research is plain. In a 2019 trial by Harvey, Krukowski, Priest and West, published in Obesity, which timed it from the app's own logs, dietary recording took about 23 minutes a day in the first month, falling to about 15 by month six. In two six-month trials, fewer than half the participants were still recording after ten weeks, whichever definition of adherence was used. Journalers surveyed by Felicia Cordeiro and James Fogarty of the University of Washington for their 2015 study, "Barriers and Negative Nudges", called it "too much effort", "time-consuming", "tedious", and named the crowd-sourced database as a barrier of its own: "multiple postings with all different information", "too many choices".
"It's a database. By the day. By the meal. So people can see all they ate today in one view. Everything else is unnecessary clutter." A MyFitnessPal user leaving, r/Myfitnesspal, 2026. From the clinic side, Angela Finn, MS, RD, clinical program manager at Baylor Scott & White Quality Alliance, put the reason to keep one in a sentence in August 2026: "the simple act of writing down what you eat encourages people to consume fewer calories." The act, not the app.
The same trial found something that decides how a journal should be built: what went with its outcome was how often people recorded, not how long they spent, which is what Harvey and her co-authors put in their title. Frequency, not effort. So the design question is not how to make the form faster. It is how to remove it.
What does a food journal you say, not type, look like?
IZeat is the calorie tracker inside ChatGPT, Claude or any other assistant. Tell the assistant you already use what you ate instead of searching for foods and entering them one by one. In practice it is a conversation you are already having: you open the assistant you use for everything else, tell it what you ate, and it writes the entry into IZeat and reads it back.
- Say the meal, with weights when you have them. "Lunch: 180 g of grilled chicken, no oil, 150 g of cooked rice, a 125 g plain yoghurt."
- Answer a question only if one is needed. The assistant asks about the portion or the cooking fat when your words leave them open, in one message, and nothing else.
- Read the receipt. Three rows with their grams, calories, macros and source; the meal total; what is left for the day against the target you chose.
- Correct by sentence. "The rice was 200 g, not 150." The row changes, the receipt shows the difference, the previous state stays in the meal's history.
Photos work the same way. A photo of a nutrition label is read and the values are said back, with the units, so a misread can be caught in the same breath. A photo of a plate names the dish and then gets the portion and fat questions, because a picture cannot show either.
| The journal you type | The journal you say |
|---|---|
| Open the app, find the meal, tap add | Say "lunch:" and the items |
| Search the database, ten entries for one food, pick one | No search box: a plain food is valued from a reference table, a label is read, the rest is an estimate marked as one |
| Type the grams into a field, fix the unit | Say the grams; "a tablespoon" is converted and the conversion is said back |
| Repeat six times, then check the total | One sentence, one receipt with the total and what is left |
| Fix a mistake by finding the entry again | "The rice was 200 g" |
Bottom line: the spoken journal costs one sentence per meal and gives back a receipt; the typed one costs the taps that the research says people stop paying.
What makes a spoken entry as honest as a weighed one?
The source on each item. A journal is only worth keeping if its totals can be trusted, and the trackers people leave lost that trust to a database where "the same food, ten results, ten calorie counts" (reviews of MyFitnessPal, read 4 September 2026).
A label you read is recorded as a label, with its values said back to you and their units explained. A plain food you weighed is valued from a standard composition table and recorded as a reference value, scaled to your grams. A figure you give is recorded as yours. Anything else is an estimate, marked as one and shown beside the weighed items as what it is.
The assistant is asked to ask, in one message, about the missing details that would materially change the estimate: the portion of a dish nobody weighed, and the fat it was cooked in, since 10 g of oil is about 88 kcal (USDA FoodData Central, checked 15 September 2026) and never shows on the plate. What it still has to assume, it states in its reply. That is the difference between an estimate and a guess: the estimate says what it is.
How can you make the next entry easier to keep?
By making each entry cheap enough to happen when the meal happens, and by never turning a gap into a failure. The aim is a journal you are still keeping when the goal you count for is still ahead of you.
A snack at 16:00: "two squares of dark chocolate, 20 g, the same bar as last week", said in the chat that is already open. The assistant asks IZeat for that earlier entry, takes the label values from it, and records today's 20 g; the receipt shows the row, the day so far and what is left. On Friday you realise Thursday's dinner was never said; you say it on Friday, with the day, and IZeat lands it on Thursday, in your time zone, and sums that day again. Saturday's breakfast is "like yesterday, without the egg": the assistant reads yesterday's from IZeat and records today's with the change.
- You record when the meal happens, where you already are. One sentence in the conversation, not a trip through an app.
- You ask for dinner from what is left. When you ask what to make, the assistant reads the day from IZeat and proposes from the remainder and what you have; nothing is recorded until you say what you ate.
- You catch up late, and nothing is held against you. A day recorded late lands on the day it was eaten; a day with no record is shown as one, the period's average is taken over recorded days only, and nothing is scored.
- You see the whole day without a tap. Every meal with its numbers, the total, the target and what is left, on one screen of the web app.
There is nothing to protect and nothing to lose, on purpose. Cordeiro and Fogarty titled their 2015 study "Barriers and Negative Nudges" for a reason, and Solbrig and colleagues wrote in *Internet Interventions* in 2017 that continual self-monitoring "sapped rather than strengthened" their participants' motivation; IZeat records without commenting. Over and under the target are written the same way.
What do you need to start?
An IZeat account and an assistant that can connect to it: Claude, ChatGPT, Claude Code, or any other that accepts an outside server. Connecting is one address and one sign-in; nothing is installed. The first conversation sets your time zone and, if you want one, a calorie target, and the journal starts with the next meal you say.
A trial without a card, then a plan you can leave in one click. Your journal is yours: exportable whole as CSV or JSON, and deletable from the account page.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
How do you keep a food journal?
Write down what you ate, with quantities, as close to the meal as you can, and keep the day's total in view; the 2019 trial behind our sources found that recording often mattered more than recording long. With IZeat you say the meal to the assistant you already use instead of writing it: it records the items with their grams and their sources and replies with the meal total and what is left for the day.
What is the easiest way to keep a food diary?
Saying it. A sentence like "lunch: 180 g of chicken, 150 g of rice, a 125 g yoghurt" is a complete entry in IZeat, with no form, no search box and no entry to pick among ten. The assistant asks only about a portion or a cooking fat you left open, in one message, and records an estimate as an estimate. The receipt shows the three rows, their sources and the total.
Is there a food diary app without data entry?
IZeat has no data entry screen at all. You tell the AI assistant you already use, ChatGPT, Claude or any other, what you ate; it is logged through IZeat, and each item says where its numbers came from. The web app is read-only: the day on one screen, the week, the history, and the account, where you export or delete your data. Nothing on the web asks you to type a meal.
How long does it take to log a meal?
We have not timed it, and we publish no minutes figure of our own. In a 2019 trial, keeping a food diary in an app took about 23 minutes a day in the first month, falling to about 15 by month six, measured from the app's own logs. Through IZeat, a meal is one sentence and one receipt back, plus a question when the portion or the cooking fat is left open; what that removes is the searching, picking and portion-setting of a form, not the thinking about what you ate.
Can I keep a food journal by voice?
Yes, if your assistant takes voice: you dictate the meal in the chat and IZeat records it the same way it would from text, with the same questions when a quantity is left open. What matters is that the words carry the grams; "a big bowl of pasta" said aloud is still a portion nobody weighed, and it is recorded as an estimate marked as one.
Do I need to weigh my food?
No, but weighed grams give the best-sourced entry: a plain food with a weight is valued from a reference table and recorded as reference, not as a guess. Without a scale, give one cue suited to the food, spoonfuls, ladles, a fraction of the plate, a known container, and the assistant records an estimate marked as one. Weigh once and you know your usual portions for good.
What if I forget a meal?
Say it when you remember, with the day: "yesterday's dinner was 200 g of salmon and potatoes". It lands on the day it was eaten, in your time zone, and the day is summed again from its rows. A day you never record stays a day with no record: the week's average is taken over recorded days only, and nothing is filled in with a zero or a guess.
Can I fix an entry after it is logged?
In a sentence: "the rice was 200 g, not 150". The row is updated, the receipt shows the old and the new figure and the day total after it, and the previous state stays in the meal's history, so you can always ask what was recorded and when. Undo shows what the last change did and asks before taking it back, within 48 hours; restore brings it back.
Does a food journal help with weight loss?
A food record is what a 2019 trial measured, not what it promised: recording often, not long, went with its outcome, and fewer than half of the participants in two other trials were still recording after ten weeks. IZeat records what you ate and compares it to the target you chose, in the same words whether the day was over or under; it does not prescribe a diet or promise a result.
Is my food journal private?
It is yours. Nothing about what you ate leaves the database for analytics: the site's analytics see pages, never food, weight or targets. You can export the whole journal from the account page as CSV or JSON, with one download for each format, and delete the account yourself, with a 30-day grace period during which signing in again cancels the deletion. Your assistant sees the conversation; IZeat keeps the record.