Spot under-dense routes costing you money with a weekly density report
Every Monday, WebRun opens Onfleet Analytics, pulls the prior week's completed route data broken down by driver and delivery zone, calculates stops-per-mile and stops-per-hour density ratios, and writes a ranked zone-by-zone density report to Google Sheets so your planning team can identify and tighten under-dense corridors.
- No credit card
- Under $0.01 per run
- Cancel anytime
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
onfleet.com/dashboardin a real browser with your saved login - no setup, no API keys. -
1
Onfleet - pull prior-week route mileage and stop counts by zone
onfleet.com How to Automate Onfleet
WebRun opens Onfleet to pull prior-week route mileage and stop counts by zone. - Open Onfleet Analytics for the prior calendar week
- For each team or delivery zone, capture total stops completed, total mileage, and total time on route
- Calculate stops-per-mile and stops-per-hour for each zone and for each individual driver
Done when Density metrics are calculated for every active zone and driver from the prior week.
-
2
Google Sheets - log ranked route density report
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log ranked route density report. - Open the route density Google Sheet
- Append a dated weekly section with each zone ranked from lowest to highest stops-per-mile
- Highlight any zone falling below your density threshold in red for planning team attention
Done when A ranked density report for the prior week is logged in Google Sheets and available for the planning meeting.
How do I automatically report route stop density from Onfleet to find inefficient corridors?
WebRun pulls Onfleet route data every Monday and calculates stops-per-mile and stops-per-hour for each delivery zone and driver from the prior week. It logs a ranked density report to Google Sheets, highlighting under-dense zones below your threshold so planning teams know exactly which corridors to tighten before next week's routes go out.
- Under-dense routes identified every Monday before new routes are planned
- Per-zone ranking shows exactly which corridors waste fuel and driver time
- Trending history in Google Sheets tracks whether density improvements are holding
Built for last mile delivery planners · fleet operations analysts · logistics directors · courier company route managers
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
What is a good target for stops-per-mile?
Benchmarks vary by delivery type - urban grocery runs often target 4 to 8 stops per mile while suburban courier routes may average 1 to 3. Set your own threshold in WebRun based on your operation's historical norms so the report flags what is genuinely under-dense for you.
Does it include only dispatched routes or also manually completed tasks?
It reads all completed tasks in Onfleet for the period, regardless of whether they were routed by Onfleet's optimizer or assigned manually by a dispatcher, giving you a true picture of how routes ran in practice.
Can it break down density by day of the week, not just the weekly average?
Yes. If you add a day-of-week column to your Google Sheet, WebRun can log a row per day rather than a weekly rollup, so you can see whether Monday routes are consistently sparser than Friday runs.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.