What does a training week put in the record?
Food, on days that look nothing like each other. A rest day and a four-hour Sunday are both recorded the same way, meal by meal, with the source on each item; what changes is the content. The things that come up here and rarely elsewhere are the ones eaten in motion: gels, bars, drink mixes and the bottle you finished on the bike, each with a label to read back rather than a portion to guess.
Those are the easy ones. The harder ones are the meals around a session, eaten in a hurry and remembered later, which is why saying a day after it happened is worth knowing how to do: "yesterday's dinner was…" lands on the day it was eaten, in your own time zone. The rest is the same discipline as anyone else's, with weights where you have them and an estimate marked as one where you do not.
What does not go in is the session itself. IZeat has no exercise entry, no watch or strap connection, and no calories-burned figure anywhere in the product; nothing you run, ride or lift changes a number in the record. That is a deliberate boundary, not a missing feature: a food record is honest about one side of the balance, and the other side is where the wide error bars live.
What does the day show on a hard training day?
What you ate, against the target in force that day. If your target is a single number all week, a long Sunday will often read as "over target" and an easy Tuesday as "remaining"; both are stated in the same neutral form, neither is marked, and nothing is added back for the ride. If you would rather the targets follow the training, they are dated: set one from Monday and another from the week the block changes, and each day is read against the one it had.
| What you might expect | What IZeat does | Why |
|---|---|---|
| Calories back after a long run | Nothing: the target does not move | No expenditure figure exists in the record |
| Your watch's burn figure in the day | Nothing: no device connects | IZeat records food only, by design |
| A bigger target on hard days | Yours to set, dated from the day you say | The target is the customer's, never calculated |
| A week read rather than a day | Average per recorded day, with the count of days | A training week is uneven by nature |
| Gels and bottles logged fast | A label read back, then one item inside the meal | They are packaged, so the figures are declared |
Bottom line: the record holds what you ate; what you burned stays an estimate nobody in this product makes.
If you want a figure for what training costs you, the published equations estimate resting energy and multiply it by an activity factor, about 1.4 to 2.4 on the FAO/WHO/UNU scale, and the best studied of them, Mifflin-St Jeor, landed within about 10 percent of the measured figure for more people than the others in the 2005 review by Frankenfield and colleagues, read 16 September 2026, which adds that noteworthy errors remain for an individual. The factor is a self-assessment, so the total is a range. That arithmetic is yours to do, or your assistant's; IZeat neither performs it nor stores it.
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 week in a block, with a 3 000 kcal and 140 g protein target set from the Monday.
- Tuesday, intervals — "Before: a banana and a coffee. After: 500 ml of chocolate milk, the label is 62 kcal per 100 ml."
- Thursday, rest — three meals, said as they happen, nothing else.
- Saturday — "I forgot to log Friday. Friday's dinner was a pizza, about half a large one, and two beers."
- Sunday, long ride — "Two gels and a bar on the bike, here are the labels, and 750 ml of drink mix."
- Sunday evening — "What did the week look like?" The period read gives the average per recorded day and how many of the seven days have entries.
Five moments, one of them a catch-up and one a question. The gels and the bar are label rows, the pizza is an estimate that states the share it assumed, and Friday lands on Friday because it was said as Friday. Monday, Wednesday and Saturday went in as they happened, so Sunday's read says six of seven days have entries, Friday among them and one day with nothing, and the average describes six days rather than the week; a day with nothing recorded is left out rather than counted as zero.
Where this record stops: this is a record of intake for people whose expenditure swings hard from day to day, and it does not follow those swings. It cannot tell you whether you ate enough for the block, whether the long ride was fuelled, or what your week cost you. It shows what went in, with sources, on the days you said it; the training side is yours, and a coach's or a dietitian's if you want one.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
Does IZeat track exercise or calories burned?
No. There is no exercise entry, no calories-burned figure and no connection to a watch, a strap or a phone's activity data; nothing you run, ride or lift changes a number in the record. IZeat holds one side of the balance, the food, with the source on each item. What you burned is an estimate, and this product makes none of them.
Can I connect my Garmin, Strava or Apple Watch?
No: wearable and health-app sync is on the list of things IZeat refuses, written into the product's own rules rather than left for later. The record stays a record of what you ate, said to the assistant you already use. If you want your training data beside your intake, the export gives you the whole food record as CSV or JSON in one click, and the rest is yours to put next to it.
How do I eat more on training days without changing my target?
You simply eat more, and the day reads as over target in the same neutral form it would use for anything else; nothing is marked and nothing is added back. If you would rather the target follow the training, targets are dated: one from the Monday of a heavy block, another when the block changes, and every day is read against the one in force that day.
How do I log gels, bars and drink mix?
From their labels, which is the fastest path there is: photograph or read out the figures, say how many you had, and the values are read back to you before the row is recorded with the label as its source. A bottle of mix is a volume, "750 ml", and the concentration comes from the label too. Said later is fine; name the day and it lands there.
Does a food record tell me if I am fuelling enough?
No, and it would need the other side of the balance to try. What it gives you is the intake side, day by day and averaged over recorded days, with the source on each item, so a week you are asking questions about is a week you can actually read. What that means for your training is between you and someone qualified to advise you.
How do I estimate what I burn, if IZeat will not?
With a published equation and an activity factor, knowing the answer is a range: the best-studied equation, Mifflin-St Jeor, landed within about 10 percent of measured resting energy for more people than the others in a 2005 systematic review, and the factor, about 1.4 to 2.4 in the FAO/WHO/UNU tables, is your own assessment of how active you are. You or your assistant can do that arithmetic; IZeat neither performs it nor stores the result.