Lease Management

Manage active leases, tenants, terms, deposits, notices, renewals, and document status across a property portfolio. This example brings Leases and Tenants together so property teams can find the next task without losing context.

It includes representative records such as Unit 4B · Rivera and Unit 12A · Chen. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Lease Management
Use this template in Figr

Template facts

Screen

Table

Primary action

New lease

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 new lease while keeping active leases, renewals and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Leases gives users an obvious place to start.
  • Supporting view: Tenants keeps the related context close.
  • Primary action: New lease stays visible when people need it.
  • First signal: Active leases shows a useful value (186).
  • Second signal: Renewals gives additional context (18).
  • Sample record: Unit 4B · Rivera.
  • Next record: Unit 12A · Chen.

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

Leases → Tenants → New lease → Review outcome

Patterns used

Table, Leases, Tenants, 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 leases and tenants. People need to distinguish Unit 4B · Rivera from Unit 12A · Chen. Keep active leases 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 “New lease”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Rental Application, Maintenance Requests, Property Detail.

Start from this in Figr

Design a lease management screen inside our existing product. Use our current components, tokens and content language. Include Leases and Tenants views, credible records like Unit 4B · Rivera, and a clear “New lease” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr