> 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/physical-safety.md).

# Physical Safety

Preview the action plans available for Physical Safety 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.
{% endhint %}

***

### Our organization takes appropriate steps to protect my safety at work

| Plan                                             | Approach  | Focus                                                                                                                            |
| ------------------------------------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Making Safety Decisions Visible to Your Team** | Behavior  | Surfaces the gap between safety measures that exist and the ones your team actually sees or experiences.                         |
| **Building a Team-Level Safety Review Cycle**    | Structure | Creates a structured process for identifying, addressing, and tracking safety concerns specific to your team's work environment. |

***

### Our organization provides me with appropriate training to do my job safely

| Plan                                                               | Approach  | Focus                                                                                                                            |
| ------------------------------------------------------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Connecting Safety Training to the Work People Actually Do**      | Behavior  | Closes the gap between generic safety training and the real risks your team encounters on the job.                               |
| **Building Role-Specific Safety Training Into Your Team's Rhythm** | Structure | Creates a structured approach to identifying training gaps and embedding ongoing, role-relevant safety learning within the team. |

***

### I feel encouraged to identify and report a workplace hazard

| Plan                                                               | Approach  | Focus                                                                                                                                     |
| ------------------------------------------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Making Hazard Reporting Feel Normal, Not Risky**                 | Behavior  | Builds a team culture where identifying safety concerns is treated as valuable, not as complaining.                                       |
| **Building a Reliable Hazard-to-Resolution Process for Your Team** | Structure | Creates a documented, repeatable system for identifying hazards, tracking them to resolution, and proving that reporting leads to action. |


---

# 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/physical-safety.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.
