Contract Drafting

Assemble agreements from approved clauses, party details, commercial terms, fallback language, and review notes. This example brings Draft and Clauses together so legal and operations teams can find the next task without losing context.

It includes representative records such as Commercial terms and Data protection. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Contract Drafting
Use this template in Figr

Template facts

Screen

Builder

Primary action

Generate draft

Pattern

Builder

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to generate draft while keeping sections, fallbacks and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Draft gives users an obvious place to start.
  • Supporting view: Clauses keeps the related context close.
  • Primary action: Generate draft stays visible when people need it.
  • First signal: Sections shows a useful value (14).
  • Second signal: Fallbacks gives additional context (5).
  • Sample record: Commercial terms.
  • Next record: Data protection.

States worth designing

  • No configuration selected: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Invalid rule or block: say what changed, protect progress, and offer a clear next step.
  • Preview generated: say what changed, protect progress, and offer a clear next step.
  • Publish blocked: say what changed, protect progress, and offer a clear next step.
  • Version restored: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Draft → Clauses → Generate draft → Review outcome

Patterns used

Builder, Draft, Clauses, contextual actions, error recovery

Why these choices work

Show constraints before adding blocks, keep a usable preview and protect unsaved changes as people test a different direction.

Pay attention to draft and clauses. People need to distinguish Commercial terms from Data protection. Keep sections 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 “Generate draft”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a contract drafting screen inside our existing product. Use our current components, tokens and content language. Include Draft and Clauses views, credible records like Commercial terms, and a clear “Generate draft” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr