Compliance Center

Track control coverage, evidence freshness, open findings, owners, and review deadlines across compliance programs. The screen connects Overview and Controls so workspace admins can find the “Start review” action while checking controls and passing.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Access control · 98% and Data protection · 94%, rather than an empty visual shell.

Compliance Center
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Start review

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Start review” action without losing sight of controls, passing and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Start review is clearly available where the task happens.
  • Main view: Overview keeps the starting point obvious.
  • Connected view: Controls supplies nearby context.
  • Metric: Controls is visible with a meaningful value.
  • Another signal: Passing helps people judge what to do next.
  • Representative record: Access control · 98% makes the example specific.
  • Second record: Data protection · 94% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading overview without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for controls; clarify who can continue.
  • Success after choosing Start review; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Overview → Controls → Start review → Review outcome

Patterns used

Analytics, Overview, Controls, Evidence, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Access control · 98% with Data protection · 94%. Make controls clear, then use passing to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Start review” action. The happy path alone is not enough.

Related UI examples: Organization Settings, Notification Preferences, Integration Settings.

Start from this in Figr

Design a compliance center screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Controls, include believable records such as Access control · 98%, and make start review easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr