PROGRAMME NAME
RISK REGISTER TEMPLATE
Project Title
Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL
Author: Project Support
Date: 08 November 2013
Filename & Version: Insert details
Project ID: Insert ID
Methodology: PRINCE2™ 2009
FMD Consultants Limited assumes no responsibility for the usage of any information contained in this
document and the way it is handled and disclaims all liability in respect of such information and its
provision. Subject to this disclaimer, you may copy and utilise the material contained in the document.
This information is based on OGC PRINCE2™ material. PRINCE2™ is a registered trade mark of the
Office of Government Commerce in the United Kingdom and other countries. All registered trademarks
recognised & accepted.
1 Document History
1.1 Location
This document is stored in the following location:
Filename
P2_risk_register_template_v01
Location
www.fmdconsultants.co.uk\web
1.2 Revision History
This document has been through the following revisions:
Version
No.
01
Revision
Date
13/09/11
Filename/Location stored:
P2_risk_register_template_v01
Brief Summary of Changes
FINAL VERSION
1.3 Authorisation
This document requires the following approvals:
AUTHORISATION
Name
Signature
Project Manager
Project Assurance (reviewer)
1.4 Related Documents
Summary of filenames and locations of related documents:
Document Type
Filename/Location stored:
Risk Management Strategy
Risk Checklist
Project ID:
BLANK TEMPLATE
Doc Ref:
Page 2 of 4
Date of Issue:
Date
2 Contents
1
DOCUMENT HISTORY ................................................................................................ 2
1.1
1.2
1.3
1.4
LOCATION ......................................................................................................................2
REVISION HISTORY ..........................................................................................................2
AUTHORISATION .............................................................................................................2
RELATED DOCUMENTS .....................................................................................................2
2
CONTENTS ................................................................................................................ 3
3
OVERVIEW ............................................................................................................... 3
4
QUALITY CRITERIA .................................................................................................... 3
3 Overview
A Risk Register provides a record of identified risks relating to the project, including
their status and history. It is used to capture and maintain information on all of the
identified threats and opportunities relating to a project.
Overleaf is an example which may be appropriate to a project.
A risk register can be:
 A document or spreadsheet or database designed specifically for a project
 A stand-alone risk register
 A record which is carried forwards in progress review minutes and presented at
Project Board Meetings
 An entry in a project management tool
 Part of an integrated Risk Register for company (or programme) wide management
of risks, actions, decisions, assumptions, issues and project or programme lesson
The format, structure and mechanism for managing risks should be defined in the
Risk Management Strategy, although for established organisations this Risk
Management Strategy is usually clearly defined therefore needs only to be followed.
4 Quality Criteria



The status of the risk indicates whether any action has been taken
Risks are uniquely identified, including information about which product they refer
to
Access to the Risk Register is controlled and it is kept in a safe place
Project ID:
BLANK TEMPLATE
Doc Ref:
Page 3 of 4
Date of Issue:
FORM [Form ID if applicable]
Ref:[Location/Filename]
Project Name:
RISK REGISTER
Programme Name:[If applicable]
Risk Identifier:
Version:
Risk Description:
Risk Category:
[A unique reference for every risk [In terms of the cause, event (threat or opportunity) and effect (description in
entered into the Risk Register words of the impact)]
e.g. 0001]
Probability:
Impact:
Expected Value:
[These should be recorded in
accordance with the project’s
chosen scales]
Pre-Response
Post-Response
[Estimate the
[Estimate the
inherent values
residual values
(pre-response
(post-response
action)]
action)]
[These should be recorded in
accordance with the project’s
chosen scales]
Pre-Response
Post-Response
[Estimate the
[Estimate the
inherent values
residual values
(pre-response
(post-response
action)]
action)]
[These should be recorded in
accordance with the project’s
chosen scales]
Pre-Response
Post-Response
[Estimate the
[Estimate the
inherent values
residual values
(pre-response
(post-response
action)]
action)]
[Type of risk in terms of
the
project’s
chosen
categories (e.g. schedule,
quality, legal]
Proximity:
[How close to the present
time the risk event is
anticipated to happen]
Risk Response Category:
[How the project will treat the risk – in terms of the project’s chosen categories
e.g.
- For threats: avoid, reduce, fallback, transfer, accept, share
- For opportunities: enhance, exploit, reject, share]
Risk Response:
[Actions to resolve the risk (should be aligned to the chosen response categories. Note that more than one risk response may apply to a risk)]
Date Registered:
[Date
the
identified]
risk
Risk Author:
was [Person who raised the risk]
Risk Owner:
Risk Actionee:
[Person responsible for [Person(s)
managing the risk]
implement
described
response]
Risk Status:
who
will [Active or Closed]
the action(s)
in the risk