Stop cost, collection density and exception handling determine unit economics more directly than the total volume collected.
Model the stop before the tonne
A return rate can look promising while each visit remains uneconomic. Labour time, travel, container exchange, documentation and failed hand-offs should be measured at the stop level.
Existing routes change the equation
Adding a controlled task to a scheduled service route may avoid a dedicated vehicle, but only if training, dwell time and liability do not overwhelm the saving. The incremental cost must be measured rather than assumed.
Exceptions are part of the base case
Wrong items, missed visits, damaged containers and rejected transfers are predictable operating events. Their frequency and recovery cost belong in the business model from the start.
Keep a minimum cost ledger
Record added minutes per stop, container exchange and depreciation, storage space, onward transport, wrong-item recovery and data-entry time, then connect each cost to the party expected to pay it. Do not assume that recovered-material revenue will fund the route before material grade, accepted yield, buyer terms and transport cost have been measured. Separate fixed development and compliance work from costs that repeat at every stop or container turn.
Use an incremental-cost equation
For a route already being served, calculate incremental cost per accepted unit as: additional labour, travel deviation, container depreciation, scanning and records, storage and onward transport, plus expected exception cost, minus verified recovery revenue, divided by accepted units. Expected exception cost is the probability of each exception multiplied by its recovery cost. This is a management equation, not an accounting standard; define every input and keep taxes, overhead allocation and one-off development cost visible rather than hiding them in a single route-cost number.
Compare three route scenarios
Build a table with dedicated collection, attachment to an existing visit and drop-off aggregation as rows. Use the same columns for stops per hour, accepted units per successful stop, failed-stop rate, minutes added, container turns, transfer frequency and cost per accepted unit. Do not award the existing-route scenario a zero travel cost: record only the avoided dedicated trip, then add any detour, dwell time and capacity loss caused by the new task. The preferred route is the one that remains viable under a conservative wrong-item and failed-visit case.
A 12-week pilot measurement sheet
At each stop record scheduled or unscheduled, arrival and departure timestamps, accepted units, gross and net weight where meaningful, rejected items by reason, container action, scan duration and incident time. At each transfer record sender, receiver, timestamp, quantity variance and acceptance status. Report median and 90th-percentile stop time, not only the average, because a small number of exceptions can determine staffing capacity. Keep environmental outcome calculations outside this sheet until the treatment route and baseline are evidenced.
Primary source and limitation
The EU Waste Framework Directive's EPR provisions identify separate collection, transport, treatment, information and data costs as relevant scheme costs; see the current consolidated text at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02008L0098-20251016. OECD's 2024 EPR principles are at https://doi.org/10.1787/67587b0b-en. Neither source supplies a universal cost per stop. The equation and scenario table above must be populated with measured local route data.