Waste Collection Route Time and Truck Count
Builds a collection route day from stops, setout weight, disposal loads, haul and tipping time.
Example
You enter
- Stops on the route 900
- Seconds per stop 22
- Average setout weight (lb) 40
- Truck payload (tons) 12
- Round trip to disposal (min) 45
- Time at the tipping face (min) 15
- Fixed time in the shift (hours) 0.5
- Break time (hours) 0.5
- Shift length (hours) 8
You get
- Collection time 5.50 h at 164 stops per hour
- Route tonnage 18.0 tons in 2 disposal loads
- Disposal loads 2
- Haul hours 1.5
- Tipping hours 0.5
- Route day 8.5
- Against the shift 0.50 h of overtime, every day
- Available hours 5
- Stops the shift allows 818 stops -- the route is 82 over (10%)
- The day after it crosses 9.50 h -- 1.00 h added in a single step
No published worked example is on file for this calculation. It is checked against a hand-worked derivation of its method and an independent reference test.
Details, formula, and sources
ScopeBuilds a collection route day from stops, setout weight, disposal loads, haul and tipping time, then reports the overtime and the stop count that actually fits. The worked 900 stop route runs 30 minutes long and fits 818 stops; crossing a payload multiple adds a whole haul cycle in one step.
Formula or tablecollection time = stops x seconds per stop; route tonnage = stops x average setout weight; disposal loads = tonnage / payload rounded up; route day = collection + haul + tipping + fixed and break time.
Source and editionElement build-up. The operation's own time study and any applicable collective bargaining agreement govern a standard used to staff or to pay.
Free accessPublic method; the element times are the operation's own measurements.
What governsEstimate. AHJ and licensed professional govern.
API field namesstop_count, seconds_per_stop, setout_weight_lb, truck_payload_tons, round_trip_min, tipping_min, fixed_time_hr, break_time_hr, shift_hours, collection_hours, route_tons, disposal_loads, haul_hours, tipping_hours, route_day_hours, overtime_hours, available_hours, max_stops, next_load_route_day_hours
- Element times entered from the operation's own study rather than assumedfacility time study
- Scope one route on one shift; it does not sequence the route or model trafficspec-v1793 scope