Fleet Tracking

Track vehicle location, utilization, route progress, idle time, maintenance risk, and delivery exceptions across an active fleet. This example brings Live fleet and Routes together so operations managers can find the next task without losing context.

It includes representative records such as Truck KA-42 · North route and Van KA-18 · Central route. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Fleet Tracking
Use this template in Figr

Template facts

Screen

Analytics

Primary action

View live map

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Operations managers need to view live map while keeping vehicles active, on route and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Live fleet gives users an obvious place to start.
  • Supporting view: Routes keeps the related context close.
  • Primary action: View live map stays visible when people need it.
  • First signal: Vehicles active shows a useful value (68).
  • Second signal: On route gives additional context (54).
  • Sample record: Truck KA-42 · North route.
  • Next record: Van KA-18 · Central route.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Live fleet → Routes → View live map → Review outcome

Patterns used

Analytics, Live fleet, Routes, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to live fleet and routes. People need to distinguish Truck KA-42 · North route from Van KA-18 · Central route. Keep vehicles active visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “View live map”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Shipment Planning, Delivery Dispatch, Warehouse Operations.

Start from this in Figr

Design a fleet tracking screen inside our existing product. Use our current components, tokens and content language. Include Live fleet and Routes views, credible records like Truck KA-42 · North route, and a clear “View live map” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr