> 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/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/mental-health.md).

# Mental Health

Preview the action plans available for Mental Health survey questions. Each question offers a behavior plan and a structure plan. Full plans open inside Compass Action Planning.

{% hint style="info" %}
**Module required.** Your organization needs the Action Planning module enabled in Compass to open these plans.&#x20;
{% endhint %}

### I feel supported in my workplace when I am dealing with personal or family issues

| Plan                                                                     | Approach  | Focus                                                                                                 |
| ------------------------------------------------------------------------ | --------- | ----------------------------------------------------------------------------------------------------- |
| **Making Support Visible Before People Have to Ask**                     | Behavior  | Shifts manager behavior so support is proactive and normalized, not reactive and awkward.             |
| **Building a Support Infrastructure That Doesn't Depend on One Manager** | Structure | Creates team-level structures so support is systematic, not contingent on individual manager comfort. |

***

### My workplace effectively handles interpersonal conflict that exists among employees

| Plan                                                         | Approach  | Focus                                                                                          |
| ------------------------------------------------------------ | --------- | ---------------------------------------------------------------------------------------------- |
| **Addressing Conflict Early Instead of Working Around It**   | Behavior  | Equips the manager and team to handle friction directly before it calcifies into dysfunction.  |
| **Building Team Norms That Prevent Conflict From Festering** | Structure | Creates repeatable structures for surfacing and resolving friction before it becomes personal. |

***

### My workplace effectively deals with situations that may threaten or harm employees

| Plan                                                        | Approach  | Focus                                                                                                           |
| ----------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------- |
| **Building a Team Where Threats Get Reported and Resolved** | Behavior  | Creates a reporting culture where concerns about safety or harm are raised quickly and taken seriously.         |
| **Strengthening the Team's Safety Response Systems**        | Structure | Builds documented processes and team capability so threatening situations are handled consistently, not ad hoc. |

***

###


---

# 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/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/mental-health.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.
