Property Inspection Checklist

Record room-by-room inspection findings, photos, severity, follow-up work, and tenant acknowledgements. This example brings Rooms and Issues together so property teams can find the next task without losing context.

It includes representative records such as Entry and locks and Kitchen appliances. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Property Inspection Checklist
Use this template in Figr

Template facts

Screen

Form

Primary action

Complete inspection

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 complete inspection while keeping areas, issues and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Rooms gives users an obvious place to start.
  • Supporting view: Issues keeps the related context close.
  • Primary action: Complete inspection stays visible when people need it.
  • First signal: Areas shows a useful value (12).
  • Second signal: Issues gives additional context (6).
  • Sample record: Entry and locks.
  • Next record: Kitchen appliances.

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

Rooms → Issues → Complete inspection → Review outcome

Patterns used

Form, Rooms, Issues, 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 rooms and issues. People need to distinguish Entry and locks from Kitchen appliances. Keep areas 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 “Complete inspection”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Property Manager Dashboard, Rent Payments, Tenant Portal.

Start from this in Figr

Design a property inspection checklist screen inside our existing product. Use our current components, tokens and content language. Include Rooms and Issues views, credible records like Entry and locks, and a clear “Complete inspection” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr