Risk Management Plan

The Risk Management Plan (RMP) details the elements of risk to a project.

ProjectName:
ProjectNumber:
Date:
Preparedby:
ProjectOwnership:

<ProjectName>
<IfApplicable>
<MM/DD/YYYY>
<Name,Title>
<Department/section/arearesponsiblefortheproject.>

Project Contacts
Name

Title/Position

Phone

Email

Primary
Other
Other
Version Control
Add new rows to the table as necessary.

VersionNumber:
Released:
Reason/Comments:
Approved By:

2007 gantthead.com

<Number>
<MM/DD/YYYY>
<Comments>
Date:

gantthead.com

Risk Management Plan

Risk Assessment and Management Table

This table can be adapted to fit the circumstances of individual projects, including non-IT projects.
The project manager should retain the category headings in the RMP template, but change, add and delete table entries within those
categories to customize the template to fit the specific project being addressed: project management risks, security risks, resource
risks, client risks, technical risks, other risks.
Use the algorithm at the end to determine the priority of risk.

Risk

Description

Likelihood1

Consequences2 *Priority
ofrisk3
**Use
algorithm

Ownerof Control
Proposed
Contingency
theRisk
Strategies: Containment Plan?
Mitigateor Actions
(Yes,No)
Accept

ProjectManagementRisks
Inadequateproject
definition
Availabilityofexpert
staff/resources
Unrealistictime
frames
Projectplandeficient
Scopecreep
Lackof
communication
Other(specify)

Likelihood = Almost Certain, Likely, Moderate, Unlikely or Rare

Consequences = Insignificant, Minor, Moderate, Major or Catastrophic

Priority of risk = Very High, High, Significant, Moderate, Low or Trivial

2007 gantthead.com

gantthead.com

Risk

Risk Management Plan

Description

Likelihood

Consequences *Priority
ofrisk
**Use
algorithm

Ownerof Control
Proposed
Contingency
theRisk
Strategies: Containment Plan?
Mitigateor Actions
(Yes,No)
Accept

SecurityRisks
Securityrequirements
met
Accuracyandintegrity
ofdataand
information
Breachofprivacy
Other(specify)
ResourceRisks
Staffturnover
Unclearrolesand
responsibilities
Levelofprojectteam
expertise
Insufficientfunding
Other(specify)
ClientRisks
Inadequatebusiness
requirements
Dissatisfactionwith
productinacceptance
tests
Trainingof
clients/users
Resistancetochange
Other(specify)
2007 gantthead.com

gantthead.com

Risk

Risk Management Plan

Description

Likelihood

Consequences *Priority
ofrisk
**Use
algorithm

Ownerof Control
Proposed
Contingency
theRisk
Strategies: Containment Plan?
Mitigateor Actions
(Yes,No)
Accept

TechnicalRisks
Procurementissues,
includingtendering
Hardwareinadequate
Softwareunavailable
Technicalproblems
Other(specify)
OtherRisks
Interdependencieswith
othersystems,etc
Levelofongoing
support
Other(specify)
1 Likelihood = Almost Certain, Likely, Moderate, Unlikely or Rare
2 Consequences = Insignificant, Minor, Moderate, Major or Catastrophic
3 Priority of risk = Very High, High, Significant, Moderate, Low or Trivia

2007 gantthead.com

gantthead.com

Risk Management Plan

**Algorithm for Determining Prioritization of Risk

Likelihood
AlmostCertain
Likely
Moderate
Unlikely
Rare

2007 gantthead.com

Consequences
Insignificant
Significant
Moderate
Low
Low
Trivial

Minor
Significant
Significant
Moderate
Low
Trivial

Moderate
High
Significant
Significant
Moderate
Moderate

Major
Veryhigh
High
High
Significant
Significant

Catastrophic
Veryhigh
Veryhigh
High
High
Significant