Fintech · Banking · Compliance

UCB CAR Portal
United Community Bank

A dual-portal system for quarterly CAR report management — enabling bank executives to complete compliance reports with guided, error-resilient flows while giving admins real-time submission visibility.

RoleUX Designer
Timeline2 Months
PlatformWeb · Desktop
↓40%
Reduction in Report Errors
2
Portal Surfaces
↓35%
Completion Time
2mo
Full Design Delivery

Turning quarterly compliance pain into a guided experience

United Community Bank (UCB) needed a new digital system to manage their quarterly Capital Adequacy Ratio (CAR) reports — a critical compliance requirement that previously relied on error-prone manual processes and disconnected spreadsheets.

I designed a dual-portal system over 2 months: an executive-facing guided report completion portal, and an admin-facing oversight dashboard for tracking submission progress and bottlenecks across the bank's branch network.

Compliance reports that caused compliance issues

Quarterly CAR reports require executives across multiple branches to complete complex regulatory forms within strict deadlines. The legacy process was entirely manual — PDFs sent via email, filled by hand, returned with errors, corrected, resubmitted — a cycle that frequently caused regulatory delays.

"By the time I've reviewed a report, fixed the errors, and sent it back, we've lost a week. And the deadline hasn't moved."
— Compliance Admin, UCB

High Error Rate

Manual data entry across complex multi-section forms produced frequent calculation errors and missing fields that required back-and-forth correction cycles.

No Visibility

Admins had no real-time view of which branches had submitted, which were in progress, and which hadn't started — creating deadline anxiety and last-minute scrambles.

No Guidance

Executives completing reports had no contextual help, no validation, and no indication of what a completed section should look like versus an incorrect one.

Disconnected Process

Each quarterly cycle restarted from scratch with no historical data reference, forcing executives to re-enter static information and context each time.

Designing for confidence, not just completion

1

Process Mapping

Ran a service blueprint exercise with admins and one executive to map the full current-state report lifecycle — from initial notification through submission and approval. Identified 11 distinct pain points.

2

Progressive Form Architecture

Broke the monolithic CAR report into a step-by-step wizard with clear section groupings, progress indicators, and section-level completion states. Each step was designed to feel achievable in isolation.

3

Inline Validation System

Designed a real-time validation layer that flags errors as users type — not just on submission. Contextual helper text explains why a field matters, not just that it's required.

4

Admin Dashboard Design

Created a submission tracker showing branch-level progress with status indicators (Not Started / In Progress / Submitted / Approved), plus a drill-down view to see which specific sections are incomplete.

5

Pre-fill & Historical Reference

Designed a system where static fields (branch details, executive info) pre-populate from the previous quarter — reducing re-entry burden and a common source of errors.

40% fewer errors. A process executives actually trust.

The guided report flow with inline validation drove a 40% reduction in report errors in the first quarter post-launch. Completion time per report dropped by 35% as executives no longer needed to re-read instructions or guess at field requirements.

The admin dashboard gave compliance managers real-time visibility for the first time — eliminating the frantic deadline-week email chains that had defined every previous quarter.

Banking SaaSCompliance UXForm Design Admin PortalFintech2 Months
← Back to all projects

Next Case Study

Wealth$hare →