Project field notes / 01

AutoNation
Mobile Service

Making fleet invoice review easier to manage—from account selection to confident batch submission.

ROLEUX/UI Designer
SCOPEFleet invoice workbench
INDUSTRYAutomobile
EMPLOYERAutoNation
Original AutoNation workbench desktop image
THE WORKBENCH / TESTED & SHIPPED
01 / The challenge

The problem: speed and accuracy

Fleet Account Managers need to move invoices forward while checking that the account, vehicle, details, and submission destination are correct. Their work spans multiple fleets and customers: finding records, reviewing and editing details, tracking statuses, and submitting invoices. Each step depends on keeping the right context visible.

I owned the UX/UI design of AutoNation Mobile Service’s fleet invoice workbench from requirements through the finished feature. The goal was a clear workflow that supported efficient processing and quality control. The workbench was tested and shipped.

My starting question

How could I help managers move faster while keeping the details they needed to make an accurate decision? I treated speed and accuracy as connected goals. The interface needed to reduce the effort of finding and reviewing invoices while keeping account context and the scope of an action visible.

01

Set the context

Choose a fleet or customer.
Find the relevant invoices.

02

Check the records

Review invoice details.
Edit and select the right records.

03

Move work forward

Submit the selected invoices.
Check their statuses.

02 / Understanding the workflow

Four decisions.
One clear path.

Moving an invoice forward means knowing whose records you’re reviewing, what needs attention, and what the next action will affect.

Workflow synthesized from stakeholder requirements and Jira tickets.
Designed for fleet account managers.
01→

Set the context

Whose invoices am I reviewing?

02→

Find the records

What needs my attention?

03→

Review & select

What belongs in this batch?

04↗

Submit & track

Where will these invoices go?

The working view / 02—03

Find the right records. Keep the details in view.

One queue connects discovery,
review, and batch selection.

Original AutoNation invoice workbench
0203
ORIGINAL WORKBENCH · Select to enlarge
01

Start with the right account.

The fleet selector establishes context before records appear. This gives the review task a clear starting point.

ENTRY POINT / Fleet selection
04

End with a deliberate checkpoint.

The submission dialog brings the recipient and optional comments into focus before the manager confirms.

Original batch submission confirmation
FINAL CHECK / Batch confirmation
The design logic

Less uncertainty.
More control.

Each opportunity addresses a point where context or action scope can become unclear.

Potential frictionDesign opportunity
01Losing account context→Keep the selected account visible.
02Searching a large queue→Combine filters with status cues.
03Uncertainty about batch scope→Keep record details close to selection.
04Unclear submission destination→Confirm the recipient before sending.

Requirements-based workflow framing, not interview findings. Original case-study screenshots; select any image to enlarge.

03 / Design decisions

Designing the review workflow

I explored multiple wireframe options for connecting account context, invoice discovery, and submission. The final workbench follows three stages of review.

Working within the design library

I used AutoNation’s existing design library to create the workbench layout, building on the company’s established visual language while organizing account selection, invoice review, and batch submission into a connected workflow.

I no longer have access to the company’s design library, so I can’t show the library itself here.

Start with the account

Managers work across fleets and customers. I made fleet selection an entry point for narrowing the workbench before reviewing individual records. This connects invoice discovery to the account the manager is working on.

Choose the account first. The fleet selector establishes the context for invoice review.
Choose the account first. The fleet selector establishes the context for invoice review. Select to enlarge.
Why I put account context first

Before a manager can decide what to review, they need to know whose invoices they are looking at. I used fleet selection to establish that context first, so filtering and review could happen within a clearly defined account.

04 / Shipped & learned

The shipped workbench

The fleet invoice workbench was tested and shipped. I owned its UX/UI design from the initial requirements through the finished feature, working with the Director of Design and project/product managers. I explored wireframe options and worked with stakeholders to develop the final workbench. Stakeholders chose to proceed without an interactive prototype. The shipped experience brings account selection, invoice discovery, status review, batch selection, and submission into a connected workflow.

THE PRODUCTION WORKBENCH · SELECT TO ENLARGE

Reflection

The central design principle was to keep account context and action scope visible. In an operational tool, a manager needs to understand both which records they are reviewing and what the next action will affect.

Next measurement

To evaluate the workbench’s impact, I would measure time to locate an invoice, accuracy of edits, batch-selection errors, and confidence before submission.

Next stop

More to explore.

Enlarged original project image