Reservation Management

Manage upcoming stays and trips, traveler details, payment status, changes, and service requests. This example brings Reservations and Guests together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Harbor House · Sep 22 and Skyline Hotel · Sep 26. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Reservation Management
Use this template in Figr

Template facts

Screen

Table

Primary action

New reservation

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new reservation while keeping upcoming, confirmed and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Reservations gives users an obvious place to start.
  • Supporting view: Guests keeps the related context close.
  • Primary action: New reservation stays visible when people need it.
  • First signal: Upcoming shows a useful value (48).
  • Second signal: Confirmed gives additional context (91%).
  • Sample record: Harbor House · Sep 22.
  • Next record: Skyline Hotel · Sep 26.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Reservations → Guests → New reservation → Review outcome

Patterns used

Table, Reservations, Guests, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to reservations and guests. People need to distinguish Harbor House · Sep 22 from Skyline Hotel · Sep 26. Keep upcoming 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 reservation”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Trip Itinerary, Guest Check-in, Travel Booking Checkout.

Start from this in Figr

Design a reservation management screen inside our existing product. Use our current components, tokens and content language. Include Reservations and Guests views, credible records like Harbor House · Sep 22, and a clear “New reservation” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr