Risk Register Basics: Turning Worries Into a Plan
A risk register is only useful if the team keeps using it. Here is a simple way to write, score and review risks that works on real projects.
Every project team worries about things that might go wrong. A risk register turns those worries into a list you can act on: what might happen, how likely it is, how much it would hurt and what you will do about it.
Write risks as cause, event and effect
Vague risks lead to vague responses. Use this structure:
Because the supplier is new to us, delivery may be late, which would delay testing by two weeks.
The cause tells you what to watch, the event is the risk itself, and the effect tells you why it matters.
Score probability and impact
Rate each risk Low, Medium or High for probability and for impact, then multiply (1 to 3 on each scale) to get a score from 1 to 9. Scores of 6 or more are high and need an active response and an owner.
Choose a response
- Avoid: change the plan so the risk cannot happen.
- Mitigate: reduce the probability or the impact.
- Transfer: move the impact to someone better placed to handle it, for example through a contract or insurance.
- Accept: acknowledge it and set aside contingency, usually for low risks.
Every high risk needs a named owner and a due date for the response action.
Review it every week
A risk register that is updated once and forgotten is a compliance exercise, not risk management. Spend ten minutes in your weekly meeting on three questions:
- Have any risks happened? Move them to the issue log.
- Have scores changed?
- Are there new risks?
Risks vs issues
A risk might happen. An issue is happening now. Keep them in separate logs so the team does not mix prevention with firefighting. A RAID log (risks, assumptions, issues, dependencies) keeps all four in one workbook.
A ready-made register
The PMer Risk Register template calculates scores and ratings automatically, includes a heat map of open risks and highlights overdue actions. It is part of our project management template pack.
Written by
Charles Bugeshi
Founder, The PMer
Industrial engineer and CAPM holder coordinating engineering projects on the East African Crude Oil Pipeline. Founder of The PMer.
More about the author