Contract Approval Workflow

Track contract reviews across legal, security, finance, and business approvers before signature. This example brings Pipeline and Approvers together so legal and operations teams can find the next task without losing context.

It includes representative records such as Northstar MSA and Atlas DPA. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Contract Approval Workflow
Use this template in Figr

Template facts

Screen

Board

Primary action

Add approval

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add approval while keeping in review, blocked and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Pipeline gives users an obvious place to start.
  • Supporting view: Approvers keeps the related context close.
  • Primary action: Add approval stays visible when people need it.
  • First signal: In review shows a useful value (28).
  • Second signal: Blocked gives additional context (6).
  • Sample record: Northstar MSA.
  • Next record: Atlas DPA.

States worth designing

  • No cards in this stage: say what changed, protect progress, and offer a clear next step.
  • Movement in progress: say what changed, protect progress, and offer a clear next step.
  • Move blocked by rules: say what changed, protect progress, and offer a clear next step.
  • Ownership updated: say what changed, protect progress, and offer a clear next step.
  • Archived item restored: say what changed, protect progress, and offer a clear next step.
  • Permission to edit missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Pipeline → Approvers → Add approval → Review outcome

Patterns used

Board, Pipeline, Approvers, contextual actions, error recovery

Why these choices work

Use real domain stages with a clear owner. Confirm high-impact moves and explain when permissions or missing work block an item.

Pay attention to pipeline and approvers. People need to distinguish Northstar MSA from Atlas DPA. Keep in review 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 “Add approval”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Clause Library, E-signature Request, Contract Drafting.

Start from this in Figr

Design a contract approval workflow screen inside our existing product. Use our current components, tokens and content language. Include Pipeline and Approvers views, credible records like Northstar MSA, and a clear “Add approval” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr