Restaurant waste: two weeks of logging that pays for itself

Food waste is money that was purchased, stored, prepared and then thrown away — so it costs more than its purchase price. Most restaurants know they waste and do not know what.

The fix is a two-week log, and it is more effective than it sounds because the act of writing something down changes the behaviour that produces it.

The four categories

Log every discard under one of these. The categories matter because each has a different fix.

1. Spoilage. Food that expired or turned before use.Fix: ordering quantity and rotation.

2. Over-production. Prepared and not sold.Fix: prep lists and par levels.

3. Preparation loss. Trim, peel, mistakes, burnt items.Fix: technique, training, portion tools.

4. Returns and remakes. Made, sent out, came back.Fix: quality checks and order accuracy.

How to run the log

A clipboard by the bin. Four columns: item, quantity, category, initials. That is the whole system — a form that takes ten seconds beats an app that takes two minutes and gets skipped.

Two weeks. Every shift. No blame in week one — if staff think the log is for catching them, they will stop logging and you will learn nothing.

At the end, total by item and by category.Almost always, two or three items account for most of the value. Those are your project; ignore the rest for now.

What the results usually say

Over-production dominates in cafés and bakeries. Baked and prepared items made to a habit rather than to a forecast.

Spoilage dominates where delivery frequency is wrong. Fresh product arriving weekly that should arrive twice a week, or vice versa.

Preparation loss dominates where training is uneven. One shift's yield is noticeably worse than another's — which is a training finding, not a discipline one.

Returns dominate where delivery is a large share. Food that travels badly. This is a menu decision. Seedelivery commission maths.

Par levels and prep lists

The single highest-return fix for over-production.

Apar level is how much of a prepared item you should have at the start of service. It comes from sales data — your POS knows how many you sold on a Tuesday for the last eight Tuesdays.

Aprep list is generated from the par level minus what is already on hand. The kitchen prepares the difference, not a habitual amount.

Reviewing par levels monthly against actual sales turns over-production from a recurring loss into a managed number.

Ordering and rotation

• Order to par, not to a round number that fills the box
• First expiry, first out — and label everything with the date it was prepared, not the date it was delivered
• Match delivery frequency to shelf life. A product with a three-day life delivered weekly will be wasted by design.
• Check the delivery. Short-dated product accepted at the door becomes your waste.

What your POS should do

• Record waste with a reason and a cost, so it appears in your food cost properly
• Show theoretical versus actual usage so you can size the gap. Seefood cost control
• Produce sales history by day of week for par-level setting
• Track expiry dates on stock where relevant
• Report waste by item and category over a period

The Ramadan and seasonal caveat

Waste patterns change completely in Ramadan — different hours, different volumes, and a buffet model if you run one. Run a separate log during it; the par levels from an ordinary month will be wrong.

What good looks like

Most restaurants that run this log properly find a 20–40% reduction in logged waste within a month, mostly from over-production. On a restaurant spending SAR 120,000 a month on food with 6% waste, cutting it to 4% is SAR 2,400 a month — recurring, for the cost of a clipboard and two weeks of attention.