Tracking food wastage so it actually shrinks

A wastage log with reason codes shows where food goes and who can fix it, which a stock count cannot. How to set one up in a restaurant kitchen.

To reduce food wastage in a restaurant, log every item thrown away as it happens, with a reason code, a quantity and the name of whoever logged it. Then review the log every week and fix the biggest reason first. A monthly stock count tells you food went missing. A wastage log tells you why, and that is the part you can act on.

Why is a stock count not enough to cut wastage?

A periodic stock count compares what you should have against what you do have. Say you are short on paneer at month-end. The count gives you one number for the gap and no explanation. The paneer could have spoiled in the walk-in, been over-prepped on a slow Tuesday, come back on plates or ended up on the floor. Each of those has a different fix and a different owner.

By the time the count runs, the evidence is weeks old. Nobody remembers which batch turned sour or which night the tandoor station prepped double. All the kitchen can do is say "be careful with paneer", and that changes nothing.

A wastage log records the cause at the moment it happens. Add a month of entries together and you have a breakdown of where the food went, not just a total. Our guide to restaurant inventory and food costing shows how that breakdown feeds into your actual food cost.

What reason codes should a restaurant wastage log use?

Keep the list short. With too many codes, staff pick whichever one is first. These four cover most of what a kitchen throws away:

Reason code	What it means	Who logs it	Usual fix
Spoilage	Raw or stored stock went bad before use: expired, mouldy, smelling off, temperature abuse	Storekeeper or whoever opens the cold room	Smaller, more frequent orders; first-in-first-out rotation; check fridge temperatures
Over-prep	Food was prepped or cooked but not sold by the end of its holding time	Station cook at closing	Prep pars based on what actually sold, by day of the week
Plate return	Food went out and came back uneaten or partly eaten	Service captain or steward	Review portion size, recipe or plating; note any repeated complaint
Spill / error	Dropped, burnt, wrong order cooked, contaminated	The cook or server involved	Training, station layout, how orders are taken and read

A fifth code, "other", is fine as long as the entry includes a short note. If "other" starts to fill up, there is a missing code. Add it.

What should each log entry contain?

Six fields, and nothing more:

Date and shift
Item, by the same name used in your stock list or recipe
Quantity and unit (kg, litres, portions, pieces)
Reason code
Logged by
A short note if needed, such as "fridge 2 door left open"

Use the same item names as your inventory. If the store calls it "paneer – 1 kg block" and the log says "cottage cheese", the entries cannot be matched to stock or cost.

Where should the log physically sit?

Put it where the waste happens, not in the manager's office. That could be a clipboard on the cold room door, a sheet by the dishwash area where plates come back, or a tablet or phone entry screen at the pass. A cook who has to walk across the kitchen in the middle of service will not log a spilled ladle of gravy.

Keep a scale near the bin. A weighed quantity is far more useful than "some" or "half tray".

How do you turn the log into less wastage?

Logging alone does not reduce anything. The weekly review does. Here is a simple routine.

Every day: the head chef or kitchen manager reads the previous day's entries. This takes a few minutes. They are looking for anything unusual: a large single entry, a cold room note, an item that shows up on several shifts.

Every week: add up entries by reason code and by item, then convert quantities to rupees using purchase or recipe cost. Pick the single biggest item-and-reason pair and agree one change.

Illustrative example (numbers invented to show the method): a kitchen's weekly review shows over-prep of dal makhani at roughly 4 kg across the week, logged mostly on Monday and Tuesday nights. Spoilage of coriander is next, at about 1.5 kg. The fix for dal is to cut the Monday and Tuesday prep batch and cook a top-up if needed. The fix for coriander is to order smaller quantities more often. The next week's log shows whether either change worked.

Over-prep pars and order quantities are both planning numbers. If your spoilage comes from ordering too much at once, the reorder point formula helps you set when to buy and how much, so stock arrives closer to when it is used.

Weekly review checklist

Totals by reason code compared with last week
Top three items by rupee value of waste
Any item that shows up under more than one reason
Notes that point to equipment, such as fridge, freezer or holding cabinet
One agreed change, with an owner and a date to check it
Last week's change: did the log show a difference?

Common mistakes

Logging only expensive items. Cheap items thrown away every day often add up to more than the occasional costly one. Log everything, then let the review sort by value.

Using the log to blame people. If a spill gets someone shouted at, spills stop being logged. The log measures the system, not the individual. Deal with repeated carelessness separately, in person.

Codes that overlap. If staff cannot tell whether something is "expired" or "spoiled", merge the two. Each code should lead to a different fix.

Never reconciling with the stock count. Every month, compare the logged waste with the shortfall the count shows. If a large gap is still unexplained, the problem is something nobody logs, such as portioning, theft or purchase entries that were never booked.

Changing five things at once. Make one change a week. Otherwise you cannot tell which one worked.

When does a detailed log not pay off?

A very small kitchen with a short menu, where the owner cooks and buys every day, may see the waste clearly without writing it down. A cloud kitchen with heavily pre-portioned stock may waste little until something goes wrong with the cold chain. In both cases a lighter version still helps: log spoilage and plate returns only, and review once a week. You can add more detail when the menu or the team grows.

FAQ

Is a wastage log a replacement for the monthly stock count? No. Keep the stock count, because it checks the books against the shelves. The log explains the gap. If the count shows a shortfall that the log does not cover, the cause is something nobody wrote down, such as theft, wrong portioning or a missed purchase entry. Then you know where to look next.

Who should be allowed to log wastage? Whoever sees the waste happen logs it: line cooks for spills and over-prep, the storekeeper for spoilage, service staff for plate returns. One person, usually the head chef or kitchen manager, reviews the log every day. If only the manager can enter waste, most of it never gets entered.

Should wastage be logged in quantity or in rupees? Log the quantity and unit, such as 2 kg or 6 portions, because that is what staff can see and weigh. Let the system or the weekly review turn quantity into rupees using your recipe and purchase costs. If you ask cooks to work out rupee values during service, the entries get slow and wrong.

What if staff stop logging after the first few weeks? Usually the log is too slow or nobody acts on it. Keep it to under a minute per entry, put the sheet or tablet where the waste happens, and talk about one finding at each pre-shift briefing. Once staff see that an entry led to a change, such as a smaller prep batch, they keep logging.