How to use a risk log
A risk log is a list of things that might go wrong on a project, with a score for each one and a note of what you plan to do about it. It takes half an hour to start and it stops the same few worries going round in your head, because they are written down, ranked and given to someone.
Risk or issue?
A risk is something that might happen. An issue is something that has already happened. "The supplier may deliver late" is a risk. "The supplier delivered late" is an issue. The log in this guide is for risks. When one comes true, move it to your issue list or task list and deal with it there.
The columns you need
| Column | What goes in it |
|---|---|
| A: ID | A number, so you can refer to the risk in conversation |
| B: Risk | What might happen, and what it would cause |
| C: Likelihood | 1 to 5 |
| D: Impact | 1 to 5 |
| E: Score | Likelihood times impact |
| F: Response | What you will do about it |
| G: Owner | One named person |
| H: Review date | When you will look at it again |
| I: Status | Open or Closed |
Write each risk as cause and effect
"Budget" is not a risk. It is a topic. A useful entry says what might happen and what it would lead to:
Because of [cause], [event] might happen, which would lead to [effect].
For example: "Because the printer is booked up in December, our order might be delayed, which would mean no stock for the Christmas market." Written like that, the response almost suggests itself.
Likelihood times impact
Each risk gets two scores from 1 to 5.
| Score | Likelihood | Impact |
|---|---|---|
| 1 | Very unlikely | Barely noticeable |
| 2 | Unlikely | Minor: a small delay or cost |
| 3 | Possible | Moderate: a real delay or cost, but recoverable |
| 4 | Likely | Major: a key date or the budget is missed |
| 5 | Almost certain | Severe: the project fails or stops |
Multiply the two to get the risk score:
Risk score = likelihood × impact
The result runs from 1 to 25. In the printer example, a delay is possible (3) and missing the market would be major (4), so the score is 3 × 4 = 12.
The reason for multiplying is that neither number means much alone. Something very likely but trivial (5 × 1 = 5) does not deserve much of your time. Something rare but severe (1 × 5 = 5) scores the same, though many teams still keep an eye on any risk with an impact of 5, whatever its score.
Turn scores into bands
Bands make the log quick to read. One common choice is:
- 1 to 5: Low. Note it and move on.
- 6 to 12: Medium. Agree a response and review it regularly.
- 15 to 25: High. Act now and review it every week.
There is no official set of bands. Choose the cut off points that suit your project and write them at the top of the sheet so everyone scores the same way.
In Excel or Google Sheets, with likelihood in C2 and impact in D2:
- Score:
=C2*D2 - Band:
=IF(E2>=15,"High",IF(E2>=6,"Medium","Low"))
Add conditional formatting to the band column, for example red for High, amber for Medium and green for Low. Use Data validation on the likelihood and impact columns so only whole numbers from 1 to 5 can be entered. Sorting the sheet by score, largest first, puts the risks that need attention at the top.
Choose a response
For every Medium and High risk, decide what you will do. There are four standard choices:
- Avoid: change the plan so the risk cannot happen. Use a different printer who is not booked up.
- Reduce: make it less likely or less damaging. Place the order three weeks earlier.
- Transfer: pass the consequence to someone else, usually through a contract or insurance.
- Accept: do nothing now, and know what you will do if it happens. This is a fair choice for low scores.
Write the response as an action with a date, not as a wish. "Order by 1 November" can be checked. "Keep an eye on the printer" cannot.
After the response is in place, score the risk again. If ordering early brings the likelihood down from 3 to 1, the score drops from 12 to 4. Some logs keep both numbers in separate columns, a score before the response and a score after, which shows whether your actions are making a difference.
Give every risk an owner and a review date
The owner is the person who watches the risk and carries out the response. It should be one name. The review date is when you will next look at the score. High risks might be reviewed weekly, low ones monthly.
At each review, ask three questions. Has the likelihood or impact changed? Has the response been done? Are there new risks to add? Close risks that can no longer happen, but leave them in the sheet with a Closed status so you keep the history.
Common mistakes
- Writing it once and never opening it again. A risk log is only useful if it is reviewed.
- Too many risks. Fifty entries hide the five that matter. Merge duplicates and close what has passed.
- Vague entries. If you cannot tell from the wording whether the risk has happened yet, rewrite it.
- Arguing over exact scores. The scores are a way to rank risks, not a measurement. If two people disagree between a 3 and a 4, pick one and move on.
A risk log sits naturally next to a task list. See how to set up a simple project plan in Excel or Google Sheets for the other half.
For a ready made version, the Project Management Pack includes a risk log next to its task list and timeline. It uses a simpler Low, Medium, High scale, so scores run from 1 to 9. You can buy it on Gumroad.