# Risk register template with an actionable worked example

Turn a vague concern into a cause, uncertain event, impact, owner, response and review trigger. Includes a filled example and a copyable register.

Canonical: https://project.responseshift.academy/risk-register-template/
Publisher: Response Shift
Updated: 2026-10-31

## Write the uncertainty precisely

A risk is an uncertain event or condition that could affect an objective. “Supplier problem” gives the team little to manage. State the cause, what might happen and the delivery effect separately. An event that has already happened belongs in an issue log, with a current response.

Risk ratings help prioritise attention; they are not measurements of certainty. Agree definitions for likelihood and impact before comparing rows. A large score without an owner, response and trigger is still an unmanaged concern.

## Worked example: delayed access devices



| Field | Fictional example |
| --- | --- |
| Cause | Supplier has not confirmed allocation of the specialist readers. |
| Uncertain event | Readers may arrive after the planned installation start. |
| Impact | Acceptance test may slip by up to four working days; the opening date could be affected. |
| Owner | Delivery lead; owns follow-up and escalation. |
| Response | Confirm allocation by day 3; obtain a priced fallback rental option. |
| Trigger | No written shipment commitment by day 3, 12:00. |
| Contingency | Sponsor decides whether to authorise rental or move opening. |
| Next review | Day 3 with supplier confirmation attached. |

## Distinguish response from reassurance

“Monitor weekly” describes attention, not a reduction in exposure. A response changes the cause, probability or effect, or deliberately accepts the remaining exposure within authority. In this example, securing allocation addresses the cause and rental limits the impact.

The risk owner is not automatically the person authorised to spend contingency. Name the approval path. If shipment is confirmed late, create an issue and link it back to this risk; do not keep describing a known delay as something that might happen.

## Copyable register row



```text
ID / objective at risk:
Cause → uncertain event → impact:
Likelihood definition / impact definition / assessment date:
Owner:
Preventive response / action owner / due date:
Trigger and evidence:
Contingency / authority needed:
Residual exposure after response:
Review date / status / linked issue:
```

- [Download the template (Markdown)](https://project.responseshift.academy/risk-register-template/risk-register-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/risk-register-template/risk-register-example.csv)

## Review the quality of the row

Could another person recognise when the trigger occurs? Does the action have a due date earlier than the possible impact? Does the owner have the information and authority needed to act? If not, revise the row before adding more risks.

Keep one causal story per row. Combining unrelated supplier, staffing and quality concerns makes ownership ambiguous. A shorter register with clear actions is more useful than an exhaustive list nobody reviews.

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: risk management background](https://www.apm.org.uk/resources/what-is-project-management/what-is-risk-management/)
