
Restaurant Wastage Log Template: Track Food Waste and Control Inventory
In short: Food that is thrown away without being written down shows up as unexplained food cost. Use this wastage log template with reason codes, fill it in every shift, cost it daily and review it weekly, so you can see whether you are losing money to spoilage, over-production, kitchen mistakes or returns, and fix the biggest cause first.
Why a wastage log matters
Most restaurants know their sales to the rupee but have no idea how much food goes into the bin. Spoiled chicken, burnt naan, returned plates, over-prepared rice at closing and staff meals that nobody wrote down all leave the store as “used” stock. When they are not recorded, they look like theft or bad recipes in your food cost, and you cannot fix what you cannot see. A simple wastage log, filled in every shift, turns that hidden loss into numbers you can act on.
The wastage log template
Copy this layout into a register, a sheet or your restaurant software. One line per item wasted.
| Date / shift | Item | Qty | Unit | Stage | Reason code | Cost (Rs) | Recorded by | Checked by |
|---|---|---|---|---|---|---|---|---|
| 12 Nov, dinner | Chicken (raw) | 2 | kg | Storage | EXP | (qty x purchase rate) | Store keeper | Manager |
| 12 Nov, dinner | Chicken karahi | 1 | plate | Served | RET | (recipe cost) | Head waiter | Manager |
| 12 Nov, close | Plain rice | 3 | kg | Prepared | OVR | (recipe cost) | Chef | Manager |
The rows above only show how to fill the columns. Use your own purchase rates and recipe costs for the cost column.
Reason codes to use
- EXP: expired or spoiled in storage (fridge failure, past use-by, pests).
- PRP: preparation loss beyond the normal trimming in the recipe.
- OVR: over-production, food cooked but not sold by closing.
- BRN: burnt, dropped or cooked wrongly in the kitchen.
- RET: returned by the customer (cold, wrong order, complaint).
- STF: staff meal, if you choose to track it here rather than as a separate expense.
- OTH: anything else, with a one-line note.
The daily and weekly routine
- Keep a wastage bin or tray. Nothing is thrown away until it has been weighed or counted and written down.
- Record at the moment. The person who wastes the item records it in that shift, not from memory the next day.
- Manager check at closing. The shift manager checks the bin against the log and signs.
- Cost it daily. Multiply quantity by purchase rate for raw items, or by recipe cost for prepared dishes. Our recipe costing guide shows how to work out recipe cost.
- Review weekly. Total wastage by reason code and by item. The top three lines tell you where to act.
- Compare with stock. At each stock count, actual usage minus recorded sales and recorded wastage leaves the unexplained gap, which is what you investigate.
What to do with the numbers
- High EXP: buy smaller quantities more often, label stock with receiving dates and use first-in, first-out on the shelf.
- High OVR: prepare in smaller batches during the evening and set closing-time quantities from past sales of that weekday.
- High RET: look at the dish, the station and the time; returns often point to a training or timing problem, not the recipe.
- High BRN or PRP: retrain on that station and check the recipe yield is realistic.
Keep it honest: the log only works if staff are not punished for recording waste. Punish unrecorded loss, not recorded waste, otherwise people stop writing it down and the loss moves back into the dark.
Moving the log into software
A paper log is a good start. In restaurant software, a wastage entry deducts the stock at the right cost, keeps the reason and the user, and shows wastage next to sales and food cost in the same report. When orders also deduct ingredients through recipes, the software can show the gap between expected and actual usage at every stock count. Our restaurant billing software checklist lists the stock features to test in a demo.
Want wastage tracked automatically?
Message us on WhatsApp and we will show you wastage entries, recipes and food cost reports in our restaurant software with your own menu.
Frequently asked questions
What is a restaurant wastage log?
It is a record of every food item a restaurant throws away, with the quantity, the stage it was wasted at, the reason, the cost and who recorded it. It turns hidden loss into numbers you can manage.
What columns should a wastage log have?
Date and shift, item, quantity, unit, stage (storage, preparation, prepared, served), reason code, cost, recorded by and checked by.
How do I calculate the cost of wasted food?
For raw items, multiply the quantity by the purchase rate. For prepared dishes, use the recipe cost of the portion. Costing every entry is what makes the weekly review useful.
How often should wastage be reviewed?
Record it every shift, check it at closing, and review the totals by reason and item once a week. Compare it with stock usage at each stock count.
Should staff meals be recorded as wastage?
You can track them in the log with their own code, or record them separately as a staff expense. The key is that they are written down, so they do not look like missing stock.
Can restaurant software track wastage?
Yes. Good restaurant software lets you post wastage with a reason, deducts it from stock at cost and shows it beside sales and food cost, so the unexplained gap at a stock count is easy to see.
This template is general guidance prepared on 15 November 2026. It does not replace food safety rules: follow your provincial food authority’s requirements for storage, handling and disposal of food.
