> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dash360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Set Up Risk

> The map: everything an administrator has to configure before a project team can use the Risk module, where each setting lives, and the order to work in.

Standing up the Risk module on a new project takes about eight settings, and they live in two different places. This page is the map. Each piece then has its own short guide in this series.

<iframe src="https://www.loom.com/embed/28d3c43c593b4088b7582f5cbefb0cf3" title="Loom video player" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

## Where the settings live

| Location                            | What it holds                                                                                         | Scope                                                     |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
| **Admin > Projects > Edit Project** | Risk ID prefixes, risk thresholds, uncertainty classes and the basis code map, spread types, calendar | This project only                                         |
| **Admin > Projects > Risks**        | Risk categories, risk types                                                                           | Global, shared by every project                           |
| **Admin > Projects > Registry**     | The words "Risk" and "Mitigated Risk" as they appear in the interface                                 | The registry set, which may be shared by several projects |

<Warning>
  Risk categories and risk types are **global lists**. Anything added shows up in every project on the system, so agree on naming with other project teams before adding entries.
</Warning>

## The order to work in

Each step depends on the ones above it, so working top to bottom avoids rework.

<Steps>
  <Step title="Registry set and calendar">
    Everything downstream leans on these. Confirm the project is pointed at the right registry set, and build the working calendar so durations respect your work week and holidays.

    See [Registry](/user-guide/admin/registry) and [Project Calendar](/user-guide/admin/project-calendar).
  </Step>

  <Step title="Risk ID prefixes, categories, and types">
    Until these exist, nobody can write a risk in a way that classifies properly.

    See [How to Set Up Risk IDs, Categories, and Types](/user-guide/risk/how-to/risk-ids-categories-types).
  </Step>

  <Step title="Risk thresholds">
    Cost, schedule, and probability bands. **All three are required**, and until they exist the Add Risk form will not open at all.

    See [How to Set Up Risk Thresholds](/user-guide/risk/how-to/risk-thresholds).
  </Step>

  <Step title="Uncertainty classes and the basis code map">
    These drive the estimating side of the Monte Carlo simulation, separately from the risk register itself.

    See [How to Set Up Uncertainty Classes](/user-guide/risk/how-to/uncertainty-classes).
  </Step>

  <Step title="Spread types">
    How each risk's exposure is distributed across its active window. The four built-in profiles cover most projects, so this is usually the quickest step.

    See [How to Set Up Spread Profiles and Calendars](/user-guide/risk/how-to/spread-profiles-and-calendars).
  </Step>
</Steps>

## Finish before handing the project over

This is setup you do once, at the start, before control account managers begin entering risks.

<Warning>
  **Changing a threshold re-ranks every risk in the project immediately.** Do it after a hundred risks are already entered and all of them shift risk level underneath the people who entered them. Get the bands right while the register is still empty.
</Warning>

## What the settings produce

Every setting above exists to serve the two pages the project team actually uses:

* The [Risk Register](/user-guide/risk/risk-register), where risks are written, classified, and tracked.
* [Risk Analysis](/user-guide/risk/risk-analysis), where the Monte Carlo simulation turns those risks plus estimating uncertainty into cost and finish-date distributions.