ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
RISK REGISTER
3
Project name:
4
Project manager:
5
6
IDDate raisedRisk descriptionLikelihoodImpactSeverityOwnerMitigating actionContingent actionProgress on actionsStatus
7
1[12/12/2015][There is a risk that.... If this happens.....][High/Medium/Low][High/Medium/Low][High/Medium/Low. See Severity Table][Person managing the risk][Actions that can be taken to reduce the likelihood of the risk occuring. May also be acceptance of the risk or transferance of the risk e.g. insurance][What will be done if this risk does occur. Usually actions to reduce the impact on the project][Action taken and date. E.g. Update 12/03/2015 mitigation actions implemented][Open, Waiting, Closed]
8
9
10
11
12
13
14
15
16
17
Notes
18
Every organisation has a different approach to the risk log. This example includes all of the information that needs to captured,
19
and has been used on numerous real world projects. However, feel free to tweak this to fit your project.]
20
21
Columns you might want to add:
22
Proximity
This indicates when the risk may occur and can be used to schedule risk mitigation activities.
23
Raised byWho identified the risk.
24
Closed date
The date the risk was closed.
25
Last update
The date that the risk entry was last updated. Useful for ensuring that mitigating actions are put in place.
26
Action by
This field can be used to differentiate between the person accountable for managing this risk and the person
27
actually carrying out the mitigating actions.]
28
29
30
Severity Table
31
Likelihood
32
123
33
Impact1LowLowMedium
34
2LowMediumHigh
35
3MediumHighHigh
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100