Waste in the hotel kitchen: the four sources and how each one is measured
Waste in a hotel kitchen is not one number: it is four different phenomena that add up on the same line of the income statement. If you do not separate them, you will attack the wrong one. Here is how each is measured and the record that tells them apart.
Your hotel controller shows you the month’s food cost and it is three points above what the recipes say it should be. Those three points have a generic name, waste, and behind that name are four things that look nothing alike: the breakfast buffet that was left over, the cook who serves generous portions, the box of strawberries that expired in the walk-in and the pack of salmon that left through the staff door. Each one is measured differently and corrected differently.
Why hotel waste is different from street restaurant waste
A street restaurant produces against demand: the dish is prepared when someone orders it. A hotel kitchen produces a great deal against forecast: the breakfast buffet is set up before the first guest comes down, the banquet is cooked for the guaranteed number, the pool bar is stocked for the whole day. When the forecast misses, food is left over, and that leftover is waste no cook caused.
On top of that, in a hotel the same storeroom supplies several revenue centers with different hours. A product the restaurant did not use on weekdays may be consumed by the bar on Saturday, or may expire in the walk-in because nobody knew it was there. And there are more hands: kitchen, room service, banquets, housekeeping staff passing through the service area. More hands, more ways out.
That is why total waste says little in a hotel. What helps is waste by source, and under the hospitality accounting standard (What USALI is and why it pays off even with twenty rooms) that shows up as a gap between theoretical cost and actual cost in the food and beverage department.
First the total: actual cost against theoretical cost
Before separating sources you need to know how much there is to explain. Actual food cost for the period is opening inventory plus purchases minus closing inventory. Theoretical cost is what the recipes say your sales should have cost: each dish sold multiplied by its standard recipe cost, added up. The difference between the two is total waste, and it is the number the four sources have to explain between them.
If you have no standard recipes, you have no theoretical cost, and then you have no waste: you have a high cost with no idea why. That is the first requirement, and it is the one most hotels skip.
Source one: overproduction
This is what was prepared and not sold: the buffet left over, the sauce of the day made for 80 when 40 went out, the breakfast bread that never reached a table. In a hotel it is almost always the largest source, and also the least culpable, because it comes from an occupancy forecast that arrived late or arrived wrong.
It is measured by weighing or counting what is discarded at the close of each service, valued at recipe cost, and recorded with the service and the revenue center that produced it. The fix is not in the kitchen: it is in the chef receiving every morning the number of occupied rooms, included breakfasts and groups for the day, and producing against that.
Source two: portions
This is the gap between what the recipe says a dish contains and what the cook actually serves. Twenty extra grams of protein per plate, multiplied by the month’s plates, is a whole percentage point of cost. It does not show up in the trash because the guest ate it. It shows up only in theoretical against actual cost.
It is measured with portion controls: weighing a sample of dishes per shift and comparing against the recipe, or comparing the usage of a key ingredient against sales of the dishes that contain it. The fix is training, portioning tools and a visible recipe at the station, not a reprimand.
Source three: expiry and mishandling
This is product that was bought and spoiled before use: it expired, the cold chain broke, it was stored badly. In a hotel it grows when the storeroom buys for five revenue centers and none of them takes responsibility for rotating what it requested. It also grows in low season, when purchasing follows habit rather than occupancy.
It is measured by recording every inventory write-off for expiry or damage, with product, quantity, cost and the revenue center that had it in custody. The fix is in purchasing and requisitions: buy against forecast occupancy, rotate first what came in first, and let every revenue center see its own inventory.
Source four: pilferage
This is what left without being sold and without being discarded. Nobody records it, by definition. It is calculated as what remains of total waste once the other three sources are subtracted: the residual nobody explains. If your first three sources are well measured, that residual is small. If you do not measure them, the residual is huge and the easiest conclusion, and almost always an unfair one, is that someone is stealing.
That is the deeper reason to separate the sources: without records for the first three, the fourth absorbs everything, and the conversation with the team becomes an accusation. With records, the fourth becomes a concrete number that rises or falls by shift, by revenue center and by product, and that can actually be investigated.
- High-value, easy-to-carry products: proteins, spirits, coffee beans, oil.
- Shifts where the residual rises without sales rising.
- Revenue centers with irregular shift closes or no inventory count of their own.
- Unrecorded staff meals, which are sometimes mistaken for theft and sometimes hide it.
The record that separates the four sources
Everything above depends on one habit: every product write-off is recorded at the moment, with its cause. Not at month-end, not from memory. A waste log only works if the cook can complete it in thirty seconds from the station, with the product, the quantity and one of four causes.
| Source | How it is recorded | Who records it | When |
|---|---|---|---|
| Overproduction | Weight or units discarded at close, valued at recipe cost, by service and revenue center | Kitchen shift lead | At the close of every service |
| Portions | Sample of dishes weighed against recipe; key ingredient usage against sales | Chef or sous chef | One sample per shift, weekly calculation |
| Expiry and damage | Inventory write-off with product, quantity, cost and center in custody | Storeroom or the center that held it | At the moment of the write-off |
| Pilferage | Total waste minus the three above | Controller | At month-end, by center and product |
The controller (Controller) is the one who brings the four records together with inventory and sales, and who can say in the meeting: this month’s waste was so much, and this is how it breaks down. Without that breakdown, the cost report (Reports) only says something is wrong.
An illustrative example with numbers
The figures below are made up to show the calculation. They do not correspond to any real property or to any industry average.
A hotel closes the month with opening food inventory of 30,000, purchases of 120,000 and closing inventory of 28,000. Actual cost is 30,000 + 120,000 − 28,000 = 122,000. Standard recipes, multiplied by what was sold across all revenue centers, give a theoretical cost of 96,000. Total waste is 122,000 − 96,000 = 26,000.
The month’s log says: overproduction 9,000 (almost all breakfast buffet over two weeks of low occupancy), portions 5,000 (the portion control on the fish and the beef cut), expiry and damage 6,000 (a walk-in that failed over a weekend). They add up to 20,000. The residual is 26,000 − 20,000 = 6,000, and that is the number to investigate by product and by revenue center, not the full 26,000.
Without the log, the meeting would have opened with “who is taking 26,000 a month?”. With the log, it opens with “the breakfast buffet needs to be produced against occupancy, and there are 6,000 that do not balance at the bar”. Those are very different conversations, and only one of them leads to a fix.
Total waste is actual cost minus theoretical cost, and it has four sources: overproduction, portions, expiry and pilferage. Record the first three at the moment, with a cause, and the fourth becomes a small residual that can actually be investigated.
What to do this week
- Calculate last month’s total waste with the opening inventory, purchases and closing inventory formula against the theoretical cost of your recipes. If you have no standard recipes, start with the ten best-selling dishes.
- Put a scale and a four-cause log at the close of every service, even on paper, and weigh what is discarded from the breakfast buffet for seven days.
- Weigh five dishes per shift of the three that carry the most protein and compare them against the recipe.
- Go through the walk-in with the storekeeper and write off everything already expired, recording product, cost and the revenue center that requested it.
- Ask the chef to receive the day’s occupancy and included breakfasts every morning before deciding how much to produce.
- At the end of the week, bring the four numbers together with the controller and calculate the residual. That is your starting point.
Inn Restaurant records inventory write-offs with a cause from the station, calculates theoretical cost from recipes and each revenue center’s sales, and shows the residual by product and by center in the controller’s report. If you want to see your hotel’s waste separated into four numbers, the 15-minute demo is booked on the contact page (contact).
More articles
Modifiers and notes: “no onion” has to survive the check being split
A note the server wrote correctly can reach the kitchen wrong, vanish when the check is split and never show up on the guest folio. This article follows a modifier through the hotel system and shows where it breaks.
Guest with an allergy: how the order note survives from the order to the folio
A hotel guest says “I am allergic to shellfish” once, to the server, at the table. That sentence has to reach the kitchen, the tray, the next order of their stay and the hotel record. Here is how to make sure it does not depend on anyone’s memory.
The order that reaches the kitchen before the server: what changes when paper disappears
In the hotel restaurant, the paper ticket takes a two-minute trip the kitchen pays for in delay, errors and dishes nobody knows whether they went out. When the order reaches a screen before the server leaves the table, the dish states, the times per station and what reaches the guest folio all change.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.