Fleet authorisation and downtime / Interface design
Keep the vehicle visible.
Keep the vehicle visible.
Inspect the repair.
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.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Fleet authorisation and downtime
- DESIGN FOCUS
- Connecting fleet availability to repair authority
01 / THE DESIGN DECISION
Availability depends on an authorised decision.
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.
02 / THE BUILD
The pages we designed.
The build brings availability, repair authority and downtime record into one workspace.
03 / PROJECT NOTES
Project scope.
We designed and built 3 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
06 / ON SCREENA closer look.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
3 views Select any view to explore
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.