# Risks Board

Managing risks is an essential part of planning and executing successful PIs. Savah's **Risks** module helps teams proactively identify, evaluate, and address potential issues using visual boards and linked features.

You can access the **Risks** module from the **left navigation menu** within your Program Board.

Savah provides **three powerful visualizations** to manage risks:

#### 1. **Risk Matrix View**

Visualize risks by **Impact vs Probability** in a 3x3 color-coded matrix, helping prioritize critical issues at a glance.

<figure><img src="/files/uxmeX19y1loTWS5i5UyP" alt=""><figcaption><p>Risk Matrix</p></figcaption></figure>

#### 2. **ROAM Board View**

Categorize risks into:

* **Resolved**
* **Owned**
* **Accepted**
* **Mitigated**

Drag and drop cards across categories to reflect the latest status and strategy.

<figure><img src="/files/XXNU8AqLe1OuuG8QfX1R" alt=""><figcaption><p>ROAM  Board</p></figcaption></figure>

#### 3. **List View**

Get a detailed table of all risks, showing:

* Titles
* Status
* Level
* Dates
* Linked items
* Teams and Sprints

You can **expand each risk** to view and manage its **linked Epics and Stories**.

<figure><img src="/files/RTVk5NuOceS1Wpe5Ph1A" alt=""><figcaption><p>Risks List View</p></figcaption></figure>

### Linking Risks to Features and Stories

You can **link risks** to:

* **Epics/Features**
* **Stories**

This integration helps in tracking how work items are impacted by or related to identified risks. It also supports transparency and alignment across stakeholders.

<figure><img src="/files/XHJy1Fr8RRr1EkXPVQxR" alt=""><figcaption><p>Link Features with Risks</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://savah.gitbook.io/savah/board/risks-board.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.