Risk register
A risk register template that scores likelihood and impact, assigns an owner to every risk, and keeps mitigation plans visible until they're closed.
About this template
Most risk registers die in a spreadsheet nobody opens after the kickoff meeting. This template keeps risks visible where the work already happens, so a risk with no owner or no mitigation plan is easy to spot before it becomes an incident.
Score every risk by likelihood and impact, assign one owner, and move it through the board as the picture changes. Track mitigation and contingency separately: a mitigation plan lowers the likelihood or impact before a risk lands, a contingency plan is the fallback if it happens anyway — most registers only capture the first and get caught out by the second. Risks that stall in "Identified" with no mitigation plan are the ones to raise in the next review.
Works alongside a RAID log if you're already tracking assumptions and dependencies elsewhere — this template just gives risk its own focused view.
What’s inside
Columns included
Task types
Custom fields
Key features
- Likelihood × impact scoring for consistent prioritization
- One owner per risk, always visible
- Separate mitigation and contingency plan fields, so fallback plans don't get skipped
- Review date tracking to catch stale risks
- Category tagging for technical, schedule, budget, and external risk
Who is this template for?
- Project managers running multi-phase projects
- PMO teams standardizing risk reviews
- Engineering teams tracking technical risk
- Agencies flagging client-side risk early
- Operations teams auditing process risk
How to use this template
Use this board to log risks as they surface, score them consistently, and keep mitigation owners accountable.
Step 1
Log every risk as it comes up
Add a card the moment a risk is identified — in planning, in a status meeting, or mid-project. Don't wait for a formal review to capture it.
Step 2
Score likelihood and impact
Rate each risk so the highest-priority ones surface first. A risk score field keeps the sort consistent across a growing register.
Step 3
Assign an owner and review on a cadence
Every open risk needs one owner and a mitigation plan. Review the board weekly or biweekly and move resolved risks to Closed.
Frequently asked questions
Related templates
RAID log
Track Risks, Assumptions, Issues, and Dependencies in one place — prioritize by probability and impact, assign owners, and drive resolution.
Project charter
A project charter template that locks down scope, sponsor, budget, and success criteria before work starts, and tracks approval status for teams running several projects at once.
Communication plan
A communication plan template that maps each stakeholder audience to a channel, frequency, and owner, so updates go out on schedule instead of by memory.