FIGR / UI TEMPLATE

Baggage Exception Queue

Triage unclaimed bags and mishandled transfers before passenger response deadlines.

This example shows how a team could handle Aviation & Airport Operations tasks in an existing product. Sample data is fictional.

Baggage Exception Queue

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Inbox

Primary action

Resolve case

Pattern

inbox workflow

State

Default, loading, empty, error, permission denied, success

Design system

Independent UI reference; no 1mg design system

What this screen helps with

Triage unclaimed bags and mishandled transfers before passenger response deadlines.

What to look for

Sections: Overview, Flights, Resources, Exceptions, Reports. Primary task: Resolve case.

States to consider

Default, loading, empty, error, permission denied, success. Add clear messages and recovery actions when data, permissions or a failed change blocks work.

Where it fits

Overview → Baggage Exception Queue → Resolve case

Patterns in this screen

inbox, filters, status labels, record detail

UX choices to review

Keep the primary task and exceptions visible. For example, BAG-2048 · wrong carousel should have a clear next action.

Plan loading, empty, failed-save and restricted-access states so users can recover without losing their work.

Try a similar screen in Figr

Adapt Baggage Exception Queue to our existing product. Respect our flows, tokens, components and constraints. Review the exception cases and missing states before creating Figma-ready screens.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗