---
title: "Review portfolio exposure and risk appetite"
description: "Read scoped totals and investigate shared dependencies behind multiple risks."
url: https://helpcenter.complytrain.net/en/articles/143-review-portfolio-exposure-and-risk-appetite
collection: "Exposure, money and reports"
updated: 2026-09-22
language: en
---

# Review portfolio exposure and risk appetite

Read scoped totals and investigate shared dependencies behind multiple risks.

Read scoped totals and investigate shared dependencies behind multiple risks.

## Check the portfolio scope

Product location: `/rms/portfolio`

Open **Risk portfolio** and choose the whole register, category or domain and before- or after-controls figures. Review how many risks are quantified and how many in scope have no estimate.

The expected annual loss total covers the included estimates. The displayed low and high bounds add individual bounds; they are not percentiles of the combined portfolio. Missing individual ranges also limit that span.

![Choose the scope and before- or after-controls figures, then state appetite, tolerance and the reasoning. This example has no threshold saved.](https://staticfiles.gleap.io/p6950dfbf97796f2087a9f022/AGATcZuefUnTn4ReH6py5VEUPv3ugdorGroEU4E5ah9n5QxEPuTq37kkofPdP8zJRsTMlGKINpQ.png "Define a scoped threshold")![The register contains a scored risk, but no computed monetary estimate. Missing quantified data is not zero exposure.](https://staticfiles.gleap.io/p6950dfbf97796f2087a9f022/I107MTqTLgMqYgJQT3B5O5yOCdvXiBAqXMFrrMObJ33EHzqGFUL2azzXDHczoFXqlNAt8hfmHK3.png "Understand an empty monetary portfolio")

## Compare with the right threshold

Product location: `/rms/settings/appetite`

In **Risk appetite**, choose **Set a threshold**:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to enter</p></th></tr><tr><td colspan="1" rowspan="1"><p>Applies to</p></td><td colspan="1" rowspan="1"><p>The whole register, one category or one domain.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Applies to figures</p></td><td colspan="1" rowspan="1"><p><strong>After controls</strong> or <strong>Before controls</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Appetite</p></td><td colspan="1" rowspan="1"><p>The expected annual loss you are willing to carry.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Tolerance</p></td><td colspan="1" rowspan="1"><p>The level beyond which you must act. It cannot be lower than appetite. Set appetite, tolerance or both.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Why these numbers</p></td><td colspan="1" rowspan="1"><p>The decision and its basis, for example the board minute that set it.</p></td></tr></tbody></table>

Choose **Save threshold**. **Thresholds in force** lists current thresholds with when they were last affirmed. **Risk portfolio** then shows **Within appetite**, **Above appetite**, **Tolerance breached** or **No threshold set** for that scope.

A scoped view without its own threshold does not inherit the whole-register threshold. **No threshold set** is different from within appetite. Retiring a threshold stops its use while retaining the record of the earlier decision.

## Investigate concentration

Product location: `/rms/concentration`

Open **Risk concentration** and use **Rebuild from the graph** when the shared dependencies need refreshing. Inspect the controls, suppliers, processes or other dependencies behind the listed risks.

Select a dependency to open its detail. It shows how many risks depend on it, their combined exposure and each risk's loading: how much that risk depends on the shared thing, from 0 to 1. The platform calculates loadings from recorded links. Use **Adjust** to set a loading by hand, with a required **Why**. **Hand back to the platform** returns it to the calculated value. Rebuilding and adjusting need the configuration permission.

Open the affected risks and review any manually adjusted loadings. This view traces recorded relationships; it is not a simulation or an assumed correlation model. A single dependency can undermine several recorded reductions, so review the actual links before deciding the follow-up work.
