What does an eating window put in the record?
Fewer, bigger meals, and later ones. A day with a noon-to-eight window is two or three entries rather than six, each denser than average, which means more items per sentence and the same rules for each: weights where you have them, the cooking fat said out loud, an estimate marked as one where nobody weighed anything.
The thing that trips people up is not the food but the date. Say a meal at 00:40 and IZeat records it for today, because today is the local date at your account's time zone; if it belonged to the evening you have just finished, say so: the assistant is asked to pass your word, yesterday, a weekday, a number of days ago, or a full date, rather than working out a date of its own, and IZeat resolves it in your time zone. Every receipt names the day in words, "Recorded for Friday 18 September 2026 (yesterday)", which is the moment to catch it.
What the record holds is meals, not hours. There is no start-fast button, no countdown, no window setting and no fasting streak, and there is nothing that notices whether today's first meal came at noon or at four. Six meal slots exist, breakfast to evening; a two-meal day fills two of them and leaves the rest empty, and nothing asks why they are empty.
What does a fasted day look like in the record?
Like a day with nothing in it, which is what it was. There is no zero to record and no way to mark a day as fasted; the day simply has no meals, and the week treats it as a gap. That matters for the figures: a period read gives the average per recorded day and says how many of the range's days have entries, so a week with two fasted days reports an average over five, not a week's average dragged down by two zeros.
| The moment | What IZeat shows | What it does not do |
|---|---|---|
| A meal at 00:40 | Recorded for today, or for yesterday if you say so; the day is named in the receipt | Work out the date itself, or use the server's clock |
| A day eaten in two meals | Two meal slots filled, four left empty | Ask about the empty ones |
| A whole day without food | A gap in the week, left out of the average | Record a zero, or count the day against you |
| Breaking the window early | Nothing at all: no eating time and no window are recorded | Notice, mark or comment |
| A long run of fasted days | The same gaps, and a count of recorded days | Congratulate, warn, or flag |
Bottom line: the pattern is yours to keep; the record dates what you ate and stays quiet about when you did not eat.
What does one fasting day look like, end to end?
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. A Friday with a window from noon to eight, and a target of 2 000 kcal and 130 g of protein.
- 12:15 — "Lunch: 200 g of chicken thigh, 250 g of cooked rice, a tablespoon of olive oil and a big salad."
- 16:00 — "How much is left?" The read gives the calories and the grams of each macro with a target.
- 19:40 — "Dinner: 300 g of beef mince at 15 percent fat, 200 g of pasta, cooked weight, and 40 g of parmesan."
- 20:15 — "A yoghurt and a square of dark chocolate, about 10 g."
- 00:30, Saturday — "I had a second yoghurt last night, after the chocolate." The assistant is asked to pass the day as yesterday, and the yoghurt is added to Friday's evening, which is already recorded.
Five sentences across thirteen hours, one of them after midnight. The chicken, the rice and the pasta are reference values for the weights given, the mince names its fat percentage so the right line is used, the olive oil is its own line at about 88 kcal per 10 g (USDA FoodData Central, checked 15 September 2026), and the salad and the chocolate are small estimates that say so. The Saturday sentence is the one worth reading twice: it names the day before, so the receipt names Friday and Friday's total moves rather than Saturday's; and because a day holds one meal of each type, the yoghurt joins Friday's evening rather than opening a second one, which is refused in words that say to add it instead.
What it does not know: IZeat does not know you fast, does not track hours, and has no opinion about windows. It cannot tell you whether the pattern suits you, and it will not notice if you stop. What it gives you is what you ate on the days you ate, dated where you said, with the source on each item and a week that counts the days it actually has.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
Which day does a meal after midnight belong to?
To today, by default, because the day is your account's local date. Say it was last night's and the assistant is asked to pass "yesterday", which IZeat resolves in your own time zone. IZeat reads today, yesterday, a number of days ago, a weekday or a full date, and never works a date out from the model's sense of time. Every receipt names the day in words, with "today" or "yesterday" beside it, which is the moment to check.
Does IZeat have a fasting timer?
No. There is no timer, no eating window, no fasting mode and no streak of fasted days; the record holds meals and their dates, not hours. If the pattern matters to you, the pattern is yours to keep. What the record adds is what you ate inside the window, with the source on each item, and a week that counts only the days with entries.
How do I record a day when I did not eat?
You do not: there is nothing to record, and no zero to enter. The day simply stays empty, and the week treats it as a gap rather than a zero, so the average is taken over the days that have entries, with the count shown beside it. Nothing marks the day, nothing asks about it, and nothing is broken by it.
Does fasting break the week's average?
No, and this is the part worth knowing: a period read gives the average per recorded day, not per calendar day, and states how many of the range's days have entries. A week with two fasted days reports the average of the five days you ate, with "5 of 7 days" beside it, rather than an average pulled down by two zeros that were never real meals.
Can I log two big meals instead of six small ones?
Yes. A day has six named slots, breakfast to evening, and you use the ones you use; two large meals fill two of them and the other four stay empty. Each meal holds a long list of items, up to forty in one call, so a dense lunch is one sentence with six foods in it, not six entries. Nothing asks why a slot is empty.
Will IZeat tell me when my window opens or closes?
No. There are no notifications about eating at all, and nothing in the product watches the clock on your behalf; IZeat is a record you write to when you eat and read when you want to know where you stand. The one thing it is strict about is which day a meal belongs to, because that is the only part a later correction cannot infer for you.
Is intermittent fasting a good idea?
Not a question this record answers. IZeat holds what you ate and compares it to the targets you chose; it does not advise on patterns, does not prescribe and does not judge a day. The assistant you connect may discuss it with you in its own voice, as it would any topic, and if the question is a medical one, it is for a doctor or registered dietitian.