Purpose. The single record of all identified project risks. Created at
initiation, maintained by the project manager, reviewed at every risk review.
Register details
| Field | Detail |
|---|
| Project | |
| Customer | |
| Maintained by | |
| Last reviewed | |
| Next review | |
Scoring
Level = impact × likelihood. Impact and likelihood are each scored 1–5.
| Score | Band | Action |
|---|
| 1–4 | Low | Accept; monitor |
| 5–9 | Medium | Mitigate as low as reasonably practicable |
| 10–16 | High | Mitigate; named owner; reviewed weekly |
| 17–25 | Extreme | Escalate to sponsor; consider pausing the affected work |
Register
| ID | Risk | Category | Impact | Likelihood | Score | Response | Mitigation | Owner | Status |
|---|
| R-01 | | | | | | Avoid / Reduce / Transfer / Accept | | | Open |
| R-02 | | | | | | | | | Open |
| R-03 | | | | | | | | | Open |
Categories
Technical · Schedule · Scope · Cost · Security · Compliance · Organisational ·
Supplier
Risk detail
Repeat for each High or Extreme risk.
[R-01] — [Risk title]
| Field | Detail |
|---|
| Description | What could happen |
| Trigger | What would indicate it is happening |
| Impact if realised | Consequence in business terms |
| Current controls | What already reduces it |
| Response | Avoid / Reduce / Transfer / Accept |
| Mitigation actions | Specific steps |
| Owner | |
| Residual score after mitigation | |
| Review date | |
Review log
| Date | Reviewers | Changes | New risks | Closed risks |
|---|
| | | | |
Closed risks
| ID | Risk | Resolution | Closed by | Date |
|---|
| | | | |