The register shows what sold. It never shows the case of romaine that turned or the pan of rice binned at close. A waste log, a dollar figure, and five fixable causes are how that money comes back.
August 29, 2026
The register tells you what left the building on a plate or in a bag. It says nothing about the case of romaine that turned in the walk-in, the hotel pan of rice made at ten and binned at close, or the salmon that came back twice because the ticket was wrong. If you want to reduce food waste in restaurants — yours, specifically — the work is not a sustainability poster in the office. It is a ten-second habit at the bin, a dollar figure on the same weekly sheet as sales and labor, and a short list of causes you fix one at a time. Waste is not a separate problem from food cost. It is food cost, hiding in the one part of the kitchen your reports never see.
Almost everything a kitchen throws away lands in one of five buckets, and knowing which bucket is yours decides what you fix first.
The first four buckets are pre-consumer waste — food that never reached a guest. The last is post-consumer. The split matters because the levers are different. Pre-consumer waste is a process problem: ordering, prep, production, and order accuracy are all decisions your team makes, which means all of them can be changed this week. Post-consumer waste is information: if half the fries come back on every third plate, the portion is wrong or the item is, and that is a menu conversation, not a kitchen scolding. In most independent kitchens the pre-consumer side is the bigger pile and the cheaper one to shrink, so start there.
Most food waste advice starts with a full audit — sorting and weighing everything the building discards for a week. Audits are useful and heavy, and plenty of operators never get past scheduling one. A waste log inverts the order of operations: start today, with a clipboard by the bin or a button on the POS line, and let the picture assemble itself over a couple of weeks. Every time something meaningful gets tossed, whoever tosses it writes four things:
The fixed reason list is the part people skip and the part that makes the log work. Free-text reasons produce a diary; six checkboxes produce a ranking. Two weeks in, you will know which bucket owns most of your waste, and you will have learned it for the cost of a clipboard.
A log that says “12 lb chicken thighs, spoiled” changes nothing. The same line times your unit cost, rolled up weekly and read out at pre-shift, changes behavior fast — a kitchen that hears “we threw away four hundred dollars last week, most of it over-prepped proteins” (your number will be your own) suddenly has opinions about the prep list. Waste in dollars also tells you what to fix first, because the biggest bucket by weight is not always the biggest by cost: a case of wilted spring mix and a binned pan of braised short ribs are very different lines on the same log.
| Waste reason | Usual cause | First fix |
|---|---|---|
| Spoiled before use | Ordering to habit instead of to counts | Order from par minus on-hand; first in, first out on the shelf |
| Over-prepped | Prep list is a guess | Build prep quantities from a sales forecast and par levels |
| Batch made, held, binned | Cooking to the rush that might come | Smaller batches, more turns, honest hold-time limits |
| Remakes and order errors | Handwritten tickets and missed modifiers | Route every order to a kitchen screen; confirm mods at entry |
| Plate waste | Portions bigger than appetites | Trim the two worst offenders; watch what actually comes back |
Two of those fixes are worth a sentence more. Prep quantity is the highest-leverage number in the building, and it should come from prep lists and par levels driven by what you actually sell by day of week — not from what the opener remembers about last Saturday. And remakes are the quietest bucket: a dish made twice costs you the food, the labor, and the table’s patience, and the fix is upstream of the kitchen — orders routed to a kitchen display arrive exactly as they were rung, with modifiers attached, instead of surviving a handwriting relay.
If you run recipe-mapped inventory counts, you already track the gap between theoretical usage — what your sales say you should have consumed — and actual usage from the count. The waste log is the missing middle of that math. Logged waste explains part of the variance: yes, we used more chicken than sales justify, and here are the two spoiled cases that explain it. Whatever the log does not explain is the real alarm — shrinkage, unlogged mistakes, or portioning drift — and now it is a small, specific number instead of a vague one. Kitchens that skip the log end up blaming their entire variance on “waste”, which conveniently asks nothing of anyone.
Overproduction is fear with a steam table. The antidote is a forecast built from your own history: what does this restaurant sell on a rainy Tuesday in October, by item, and what does that mean for tomorrow’s prep? Your POS already holds the sales history; the discipline is letting it override the instinct to cook for the best Friday you ever had. Orders that arrive through your own online ordering channel help here too — direct orders land in the same system as in-house sales, so the demand picture your forecast draws from is complete instead of scattered across tablets. Forecast, prep to the forecast, log what still gets binned, and tighten next week.
Prevention beats diversion, but no kitchen gets to zero. For safe, unserved surplus, donation is more workable than the old fear suggests: both the United States and Canada protect good-faith food donors from liability — federally in the US, provincially in Canada — so “we would get sued” is mostly out of date, though your local health rules govern what can move and how. Composting programs vary widely by city, and several jurisdictions now require organics diversion for food businesses, so it is worth one phone call to find out where yours stands. And a defined staff meal — planned, costed, on the books — beats the informal graze that otherwise absorbs your mistakes invisibly.
Run the loop weekly, and keep it small: read the waste total in dollars, read which reason and which station lead the list, pick one fix, and check it against next week’s log. Cut the Friday rice batch in half and see if the “over-prepped” line shrinks. Move produce deliveries a day later and watch the spoilage line. One verified fix a week compounds; a binder of intentions does not. On Novaryq, the pieces sit in one place — sales history, prep-ready inventory, recipe-level depletion, and order-accurate kitchen screens on one platform, one plan — so the waste conversation runs on numbers you already have instead of a second bookkeeping job.
With a waste log: every meaningful toss gets an item, a quantity, a reason from a short fixed list, and a station, recorded at the bin in seconds. Multiply by unit cost and roll it up weekly. Two weeks of honest logging usually identifies the biggest bucket without a formal audit.
Pre-consumer waste — spoilage from over-ordering, over-prepping, overproduction on batch items, and remakes from order errors — is typically the larger and more fixable share. Plate waste matters too, but it is mainly a signal that portions or menu items need adjusting.
Yes, because wasted food is already inside your food cost percentage — you paid for it and sold nothing against it. Cutting waste narrows the gap between theoretical and actual usage, which shows up directly in your weekly food cost number.
Safe, unserved surplus usually can be donated: the US has federal liability protection for good-faith donors and Canadian provinces have equivalents. Check local health rules for what qualifies, and treat donation as the backstop — prevention through ordering, prep, and forecasting is where the money is.