FIGR / UI TEMPLATE
Coordinate weather holds, diversions, crew gaps and passenger recovery plans.
This example shows how a team could handle Aviation & Airport Operations tasks in an existing product. Sample data is fictional.
BUILD ON THIS
Explore this screen, then bring in your own product and design system to shape the next version.
Workspace
Start recovery
workspace workflow
Default, loading, empty, error, permission denied, success
Independent UI reference; no 1mg design system
Coordinate weather holds, diversions, crew gaps and passenger recovery plans.
Sections: Overview, Flights, Resources, Exceptions, Reports. Primary task: Start recovery.
Default, loading, empty, error, permission denied, success. Add clear messages and recovery actions when data, permissions or a failed change blocks work.
Overview → Disruption Command Center → Start recovery
workspace, filters, status labels, record detail
Keep the primary task and exceptions visible. For example, Weather hold · JFK departures should have a clear next action.
Plan loading, empty, failed-save and restricted-access states so users can recover without losing their work.
Adapt Disruption Command Center to our existing product. Respect our flows, tokens, components and constraints. Review the exception cases and missing states before creating Figma-ready screens.
KEEP EXPLORING
Browse other product UI examples, compare patterns, and pick the direction that suits your product.