PRINCE2 (TM) Exception Report

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 Exception Report is produced when a Stage Plan or Project Plan is forecast to exceed tolerance levels set. It is prepared by the Project Manager in order to inform the Project Board of the situation, and to offer options and recommendations for the way to proceed.

2.2. Contents

2.2.1. The Exception Report should cover the following topics.

2.2.2. Title

2.2.3. Cause

2.2.4. Consequences

2.2.5. Options

2.2.6. Recommendation

2.2.7. Lessons

2.3. Advice

2.3.1. The Exception Report is derived from the: Current plan and actuals; Issue Register, Risk Register and Quality Register; Highlight Reports (for stage/project-level deviations) or Checkpoint Reports (for team-level deviations) and Project Board advice of an external event that affects the project.

2.3.2. An Exception Report can take a number of formats, including as an Issue raised at a minuted progress review (physical meeting or conference call), as a document or email issued to the next-higher level of management or as an entry in a Project Management Tool. For urgent exceptions, it is recommended that the Exception Report is oral in the first instance, and then followed-up in the agreed format.

2.3.3. The following quality criteria should be observed:

2.3.3.1. The current plan must accurately show the status of time and cost performance

2.3.3.2. The reason(s) for the deviation must be stated, the exception clearly analysed, and any impacts assessed and fully described

2.3.3.3. Implications for the Business Case have been considered and the impact on the overall Project Plan has been calculated

2.3.3.4. Options are analysed (including any risks associated with them) and recommendations are made for the most appropriate way to proceed

2.3.3.5. The Exception Report is given in a timely and appropriate manner.

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 the 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. Report

4.1. Title

4.1.1. [Given overview of the exception being reported]

4.2. Cause

4.2.1. [Describe the cause of the deviation from the current plan]

4.3. Consequences

4.3.1. [Describe what the implications are if the deviation is not addressed for; The project; Corporate or Programme Management]

4.4. Options

4.4.1. [Describe the options that are available to address the deviation and what would the effect of each option be on the Business Case, risks and tolerances]

4.5. Recommendations

4.5.1. [From available options, provide a recommendation, and explain why]

4.6. Lessons

4.6.1. [Detail what can be learned from the exception, on this project or future projects]