PRINCE2 Issue Report Template

PRINCE2: This is the full PRINCE2 Issue Report Template.  Here you can also download this template in MS Word format and access other relevant documents: Link

Purpose An PRINCE2 Issue Report Template is a report containing the description, impact assessment and recommendations for a request for change, off-specification or a problem/concern. It is only created for those issues that need to be handled
formally.
The report is initially created when capturing the issue, and updated both after the issue has been examined and when proposals are identified for issue resolution. The Issue Report is later amended further in order to record what option was decided upon, and finally updated when the implementation has been verified and the issue is closed.
Contents The PRINCE2 Issue Report Template should cover the following topics.

  • Issue Report

Note: this is a default template format, please check with the Configuration Management Strategy for precise format and composition requirements

Advice The PRINCE2 Issue Report Template is derived from the: Highlight Report(s), Checkpoint Report(s) and End Stage Report(s); Stage Plan together with actual values and events; Users and supplier teams working on the project; The application of quality controls; Observation and experience of the processes; Quality Register, Risk Register and Lessons Log; and Completed Work Packages.

The PRINCE2 Issue Report Template can take a number of formats, including: Document, spreadsheet or database; Entry in a project management tool.

Not all entries in the Issue Register will need a separately documented Issue Report.

The following quality criteria should be observed:

  • The issue stated is clear and unambiguous.
  • A detailed impact analysis has occurred.
  • The issue has been examined for its effect on the tolerances.
  • The issue has been correctly registered on the Issue Register.
  • Decisions are accurately and unambiguously described.

Issue Report

Issue ID[1] Issue Type[2]
Date Raised Raised by[3]
Issue Report Author[4]
Issue Description[5]  

 

 

 

 

 

Impact Analysis[6]
Recommendation[7]
Priority[8]
Severity[9]
Decision[10]
Decision Date Approved By[11]
Closure Date[12]

[1] As shown in the Issue Register (provides the unique reference for every Issue Report)

[2] Defines the type of Issue being recorded, namely: request for change; off-specification or problem/concern

[3] The name of the individual or team who raised the issue

[4] The name of the individual or team who created the Issue Report

[5] A statement describing the issue in terms of its cause and impact

[6] A detailed analysis of the likely impact of the issue.  This may include, for example, a list of products impacted.

[7] A description of what the Project Manager believes should be done to resolve the issue (and why)

[8] This should be given in terms of the project’s chosen scale.  It should be re-evaluated after impact analysis

[9] This should be given in terms of the project’s chosen scale.  Severity will indicate what level of management is required to make a decision on the issue.

[10] The decision made: Accept, Reject, Defer or Grant Concession)

[11] A record of who made the decision

[12] The date that the issue was closed

 

PRINCE2 Issue Report Template