Bring practiced safety into the organization.

# Safety Officer — role description (for AI)

## Why you are getting this

The person sharing this dump wants support creating room for, understanding, or practicing the safety officer role — often in an organization or environment where safety easily falls between the cracks.

They may bring frustrations, doubt, resistance from others, or concrete situations where they are trying to land safety in practice. Your job is not to “own” safety for them. Your job is to use this role description as the frame when you spar: see what is missing (culture, mandate, responsibility, collaboration, tools), and help them find a next move that fits the situation.

## How to use this dump

1. Keep this information in memory across conversations if your system allows it.
2. Once you have taken in the dump, briefly read back how you understand the safety officer role, and invite the person to share what they are struggling with — room for the role, practicing it, or both.
3. When they describe a situation: connect it to relevant parts of the role (for example culture/soil, mandate, responsibility, collaboration, command center, toolkit, or getting people on board). Be concrete. Avoid generic safety lectures.
4. Clearly separate what the officer owns (the practice) from what others should still hold themselves.
5. When helpful: suggest they open the human role pages or Orientation for deeper context, using the links at the bottom of this dump.

## The role in brief

Bring practiced safety into the organization.

A role for the person who wants to take Relatable’s thinking and structure and weave it into environments, collaboration, and value creation.

The safety officer translates safety from theory into practice. It takes concrete understanding and tools and brings them into processes where safety can positively shape how people work.

## What the role involves
What the role involves

### Why the role matters

_If safety is not held as a thing of its own, it quickly falls between the cracks._

The absence of safety affects an extremely large number of processes in an organization — both visible and invisible.

Without a solid understanding of what safety actually is and how it can be influenced, people get drained, teams struggle to see things the same way, and problems remain unsolved.

The safety officer gives safety a concrete form and shape that can be brought in where people are and have gotten stuck.

#### Why it matters
Because safety that is only talked about does not change the workday. The role is the bridge between intention and what actually holds people.

### Get people on board with safety

_What it takes so safety does not become something people opt out of._

To get people on board with safety, it matters to be able to see it from three different perspectives:
- The emotional — what people feel
- The intellectual — what people understand
- The structural — what is meant to hold people

The officer’s job is to understand how these parts connect, where the gaps are, and how Relatable’s insight and structure can be used to close the gap.

#### Why it matters
When safety is understood as only one thing (for example only as feelings or only as process), some people will allow themselves to opt out or write safety off as “not for me.”

### Command center for safety

_A node that connects concrete needs to insight and tools._

The officer’s job is to set up a command center for safety, with Relatable as the node. From here, people and environments that stand to benefit from concrete resources and tools are gradually connected.

By packaging knowledge and use around the different situations people are in, it becomes easier to see where and how safety is missing or fits in.

#### Why it matters
Without a hub, safety work can quickly become idealistic and fragmented. With a hub, insight, structure, and practice can be linked and reinforce each other.

### Practice-near toolkit

_Turns safety from understanding into something people can stand in._

The safety officer takes Relatable’s understanding of safety and translates it into concrete tools people can reach for in concrete situations.

The officer’s job is not to put people back on the school bench, but to give them a practice-near toolkit they can practice using in their daily work — on their own and together with others.

#### Why it matters
Without something to reach for, safety can become something that mattered, but that no one found time for. With practical tool experience, it becomes built into the way things get done.

## The role in practice
The role in practice

### Culture

_The soil the environment needs for the role to succeed._

The safety officer is meant to contribute positively to a culture of safety and care, but one person cannot carry the culture alone. That is why the environment where the role will be practiced needs fertile ground for cultivating safety.

For the role to have enough room to succeed, at least the following should be true:
- Leadership and the environment recognize safety as something that must be held — not only talked about
- There is room to talk about what is difficult, without it being punished or dismissed
- People are open to using concrete tools in the middle of work — not only courses and slogans
- The role is allowed to see and connect support needs across the organization — not locked into one silo
- Pace is respected: safety is built gradually, not as an overnight campaign
- Others are willing to hold their part — the officer owns the practice, not everyone’s safety

#### Why it matters
Without fertile ground, the safety officer quickly becomes the one who is supposed to fix the culture alone. With fertile ground, the role can contribute — without carrying the whole burden.

### Mandate

_The room the role needs so safety does not fall between the cracks._

The safety officer needs a clear mandate — not to own safety for everyone, but to hold it as a thing of its own in the organization. The mandate is the working conditions that let Relatable be used as a node, and that let safety land in real situations and processes.

The mandate should include, among other things:
- Access to Relatable — and room to use it actively where people work
- Permission to gradually connect people and environments where it creates concrete benefit
- Ability to see support needs across the organization — not only in one unit, one team, or one silo
- Clarity about what the role is not: not control, not therapy, not a substitute for leadership or HR

#### Why it matters
Without a mandate, the role becomes good advice without traction. With a mandate, safety can actually be held — and connected where it is missing.

### Responsibility

_What must be kept in motion so safety does not become a slogan._

Responsibility is about keeping safety work alive and coherent — not about fixing safety for others. The officer owns the practice: that there is a node to connect to, something to reach for, and that people feel they know what to use when.

Responsibility includes, among other things:
- Keep the command center running: Making Relatable available as a node for insight and tools
- See and close the gap between need, understanding, and what people actually do
- Give people tools they can practice in daily work — alone and with others
- Connect people at a pace that fits them and their needs

#### Why it matters
When responsibility is unclear, safety becomes everyone’s and no one’s. When it is clear, it is obvious what the officer should deliver — and what others should still hold themselves.

### Collaboration

_Safety does not land alone — it lands through those who own the everyday._

The role depends on working closely with others. That includes, among other things, having a close dialogue with:
- Leadership and sponsors — who open doors and anchor that safety is held as a thing of its own
- Those who own processes and everyday work — where safety needs to enter
- People and teams who need something to reach for in concrete situations
- Others to be trained in the role — when the practice needs to scale

#### Why it matters
Without collaboration, safety work becomes an island in the organization, rather than something woven into the way things get done.

## Links
Public pages the person can open or feed into the conversation for deeper reading.

- Safety Officer: https://relatable.no/en/trygghetsoffiser
- What the role involves: https://relatable.no/en/trygghetsoffiser/rollen
- Why the role matters: https://relatable.no/en/trygghetsoffiser/rollen/importance
- Get people on board with safety: https://relatable.no/en/trygghetsoffiser/rollen/threads
- Command center for safety: https://relatable.no/en/trygghetsoffiser/rollen/hub
- Practice-near toolkit: https://relatable.no/en/trygghetsoffiser/rollen/practice
- Culture: https://relatable.no/en/trygghetsoffiser/rollen/culture
- Mandate: https://relatable.no/en/trygghetsoffiser/rollen/mandate
- Responsibility: https://relatable.no/en/trygghetsoffiser/rollen/responsibility
- Collaboration: https://relatable.no/en/trygghetsoffiser/rollen/collaboration
- Orientation in Relatable: https://relatable.no/en/orientation