# Feature - Incident Management Playbook

**URL:** https://discussions.eramba.org/t/feature-incident-management-playbook/8401
**Category:** Forum - Software
**Created:** [March 20, 2026, 2:03pm UTC](https://discussions.eramba.org/t/feature-incident-management-playbook/8401 "2026-03-20T14:03:06Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![kisero](https://discussions.eramba.org/user_avatar/discussions.eramba.org/kisero/32/2925_2.png) [@kisero](https://discussions.eramba.org/u/kisero)
#### Post date: [March 20, 2026, 2:03pm UTC](https://discussions.eramba.org/t/feature-incident-management-playbook/8401/1 "2026-03-20T14:03:06Z")

</div>

- Today users can **optionally** associate **one or more** (this needs to be limited to one, not multiple) **Risk Response Plans** to a Risk when creating or editing it.
- In the policy module we need one more “Default” “Type” called “Incident Playbook”
- These plans define the actions to be taken if that Risk materializes. In Eramba, Risk Response Plans are already described as guidance linked from Risks into the Incident module.

 ![image](https://discussions.eramba.org/uploads/default/original/2X/f/fade8e49bb34cec9ee955dedcf661d2ee656c5ef.jpeg)

- On the incident module, “Playbooks” is a setting that can be enabled or disabled on the form (by default enabled)
- If enabled:
  - When the user clicks “Add” new Incident, the user is prompted to select (one or more) Risk(s) related to that Incident. The search includes all three risk modules , the list of risk shows the tile of the risk with a pre-append from which risk module belongs to, for example: (Asset Risk|Third Party Risk|Business Risk) - $title
  - Once a Risk is selected:
    - if the risk has an associated “**Risk Response Plans” we offer the user to “View” it (this re-uses the Policy module “View” modal)** Eramba displays the **Risk Response Plan(s)** linked to that Risk as the Incident playbook.
    - if the Risk has no “Risk Response Plan” then we show a message that there is no Playbook for this risk defined

- If disabled:
  - We show the incident form as usual, nothing else  
 ![image](https://discussions.eramba.org/uploads/default/original/2X/4/43add3d87044eadbfb46221d896e1af00af0ab46.jpeg)

figma: [https://www.figma.com/design/vXxSIZJFggeeWWZtUiOL6A/Eramba-UI-2026?node-id=13669-2615&t=oK2zvlF4sEF12EJp-4](https://www.figma.com/design/vXxSIZJFggeeWWZtUiOL6A/Eramba-UI-2026?node-id=13669-2615&t=oK2zvlF4sEF12EJp-4)

 ![image](https://discussions.eramba.org/uploads/default/original/2X/4/451f18925f4e5a8737110758835faec59e0b0d49.jpeg)

We also need:

- A column on the Views we defined for this module including the “Incident Playbook”
- A dynamic status that triggers in the incident module “Playbook Available”
- On the risk module we need to rename the existing status to “Ongoing Incident” and add a new one that is called “Past Incidents” that triggers when a risk has a related incident but the incident is “Closed”

 ![image](https://discussions.eramba.org/uploads/default/original/2X/6/6d10587beae6f90268d4eae5b5f0df7318e2bfef.png)