Contract Repository

Centralize executed and draft agreements with owners, counterparties, dates, obligations, and searchable metadata. This example brings Contracts and Folders together so legal and operations teams can find the next task without losing context.

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

Contract Repository
Use this template in Figr

Template facts

Screen

Table

Primary action

Upload contract

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 upload contract while keeping contracts, renewing soon and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Contracts gives users an obvious place to start.
  • Supporting view: Folders keeps the related context close.
  • Primary action: Upload contract stays visible when people need it.
  • First signal: Contracts shows a useful value (428).
  • Second signal: Renewing soon gives additional context (23).
  • Sample record: MSA · Northstar Labs.
  • Next record: DPA · Atlas Cloud.

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

Contracts → Folders → Upload contract → Review outcome

Patterns used

Table, Contracts, Folders, 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 contracts and folders. People need to distinguish MSA · Northstar Labs from DPA · Atlas Cloud. Keep contracts 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 “Upload contract”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Contract Detail, Contract Drafting, Clause Library.

Start from this in Figr

Design a contract repository screen inside our existing product. Use our current components, tokens and content language. Include Contracts and Folders views, credible records like MSA · Northstar Labs, and a clear “Upload contract” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr