Enterprise Risk Register (RAID)
Corporate risk register: taxonomy, probability x impact scoring, controls and heat-map
Enterprise Risk Register (RAID) is a dedicated organisation-wide risk management register, distinct from a project's RAID log: risks here stand on their own as governance objects owned by a risk owner, not tied to a project, task or employee record. Every risk is scored, mitigated with controls and tracked through a full lifecycle with a probability x impact heat-map.
Key Features
Hierarchical Risk Taxonomy
Risks are classified with hierarchical categories (e.g. Strategic > Market Risk) for consistent classification across the organisation.
Probability x Impact Scoring
Each risk is rated 1 to 5 on both probability and impact axes; the engine automatically computes the inherent, pre-control score and severity level.
Controls & Residual Risk Compounding
One or more controls can be attached to a risk, each with a control type (preventive/detective/corrective/directive) and effectiveness rating; the engine compounds the effectiveness of every implemented or verified control into a residual, post-control score and severity level.
Risk Appetite Breach Notification
An appetite threshold is set per risk (defaulting from its category); the register flags the breach and notifies the risk owner via activity the moment the residual score exceeds it.
5x5 Heat-Map Wizard
A full probability x impact heat-map, optionally scoped to a category, shows risk counts and appetite breaches per cell for a fast portfolio overview.
Full Risk Lifecycle
Risks move through Identified, Assessing, Mitigating, Monitoring and Closed states with a Reopen path, and every step is tracked via chatter and activities (mail.thread + mail.activity.mixin).
Use Cases
Screenshots
01 Risk Register Kanban
03 Risk Form
06 Risk Categories List
Why Choose This Module
Corporate risk registers are often maintained in static spreadsheets that go stale the moment a control is implemented or a probability changes. This module keeps inherent and residual scoring, control effectiveness and appetite breaches live and computed, with a heat-map and full activity trail so risk owners and governance committees always see the current picture, not last quarter's snapshot.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: mail
- Support: odoo@gencbaris.com
- Update date: 2026-07-13
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1192 |
| Technical Name |
enterprise_risk_register_raid |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module