Occupancy Analytics

Analyze occupancy, vacancy duration, move-ins, move-outs, leasing velocity, and unit performance across a portfolio. This example brings Occupancy and Vacancy together so property teams can find the next task without losing context.

It includes representative records such as Central Park Residences and Lakeview Towers. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Occupancy Analytics

Template facts

Screen

Analytics

Primary action

Export report

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to export report while keeping occupancy, vacant units and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Occupancy gives users an obvious place to start.
  • Supporting view: Vacancy keeps the related context close.
  • Primary action: Export report stays visible when people need it.
  • First signal: Occupancy shows a useful value (94.2%).
  • Second signal: Vacant units gives additional context (23).
  • Sample record: Central Park Residences.
  • Next record: Lakeview Towers.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Occupancy → Vacancy → Export report → Review outcome

Patterns used

Analytics, Occupancy, Vacancy, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to occupancy and vacancy. People need to distinguish Central Park Residences from Lakeview Towers. Keep occupancy 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 “Export report”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Rent Payments, Property Inspection Checklist, Property Manager Dashboard.

Start from this in Figr

Design a occupancy analytics screen inside our existing product. Use our current components, tokens and content language. Include Occupancy and Vacancy views, credible records like Central Park Residences, and a clear “Export report” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr