Clause Library

Manage approved clauses, fallback language, jurisdictions, risk positions, and guidance for contract drafting. This example brings Clauses and Categories together so legal and operations teams can find the next task without losing context.

It includes representative records such as Limitation of liability and Data processing. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Clause Library
Use this template in Figr

Template facts

Screen

Table

Primary action

Add clause

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add clause while keeping clauses, approved and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Clauses gives users an obvious place to start.
  • Supporting view: Categories keeps the related context close.
  • Primary action: Add clause stays visible when people need it.
  • First signal: Clauses shows a useful value (186).
  • Second signal: Approved gives additional context (91%).
  • Sample record: Limitation of liability.
  • Next record: Data processing.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Clauses → Categories → Add clause → Review outcome

Patterns used

Table, Clauses, Categories, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to clauses and categories. People need to distinguish Limitation of liability from Data processing. Keep clauses 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 clause”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Contract Drafting, Contract Approval Workflow, Contract Detail.

Start from this in Figr

Design a clause library screen inside our existing product. Use our current components, tokens and content language. Include Clauses and Categories views, credible records like Limitation of liability, and a clear “Add clause” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr