Rental Application

Collect applicant identity, income, employment, references, documents, and consent for a rental application. This example brings Applicant and Income together so property teams can find the next task without losing context.

It includes representative records such as Applicant details and Employment and income. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Rental Application
Use this template in Figr

Template facts

Screen

Form

Primary action

Submit application

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 application while keeping steps, applicants and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Applicant gives users an obvious place to start.
  • Supporting view: Income keeps the related context close.
  • Primary action: Submit application stays visible when people need it.
  • First signal: Steps shows a useful value (4).
  • Second signal: Applicants gives additional context (2).
  • Sample record: Applicant details.
  • Next record: Employment and income.

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

Applicant → Income → Submit application → Review outcome

Patterns used

Form, Applicant, Income, 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 applicant and income. People need to distinguish Applicant details from Employment and income. Keep steps 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 application”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Property Detail, Lease Management, Property Search.

Start from this in Figr

Design a rental application screen inside our existing product. Use our current components, tokens and content language. Include Applicant and Income views, credible records like Applicant details, and a clear “Submit application” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr