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.

Analytics
Export report
Analytics
Default, loading, empty, error, permission, success
Configurable product UI theme
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.
Occupancy → Vacancy → Export report → Review outcome
Analytics, Occupancy, Vacancy, contextual actions, error recovery
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.
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.