Issue Report - FREE project template

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History

1.8.1.1. Revision # [....]

1.8.1.1.1. Revision Date

1.8.1.1.2. Previous Revision Date

1.8.1.1.3. Summary of Changes

1.8.1.1.4. Changes Marked

1.8.1.2. Revision # [....]

1.8.1.2.1. Revision Date

1.8.1.2.2. Previous Revision Date

1.8.1.2.3. Summary of Changes

1.8.1.2.4. Changes Marked

1.8.1.3. Revision # [....]

1.8.1.3.1. Revision Date

1.8.1.3.2. Previous Revision Date

1.8.1.3.3. Summary of Changes

1.8.1.3.4. Changes Marked

1.8.1.4. Date of next revision:

1.8.1.4.1. [....]

1.8.2. Approvals

1.8.2.1. Approval # [....]

1.8.2.1.1. Name

1.8.2.1.2. Signature

1.8.2.1.3. Title

1.8.2.1.4. Date of Issue

1.8.2.1.5. Version

1.8.2.2. Approval # [....]

1.8.2.2.1. Name

1.8.2.2.2. Signature

1.8.2.2.3. Title

1.8.2.2.4. Date of Issue

1.8.2.2.5. Version

1.8.2.3. Approval # [....]

1.8.2.3.1. Name

1.8.2.3.2. Signature

1.8.2.3.3. Title

1.8.2.3.4. Date of Issue

1.8.2.3.5. Version

1.8.3. Distribution

1.8.3.1. Distribution # [....]

1.8.3.1.1. Name

1.8.3.1.2. Title

1.8.3.1.3. Date of issue

1.8.3.1.4. Version

1.8.3.2. Distribution # [....]

1.8.3.2.1. Name

1.8.3.2.2. Title

1.8.3.2.3. Date of issue

1.8.3.2.4. Version

2. Overview

2.1. Purpose

2.1.1. An Issue Report 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.

2.1.2. 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.

2.2. Contents

2.2.1. The Issue Report should cover the following topics.

2.2.2. Issue Report

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

2.3. Advice

2.3.1. The Issue Report 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.

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

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

2.3.4. The following quality criteria should be observed:

2.3.4.1. The issue stated is clear and unambiguous

2.3.4.2. A detailed impact analysis has occurred

2.3.4.3. All implications have been considered

2.3.4.4. The issue has been examined for its effect on the tolerances

2.3.4.5. The issue has been correctly registered on the Issue Register

2.3.4.6. Decisions are accurately and unambiguously described.

3. How to use this template

3.1. How to share this template with your team

3.1.1. Send an email

3.1.1.1. 1. Click Share this map

3.1.1.2. 2. Select Invite People

3.1.1.3. 3. Write a message

3.1.1.4. 4. Click Invite

3.1.2. Send a link

3.1.2.1. 1. Click Share this map

3.1.2.2. 2. Tick Link to share

3.1.2.3. 3. Copy the link to share it

3.1.3. Export

3.1.3.1. 1. Click down arrow, bottom right

3.1.3.2. 2. Select the export option you want

3.2. How to complete this template

3.2.1. Complete the sections in square brackets

3.2.1.1. [....]

3.2.2. Read these sections for help on this template

3.2.2.1. Purpose

3.2.2.2. Advice

3.2.3. Navigate using the links in Contents

3.2.3.1. Contents

3.3. Attribution

3.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

3.4. Get this template here

4. Issue Report

4.1. Issue ID

4.1.1. [Provide a unique reference for every Issue Report]

4.2. Issue Type

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

4.3. Date Raised

4.4. Raised by

4.4.1. [Give the name of the individual or team who raised the issue]

4.5. Issue Report Author

4.5.1. [Give the name of the individual or team who created the Issue Report]

4.6. Issue Description

4.6.1. [Describe the issue in terms of its cause and impact]

4.7. Impact Analysis

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

4.8. Recommendation

4.8.1. [Describe what the Project Manager believes should be done to resolve the issue (and why)]

4.9. Priority

4.9.1. [Give the priority in terms of the project’s chosen scale. It should be re-evaluated after impact analysis]

4.10. Severity

4.10.1. [Give the priority in terms of the project’s chosen scale. Severity will indicate what level of management is required to make a decision on the issue.]

4.11. Decision

4.11.1. [Note the decision made: Accept, Reject, Defer or Grant Concession)]

4.12. Decision Date

4.13. Approved By

4.13.1. [Record who made the decision]

4.14. Closure Date

4.14.1. [Record the date that the issue was closed]

5. Sign-up FREE to edit this map