Legal Intake

Capture business context, request type, urgency, counterparties, attachments, and target dates for new legal work. This example brings Request and Context together so legal and operations teams can find the next task without losing context.

It includes representative records such as Describe the request and Add business context. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Legal Intake
Use this template in Figr

Template facts

Screen

Form

Primary action

Submit request

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 submit request while keeping fields, urgency and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Request gives users an obvious place to start.
  • Supporting view: Context keeps the related context close.
  • Primary action: Submit request stays visible when people need it.
  • First signal: Fields shows a useful value (9).
  • Second signal: Urgency gives additional context (Normal).
  • Sample record: Describe the request.
  • Next record: Add business context.

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

Request → Context → Submit request → Review outcome

Patterns used

Form, Request, Context, 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 request and context. People need to distinguish Describe the request from Add business context. Keep fields 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 “Submit request”. Make error recovery as clear as the happy path.

Related screen examples to explore next: E-signature Request, Matter Management, Contract Approval Workflow.

Start from this in Figr

Design a legal intake screen inside our existing product. Use our current components, tokens and content language. Include Request and Context views, credible records like Describe the request, and a clear “Submit request” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr