Contract Detail

Review contract terms, owners, obligations, redlines, attachments, approvals, and renewal dates from one record. This example brings Summary and Terms together so legal and operations teams can find the next task without losing context.

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

Contract Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Edit contract

Pattern

Detail

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to edit contract while keeping value, term and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Summary gives users an obvious place to start.
  • Supporting view: Terms keeps the related context close.
  • Primary action: Edit contract stays visible when people need it.
  • First signal: Value shows a useful value (240k).
  • Second signal: Term gives additional context (24 mo).
  • Sample record: Limitation of liability updated.
  • Next record: Security exhibit approved.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Summary → Terms → Edit contract → Review outcome

Patterns used

Detail, Summary, Terms, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to summary and terms. People need to distinguish Limitation of liability updated from Security exhibit approved. Keep value 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 “Edit contract”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a contract detail screen inside our existing product. Use our current components, tokens and content language. Include Summary and Terms views, credible records like Limitation of liability updated, and a clear “Edit contract” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr