Maintenance Requests

Triage tenant maintenance requests with urgency, property context, photos, vendor assignment, and resolution status. This example brings Inbox and Assigned together so property teams can find the next task without losing context.

It includes representative records such as Water leak · Unit 7C and Heating issue · Unit 12A. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Maintenance Requests
Use this template in Figr

Template facts

Screen

Inbox

Primary action

New request

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new request while keeping open, urgent and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Inbox gives users an obvious place to start.
  • Supporting view: Assigned keeps the related context close.
  • Primary action: New request stays visible when people need it.
  • First signal: Open shows a useful value (27).
  • Second signal: Urgent gives additional context (5).
  • Sample record: Water leak · Unit 7C.
  • Next record: Heating issue · Unit 12A.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Inbox → Assigned → New request → Review outcome

Patterns used

Inbox, Inbox, Assigned, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to inbox and assigned. People need to distinguish Water leak · Unit 7C from Heating issue · Unit 12A. Keep open 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 request”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Lease Management, Tenant Portal, Rental Application.

Start from this in Figr

Design a maintenance requests screen inside our existing product. Use our current components, tokens and content language. Include Inbox and Assigned views, credible records like Water leak · Unit 7C, and a clear “New request” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr