Waste collection routing is mathematically different from delivery routing, and applying delivery software to it produces plans that look reasonable and perform badly.
Arc routing versus node routing
Delivery routing is node routing: visit a set of points, in any order, minimising travel between them.
Residential waste collection is arc routing: service every street segment, ideally without traversing any twice. The work is on the road itself, not at points along it.
The practical differences:
- Collection happens continuously along a street, not at discrete stops
- Both sides of the street may be serviced in one pass or require two, depending on vehicle and local practice
- One-way streets, turn restrictions and dead ends drive the plan far more than in delivery routing
- Reversing is dangerous and often prohibited, making route geometry critical
- Vehicle fill increases progressively along the route, and disposal trips must be planned into it
Commercial waste collection is closer to node routing — discrete containers at business premises — which is why some general routing tools work adequately for commercial and poorly for residential.
Ask directly: does your engine solve arc routing, or does it approximate street collection as a series of stops?
The constraints that matter
| Constraint | Effect |
|---|---|
| Vehicle capacity by weight and volume | Determines disposal trip timing |
| Disposal site locations and hours | Route must include tip trips |
| Compaction ratio by material | Volume capacity varies with waste type |
| Collection frequency by material stream | Multiple overlapping schedules |
| Time restrictions | Noise ordinances, school zones, commercial hours |
| Vehicle access | Narrow streets, height restrictions, weight limits on bridges |
| Crew size and configuration | Affects service rate per property |
| Reversing prohibitions | Safety-driven, and it shapes route geometry |
| Assisted collections | Specific properties requiring extra service |
| Missed collection returns | Reactive work inserted into fixed rounds |
Multiple waste streams
Modern collection runs several streams — residual, recycling, organics, glass — each with its own frequency, vehicle type and disposal destination. This creates a scheduling problem on top of the routing problem:
- Alternating week collections
- Different vehicles for different streams
- Shared crews across streams
- Contamination handling and rejection procedures
- Bulky and special waste as separate work
Software must handle the calendar as a first-class concept, not as an afterthought.
Commercial collection
Different again, and closer to conventional route management:
- Container service at business premises, with container sizes and types
- Service frequency by contract
- On-demand and extra lifts
- Container placement, exchange and removal as separate work types
- Contract billing linked to service events
- Proof of service, increasingly with photographs
- Weight capture per lift, where the vehicle supports it
Weight capture matters commercially: charging by weight rather than by lift changes both the customer relationship and the route economics.
Municipal considerations
Public sector collection adds requirements that private operators do not face:
- Service level transparency — published collection calendars, missed collection reporting
- Citizen communication — collection day changes, holiday schedules, service alerts
- Public reporting on tonnages, recycling rates and service performance
- Procurement transparency in software selection
- Equity of service across neighbourhoods, which constrains optimisation
- Political sensitivity to collection day changes, which are genuinely disruptive to residents
That last point is operationally significant: a mathematically optimal round redesign that changes collection day for thousands of households carries a real communication cost and a real political cost, and it should be planned as a public communication exercise rather than as a routing exercise.
Metrics
- Properties or lifts per vehicle hour
- Tonnage per route
- Distance per tonne collected
- Repeat traversal percentage (arc routing efficiency)
- Missed collections per 100,000
- Contamination rate by stream
- Disposal trips per route
- Fuel per tonne collected
Frequently asked questions
Can general route optimisation software handle residential waste collection?
Poorly, for residential street collection, because it models the work as discrete stops rather than as street segments. Commercial container collection is closer to conventional routing and is served adequately by more general products.
How often should collection rounds be redesigned?
Rounds drift as housing stock, participation rates and waste composition change — a review every few years is typical, with more frequent adjustment where development is rapid. The constraint is usually the communication cost of changing residents' collection days rather than the analysis.
What is the biggest efficiency lever in waste collection?
Round balancing and reducing repeat traversal, followed by optimising disposal trip timing so vehicles are not driving to the tip half full. Both require a routing engine that understands the actual collection model.
How do we handle missed collections?
Track them by cause — access blocked, bin not presented, crew error, vehicle failure — and route returns efficiently rather than dispatching individually. Missed collection returns are expensive and the cause analysis usually reveals a small number of correctable problems.
Does weight-based charging change routing?
For commercial collection it changes the economics of each lift and makes container-level weight capture valuable. For residential it is politically sensitive and rarely implemented, but where it exists it changes participation behaviour and therefore route loads.
