Waste Report demand analysis
Stage 2 · Analysis
The operator jobs behind Waste Report searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Define what the report measured
Select the Kitchen, period, Waste event scope, quantity units and inclusion rules before showing totals.
A report must disclose coverage and measurement method. Unrecorded Waste is missing evidence, not zero.
Evidence: restaurant food waste measurement · food waste measurement hospitality
- 2
Understand where and why Waste occurred
Group recorded Waste by item, type, reason, source, operational stage, Station or service context.
Groups use event-time facts and stable references. Unknown reasons remain an explicit category rather than being inferred.
Evidence: restaurant waste by reason report · food waste by kitchen stage
- 3
Compare compatible physical quantities
Aggregate weight, volume or count only where the units are directly compatible or a trusted conversion exists.
Unlike units and item counts cannot be combined into a meaningless grand total.
Evidence: food waste tracking by weight restaurant · kitchen waste log analysis
- 4
Show supported Waste cost separately
Resolve cost for eligible events and expose cost coverage alongside unknown-cost Waste.
Cost is derived from authoritative item evidence with compatible units. It must not be applied to events lacking that evidence or labelled accounting loss.
Evidence: food waste cost report · restaurant waste percentage
- 5
Compare trends without inventing causes
Compare equivalent periods, reasons and operational contexts to identify repeated recorded patterns.
A pattern supports investigation. It does not prove a cause, avoided cost or reduction outcome.
Evidence: food waste trend dashboard · compare restaurant waste periods
Record map
Evidence the capability owns, references, or derives
kitchen.waste-report.events
Waste events
Owner: Waste
Waste Report reads canonical Waste events and cannot fill missing events or rewrite their observations.
- event identity and occurrence
- quantity and unit
- reason and source
- operational references
kitchen.waste-report.summary
Waste report
Owner: Waste Report
The report derives compatible grouped quantities and supported cost coverage without becoming a second Waste record or accounting loss.
- Kitchen-local period
- grouping and unit semantics
- event counts and quantities
- supported costs and coverage
- comparison scope and exclusions
Required record questions
What must Waste Report make knowable?
- Which Kitchen, owner-local period and Waste-event inclusion rules define the report?
- How many recorded events exist and what known collection gaps remain?
- Which Waste types, reasons, sources, stages, Stations, services or items are grouped?
- Which quantity units can be aggregated directly and which must remain separate?
- Which trusted conversion source, if any, permits another aggregation?
- Which event costs resolve from authoritative Ingredient, Recipe, Dish or Drink evidence?
- What proportion of events and physical quantity has supported cost coverage?
- Which currency groups must remain separate?
- Which comparison period has equivalent scope and measurement semantics?
- Which pattern is an observation rather than a proven cause or saved amount?