Raw meat and cooked meat
When meat cooks, water leaves, and the cooked piece does not weigh the same as the raw piece. The FoodData Central row has to match the state on the scale: raw with raw, cooked with cooked.
Water leaves, and the scale sees it
A raw piece and the same piece after frying or boiling are not one mass, because water leaves with heat and is no longer on the plate. The scale under cooked meat shows a different weight, and that is not a reason to invent a shrinkage percent: no such percent is on the sheet. There is a rule of state. The database row has to speak of the kind of meat you weighed.
Grain, in a different task, behaves otherwise: water enters, and a cooked spoon is not the dry grain. Meat is not copied from that story or from that multiplier. There is no “rice triples” factor for rice, and there is no mirror-image division by three for meat. Both bans say the same thing: state is not replaced by a universal number.
Raw weight and a raw row
If the meat was weighed before the pan and that raw weight is what you mean to count, open the raw row for those grams. The diary then describes the food before the water left. A cooked row is not stretched over raw grams: the cooked row has different water and a different guide per 100 g.
A raw weight belongs in the log only if it is not later swapped for an eaten piece of some other weight. Part of the raw meat may never have reached your plate: fat poured off, broth, a neighbor’s share. What was eaten is what gets written. A raw row does not license entering the whole shop package if the plate held a cooked portion of another mass.
Cooked weight and a cooked row
If you weighed what is on the plate after cooking, you need a cooked-meat row for that cooked weight. The state on the label is as functional here as it is for grain. A raw label on a cooked piece disagrees with water that has already left. Matching the name does not rescue a mismatch of state.
Even a row that is right about the state is a guide per 100 g, not the passport of your pan, and brands differ. A label, if the meat was packed raw, speaks of the raw food and of its own serving, which is not always 100 g. After frying, that label does not by itself become the row for the cooked plate. Either the raw weight of your own portion is what you count, or you weigh the cooked meat and open the cooked row.
One piece, one account
You cannot enter a raw weight on a raw row and then add the cooked weight of the same piece on a cooked row. That would be two lunches. Choose the moment of weighing and stay with it. If the moment was raw, do not “clarify” the day by laying a cooked row on top.
If the moment of weighing is forgotten, memory is not repaired with a shrinkage coefficient. The state is marked unclear, and next time you weigh what you are eating now. Honest uncertainty is shorter than an invented percent. The database works with a clear state and does not rescue a confused one.
What this text draws on
- USDA FoodData Central: guides per 100 g; brands differ. A dry-food row is not a cooked portion, because water changes the weight. Do not use a “rice triples” factor.
- FDA Nutrition Facts: energy is stated per labeled serving; a package can contain several servings. A labeled serving is not always 100 g.
A short paraphrase of open guides and reviews (WHO, national recommendations, peer‑reviewed summaries). Not a quotation and not a treatment protocol.
Short answers
Can a raw weight be run through a cooked row?
No. Water leaves during cooking, the weight changes, and the row has to match the state on the scale.
Is there a coefficient for how much meat shrinks?
It is not on this sheet, and a homemade one must not be inserted. Raw meat is counted on a raw row, cooked meat on a cooked row.