Why do estimates matter more in a cut?
Because the margin is small and the unmeasured items are not. The same tablespoon of oil, about 13.5 g in USDA FoodData Central's household measures, read 17 September 2026, so about 120 kcal, costs the same whether you are gaining or losing; on a 3 200 kcal day it is noise, and on a 1 700 kcal day it is a meaningful share of the difference you were aiming for. Oil is about 884 kcal per 100 g in the same database, checked 15 September 2026, which puts 10 g at about 88 kcal.
The point is not that estimates are bad; a day of marked estimates is a legitimate day, and a plate nobody weighed still belongs in the record. The point is knowing which rows they are. IZeat keeps a source on every item, label, reference, your own figure or estimate, and marks a meal with the least certain source among its rows, so the estimated lines are visible when you come back to a week that did not go the way you expected.
Protein is the other figure people cutting watch, and the published range for resistance-trained people in a deficit is higher than the general one; what the ranges say, and who chooses the rest has the quotation and the population it applies to. Whatever figure you settle on, IZeat stores it as a target and shows the grams left; it proposes none.
What does the record do, and refuse to do, in a deficit?
It reports the distance to the target you chose, and nothing more. A day under it says what is left; a day over it says by how much, in the same type and the same colour. There is no red for a day you ate, no message when a day is low, no streak of days under target, no day held up as the model and no ranking of one day against another. That is a rule rather than a taste: a record read at the moment people judge themselves has no business adding to it.
| In a cut you might want | What IZeat gives | What it refuses |
|---|---|---|
| To know what is left before dinner | The calories and the grams of each macro with a target | Suggest a meal: if you ask for one, the answer is your assistant's, not an IZeat calculation |
| To know which figures are soft | The source on every item, estimates marked | To hide an estimate behind a round number |
| To see whether the week held | The average per recorded day and the count of days | To project a weight or a date |
| Encouragement on a low day | Nothing at all | To congratulate a deficit, ever |
| A reason the scale stalled | A record you can read row by row | To tell you it was the food |
Bottom line: the record shows what you ate and how sure each item is; the rest is yours.
When a week does not move as expected, the record is the first place to look and it will not do the looking for you. The estimated rows come first, then the cooking fat, then the days that look thin, then the days with nothing recorded, which are gaps rather than zeros in the week's average. If the record holds up to that reading, the next conversation is with someone qualified rather than with a diary.
What does one day in a cut 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 Tuesday, with a target of 1 900 kcal and 150 g of protein that you set yourself.
- 07:15 — "200 g of skyr, 30 g of granola, here is the label, and a coffee."
- 12:30 — "Lunch: 180 g of chicken breast, weighed cooked, 150 g of rice, cooked, and a big salad with a teaspoon of oil."
- 16:45 — "How much protein is left?" The read gives the grams remaining and the calories with them.
- 19:45 — "Dinner was at my brother's: a lasagne, about a quarter of the dish, and a slice of bread."
- 19:47 — The assistant is asked what the dish was and roughly how big, before the row is estimated and marked as one.
Five sentences, the last of them a question the assistant is asked to put before it estimates. The skyr and the chicken are reference values for the weights you gave, with the chicken's state said out loud because cooked and raw differ; the granola comes from its label; the lasagne is the estimate of the day, and the record says so. A week later, if the numbers look odd, that lasagne is the first row you check.
What it cannot tell you: IZeat does not set the deficit, does not know what you burned, and does not record your weight, so it cannot tell you whether the cut is working. It shows what you ate, how sure each item is, and how many days of the week you actually recorded. If counting starts to feel like something other than a tool, that is worth saying to someone qualified.
Frequently asked questions
Short answers to the questions people type, each one sourced above.
How exact does tracking need to be in a cut?
Inspectable enough that you know which rows are soft. A weighed food from a reference table and a label read back are firm; a plate nobody weighed is an estimate, and IZeat marks it as one. In a small margin the unmeasured items, the cooking fat above all, are where a week quietly drifts, so those are the ones worth a scale or a spoon count.
How do I keep protein in view during a cut?
Set a protein target and it appears on every receipt and every read of the day, with the grams still to go beside the calories. It can sit alone or beside a calorie target, and changing it is a new dated target rather than an edit, so an earlier week still reads against the figure that applied then. What the published ranges say, and which population they were written for, is on the page about protein when losing weight; IZeat itself proposes no figure.
My weight stalled. Can the record tell me why?
It can show you where to look, which is not the same thing. Start with the estimated rows, then the cooking fat, then the days that look thin, then the days with nothing recorded, which the week leaves out rather than counting as zeros. A record is declared, reference and estimated figures together; an entry every day does not certify that everything went in. If it holds up, the next conversation is with someone qualified.
Should I weigh everything?
That is your call, and the useful version is narrower: weigh the things that move the figure most, the cooking fat and the dense foods, and let a size word cover the rest. A day of marked estimates is a legitimate day; what makes it usable is that the record says which rows they were, so you can tighten one item rather than start the week again.
Can I set a lower target for some days?
Targets are dated, so a change starts on the day you name and holds until the next one; the days before keep the target they had. Setting one number for weekdays and another for the weekend means two targets each week, which is two dated targets to keep track of each week. Either way IZeat records the change and reports each day against the target in force that day.
Does the record know if I am losing muscle?
No. It holds food, with the source on each item, and compares it to the targets you chose; it records no weight, no measurements and no body composition, and it estimates nothing about what your body used. What a cut is costing you is measured elsewhere, if it is measured at all, and that reading is yours and, if you want one, a professional's.