How to use the Food Waste Log Analyzer.
A food waste log should distinguish preparation loss, spoilage and plate waste. Use consistent units and time periods, and investigate patterns before claiming a cause or calculating avoidable savings.
Make the workflow fit your task.
Group waste records by type, ingredient, date and consistent unit, then calculate totals and shares. Separate observed patterns from possible causes and keep cost estimates tied to actual purchase data. Choose a focused follow-up rather than assuming all waste is avoidable.
- What you provide
- Recorded waste quantities, reasons and costs.
- What you get
- Patterns and reduction hypotheses from supplied data.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
One week records 2 kg preparation trim, 3 kg spoiled produce and 1 kg plate waste.
Completed example
Total recorded waste: 6 kg. Spoilage accounts for 50% by weight. Review purchasing, storage and demand for the spoiled items; the log alone does not establish the cause or monetary value.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should preparation trim automatically count as avoidable food waste?
Some loss may be inherent to the process. Classify it and review yield before assigning an avoidable amount.
Why does a high spoilage total not establish a storage failure?
Demand, ordering, handling or other factors may contribute. Investigate with additional records before naming a cause.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑