Travel Cancellation & Rebooking

Show refund eligibility, change fees, replacement options, and downstream itinerary impact before changing a trip. This example brings Booking and Options together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Review cancellation terms and Compare replacement flights. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Travel Cancellation & Rebooking
Use this template in Figr

Template facts

Screen

Form

Primary action

Confirm change

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 confirm change while keeping refundable, change fee and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Booking gives users an obvious place to start.
  • Supporting view: Options keeps the related context close.
  • Primary action: Confirm change stays visible when people need it.
  • First signal: Refundable shows a useful value (940).
  • Second signal: Change fee gives additional context (80).
  • Sample record: Review cancellation terms.
  • Next record: Compare replacement flights.

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

Booking → Options → Confirm change → Review outcome

Patterns used

Form, Booking, Options, 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 booking and options. People need to distinguish Review cancellation terms from Compare replacement flights. Keep refundable 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 “Confirm change”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Host Property Manager, Guest Check-in, Reservation Management.

Start from this in Figr

Design a travel cancellation & rebooking screen inside our existing product. Use our current components, tokens and content language. Include Booking and Options views, credible records like Review cancellation terms, and a clear “Confirm change” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr