Baseline
Miles per stop, stops per route-hour, overtime, and service-window hit rate, by route and by day, from your own data.
Route & operations consulting
Routing problems with no obvious answer. We find one.
Miles per stop, route density, service windows, overtime. When fixing one breaks another, that is the conundrum. We model the whole system, then hand you a plan you can run on Monday.
- Who we serve
- Waste haulers, municipal fleets, field service
- How we work
- Assess, model, implement, measure
- Tools
- ArcGIS, Python, your routing software
- Rebalanced route
- Current route
- Miles / stop
- 0.42-18%
- Stops / route-hr
- 27.6+11%
- Overtime hrs / wk
- 6.5-54%
- Route A
- Route B
- Route C
- Stops / route (spread)
- 212–318→ 260–271
- Boundary crossings
- 41→ 4
- Route-hrs variance
- 2.6h→ 0.4h
Why it's a conundrum
Every fix moves the problem somewhere else.
Routing is a system. Pull on one part and another part tightens. That is why the obvious answer is so often the wrong one, and why we model the whole operation before we recommend anything.
- Move these customers to Tuesday Tuesday is now overloaded
- Reduce miles Driver time goes up
- Add stops per route Service time becomes the bottleneck
- Close a disposal facility Every route changes
- Cluster geographically Frequency, capacity, service windows, and driver constraints push back
Bring us questions like these
The ones without a clean answer.
- 01
How do we service 1,200 customers with 14 trucks while keeping overtime below 5%?
- 02
Why are these routes technically efficient but consistently two hours over plan?
- 03
How do we reroute 8,000 customers after closing a facility?
- 04
Which customers should move to another service day without creating a new problem somewhere else?
What you get
Artifacts you can act on, not a slide deck.
Every engagement produces the same four things. They are built from your data and they stay with you.
Density map
Where your stops actually are versus where your routes actually go, with the boundary crossings and backtracking made visible.
Scenario comparison
Two or three rebalanced plans with the trade-offs quantified, so the decision is yours and the consequences are known in advance.
Implementation plan
Day codes, sequence files, and customer notifications ready for your routing software, plus the metrics we will watch for the first eight weeks.
- Weekly StPR
- Pre-change baseline
- Baseline StPR
- 22.2
- Week 14 StPR
- 27.6+24%
- Weeks to stabilise
- 4
How we work
Four steps. The last one is the one most people skip.
- 01
Assess
Stop history, day codes, service boundaries, constraints. We establish the baseline before touching a route.
- 02
Model
Scenarios built on the whole system, so fixing one thing does not quietly break another.
- 03
Implement
We work next to dispatch and drivers through go-live. The plan has to survive a real Monday.
- 04
Measure
Weekly metrics against the baseline until the change holds. If it drifts, we find out why.
Where the problem shows up
Same conundrum, different fleet.
Our depth is waste. The method transfers to any operation with trucks, stops, and constraints that fight each other.
Waste Management
Residential density, commercial windows, roll-off dispatch, and facility changes that ripple through every route.
Waste routing servicesMunicipal Services
School buses, plows, and public works fleets with coverage requirements that do not bend to convenience.
Municipal servicesFleet Service Operations
Grease, propane, laundry, and other recurring service fleets losing margin to spread-out stops and overtime.
Fleet service operationsWho you'll work with
Practitioners, not account managers.
Conundrum is a small team of operations and analytics practitioners. The people who scope your problem are the same people who build the model and stand next to your dispatchers when it goes live.
More about how we workStart with the baseline
Bring us the routing conundrum.
Tell us what you are trying to change and what keeps getting in the way. We will come back with the questions we need answered and what the analysis would cover.
Get a Route Efficiency Analysis