Host Property Manager

Manage listings, occupancy, guest requests, pricing, housekeeping, and property issues from one host workspace. This example brings Portfolio and Calendar together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Harbor House · cleaning due and Loft 14 · late arrival. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Host Property Manager
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add property

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add property while keeping occupancy, adr and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Portfolio gives users an obvious place to start.
  • Supporting view: Calendar keeps the related context close.
  • Primary action: Add property stays visible when people need it.
  • First signal: Occupancy shows a useful value (82%).
  • Second signal: ADR gives additional context (186).
  • Sample record: Harbor House · cleaning due.
  • Next record: Loft 14 · late arrival.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Portfolio → Calendar → Add property → Review outcome

Patterns used

Workspace, Portfolio, Calendar, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to portfolio and calendar. People need to distinguish Harbor House · cleaning due from Loft 14 · late arrival. 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 “Add property”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Guest Check-in, Travel Cancellation & Rebooking, Reservation Management.

Start from this in Figr

Design a host property manager screen inside our existing product. Use our current components, tokens and content language. Include Portfolio and Calendar views, credible records like Harbor House · cleaning due, and a clear “Add property” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr