> For the complete documentation index, see [llms.txt](https://isubasinghe.gitbook.io/isithas-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isubasinghe.gitbook.io/isithas-wiki/software_engineering/management/risk_management/risk_management_process.md).

# Risk management process

## Basic idea

Five steps, run continuously: Plan → Identify → Analyse/Assess → Respond → Monitor/Control. The first time through builds the RMP; subsequent passes keep it current.

## Key formulas

* Prioritisation: $RE = P \cdot I$
* Response strategies: avoid, transfer, mitigate, accept.

Plan

* How to approach and plan risk management activities

  Identify
* Identify the possible risks

  Analyse and assess
* Identify the relative priorities of the identified risks

  Respond (Action)
* How can we reduce the likelihood or impact of risks?

  Monitor and control
* How can we detect the ongoing status of our risks? How can we control them effectively and efficiently?


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://isubasinghe.gitbook.io/isithas-wiki/software_engineering/management/risk_management/risk_management_process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.