# Filters

Use **Filters** when you want to answer questions like:

* What is off track right now?
* Which initiatives are overdue?
* Which teams need attention this quarter?
* Which goals report to me, or are missing owners or targets?

Filters is the fastest way to explore your workspace across plans, teams, owners, contributors, and timelines without building a dashboard first.

{% hint style="info" %}
Names like **Objectives**, **Outcomes**, and **Initiatives** may be different in your workspace. Tability uses your custom terminology everywhere in Filters too. See [Customise terms](/docs/become-a-tability-power-user/features/workspace-settings/customise-terms.md).
{% endhint %}

## How Filters is organised

Open **Filters** from the left sidebar.

Tability keeps three filter views:

* **Objectives**
* **Outcomes**
* **Initiatives**

When you open Filters, Tability sends you back to the last filter view you used. Each view has:

* a left sidebar for **segments**
* a top bar for adding or removing filter fields
* a result list you can **sort**
* options to **save a segment**, **share** the current view, or **export** results

## Build a filtered view

1. Open the filter view you want to work in.
2. Click **Filter +** to add a filter field.
3. Choose the values you want to narrow on.
4. Add more fields if you want to combine conditions.
5. Remove a single field with its **x**, or click **Reset filters** to go back to the default view.

Most workspaces start from active or in-progress items, then narrow down from there.

## What you can filter by

The exact filter menu depends on the view you are in.

### Objectives

Objective filters focus on planning and progress. You can filter by:

* plan status
* team
* plan
* path
* progress above or below a threshold
* confidence above or below an NCS threshold
* tags
* timeline

This view also supports sorting by title, plan, progress, confidence, newest, and oldest.

### Outcomes

Outcome filters are broader because they are commonly used for reporting. You can filter by:

* plan status
* owner
* contributor
* team
* plan
* path
* confidence
* weight
* outcome type
* completion state
* progress above or below a threshold
* tags
* timeline
* insights such as missing targets, pending check-ins, overdue check-ins, missing owners, not aligned, or reporting to you
* outcome labels such as committed or aspirational when those labels are enabled in your workspace

This view supports sorting by title, plan, owner, progress, newest, and oldest.

### Initiatives

Initiative filters are geared toward delivery tracking. You can filter by:

* plan status
* team
* plan
* path
* owner
* contributor
* planning state
* work status
* completion state
* tags
* timeline
* closed date
* insights such as overdue, due this week, completed on time, missing owners, or reporting to you

This view supports sorting by title, plan, owner, due date, status, work status, newest, and oldest.

## Use segments to save useful views

The left sidebar is built around **segments**.

You can use it to:

* search existing segments
* reopen segments you already use often
* mark segments as favourites
* jump into preset views like **My teams**, **Active**, **Draft**, or view-specific insight shortcuts

To save a segment:

1. Build the filter combination you want.
2. Click **Save segment**.
3. Name the segment.
4. Reuse it later from the sidebar.

Saved segments are especially useful when you want the same filtered view for weekly reviews, leadership check-ins, or dashboard widgets.

## When to use Filters vs Dashboards

Use **Filters** when you want to explore, troubleshoot, or create a saved workspace slice quickly.

Use **Dashboards** when you want a persistent report made of widgets, charts, leaderboards, or shared reporting layouts.

In practice:

* start in **Filters** to find the right slice of work
* save it as a **segment** if you will reuse it
* move to **Dashboards** when you want a repeatable report for a team, manager, or stakeholder audience


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.tability.io/docs/become-a-tability-power-user/features/reporting/filters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.