Compliance Review

Triage policy, privacy, marketing, vendor, and regulatory reviews with owners, evidence, comments, and deadlines. This example brings Queue and Policies together so legal and operations teams can find the next task without losing context.

It includes representative records such as New data processor review and Email consent language. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Compliance Review
Use this template in Figr

Template facts

Screen

Inbox

Primary action

New review

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new review while keeping open reviews, high risk and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Queue gives users an obvious place to start.
  • Supporting view: Policies keeps the related context close.
  • Primary action: New review stays visible when people need it.
  • First signal: Open reviews shows a useful value (31).
  • Second signal: High risk gives additional context (5).
  • Sample record: New data processor review.
  • Next record: Email consent language.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Queue → Policies → New review → Review outcome

Patterns used

Inbox, Queue, Policies, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to queue and policies. People need to distinguish New data processor review from Email consent language. Keep open reviews visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “New review”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Matter Management, Renewal Calendar, Legal Intake.

Start from this in Figr

Design a compliance review screen inside our existing product. Use our current components, tokens and content language. Include Queue and Policies views, credible records like New data processor review, and a clear “New review” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr