Key takeaways
- A late meal is recorded on the day it was eaten, not the day you said it: "yesterday", "3 days ago" up to 31 days back, a weekday, or a full date.
- The receipt names the day in words, "IZeat · Recorded for Tuesday 15 September 2026 (2 days ago): lunch — …", so a meal on the wrong day is caught in the same breath.
- "Last week" is not a day: IZeat records nothing and asks, through the assistant, which one you meant; a meal on the wrong day is worse than a missing one.
- A meal type already recorded for that day is not stored twice: the assistant adds to it, or records the extra food as another meal type.
How do you say a meal for a past day?
- Identify the day the meal was eaten; use an exact date when a weekday might be ambiguous.
- Reconstruct the foods from what you remember, supported by labels, shopping records or photos where available.
- Choose that day in your diary, or name it to your assistant. Check whether the meal already exists before adding food.
- Verify the returned date and meal contents, keeping unknown meals and estimated quantities explicit.
With the day in the sentence, in your own words. "Yesterday's lunch was a chicken salad and a roll." "Dinner on Tuesday was pasta, about 200 g cooked, with a tomato sauce." "Three days ago I had two eggs and toast for breakfast." The assistant is asked to pass your word for the day, not a date it worked out, and IZeat does the arithmetic against your own today, in your time zone, rather than letting the assistant work out a date.
The day is your local one, which matters most to anyone whose meals cross midnight: an eating window that opens at noon and closes at eight leans on the same rule. What IZeat reads: today, yesterday, a number of days ago up to 31, a weekday, which means the most recent one, today included, or a full date written out. What it refuses on purpose: "last week", "the other day", "a while ago", because a guess at those puts a meal on the wrong day; IZeat answers that it could not read the day and records nothing, and the assistant is asked to find out which day you meant. The day in your time zone is the account's, so a dinner said at one in the morning still belongs to the evening it was eaten if you say so.
| What you say | What IZeat records it for | What the receipt names |
|---|---|---|
| "Yesterday's dinner was…" | The day before your today | "IZeat · Recorded for Wednesday 16 September 2026 (yesterday): dinner — … (estimated)" |
| "Tuesday lunch was…" | The most recent Tuesday, today included | "IZeat · Recorded for Tuesday 15 September 2026 (2 days ago): lunch — …" |
| "Three days ago I had breakfast…" | Three days before today | The day in words, with "(3 days ago)" |
| "On 2 September 2026 I had…" | That date, passed in full with its year | The date in words, without a relative word once it is more than six days back |
| "Last week I had a pizza" | Nothing yet | "IZeat could not read the day", and the assistant is asked which day you meant |
| "Lunch was…" with no day | Today | "IZeat · Recorded for … (today)" |
Bottom line: say the day the way you would say it to a friend, and read it back in the receipt before moving on.
What happens when that day already has a meal?
Each day has six slots: breakfast, morning snack, lunch, afternoon snack, dinner and evening. A meal type recorded once for a day is not recorded twice: if Tuesday's dinner is already there and you say "Tuesday dinner was also a piece of cake", IZeat answers that dinner is already recorded, with what it contains, and names two ways on: add the cake to that dinner if it was part of it, or record it under another meal type, the evening for instance, if it was eaten at another time. Nothing is recorded until the assistant relays that and you say which you meant.
Catching up in the wrong order is fine. Say Tuesday's dinner on Thursday, then Tuesday's lunch on Friday; each lands on Tuesday, and the day total is computed from its rows whenever you read it, rather than kept as a separate stored daily total. Ask "what did I eat on Tuesday?" and the assistant reads the day from IZeat, signed, with each row and its source.
A mistake in a late entry is corrected the same way as any other: "Tuesday's pasta was 150 g, not 200" updates the row, and the previous state stays in the meal's change history. Taking back the last write entirely, rather than correcting it, is a two-step undo within 48 hours of the write, confirmed within ten minutes of being shown, and the 48 hours count from when you said it, not from the day it was recorded for.
What is a remembered day worth?
IZeat is the five-star chef calorie tracker that suggests satisfying, great-tasting meals, so you enjoy every calorie you have left. It works inside ChatGPT, Claude or any other assistant: IZeat knows your numbers for the day, which foods fill you up and what you like. Connection requires an MCP-capable assistant with external connections supported and permitted for your account. A meal entered later keeps the source supported by each item’s inputs. A labelled pot with known consumption can still use label values; a remembered weight with a matching plain-food reference can use reference values. Unknown portions or reconstructed preparation are estimates. The date of entry alone does not make every row estimated.
A period average covers days with recorded entries; their count does not establish completeness. Logging Wednesday’s dinner alone includes Wednesday among recorded days, but its total omits breakfast and lunch. Keep that limitation visible when interpreting the period. IZeat does not automatically know whether every meal has been entered.
Thursday evening, two days behind: “Tuesday breakfast was oats and milk; lunch a bakery sandwich; dinner pasta. Wednesday I only remember dinner.” Record the meals on their named days, clarify quantities you can remember, and mark estimated portions. When you read the week, check the meal list yourself for Wednesday’s missing entries before treating its total as daily intake.
The limit: a reconstruction may omit snacks, drinks or cooking fat. If a missing quantity cannot be recovered, retain an estimate rather than claiming precision. If a whole meal is unknown, do not invent it. A partial diary is useful context, but does not by itself establish the day’s full intake.
For the wider method, see the calorie tracking guide.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
Can you log food for a previous day?
Yes: say the day with the meal, "yesterday's dinner", "Tuesday lunch", "three days ago" up to 31 days back, or a full date. The assistant is asked to pass your word, not a date it worked out; IZeat resolves it in your time zone, then names the day in words in the receipt so you can see it landed where you meant. A weekday means the most recent one, today included.
What if I say "last week" or "the other day"?
IZeat does not read those as a day, on purpose: a guess would put the meal on the wrong date, which is worse than a missing one. The assistant is asked to relay that and ask which day you meant. Once you name it, yesterday, a weekday, a number of days ago or a date, the meal is recorded for that day and the receipt names it.
What if that day's lunch is already recorded?
It is not stored twice. IZeat answers that lunch is already recorded for that day, with what it contains, and offers two ways on: add the new items to that lunch, or record them under another meal type if they were eaten at another time, the afternoon snack for instance. The assistant is asked to relay that and ask which you meant. A day has six meal types, breakfast to evening, each recorded once.
Can I correct a meal I logged late?
In one sentence, like any meal: "Tuesday's pasta was 150 g, not 200" updates the row and the day total follows, and the previous state stays in the meal's history. Undoing the last write entirely is separate: a two-step confirmation, given within ten minutes of the preview and within 48 hours of the moment you recorded it, whatever day the meal was for.
Does a late entry count in the weekly average?
Yes. A day with entries is included in the recorded-day average, whether entered on time or later. The recorded-day count is not a completeness score. A day with only dinner can lower that average because other meals are absent; inspect those gaps before interpreting usual intake.
Is it worth logging a day I half remember?
It can preserve useful information if you keep the missing meals and uncertain quantities explicit. IZeat can count a day with only one meal among recorded days; that does not make it complete. Inspect the meal list before using the average as a full-day intake estimate.
What time zone does the day use?
Yours, the one your account holds; never the server's and never the assistant's guess. A dinner said at one in the morning is recorded for today unless you say it was yesterday's, in which case the assistant is asked to pass "yesterday" and it lands on the evening it was eaten. The receipt names the day in words every time, which is the moment to check it.