PROGRAMME NAME

RISK REGISTER TEMPLATE[A1]

Project Title

Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL

Author:Project Support

Date:01 January 2016

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.

1Document History

1.1Location

This document is stored in the following location:

Filename / P2_risk_register_template_v01
Location /

1.2Revision History

This document has been through the following revisions:

Version No. / Revision Date / Filename/Location stored: / Brief Summary of Changes
01 / 01/01/2016 / P2_risk_register_template_v01 / FINAL VERSION

1.3Authorisation

This document requires the following approvals:

AUTHORISATION / Name / Signature / Date
Project Manager
Project Assurance (reviewer)

1.4Related Documents

Summary of filenames and locations of related documents:

Document Type / Filename/Location stored:
Risk Management Strategy
Risk Checklist

2Contents

1Document History

1.1Location

1.2Revision History

1.3Authorisation

1.4Related Documents

2Contents

3Overview

4Quality Criteria

3Overview

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.

4Quality 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: / Doc Ref:
Risk Register Template / Page 1 of 4 / Date of Issue:
RISK REGISTER / FORM [Form ID if applicable]
Ref:[Location/Filename]Version:
Programme Name:[If applicable] / Project Name:
Risk Identifier:
[A unique reference for every risk entered into the Risk Register e.g. 0001] / Risk Description:
[In terms of the cause, event (threat or opportunity) and effect (description in words of the impact)] / Risk Category:
[Type of risk in terms of the project’s chosen categories (e.g. schedule, quality, legal]
Probability:
[These should be recorded in accordance with the project’s chosen scales] / Impact:
[These should be recorded in accordance with the project’s chosen scales] / Expected Value:
[These should be recorded in accordance with the project’s chosen scales] / Proximity:
[How close to the present time the risk event is anticipated to happen]
Pre-Response
[Estimate the inherent values (pre-response action)] / Post-Response
[Estimate the residual values (post-response action)] / Pre-Response
[Estimate the inherent values (pre-response action)] / Post-Response
[Estimate the residual values (post-response action)] / Pre-Response
[Estimate the inherent values (pre-response action)] / Post-Response
[Estimate the residual values (post-response action)]
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 risk was identified] / Risk Author:
[Person who raised the risk] / Risk Owner:
[Person responsible for managing the risk] / Risk Actionee:
[Person(s) who will implement the action(s) described in the risk response] / Risk Status:
[Active or Closed]
Project ID: / Doc Ref:
Risk Register Template / Page 1 of 4 / Date of Issue:

[A1]General Guidelines:

This document provides a template for the creation of a Prince2 Risk Register conforming to the Office of Government Commerce (OGC) guidelines.

This header page is provided for version number reference and does not need to be included with the Risk Register which will be stored in the Risk File.

This header section has comments which give guidance on the structure, content or options for the document.

Comments can be managed via the ‘Review’ tab within MS Word. All comments can be displayed in a reviewing pane (horizontal or vertical) by clicking on the Reviewing Pane icon within the Review Tab. Individual comments or all comments can be deleted via the Delete icon in the Comments box on the Review Tab.

The document can be printed without comments by selecting the “Print what” dropdown on the Print screen and choosing “Document” rather than “Document showing markup”.

It may be appropriate to delete all guideline comments before the Risk Register is circulated for review, at which point reviewers will add their own review comments.