> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-7-communicate-and-take-action/action-planning-in-compass/status-page.md).

# Status Page

The Status page gives HR administrators and consultants visibility into action planning progress across the entire organization, so you can identify who is making progress and who needs follow-up.

{% hint style="info" %}
**Beta feature.** Action Planning is currently available as a beta release. Features and interface details may change as we refine the experience.
{% endhint %}

***

### Actions tab

The **ACTIONS** tab displays a table with columns for Action, Owner, Milestones (completed/total), Next Due date, and Status.

Filter the view using these chips at the top:

* **All**: Every plan in the organization.
* **Complete**: Plans with all milestones done.
* **Overdue**: Plans with milestones past their due date.
* **Unassigned**: Plans not yet assigned to a user.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2F0y9I61PeVtCQUMTL0JUU%2FScreenshot%202026-04-03%20at%2011.47.01%E2%80%AFAM.png?alt=media&#x26;token=20c5ee9c-62d0-4707-8f7f-58d587f1029d" alt=""><figcaption></figcaption></figure>

***

### Users tab

The **USERS** tab shows all assigned users with their node assignment and milestone progress.

Filter the view using these chips:

* **All**: Every assigned user.
* **No Plans**: Users who have not created any plans. This filter is useful for identifying people who need follow-up.

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FBmjd9IKy0KRqWqf9tyrM%2FScreenshot%202026-04-03%20at%2011.48.59%E2%80%AFAM.png?alt=media&#x26;token=69cf493f-b24a-426d-93fc-6cb865606efe" alt=""><figcaption></figcaption></figure>

***

### Filtering by reporting structure

The reporting structure tree appears in the left sidebar. Each node shows a progress bar and count (for example, "0/9"). Click any node to filter the content area to that team or department.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talentmap.com/knowledge-base/step-7-communicate-and-take-action/action-planning-in-compass/status-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.