# Project risk register

Project: … · Register version: v1.0 · Data as of: YYYY-MM-DD · Maintained by: … · Template: https://affine.pro/blog/risk-register-template

| ID | Cause → event → effect | L (1–5) | I (1–5) | Score / priority | Trigger | Mitigation (now) | Contingency (if triggered) | Owner | Status | Next review | Residual L × I |
|---|---|---|---|---|---|---|---|---|---|---|---|
| R-01 | Because … , … may happen, leading to … | | | | | | | | Open | YYYY-MM-DD | |
| R-02 | Because … , … may happen, leading to … | | | | | | | | Open | YYYY-MM-DD | |
| R-03 | Because … , … may happen, leading to … | | | | | | | | Open | YYYY-MM-DD | |

## Scales (agree these before scoring)

| Rating | Likelihood | Impact (worst effect on one objective) |
|---|---|---|
| 1 | Rare: No precedent on comparable projects and no warning signs. | Minimal: Under 1 week of slip, or under 1% of budget, no visible scope change. |
| 2 | Unlikely: Happened once on comparable work; no current warning sign. | Minor: 1-2 weeks of slip, or 1-3% of budget, or an internal-only feature trimmed. |
| 3 | Possible: Happened on several comparable projects, or one warning sign is present. | Moderate: 2-4 weeks of slip, or 3-5% of budget, or a planned feature deferred. |
| 4 | Likely: Happened on most comparable projects, or two or more warning signs are present. | Major: 4-8 weeks of slip or a fixed date missed, or 5-10% of budget, or a key launch feature deferred. |
| 5 | Almost certain: Trigger conditions are already forming; expect it unless you act. | Severe: More than 8 weeks of slip, over 10% of budget, or a core project objective fails. |

Priority: 15–25 Critical · 10–14 High (any impact of 5 is at least High) · 5–9 Medium · 1–4 Low.
Scores rank risks for discussion; they are not probabilities.

Status values: Open · Mitigating · Accepted · Escalated · Materialized (log an issue) · Closed (record date and reason).
