Audit Report

Redesigning the Audit Report for

Compliance Power Users

UX Strategy

Enterprise SaaS

Design Systems

Overview

Context

Sentinel is a compliance-driven SaaS platform used by Customs brokers to automate and manage customs clearance jobs. The platform enables the end-to-end handling of complex documentation — including Invoices, product codes and declarations — ensuring every detail complies with trade and tax regulations.

One of the core modules in Sentinel is the Audit Report, which plays a crucial role in error detection and compliance verification.

The Audit Report identifies all the Errors, warnings and data formatting issues that arise during Job creation. These include omissions in mandatory fields, invalid formatting and issues like duplicate invoice numbers within a financial year.

It enables users to view, prioritize and resolve issues across multiple layers — from Job-level fields to Invoice-level discrepancies and Item-level data accuracy.

The Audit Report is a critical feature triggered during the job creation process. It lists:

In its original form (Version 1), the Audit Report was functional but flawed. Users — Primarily customs brokers — had to sift through dense tables, jump between multiple tabs, and track issues manually across forms. This not only slowed workflows but also introduced risk in regulatory compliance.

The goal of this project was to redesign the Audit Report experience to be more structured, intuitive and user-friendly, allowing customs brokers to resolve issues faster, with more clarity and confidence.

My Role

As the Product Designer, I led the end-to-end UX process for this feature.

Conducted user research with internal QA and client-side compliance users

Built and iterated wireframes and high-fidelity prototypes in Figma

Extended our token-based design system

Worked in agile sprints with PMs, engineers, and QA to ensure seamless implementation

As the Product Designer, I led the end-to-end UX process for this feature. I collaborated with:

1 Product Manager

3 Engineers

QA & Customer Success Leads

Responsibilities

Research and stakeholder interviews

Wireframes and hi-fi prototyping (Figma)

Design system contribution

Usability testing and dev handoff

Some notes goes here

Users & Stakeholders

Primary Users

We broke down feedback into usability pain points:

Stakeholders

Product Manager, Engineering Lead, Customer Success & Domain Expert.

Customs brokers often operate under strict deadlines, navigating a flood of jobs simultaneously. Any friction in resolving errors can lead to shipment delays, penalties or missed clearances.

Some notes goes here

Discovery & Research

We started with contextual inquiry and usability audits to understand the real-world behavior around the Audit Report. Despite being central to job validation, it was underutilized or bypassed entirely by many users.

Research Activities
Key Insights

Some notes goes here

Problems in Audit Report V1

When we examined the original version of the Audit Report, we saw a feature that technically worked — but failed to respect the way power users actually think and operate. Customs brokers aren’t casual users; they rely on efficiency, spatial memory, and rapid mental shortcuts. Version 1 interrupted all of that.

We broke down feedback into usability pain points:

We’re not designing for beginners. These are super users, people who live in this product for hours, who think in shortcuts and who hate inefficiency

Some notes goes here

Design Process

We followed a structured, iterative process to redesign the experience without overwhelming users — especially those handling 50+ jobs per day.

We broke down feedback into usability pain points:

Some notes goes here

Design Principles for Version 2

To serve our super users, we set design principles:

Context over complexity: Show issues in the right place, not in isolation.

Actionable, not informational: Every element must help users fix, not just know.

Seamless multitasking: Let users see issues and form side-by-side.

Trust through clarity: Make hierarchy and location visually obvious.

Some notes goes here

Version 2 – What Changed?

Some notes goes here

NDA Note

Due to confidentiality with Unifo, full UI visuals and sensitive client data are omitted. However, the design process, decisions and outcomes represent my actual contributions. I’m happy to walk through anonymized flows and design logic in a live session.

Some notes goes here

Outcomes & Results

The redesign led to tangible improvements in user workflow, satisfaction and system efficiency.

Some notes goes here

Reflection & Takeaways

Designing the Audit Report was a deep dive into systems thinking, compliance UX, and designing for speed and clarity under pressure. I learned to trust user behaviour over assumptions.

Here are my biggest takeaways:

Designing for power users means embracing speed, not simplification

This project made me deeply aware that power users don’t want extra UI, they want fewer clicks, faster access, and smarter defaults.

Hierarchy matters more than volume

Redesigning from dense tables to structured cards showed me that surfacing the right information in the right order is far more valuable than showing everything at once.

Design systems are enablers, not constraints

Reusable tokens and components helped us scale faster, reduced handoff friction and ensured consistency without compromising creativity.

Good UX gives helpful feedback, not just instructions

The Audit Report didn’t just show errors — it helped users understand what went wrong and how to fix it, right in the flow of work. That made the experience feel supportive, not frustrating.

Some notes goes here

Explore next

Get in touch

Send an email or DM and I'll get back to you asap.

All rights reserved © 2025 Vamsi Adurthy

Get in touch

Send an email or DM and I'll get back to you asap.

All rights reserved © 2025 Vamsi Adurthy

Get in touch

Send an email or DM and I'll get back to you asap.

All rights reserved © 2025 Vamsi Adurthy

Lights on·off