The Route Planner metrics dashboard surfaces everything we capture about how your fleet is running. This article defines every number you'll see, in the order it appears on the page. Hover the ⓘ icon next to any metric in-app for the same definition.
Headline scores
The two scores at the top are 0–100 trend lines. Both use these bands:
Band | Range |
Good | ≥80 |
Fair | 60–79 |
Needs attention | <60 |
Fleet utilization score — How fully each active vehicle is being used on the days it runs. Per-vehicle utilization = route hours ÷ (active days × 8h). Each vehicle is scored individually (Optimized ≥90% → 100, Average 70–89% → 70–99 interpolated, Under-utilized <70% → 0–69 proportional), then averaged. Per-vehicle averaging means a truck that fills its day every time it runs scores well even if it's not dispatched often — the right answer for small-market or on-call vehicles. Inactive vehicles (zero route hours) are excluded. The 8-hour workday is fleet-wide, so part-time or hotshot vehicles may show as under-utilized even when meeting their SLA.
Driver score — A rollup of four customer-facing signals: on-time arrival, POD completion, actual-vs-plan efficiency, and route completion. Each component is on a 0–100 scale (rates × 100; efficiency = 100 when actual ≤ planned, decreasing as actual exceeds planned). Components with no data are skipped. Weighted equally — on-time and completion rate tend to co-vary, a known simplification.
↑ / ↓ vs prior — Points change vs. the same-length window immediately before the selected range. A 30-day view compares against the prior 30 days.
Stat cards
Totals across the period. The % change next to each compares to the same-length window right before it — hover to see the exact prior-period dates.
Card | What it shows |
Routes completed | Total routes finished in the period |
Stops served | Total stops visited across completed routes |
Distance (mi) | Total miles driven on routes |
Route hours | Total PMH across the fleet |
Avg. duration | Total hours × 60 ÷ total routes |
Avg. stops / route | Total stops ÷ total routes |
Fleet utilization
Per-vehicle utilization = route hours ÷ (active days × 8h), bucketed:
Bucket | Range | Meaning |
Optimized | ≥90% | Consistently running close to a full shift |
Average | 70–89% | A fair amount of slack |
Under-utilized | <70% | Lots of idle time on working days |
Inactive | 0 route hours | Didn't run in the period |
Inactive vehicles are listed separately so they don't drag the fleet score down — but they're still surfaced, since unused trucks are still a cost.
Deployment rate — (vehicles with any route hours) ÷ (total vehicles). Complements the utilization score: a fleet can run its active trucks hard while half the lot stays parked.
PMH (paid mile hours / route hours) — Productive time. Wheels turning on a route, not clocked-in time — gaps, lunch, and depot returns aren't included.
SMH (scheduled mile hours) — Available time. Active days × 8h. Used as the utilization denominator. Shorter or longer real shifts will skew this; reach out to your account team if a per-account workday would help.
Active days — Calendar days the vehicle or driver ran at least one route. Lets utilization measure how full each working day was, not how often the resource was dispatched.
Driver score inputs
On-time arrival rate — On-time stops ÷ on-time-eligible stops. Stops without a delivery window aren't eligible. Small fleets can swing significantly on a handful of late stops — check the count tooltip for sample size.
POD completion rate — Completed task instances ÷ required task instances, across every task type configured for your account. Persistently low rates trigger an alert.
Actual vs. plan — (actual − planned) ÷ planned, averaged across routes. Negative = faster than planned, positive = slower. Large positive values usually mean over-stuffed routes, unexpected traffic, or stops taking longer than the configured dwell time. Only includes routes with both a planned and actual duration.
Completion rate — Completed ÷ attempted routes. Cancelled, abandoned, or failed routes pull it down.
Driver performance table
A per-driver view of the period:
Column | What it shows |
Routes | Routes completed |
Stops | Stops visited |
POD | POD completion rate (inline bar = 0–100% fill) |
On-time | On-time arrival rate, only on stops with a delivery window |
Hours | Route hours (PMH) |
Mileage | Miles driven on routes |
Inactive drivers — Drivers in your roster with zero route hours in the period. Listed separately at the bottom so coaching focus stays on active drivers.
Driver leaderboard — Ranks drivers by route activity. Surfaces top performers and workload imbalance.
Trends over time
Routes over time — Routes per time bucket (day / week / month). With multiple accounts and By Branch on, each branch is a line; with Aggregate, buckets are summed across branches.
Avg routes by weekday — Mean route count for each Mon–Sun. Surfaces weekly seasonality so dispatchers can match staffing to peak days.
Route efficiency
A side-by-side look at planned vs. actual execution.
Avg. planned duration — Route Planner's estimate, in minutes.
Avg. actual duration — Real start-to-finish, in minutes.
Avg. dwell time — Average time at a stop before departing. High dwell can mean stops need more service time configured, or process issues at the destination.
Vehicle utilization (per vehicle)
Same bucketing as the fleet view (Optimized ≥90%, Average 70–89%, Under-utilized <70%, Inactive at zero).
Util % — PMH ÷ SMH. Days the vehicle didn't go out aren't counted, so this reflects how full a working day was.
Mileage (per vehicle) — Total miles on routes, with typical-day mileage (total miles ÷ active days) for context.
Routes per vehicle — Routes completed per vehicle, busiest to least. Surfaces workload imbalance.
Hours per vehicle — Route hours per vehicle. A clearer workload view than route count since route lengths vary.
Miles per vehicle — Road miles per vehicle. High-miles, low-hours = long-haul; the inverse = dense urban delivery.
POD compliance
POD overall completion — Completed task instances ÷ required task instances, across all task types. Low numbers usually mean a coaching or process gap rather than a technology issue.
POD task breakdown — Completion rates per individual POD task type (photo, signature, notes, scans). Helps identify which step drivers are skipping.
POD failure reasons — When a delivery can't be completed, drivers pick a reason — ranked by frequency. Separates recipient issues (not home, wrong address) from goods issues (damaged) and dispatch issues (out of service area).
Alerts & observations
Alerts are colored by severity:
Color | Severity | Meaning |
Red | At Risk | Below threshold — needs attention now |
Yellow | Warning | Trending toward a problem |
Green | Positive | Healthy trend or improvement |
Blue | Info | Pattern observation, no action required |
What triggers an alert:
Trigger | Condition |
Workload skew | Top driver logs ≥1.3× the fleet-average route hours. Only evaluated for a single account. |
Route volume growth | Second-half route volume >5% above first-half. Requires ≥4 buckets to evaluate. |
POD below threshold | Fleet POD < 70%. Surfaced as At Risk (red). |
Peak day | Calls out the weekday with the highest average route count. Info only. |
Controls
Date range — The window the dashboard reports against. Default is the last 90 days.
Aggregate vs. By Branch — When multiple accounts are selected, sums into a single fleet view or splits per account. (The fleet utilization score is always computed against the full fleet regardless.)
Driver filter / Vehicle filter — Scope every section to a subset. Disabled when multiple accounts are selected.
Questions about a number you're seeing? Reach out to your account team.