# Risk Register – Excel & Confluence

## 1 / Quick guide

Copy this page for your project. All risks, roles and dates below are fictional examples from an IT rollout. Replace or remove the examples before use.

**Choose one register as your single source of truth:** use either this Confluence register or the Excel workbook as the master register. Maintain status, assessments, owners and reviews there. Avoid maintaining the same information in parallel.

## 2 / Project information

| Project | Fictional IT rollout – replace before use |
| --- | --- |
| Register owner / maintained by | Agree within the project |
| Review and escalation | Weekly risk review; identify an escalation authority with the power to make decisions. |
| Master register | This Confluence page, if selected; do not maintain Excel in parallel. |

## 3 / Master risk register

L = likelihood; I = impact. Record the original assessment when identifying the risk. Update the current assessment deliberately after professional review; briefly explain changes in the detail section. Scores and priorities in this native Confluence table are maintained manually.

| ID | Risk / Category | Original L/I/Score | Current L/I/Score | Priority | Risk owner | Responses | Status | Next review |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| R-001 | Rollout approval might be delayed / Organisation | 2 / 3 / 6 | 2 / 3 / 6 | High | Project manager | Agree an approval schedule | Open |  |
| R-002 | Local contacts might be unavailable / Resources | 2 / 2 / 4 | 2 / 2 / 4 | Medium | Site coordinator | Confirm resource availability | Under assessment |  |
| R-003 | Devices might not be ready for use / Technology | 1 / 3 / 3 | 1 / 3 / 3 | Medium | Technical workstream lead | Carry out readiness checks | Monitoring |  |
| R-004 | Pilot devices might not be delivered / Suppliers | 2 / 3 / 6 | 2 / 3 / 6 | High | Procurement coordinator | Obtain a firm delivery update | Response in progress |  |
| R-005 | Training materials might arrive late / Communication | 1 / 2 / 2 | 1 / 2 / 2 | Low | Training coordinator | Review materials in advance | Open |  |

## 4 / Assessment guide

| Level | Likelihood | Impact |
| --- | --- | --- |
| 1 – Low | Unlikely | Minor disruption |
| 2 – Medium | Possible | Noticeable effects |
| 3 – High | Likely | Significant effects on project objectives |

**Score = L × I:** green 1–2 = low, yellow 3–4 = medium, red 6–9 = high. Scores of 5, 7 and 8 cannot occur on this scale. This qualitative assessment is not a statistical forecast. Rare events with potentially catastrophic consequences may require special action and escalation regardless of their score.

## 5 / Risk matrix – update manually

**No automatic synchronisation:** this native Confluence table does not pick up changes from the register. After reassessing a risk, manually move its ID to the appropriate cell. The matrix is only a view of the master register; do not maintain additional copies of status, ownership or responses here.

<div class="risk-matrix" tabindex="0" role="region" aria-label="Risk matrix – scroll horizontally if needed"><table><caption>Risk matrix: impact (rows) × likelihood (columns)</caption><thead><tr><th scope="col">I ↓ / L →</th><th scope="col">1</th><th scope="col">2</th><th scope="col">3</th></tr></thead><tbody><tr><th scope="row">3</th><td class="risk-mittel"><strong>Score 3</strong><br>R-003</td><td class="risk-hoch"><strong>Score 6</strong><br>R-001, R-004</td><td class="risk-hoch"><strong>Score 9</strong><br>–</td></tr><tr><th scope="row">2</th><td class="risk-niedrig"><strong>Score 2</strong><br>R-005</td><td class="risk-mittel"><strong>Score 4</strong><br>R-002</td><td class="risk-hoch"><strong>Score 6</strong><br>–</td></tr><tr><th scope="row">1</th><td class="risk-niedrig"><strong>Score 1</strong><br>–</td><td class="risk-niedrig"><strong>Score 2</strong><br>–</td><td class="risk-mittel"><strong>Score 3</strong><br>–</td></tr></tbody></table></div>

## 6 / Optional detail section

For complex risks, add the risk ID, cause/event/consequence, assumptions, justification for reassessment, evidence of response effectiveness and links to actions or decisions. Do not duplicate status, owner or assessment fields; these belong exclusively in the master register.

**Fictional example R-001:** “Agree an approval schedule” is a planned action. Until its effectiveness has been checked, the current assessment remains 2 × 3 = 6. Record a lower residual risk only after a justified reassessment.

## 7 / Regular review

1. Describe new risks specifically as “If …, then …”; assign a unique ID.
2. Maintain owners, responses and the next review date in the master register.
3. Review likelihood, impact and response effectiveness regularly. Entering an action alone does not reduce an assessment.
4. Escalate critical risks in time, stating the decision required.
5. Manage risks that have occurred as issues and link them; set status to “Occurred”. Use “Closed” only with a clear reason.
6. Active statuses: Open, Under assessment, Response in progress, Monitoring. Exclude Closed and Occurred from the active matrix.
7. Reconcile matrix IDs manually after changes. Do not include confidential information in examples intended for public use.