E-signature Request

Prepare a document for signature, assign signers, set signing order, add reminders, and verify completion requirements. This example brings Document and Recipients together so legal and operations teams can find the next task without losing context.

It includes representative records such as Upload final agreement and Add signers. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

E-signature Request
Use this template in Figr

Template facts

Screen

Form

Primary action

Send for signature

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to send for signature while keeping signers, fields and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Document gives users an obvious place to start.
  • Supporting view: Recipients keeps the related context close.
  • Primary action: Send for signature stays visible when people need it.
  • First signal: Signers shows a useful value (3).
  • Second signal: Fields gives additional context (14).
  • Sample record: Upload final agreement.
  • Next record: Add signers.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Document → Recipients → Send for signature → Review outcome

Patterns used

Form, Document, Recipients, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to document and recipients. People need to distinguish Upload final agreement from Add signers. Keep signers 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 “Send for signature”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Contract Approval Workflow, Legal Intake, Clause Library.

Start from this in Figr

Design a e-signature request screen inside our existing product. Use our current components, tokens and content language. Include Document and Recipients views, credible records like Upload final agreement, and a clear “Send for signature” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr