
By Jonathan Anthony Burkett
Reporting and original analysis | November 18, 2026
A container of unused food is visible at the end of a shift. The decisions that helped produce it may be much less visible: an order based on an old pattern, a preparation quantity chosen before an update arrived or a handover that did not mention a change. Counting the unused amount is a useful beginning. Preventing a repeat requires asking how the organization reached that amount and which part of the process can respond. A waste record becomes more valuable when it can travel back toward a decision someone is able to examine.
ISO’s current COP31 brief on food loss and waste identifies ISO 20001:2026, published in September, as a management system standard dedicated to the subject. The brief describes measurement, investigation of causes, responsibilities, preventive action and progress tracking across the food value chain. This is a current implementation discussion about an existing standard, not an announcement that the standard was published today. The following is original operational analysis. It does not report a tested intervention or provide a clause-by-clause account of a standard whose full requirements are not reproduced here.
Begin with a record that can be interpreted
Consider a hypothetical café recording leftover prepared portions. If one day shows twenty unused portions, the number invites questions rather than supplying an answer by itself. How many portions were prepared? Which service period does the record cover? Were the portions counted consistently? The example uses invented quantities solely to illustrate interpretation. It does not represent an actual café or measured performance. A useful record keeps enough context to distinguish an apparent change from a real change in the operation being examined, while avoiding the unnecessary collection of personal customer information.
The unit matters. A record in portions is not automatically comparable with one in kilograms or monetary value. Each can answer a different question, and converting among them requires an explicit basis. A business might choose one measure for an operational task and another for financial reporting. The danger is presenting the figures as interchangeable without explanation. This is a general measurement observation, not a statement that the standard mandates a particular unit. The organization needs a method that fits its purpose and remains understandable to the people who record and use the information.
The boundary of the record also needs attention. Does the count concern preparation leftovers, damaged incoming stock or another category? Combining different sources of loss into one total may conceal which decision needs review. A broad total can still be useful for some purposes, but a practical response may require a more specific breakdown. The aim is not to create categories indefinitely. It is to give the next person enough information to ask a productive question about what happened, rather than expecting a large number to explain its own origin.
Follow one example through the handover
Suppose the café’s expected demand changed, but the person preparing the food received the update late. The unused portions might then reflect a communication problem as well as a quantity decision. A discussion that begins and ends with blaming the person at the counter would miss that possibility. The people involved can reconstruct the sequence: when the estimate changed, who knew and how the information was supposed to reach preparation. This is a hypothetical process review. It establishes no finding about a real workplace or about the cause of any recorded loss.
The review can identify a small preventive change to investigate. Perhaps an update needs to be confirmed before a particular preparation decision. The organization would still need to evaluate whether that change fits the work and how its effect would be assessed. It would be premature to call the idea successful merely because the explanation sounds convincing. The next record should help test what happened under the revised process. A proposal, an implemented change and a demonstrated improvement are different stages, each deserving wording that matches the evidence available.
Responsibilities should be understandable to the people carrying them. Assigning someone to reduce waste without specifying their authority may leave them accountable for decisions they cannot change. A preparation team might see the leftovers while an ordering decision is made elsewhere. Coordination then matters more than a slogan attached to one role. ISO’s brief emphasizes action across the value chain, including processing, storage and logistics. The practical inference is to look beyond the point where unused food becomes visible and identify the decision-makers whose information or choices bear on the problem.
Compare progress without hiding a changed situation
A lower total in a later period may have several explanations. Demand may have fallen, fewer portions may have been prepared or the recording method may have changed. An honest progress account explains the conditions relevant to the comparison. That does not make improvement impossible to demonstrate. It makes the demonstration more informative. A reader should be able to understand whether the organization is describing an absolute total, a rate or a particular part of the process. The strongest claim is one whose scope remains visible beside the number.
The BSI launch announcement of September 30 similarly describes ongoing monitoring, documented processes and continuous improvement. Reading an announcement is not equivalent to implementing the standard or establishing certification. An organization making such a claim would need evidence appropriate to it. For readers outside the business, a useful question is how the reported figure connects to an actual change in work. A named framework can organize that work, but the name alone does not show what changed, who carried it out or how the result was checked.
The operational value of this discussion lies in the route from a visible remainder to an examinable decision. Define the record, preserve its context and follow the sequence that produced it. Then give a proposed change an owner, a purpose and a way to be evaluated. Food loss and waste prevention involves real processes that differ across settings. A practical account should make those processes easier to inspect, rather than replace them with a confident total whose relationship to everyday work remains unexplained.
Image note: Illustrative stock photograph about documenting an operational question; not a food-waste audit, certification record or measured improvement. Credit: Barbara Olsen / Pexels. Source photograph; Pexels license.
#upstormed #jonathananthonyburkett #jonathanburkett #ISO20001 #FoodWaste




Leave a Reply