> 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="/files/Iam1OcZzbMYUENUn5eJi" 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="/files/DOoNNL6gwrjfeS5WFgTl" 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.