Advanced Search Filters

Refine large result sets with composable filters, facets, chips, counts, and reusable filter combinations. The screen connects Results and Filters so product teams can find the “Save filters” action while checking results and filters.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise accounts in renewal and Open incidents with high severity, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Primary action

Save filters

Pattern

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Save filters” action without losing sight of results, filters and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Save filters is clearly available where the task happens.
Main view: Results keeps the starting point obvious.
Connected view: Filters supplies nearby context.
Metric: Results is visible with a meaningful value.
Another signal: Filters helps people judge what to do next.
Representative record: Enterprise accounts in renewal makes the example specific.
Second record: Open incidents with high severity shows the pattern works beyond one item.

States worth designing

No matching records; show what people can do instead of leaving a blank panel.
Loading results without changing the layout unexpectedly.
Search or filter request failed; explain the problem and preserve work.
Permission denied for filters; clarify who can continue.
Success after choosing Save filters; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Results → Filters → Save filters → Review outcome

Patterns used

Search, Results, Filters, Saved views, accessible states, contextual actions

Why these choices work

Preserve the query and chosen filters as people inspect results. Make no-results recovery useful instead of a dead end.

In this design, people should be able to compare Enterprise accounts in renewal with Open incidents with high severity. Make results clear, then use filters to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Save filters” action. The happy path alone is not enough.

Related UI examples: Global Search, Saved Searches, Command Palette.

Start from this in Figr

Design a advanced search filters screen for our existing software product. Use our real design-system tokens, components and product language. Show Results and Filters, include believable records such as Enterprise accounts in renewal, and make save filters easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr