---
title: "Risk Register"
subtitle: "Sanitized PM Artifact Sample"
date: "07 April 2026"
fontsize: 10.5pt
geometry: margin=0.75in
mainfont: "Noto Sans"
colorlinks: true
...

**Version:** 1.0  
**Document Owner:** Project Manager  
**Review Cadence:** Weekly  
**Status:** Active

---

## 1. Purpose

This register is used to identify, assess, and manage delivery risks before they become active issues. It helps maintain visibility of project exposure, assigns ownership, and supports timely mitigation and escalation.

## 2. Risk Scoring Reference

### Probability

- **Low** - unlikely under current conditions
- **Medium** - plausible if signals continue
- **High** - likely without intervention

### Impact

- **Low** - limited effect on local work only
- **Medium** - visible effect on milestone confidence or coordination
- **High** - material impact on delivery timing, readiness, or stakeholder alignment

### Severity

- **Low** - monitor
- **Medium** - active mitigation required
- **High** - escalation or contingency planning required

## 3. Active Risk Register

| Risk ID | Risk Title | Description | Category | Prob. | Impact | Sev. | Owner | Mitigation | Contingency | Trigger / Early Signal | Status | Review Date |
|---|---|---|---|---:|---:|---:|---|---|---|---|---|---|
| R-01 | External dependency delay | Required input from a supporting team may not arrive in time for the workflow design milestone. | Dependency | Medium | High | High | Project Manager | Track dependency weekly, confirm owner, escalate if date confidence drops. | Re-sequence milestone scope and isolate blocked items. | Dates remain tentative, no confirmed owner, repeated follow-up needed. | Open | 07 Apr 2026 |
| R-02 | Requirements remain ambiguous | Critical workflow rules may remain unclear during planning, creating rework later. | Scope | Medium | Medium | Medium | Operations Lead | Run focused clarification sessions, document assumptions, confirm decisions early. | Freeze uncertain items and move them to controlled follow-up scope. | Contradictory interpretations, unresolved comments, repeated clarification loops. | Open | 07 Apr 2026 |
| R-03 | Stakeholder alignment weakens | Key stakeholders may diverge on priorities or acceptance conditions. | Stakeholder | Medium | High | High | Sponsor / PM | Use structured review points and decision summaries. | Escalate for sponsor decision and reset scope interpretation. | Late objections, mixed approval language, disagreement on what "done" means. | Open | 07 Apr 2026 |
| R-04 | Release readiness judged too late | Readiness evidence may be incomplete until close to release. | Release / Quality | Medium | High | High | QA / PM | Introduce readiness checklist early and review before final stage. | Delay go-live decision until evidence is complete. | Testing status unclear, open defects unresolved, no sign-off path confirmed. | Open | 07 Apr 2026 |
| R-05 | Key specialist becomes bottleneck | One specialist may become a constraint across multiple dependent tasks. | Resource | Medium | Medium | Medium | Functional Lead | Rebalance workload, confirm backup support, sequence work earlier. | Reduce scope for current milestone and re-forecast timing. | Repeated waiting on one owner, review tasks pile up, delayed handoffs. | Open | 07 Apr 2026 |
| R-06 | Status remains cosmetically green | Reporting may not reflect real delivery confidence if concerns are not surfaced early. | Governance / Control | Low | High | Medium | Project Manager | Use milestone confidence checks and explicit blocker review. | Trigger management review and re-baseline confidence openly. | "On track" language without evidence, unresolved risks omitted from status. | Open | 07 Apr 2026 |

## 4. Risk Category Reference

This sample register tracks risks across the following control areas:

- timeline
- dependency
- resource
- scope
- stakeholder
- quality
- release readiness
- governance / control

## 5. Review Logic

### Weekly Review Questions

- Did any probability or impact level change?
- Did any risk become an active issue?
- Is mitigation progressing or stalled?
- Does any risk now threaten milestone confidence?
- Is escalation required?

### Escalation Rule

Escalate when:

- severity becomes high
- mitigation is blocked
- milestone timing is threatened
- cross-team dependency risk remains unresolved beyond the agreed review point

### Issue Conversion Rule

A risk should move into the Issue / Blocker Log when the negative event has already occurred and active resolution tracking is needed.

## 6. Notes

This sample is intentionally simplified for website download use. In practice, the register may also include linked milestones, residual risk, escalation status, or references to decision records and issue logs.