Risk Management Plan
Risk Management Plan
Risk Management Plan
<PROJECT NAME>
<PROJECT REFERENCE>
<DD/MM/YYYY>
stakeholdermap.com
RISK MANAGEMENT PLAN
DOCUMENT CONTROL
DOCUMENT INFORMATION
Information
Document Id [Document Management System #]
DOCUMENT HISTORY
DOCUMENT APPROVALS
Project Manager ©
Quality Manager
(if applicable)
stakeholdermap.com
RISK MANAGEMENT PLAN
Procurement Manager
(if applicable)
Communications Manager
(if applicable)
(if applicable)
stakeholdermap.com
RISK MANAGEMENT PLAN
Table of Content
<PROJECT NAME>.................................................................................................................................................................... I
<PROJECT REFERENCE>........................................................................................................................................................... I
<dd/mm/yyyy>................................................................................................................................................................ i
DOCUMENT CONTROL.............................................................................................................................................I
DOCUMENT INFORMATION....................................................................................................................................................... I
DOCUMENT HISTORY............................................................................................................................................................... I
DOCUMENT APPROVALS.......................................................................................................................................................... I
TEMPLATE GUIDE...................................................................................................................................................1
RISK MANAGEMENT METHODOLOGY...................................................................................................................2
THE RISK MANAGEMENT METHOD...........................................................................................................................................2
RISK IDENTIFICATION.............................................................................................................................................3
HOW RISKS WILL BE EXPRESSED.............................................................................................................................................3
stakeholdermap.com
RISK MANAGEMENT PLAN
TEMPLATE GUIDE
How to use this template
This is a guide to the common sections included in a Risk Management Plan. Sections may be
added, removed or amended to suit your project. Example tables have been added (where relevant)
these are just a suggestion; you may decide to format these sections differently.
stakeholdermap.com
RISK MANAGEMENT PLAN
Text in Blue italics is designed to assist you in completing the template. Delete this text before sharing
the final document.
This project will use Acme’s risk management method defined in the Acme Project Management
Methodology. It is a simple four step method which is repeated continuously through the project
lifecycle. Once a risk is identified, it is assessed, responses to manage the risk are agreed, and
progress is monitored:
1. Identify – risks are identified on an ongoing basis, through formal risk identification
2. Assess – once identified a risk is assessed to establish the likelihood of it occurring and the
3. Respond – there several possible actions that can be taken to reduce the likelihood of a risk
occurring or the impact of the risk, for example transferring, avoiding, and mitigating. In this
stakeholdermap.com
RISK MANAGEMENT PLAN
4. Monitor – progress of the risk responses needs to be monitored and controlled, with
corrective action taken if needed. Typically, progress is assessed via project team meetings.
RISK IDENTIFICATION
<Describe how risks will be identified and captured. Risks can be revealed from many sources and at
any time during the project, so risk identification needs to be an ongoing process.
This statement ensures that the cause of the risk (the assumption) is clear, as is the impact. For
example, if you are assuming shipping will take 10 days, risk of delay could be expressed as:
stakeholdermap.com
RISK MANAGEMENT PLAN
IF shipping takes longer than 10 days THEN the project will face a cost of $500 per day in
unused warehouse space.
Identified risks can be documented on a risk form and sent to the Risk Manager for assessment.
Risk description
Deliverables impacted
stakeholdermap.com
RISK MANAGEMENT PLAN
stakeholdermap.com
RISK MANAGEMENT PLAN
Risks will be assessed by impact and likelihood using a 1 to 4 numeric scale. The combined score is
the risk priority and will drive the response to each risk.
Likelihood scale:
1 – the risk is very unlikely to happen for example it is statistically unlikely, or action has already been
taken to reduce the likelihood.
2 – the risk is unlikely to happen, but is not unheard of, for example a supplier goes unexpectedly into
liquidation or a regulatory change forces a change of materials or project approach.
3 – the risk is likely to happen for example rain in September in UK or it is a common risk on projects
of this type. For example, scope creep on IT projects.
4 – the risk is highly likely to happen, perhaps it is a common occurrence on projects or a common
issue with location, environment, materials, equipment or the technology used. For example, projects
are often impacted by staff illness.
Impact scale:
1 – the risk will have little impact, perhaps there are plans or procedures in place that will reduce the
impact, or there is a simple low-cost alternative. For example, holding a skype meeting is a key
person can’t make it to the office.
2 – the risk will have some impact, but it can be managed or reduced easily. For example, getting
cover for a non-critical staff member who is off sick or a short delay while a contingency plan is put in
place.
3 – the risk will have a significant impact. It is likely to require involvement of senior management and
trigger a re-assessment of the business case. For example, equipment failure causing a delay to the
go live date.
4 – if the risk occurs the project will no longer be viable, perhaps the business case can no longer be
achieved, the additional costs would make it ruinous or the delay would be so long as to make the
project pointless.
Risks with priority between 4 – 8 will be managed using the most appropriate risk response.
Priority 9, 12 and 16 risks may result in the project being cancelled or put on hold until a risk response
can be implemented that will reduce the priority to 8 or below.
RISK IMPACT
1 2 3 4
RIS
stakeholdermap.com
RISK MANAGEMENT PLAN
1 1 2 3 4
2 2 4 6 8
K LIKELIHOOD
3 3 6 9 12
4 4 8 12 16
3 x 3 Risk Matrix
4 x 4 Risk Matrix
5 x 5 Risk Matrix
RISK RESPONSES
<Risks are often managed by reducing the likelihood of the risk happening or the impact. Other
responses are also valid such as transferring the risk, accepting the risk and avoiding the risk.
Describe the risk responses that you will use to manage risk on this project.>
An example is below:>
Progress will be monitored on a weekly basis. The agenda for the weekly project team member will
include space for a review of the risk register focusing on the progress of the risk responses. Risks
that are scored between 8 and 16 will be reviewed at the monthly Risk Review Board meeting chaired
by the Risk Manager.
RISK FUNDING
<Breakdown the funding/budget needed to manage risk on the project. This includes: the cost of risk
mitigation, cost for expert consultants, insurance cost, and a contingency allowance.
This section should also describe how the funding will be allocated, accessed, controlled and
measured.>
stakeholdermap.com
RISK MANAGEMENT PLAN
Project Management Templates – FREE project management templates in Word and Excel
stakeholdermap.com