# What does this week's waste log actually show? A restaurant owner has a week of waste entries and wants to see what was recorded before changing an order or prep list. The first job is to make the numbers legible and expose the gaps. This fictional example uses a small handwritten-style log. The amounts and reasons are invented for the walkthrough. Canonical: https://areinum.com/examples/restaurant-waste-log-review/ Language: en Updated: 2026-10-31 ## Fictional example The owner's request: Summarise this week's waste log by ingredient and recorded reason. Flag anything that cannot be counted. Information provided: - Fictional log: tomatoes 1.2 kg overripe and 0.8 kg prep surplus; bread four slices stale and two slices with no reason; soup with no quantity or unit. Example result: Tomatoes: 2.0 kg total, split between the two recorded reasons. Bread: six slices total, including two with no recorded reason. Soup: quantity and unit missing, so excluded from quantity totals. The next step: The owner decides which incomplete entries to check and whether the recorded pattern warrants a closer look at prep. ## Start with the quantities staff recorded On Monday, the log records 1.2 kg of tomatoes as overripe. On Wednesday it records another 0.8 kg of tomatoes as prep surplus. Bread appears twice: four slices marked stale and two slices with no reason entered. A soup entry has no quantity or unit. Those labels are the reasons entered in the log. They do not explain, by themselves, why too many tomatoes were prepared or why bread went stale. ## Add quantities that can be compared A prepared summary could show tomatoes at 2.0 kg in total, with 1.2 kg recorded as overripe and 0.8 kg as prep surplus. Bread totals six slices, of which four were marked stale and two have no recorded reason. The soup entry remains outside the quantity totals until someone can confirm its amount and unit. Kilograms and slices stay on separate lines. ## Decide what is worth looking at next The owner might ask the relevant shift about the two bread slices and the soup entry, then compare the tomato log with the restaurant's prep notes. That is a starting point for a conversation; the entries alone do not establish the underlying cause. The owner decides whether a change to prep or ordering is appropriate. The summary does not place an order or alter production. ## Leave missing details open If the soup quantity cannot be recovered, it remains an incomplete entry. A clear list of what was recorded and what was not is still useful for the next review. ## Questions you may have ### Can different units be combined into one waste total? Not meaningfully in this example. Tomatoes are measured in kilograms and bread in slices, so each has its own total. ### Do the recorded reasons explain the underlying cause? They show the reasons staff entered for individual items. The owner may need other information to understand why the waste happened. ### What should happen to an entry with no quantity? Keep it on the review list as incomplete. Do not invent a quantity or include it in a numerical total. ## Sources and further reading - [Working to reduce food waste](https://www.restaurant.org/education-and-resources/resource-library/working-to-reduce-food-waste/): The National Restaurant Association discusses recording food waste details for production and purchasing planning. - [How do I do expenses, wastage logs and inventory for my restaurant?](https://www.reddit.com/r/restaurant/comments/1b2v658/how_do_i_do_expenses_wastage_logs_and_inventory/): A restaurant discussion asks about expenses, waste logs and inventory. ## Related reading - [AI for restaurants and cafés: review food costs and cash differences](https://areinum.com/ai-for-restaurants-and-cafes/) - [Find the information behind an answer](https://areinum.com/product/data-checks/) - [How to check work prepared by AI](https://areinum.com/guides/check-work-prepared-by-ai/) Explore the demo: https://platform.areinum.com/ See how Areinum approaches this work. Demo access may need to be arranged.