Risk Blocks
Reference for the 4 risk and scenarios category blocks: Risk, Risk Register, Failure Scenario, and Scenario / What-If.
The Risk and Scenarios category includes 4 blocks for documenting risks, failure modes, and scenario analysis. These blocks help teams manage uncertainty and plan for resilience.
Risk Block
Documents a single risk with likelihood, impact, and mitigation.
| Property | Type | Description |
|---|---|---|
| title | string | Risk name (required) |
| description | string | Detailed risk description (required) |
| impact | enum | Impact level (required): Low, Medium, High |
| likelihood | enum | Probability (required): Low, Medium, High |
| category | string | Category: architectural, operational, security, performance, compliance, delivery |
| status | string | Status: identified, mitigated, accepted, monitored, retired |
| responseType | string | Response: mitigate, accept, avoid, transfer |
| mitigation | string | Mitigation strategy |
| residualRisk | string | Risk remaining after mitigation |
| detectionSignals | array | How to detect if risk materialises |
| owner | string | Who owns this risk |
Risk Register Block
Documents a collection of risks in a tabular format with visual matrix.
| Property | Type | Description |
|---|---|---|
| title | string | Register title (required) |
| scope | string | What this register covers |
| reviewCadence | enum | Review frequency: weekly, monthly, quarterly, ad-hoc |
| lastReviewed | date | Date of last review |
| entries | array | Array of risk items (required) |
Failure Scenario Block
Documents failure modes with detection and recovery procedures.
| Property | Type | Description |
|---|---|---|
| title | string | Scenario title (required) |
| description | string | Scenario description (required) |
| impact | string | Business and technical impact (required) |
| severity | enum | Severity: low, medium, high, critical |
| detectionSignals | array | How to detect the failure |
| immediateResponse | string | First response actions |
| recoveryStrategy | string | Full recovery approach |
| timeToRecover | string | Expected recovery time |
| dataImpact | string | Data loss or corruption risk |
| userImpact | string | End-user experience impact |
| lessonsLearned | string | Post-incident insights |
| status | enum | Status: hypothetical, tested, occurred, mitigated |
Scenario / What-If Block
Documents hypothetical scenarios for planning and flexibility analysis.
| Property | Type | Description |
|---|---|---|
| title | string | Scenario title (required) |
| description | string | Scenario description (required) |
| trigger | string | What causes this scenario |
| assumptionsChanged | array | Assumptions that would change |
| constraintsIntroduced | array | New constraints introduced |
| stressPoints | array | Systems under stress |
| possibleResponses | array | Potential response actions |
| insights | string | Key learnings from analysis |
| status | enum | Status: exploratory, planned, executed |