Download this template free
No sign-up needed. Word and Excel files also open in Google Docs, Google Sheets and Apple Pages/Numbers. Letter size (8.5 × 11 in).
Risk Register
Score likelihood and impact from 1 (very low) to 5 (very high). Risk score = likelihood × impact. 15–25 high · 8–14 medium · 1–7 low.
| ID | Risk description | Category | Likelihood (1–5) | Impact (1–5) | Score | Response / mitigation | Owner | Status |
|---|---|---|---|---|---|---|---|---|
| R1 | [Key supplier misses delivery date] | Schedule | 3 | 4 | 12 | [Order early; identify backup supplier] | Open | |
Preview of the template. Highlighted [brackets] show text to replace.
How to build a risk register
- Brainstorm risks. Ask your team: what could delay the project, push it over budget, hurt quality or harm people? Review lessons learned from similar projects.
- Describe each risk clearly. A useful format is cause → event → effect: “Because our only supplier is overseas, shipments may be delayed, pushing back launch.”
- Score likelihood and impact. Use a 1–5 scale for each. The Excel template multiplies them to give a risk score from 1 to 25.
- Plan a response. For each significant risk, decide whether to avoid, reduce, transfer or accept it, and describe the specific actions.
- Assign an owner. One person is responsible for watching each risk and carrying out the response.
- Review regularly. Rescore risks as circumstances change, and report the top risks in your status report.
Risk scoring matrix
| Likelihood ↓ / Impact → | 1 Very low | 2 Low | 3 Medium | 4 High | 5 Very high |
|---|---|---|---|---|---|
| 5 Almost certain | 5 | 10 | 15 | 20 | 25 |
| 4 Likely | 4 | 8 | 12 | 16 | 20 |
| 3 Possible | 3 | 6 | 9 | 12 | 15 |
| 2 Unlikely | 2 | 4 | 6 | 8 | 10 |
| 1 Rare | 1 | 2 | 3 | 4 | 5 |
Focus your attention on risks scoring 15 or more first.
Common risk categories
- Schedule: delays from suppliers, approvals or dependencies
- Budget: cost overruns, price increases, currency changes
- People: key staff leaving, skills gaps, overloaded team members
- Technical: integration problems, data loss, security breaches
- External: regulation, weather, market changes
- Reputation: customer complaints, public criticism
Frequently asked questions
What is a risk register?
A risk register is a list of the things that could go wrong on a project or in a business, with an assessment of how likely and serious each one is, what you will do about it and who is responsible.
What are the four risk responses?
Avoid (change the plan so the risk cannot happen), reduce (lower its likelihood or impact), transfer (shift it to someone else, for example with insurance or a contract), and accept (live with it and monitor it).
What is the difference between a risk and an issue?
A risk is something that might happen in the future. An issue is a problem that is happening now. When a risk occurs, it becomes an issue and should be managed as one.
How often should a risk register be reviewed?
Review it at least monthly, or weekly on fast-moving projects. Add new risks as they appear and close risks that have passed.
Related templates and guides
Project Plan Template
Define goals, scope, milestones, tasks and owners for any project in one clear document, from a website launch to an office move.
TemplateProject Status Report Template
A one-page weekly status report with red, amber or green ratings, so stakeholders can see project health in seconds.
TemplateSWOT Analysis Template
A clean four-quadrant SWOT grid with guiding questions in each box, plus space to turn your findings into actions.
TemplateRACI Chart Template
A responsibility matrix that shows who does the work, who signs it off, who gives input and who needs to know, for every task in a project.