Growing a crop is only part of the journey to feeding people. Produce still has to be collected, handled, stored and moved to a buyer. When something goes wrong between these stages, the cost includes the resources already invested in production. A useful food-loss project starts with a specific problem and a way to measure it. This guide offers a planning checklist for discussions between growers, suppliers and buyers, rather than a universal storage recipe for every crop.
Define the Problem Before Choosing Equipment
The FAO distinguishes food loss in the supply chain before retail from waste associated with retailers, food service and consumers. That distinction matters when deciding who can change a process. A farm packing team can improve its own handling arrangements, but it cannot independently fix every rejection decision or transport delay downstream.
Choose one product, one journey and one recurring concern. For example, investigate damaged produce arriving at a collection point, rather than announcing a target to eliminate all waste across the business. Write down what counts as a loss, which stages are included and who will review the findings. Keep quality downgrades separate from material that leaves the intended food market entirely.
Map the Actual Journey
Walk through the process with the people who do the work. Record collection points, containers, waiting areas, loading arrangements and the handover to the next business. Ask where produce waits longest, where it is handled repeatedly and where responsibilities become unclear. A simple sketch can reveal a problem that is missing from the official process diagram.
Include the less convenient days. A journey observed during quiet weather with a full team may look very different during a busy harvest or vehicle breakdown. Make notes about the circumstances without blaming individuals. The aim is to understand how the process behaves under pressure, including the workarounds people use to keep it moving.
Build a Baseline You Can Explain
In its food-loss assessment methodology, the FAO describes following a defined load through selected stages and measuring changes in quantity or quality. Use that principle to plan a proportionate baseline with appropriate technical support. Decide what will be measured, when observations happen and how samples will be selected before collecting results.
Do not combine unlike products or compare a quiet week with a peak period without recording the difference. A practical record might include batch identity, quantity entering a stage, quantity leaving it, reasons for rejection and relevant timings. Agree units and categories across the team. A percentage becomes meaningful only when everyone understands its denominator and the boundaries of the measurement.
Separate Symptoms From Possible Causes
A rejection at delivery is a symptom, not automatically proof of where the damage happened. Handling, packaging, delays, product condition and buyer expectations can interact. Record observations and questions separately from conclusions. Photographs taken with permission can help people discuss the same evidence instead of relying on memory.
Ask the receiving business which criteria were not met and whether the problem was visible at an earlier handover. Check that descriptions such as damaged, unsuitable or poor quality mean the same thing to both sides. If evidence points to a technical issue, involve someone qualified to assess that product and process before recommending a change.
Review Storage as a System
The right storage arrangement depends on the crop, its condition, the intended market and the time before dispatch. Avoid assuming that a colder room or a larger building is automatically the answer. Ask a competent specialist to review the relevant product requirements alongside airflow, monitoring, capacity, maintenance and the way staff use the space.
Consider ordinary operating questions as well as equipment specifications. Who notices a fault? What happens during a power interruption? Can the team identify which batches arrived first? Is monitoring information actually reviewed? An investment proposal should explain how the storage system will be operated on a difficult day, including the people and recurring costs needed to maintain it.
Improve Handover Information
A load can be physically well prepared but still delayed because the collection time, quantity or destination is unclear. Agree a concise handover record with the next business. Include the information genuinely needed to identify and handle the consignment, and make clear who must be contacted when a delivery plan changes.
Discuss contingencies before a vehicle is late. Decide how the team will confirm revised arrival times and whether another suitable arrangement is available. Keep those decisions consistent with product-specific requirements and the buyer’s agreed procedures. A useful plan assigns responsibility to a named role rather than relying on somebody noticing a problem and improvising.
Test One Change at a Time
Choose an improvement that addresses the strongest evidence. It might concern container movement, collection scheduling, a maintenance routine or clearer grading instructions. Define the test period and the result that would justify continuing. Where possible, compare similar batches and record other changes that could influence the outcome.
Include the costs of the test. Reduced rejection is valuable, but additional handling, energy, packaging and staff time also matter. Ask whether the change shifts losses to another business or creates a new bottleneck. A useful improvement should make sense across the defined journey, not simply improve one team’s figures by moving the problem elsewhere.
Turn Findings Into a Repeatable Routine
Finish with a short review that people can use. Record the baseline, the change tested, the observed result and the limits of the evidence. Decide who will maintain the new routine and when it will be reviewed. Keep unsuccessful trials too; they can stop the same assumption being tested repeatedly without learning anything.
Share the review with the people who supplied the original observations. Ask whether the written findings reflect their experience and whether the new routine is workable during the busiest part of the season. Their feedback can expose a practical weakness before the process becomes an expectation for every future delivery.
Food-loss reduction is a continuing management task rather than a single purchase. Start with a clear boundary, involve the people at each handover and make comparisons that stand up to questions. That approach gives growers and supply-chain partners a stronger basis for investment, while recognising that different products and seasons may need different solutions.
Leave a Reply