Fleet Utilization Report

This guide helps you understand and act on insights from the Fleet Utilization report. It enables you to evaluate how actively your fleet is being used, identify under- or over-utilized vehicles, and uncover inefficiencies in driving patterns, idling, or route planning.

Utilization Overview

1. Active utilization rate (%)

The average share of a 24-hour day that vehicles were used (ignition on), calculated only on days with one or more trips. This provides a fleet-wide view of how intensively vehicles are used on the days they are actually operating.

• A 25% utilization rate equals roughly 6 hours of daily engine-on time on active days.
• A higher utilization rate means vehicles are spending more time in active operation (driving or idling) on days when the fleet is in use.
• A lower utilization rate suggests long periods of vehicle inactivity, possibly indicating underutilization, inefficient scheduling, or excess fleet capacity.

Using the numbers 💡

• Consistently low utilization (e.g. below 10–15% ~ 2.5-3.6 hours) suggests your vehicles may be underused when deployed.
• If the number of active vehicles increases and the average utilization rate drops, it may indicate inefficient distribution of work for the added vehicles (e.g. shorter trips, excessive idling, or over-dispatching).
• Compare with trip counts, engine hours, and idling to understand what’s driving low usage.
• Deep dive into the utilization rate for individual vehicles in the table view.

Drive time

1. Avg. daily drive time

The average time each vehicle spends in motion with the engine on, excluding idle time. Calculated per day across the selected fleet, team(s), and time range.

This metric helps you understand how actively vehicles are being driven — regardless of how far they travel.

Lower values may indicate vehicles are being used lightly or inefficiently, while unusually high values can point to overworked vehicles or long driving shifts.

2. Total drive time

The total amount of time all vehicles were driven, excluding idling, during the selected date range, across the chosen fleet or team(s).

Use this to monitor overall driving activity and operational load over time. The chart shows daily breakdowns for deeper insight.

Idling

Idle time begins when a vehicle has had a speed below 1 km/h and the engine RPM has been above 300 for 180 seconds.

⚠️  Only ICE (internal combustion engine) vehicles are included in idling data.

1. Avg. daily idling

The average time per day that ICE vehicles are idling, i.e. the engine is running but the vehicle is not moving. Measured per vehicle across the selected date range.

High idling time contributes to fuel waste, higher emissions, and unnecessary engine wear. Use this insight to identify and address inefficient driving or waiting habits.

2. Total Idling

The total idling time for all ICE vehicles in the fleet. The daily chart helps visualize whether idle times are increasing, stabilizing, or decreasing.

Distance

1. Avg. daily distance

The average number of kilometers driven per vehicle per day. This metric reveals how much each vehicle is being used and helps identify over- or underutilization.

Use this data to balance usage across the fleet or determine whether some vehicles could be retired or reassigned.

2. Total distance

The total number of kilometers driven by the fleet or selected team(s) in the selected period. A helpful indicator of operational scale. High distance with low utilization may suggest uneven vehicle use or inefficiencies.

Using the numbers 💡

Use the Distance data to understand how much your fleet moves — but combine it with other metrics to uncover why.

• Combine with utilization rate

  Low average distance per vehicle alongside high utilization suggests engines are on but vehicles aren’t covering ground—likely frequent stops, congestion, or idle periods. High distance with low utilization points toward long, steady routes where vehicles spend little time running when parked.

• Cross‑check with engine hours

  High engine hours + low distance indicates slow average speeds or stop‑and‑go traffic; low engine hours + high distance signals efficient cruising with limited time spent running in traffic or during stops.

• Identify under‑ or over‑used assets

  Filter by team to find vehicles that consistently log much less—or much more—distance than the fleet average. Consider rebalancing assignments or rotate vehicles to spread wear.

• Spot demand cycles

  Rising distance over weeks or months with a steady fleet size flags growing workload; declines may foretell slack periods. Adjust staffing, capacity, and maintenance windows accordingly.

• Validate route efficiency

  Increasing average distance while trip count stays flat means routes are getting longer—check for detours, wider service areas, or routing drift. Increasing trip count with flat distance shows denser delivery patterns that might benefit from batching.
  
  

Trips

1. Avg. Trip Distance

The average distance per trip, helping assess how far vehicles typically travel at a time. Short trips with high idling could point to inefficiencies in routing or delivery scheduling.

2. Avg. Trip Duration

The average time per trip, measured in minutes and seconds. Use this alongside distance to assess average speeds and usage patterns.

3. Avg. Daily Trips

The average number of trips per vehicle per day. Use this to assess whether vehicles are being efficiently routed or overloaded with small stops.

Using the numbers 💡

• Combine with distance

  • High trips / low distance: vehicles are doing many short stops—efficient for dense routes but increases start‑stop wear and potential idle time.
  • Low trips / high distance: fewer, longer runs—check whether this aligns with service goals or indicates route creep.

• Compare with engine hours

  • Low trips + high engine hours + high distance: long‑duration jobs (likely expected for long‑haul work).
  • Low trips + high engine hours + low distance: inefficient scheduling or prolonged waiting/idle periods between short tasks—review dispatch timing and idling metrics.

• Watch trip duration trends

  Rising average duration while distance stays flat suggests congestion, route detours, or on‑site delays. Consider rerouting or rescheduling to avoid peak traffic.

• Assess load distribution

  Large differences in daily trip counts across teams or vehicles reveal workload imbalances. Reassign tasks to prevent under‑ or over‑utilizing specific assets.

• Look for scheduling gaps

  Many short trips coupled with high idle time between them indicates opportunities to batch deliveries or tighten schedules, reducing non‑productive engine hours.