# Fleet Activity The **Fleet Activity** tab gives you an at-a-glance read of how hard your fleet is working: who is leaving on time, how vehicles are being used through the week, what fuel they are burning, and where they are spending their time. It is the operational counterpart to the Compliance tab. > **Permissions:** Any user with the **Dashboard** permission can open this tab. KPI tiles, charts, and lists are scoped to the depots, fleets, and cost centres your role grants you access to. > **Note:** Fleet Activity and Safety Overview show the last 30 days. There is currently no date picker on these tabs. To open the tab, click **Dashboard** in the sidebar, then select **Fleet Activity** from the tab strip.
## The KPI strip The strip across the top of the page is a row of summary tiles. Each tile shows a headline value, a unit, and a delta against the previous period. Tiles use colour and an icon to signal whether the metric is healthy, slipping, or in trouble: * A green tone indicates the metric is on or above target. * An amber tone indicates a watch-list metric. * A red tone indicates a metric that is failing. * A muted tone is used for purely neutral counts. Typical tiles include the count of active vehicles, on-time departure performance, idle time, distance covered, and fleet MPG. The exact set is driven by the data we have for your tenant, so empty data sources are simply omitted rather than shown as zero. > **Tip:** Hover any tile to read its long-form label and delta description. The arrow on the delta tells you whether the value moved up, down, or stayed flat versus the previous 30-day window. ## Departure compliance The **Departure compliance** card focuses on the start of each shift. It tells you what proportion of vehicles departed on time, how many started late, how many finished early, and how many shifts were missed entirely. Beneath the headline figures, the **Repeat late starters** list shows the drivers and vehicles that have been late more than once in the period. Each row carries the driver's avatar (or initials), the vehicle registration on a yellow plate, the count of late starts, and the average minutes late. Use it as a coaching watch list. > **Tip:** Where the same vehicle is appearing repeatedly, jump into the [Vehicle details](/documentation/core-modules/vehicles/vehicle-details.md) page to check trip patterns and driver assignment. ## Vehicle utilisation The **Vehicle utilisation** heatmap sits to the right of departure compliance. Each column is a day in the period and each row is a vehicle. Cells are shaded by the number of active hours: lighter cells mean the vehicle barely moved that day, darker cells mean a long working day. Use this view to spot: * Vehicles that have been parked for several days in a row. * Days where a depot's fleet was clearly under-utilised. * Patterns at the weekend or around bank holidays. The card heading carries a range label — typically "last 30 days" — to remind you what window the cells represent. ## Fuel consumption trend The **Fuel consumption trend** chart plots daily fleet MPG as a line, with the target and benchmark drawn as reference levels. Days where no fuel was consumed are skipped rather than zeroed, so the line shows true gaps instead of dropping to the floor. Look for: * A persistent downward drift in MPG, which often signals tyre pressures, route changes, or driving-style issues. * Single-day spikes that might be data quality problems rather than real consumption. * Sustained periods below the benchmark, which can usually be tied back to specific routes or shifts. ## Excess idle time The **Excess idle time** card lists the vehicles and drivers contributing the most idle hours over the period, ordered worst first. Each row shows the driver, the vehicle registration, and the total idle hours. The card also surfaces an estimate of the fuel wasted on idling so you can quickly translate hours into a financial impact. Use it to prioritise toolbox talks or in-cab interventions. ## Time on site The **Time on site** card breaks down where vehicles spend their hours: on the road, at customer sites, at depots, or in other locations. It renders as a doughnut with each slice carrying a category label, percentage, and total hours. The card heading shows the total hours summed across categories. This is most useful for fleets where customer dwell time is a cost driver — for example, parts deliveries or installer visits. ## Top customer sites The **Top customer sites** list ranks the customer locations your vehicles visit most. Each row carries: * The site name and location. * The number of visits in the period. * The total hours spent on site. * A trend indicator showing whether visits or hours are climbing, falling, or flat versus the previous window. Use it to validate route planning, to identify customers absorbing more time than expected, and to feed billing or service-level reviews. ## Loading and error states If the page is still fetching data, you see a **Loading** placeholder. If the underlying activity service returns an error, the page shows a single red banner with the error message instead of the cards. Refresh the page once the upstream issue is resolved. ## Related articles * [Dashboard overview](/documentation/core-modules/dashboard.md) * [Safety Overview](/documentation/core-modules/dashboard/safety-overview.md) * [Fusion Insight](/documentation/core-modules/dashboard/fusion-insight.md) * [Vehicle details](/documentation/core-modules/vehicles/vehicle-details.md) * [Coaching sessions](/documentation/coaching/coaching/sessions.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fleetfusion.ai/documentation/core-modules/dashboard/fleet-activity.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.