Keep the vehicle visible.
Inspect the repair.

Availability — identifying labels masked
Availability
THE PROJECT

We connected the fleet availability view to a repair authority and a downtime record.

A held vehicle has a reason, and the person reviewing it can move directly into the work being considered.

PROJECT TYPE
Interface design & front-end development
DOMAIN
Fleet authorisation and downtime
DESIGN FOCUS
Connecting fleet availability to repair authority
THE DESIGN DECISION

Availability depends on an authorised decision.

A vehicle's availability depends on both its repair state and the authority to proceed. A downtime record alone cannot explain why work is waiting.

The estimate sits in a lighter document view against the operational status screen. We used that change in density to support careful reading before an authorisation decision. Downtime remains part of the vehicle history rather than disappearing when a repair is proposed.

THE BUILD

The pages we designed.

The build brings availability, repair authority and downtime record into one workspace.

Screen

Availability

We connected the fleet availability view to a repair authority and a downtime record.

View the screen ↓
Screen

Repair authority

Presents the proposed repair and itemised estimate beside the vehicle awaiting authorisation.

View the screen ↓
Screen

Downtime record

One held vehicle. A recorded cause, an accountable decision and a conditional next step.

View the screen ↓

Expanded project screenshot
FROM THIS PROJECT TO YOURS

Have a similar project?
Let’s discuss the work.

Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.

Discuss your project Explore custom software development

Search Anteomnio

A few places to start

↑ ↓ to explore · Enter to openFull search page