Guest Check-in

Collect guest identity, arrival details, room preferences, and required acknowledgements before check-in. This example brings Guest and Arrival together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Confirm guest details and Add arrival time. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Guest Check-in
Use this template in Figr

Template facts

Screen

Onboarding

Primary action

Continue check-in

Pattern

Onboarding

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to continue check-in while keeping steps, guests and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Guest gives users an obvious place to start.
  • Supporting view: Arrival keeps the related context close.
  • Primary action: Continue check-in stays visible when people need it.
  • First signal: Steps shows a useful value (4).
  • Second signal: Guests gives additional context (2).
  • Sample record: Confirm guest details.
  • Next record: Add arrival time.

States worth designing

  • No setup steps complete: say what changed, protect progress, and offer a clear next step.
  • Step in progress: say what changed, protect progress, and offer a clear next step.
  • Identity check failed: say what changed, protect progress, and offer a clear next step.
  • Invite sent: say what changed, protect progress, and offer a clear next step.
  • Access denied: say what changed, protect progress, and offer a clear next step.
  • Setup complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Guest → Arrival → Continue check-in → Review outcome

Patterns used

Onboarding, Guest, Arrival, contextual actions, error recovery

Why these choices work

Make each setup step and completion state clear. Allow admins to resume without repeating the work they finished.

Pay attention to guest and arrival. People need to distinguish Confirm guest details from Add arrival time. Keep steps 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 “Continue check-in”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Reservation Management, Host Property Manager, Trip Itinerary.

Start from this in Figr

Design a guest check-in screen inside our existing product. Use our current components, tokens and content language. Include Guest and Arrival views, credible records like Confirm guest details, and a clear “Continue check-in” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr