risk-register

To create a risk register, assign a stable ID to each risk, define owners, and set likelihood and impact scores. The register computes residual risk scores by evaluating inherent risk against defined controls, maintaining history and review cadence.

Yes, you can ingest risks from upstream sources including monte-carlo-simulation, pre-mortem, risk-matrix, and fmea. The register centralizes these inputs with stable IDs, capturing categories, owners, and computed residual scores for governance.

You can export the risk register in Markdown and CSV formats. These outputs support reporting, auditing, and governance reviews by providing a centralized source of truth for risk identification, scoring, and history.

Maintain risk history by defining clear statuses and review cadences for each risk entry. The register tracks historical changes, ownership, and residual scores, ensuring continuous compliance and governance monitoring across subject areas.

Yes, the register produces diagram outputs to support risk discussions and decision making. These visualizations complement the Markdown and CSV exports, helping teams analyze mitigations and ongoing project governance.

You need to define risk categories, assign owners, and specify controls to compute residual risk. The canonical register captures IDs, statements, likelihood, impact, and inherent risk scores, applying controls to calculate residual values.