Risk & Change
Risk Register
MyPMP
QMS Template
| Ref | Risk / event | Likelihood | Impact | Response | Owner | Status |
|---|---|---|---|---|---|---|
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Risk Register for $1/mo, or get everything with membership ($9/mo or $99/yr).
β οΈ Risk & Change
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Risk Register template
A Risk Register is a living log of identified project risks, capturing each threat or opportunity alongside its likelihood, impact, owner, and response plan. It gives the project team a single, prioritised view of what could derail delivery and who is accountable for acting. Kept current, it turns reactive firefighting into deliberate, tracked risk management.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Risk Register
- βΈDuring project initiation to capture risks surfaced in planning workshops
- βΈAt recurring risk reviews or steering committee meetings to update status and scores
- βΈWhen a new threat emerges mid-delivery and needs an owner and response
- βΈBefore stage gates or go/no-go decisions to show residual exposure
What a good Risk Register includes
- βUnique risk ID and a clear cause-event-effect description
- βCategory (e.g. technical, financial, resource, external)
- βProbability and impact ratings, with a calculated risk score
- βResponse strategy: avoid, mitigate, transfer, or accept, plus specific actions
- βNamed risk owner and target/review dates
- βCurrent status and residual score after mitigation
What's inside this template
The interactive form above gives you:
A table of Ref, Risk / event, Likelihood, Impact, Response, Owner, StatusNotes
Tips & common mistakes
- π‘Write risks as 'cause leads to event leads to effect', not vague one-word labels, so the response is actionable
- π‘Assign every risk a single accountable owner, not a whole team, or nothing gets done
- π‘Review and re-score regularly, closed and stale risks distort your exposure picture
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
What is the difference between a risk and an issue?οΌ
A risk is a potential future event that may affect the project, while an issue is a problem that has already occurred. Risks live in the register with response plans; issues move to an issue log for immediate resolution.
How do you calculate a risk score?οΌ
Multiply the probability rating by the impact rating, typically on a 1-5 scale each, giving a score from 1 to 25. Higher scores flag risks needing the most attention and prioritised responses.
Who should own the Risk Register?οΌ
The project manager owns and maintains the register overall, but each individual risk should have a named owner responsible for monitoring it and carrying out the agreed response.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membership